ACTIVE DEPARTMENT / PROGRAMMING + SECURITY + SYSTEMS
Code that builds things, measures things, breaks our own assumptions, recovers evidence, interrogates networks, dissects binaries, talks to hardware, preserves archives, and makes the rest of Cyberdelia reproducible.
This is the working software desk, not a directory of logos. Cyberdelia-built tools, third-party workbench software, preserved freeware, source packages, reviews, test notes, and training material are kept separate so readers can tell what we made, what we use, what we mirror, and what we merely discuss.
BUILT HERE / CYBERDELIA SOFTWARE
Every Cyberdelia utility should eventually ship with source or a clear implementation description where appropriate, version history, dependencies, build instructions, tests, example data, failure modes, and a reproducible release package. A cool binary with no provenance is just another mystery meat executable.
Dependency-free Python verifier for Cyberdelia-compatible archive manifests. It checks SHA-256 values, byte counts, mirror paths, and provenance sidecars and returns a failing exit code when custody evidence disagrees with the bytes on disk.
Download ZIP · ZIP SHA-256 · README · Source
Manifest generation, checksum verification, source/mirror state tracking, derivative separation, file inventory, broken-link auditing, and the public FTP/archive directory layer already form the first working software family.
Adapters, metadata normalization, cached source records, reproducible analysis jobs, dataset manifests, plotting, and result packaging for astrophysics, SETI, UAP records, and future research programs.
Evaluation harnesses, role-routing experiments, calibration scoring, ablations, cost accounting, disagreement analysis, and reproducible comparison against simpler baselines.
Small utilities for capture inventory, protocol summaries, asset baselining, DNS/TLS inspection, service-change detection, and report generation on networks the operator is authorized to inspect.
Helpers for firmware inventory, serial-console notes, binary metadata, checksums, string extraction, component maps, interface documentation, and repeatable lab records around hardware we own or are authorized to analyze.
File hashing, metadata extraction, timeline assembly, duplicate detection, archive unpacking, media inventory, source-path preservation, and report packaging for lawful recovery and research workflows.
WORKBENCH / THIRD-PARTY TOOLS
Cyberdelia's software coverage treats tools as instruments. Reviews should explain what the program measures or changes, how trustworthy the result is, which assumptions it makes, what evidence it leaves behind, and where inexperienced use produces nonsense.
Languages, IDEs, version control, package managers, test frameworks, profilers, linters, reproducible environments, documentation generators, and the machinery required to turn source into something another person can rebuild.
Packet capture, protocol decoding, traffic baselining, service discovery, latency and path diagnostics, DNS/TLS inspection, flow analysis, and network observability. The useful question is what the network actually did, not what the diagram said it was supposed to do.
Vulnerability assessment, web-application testing, configuration review, authentication analysis, exposure mapping, sandbox exercises, and adversarial validation of systems the operator is permitted to test. Offensive technique is taught to illuminate defensive failure modes and verification.
Disassemblers, decompilers, debuggers, format inspection, strings, imports, dynamic tracing, sandboxing, and behavioral comparison. Unknown or hostile samples belong in isolated analysis environments, not on production machines because curiosity overruled survival instinct.
Serial tools, logic analysis, bus inspection, firmware extraction, flash utilities, device logging, protocol decoders, build toolchains, and documentation around microcontrollers, sensors, embedded Linux, and physical interfaces.
Disk and filesystem inspection, recovery, hashing, metadata, timelines, media inventories, log analysis, and evidence-preserving copies. Original objects remain separate from transformed or searchable derivatives.
Shells, configuration management, task runners, scheduled jobs, backups, deployment tooling, infrastructure inventories, health checks, rollback, and scripts that remove manual error without hiding what changed.
Python/R ecosystems, notebooks used carefully, databases, array/dataframe tools, signal processing, plotting, numerical libraries, containers, workflow engines, and compute queues for research datasets large enough to make a laptop reconsider its career.
Encryption tools, key handling, signatures, hashes, password managers, certificate inspection, secure transport, privacy utilities, and practical verification. Cryptography fails spectacularly when people use strong mathematics with weak operational habits.
FREEWARE DEPARTMENT / PRESERVATION
The FTP should eventually hold selected freeware, open-source releases, public-domain utilities, manuals, source packages, old versions needed for historical systems, and Cyberdelia-built releases. "Freeware," "open source," "public domain," and "free to download" are different license states and must never be collapsed into one convenient lie.
Every mirrored package retains the author's or project's original download/repository link, project name, version, release date when known, and license or redistribution basis.
Preserved binaries and source archives receive Cyberdelia mirror paths, retrieval dates, sizes, MIME/type information, cryptographic hashes, and clear version labels.
Packages should distinguish upstream, verified checksum match, locally scanned, legacy/unverified, source-only, quarantine/lab-only, and reviewed states. Historical usefulness and present-day safety are not the same property.
Documentation, readmes, changelogs, license files, source snapshots, build instructions, and known compatibility notes matter because an orphan executable without context is barely an archive.
EDITORIAL / SOFTWARE SHOULD TEACH
Cyberdelia's long-form standard applies here too. Major software pieces should explain architecture, history, protocol or file-format context, practical workflows, failure modes, security implications, competing tools, reproducible examples, and the evidence a reader should inspect. Reviews should survive version churn by teaching the underlying system rather than only the current menu layout.
Recurring formats include Greyhat Teardown, Protocol Autopsy, Toolchain Field Guide, Binary Anatomy, Failure of the Month, Build Log, Defensive Lab, Firmware Desk, Network Case Study, and Freeware Archaeology.
CURRENT STATUS
Cyberdelia now has a released original utility with source, license, changelog, Cyberdelia custody README, per-file hashes, normalized manifest, deterministic ZIP, and recorded download SHA-256. The broader software catalog, reviewed workbench, additional original utilities, and public freeware mirror remain active build work and are marked individually as they become real.