CYBERDELIA SKUNKWORKS
American cyber-technology laboratory and publication
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 software reviews, preserved freeware, source packages, 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
Read-only Python intake utility for FOIA and declassified record sets. It recursively inventories source files, records SHA-256 and byte counts, emits JSON + CSV manifests, and identifies exact duplicate groups without modifying the evidence directory.
Download ZIP · ZIP SHA-256 · README · Source
Dependency-free Python release auditor for FOIA, declassification, and public-record drops. It inventories two directory snapshots with SHA-256, classifies added, removed, changed and unchanged files, and detects probable renames when the bytes are identical but the path moved.
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.
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 two released original utilities with source, licenses, changelogs, Cyberdelia custody READMEs, per-file hashes, normalized manifests, deterministic ZIPs, and recorded download SHA-256 values. The broader software catalog, third-party software reviews, additional original utilities, and public freeware mirror remain active build work and are marked individually as they become real.