Each report is a deep, public-evidence audit of a real asset that the core team publishes to demonstrate what the tool produces.

Reports are immutable: once published, a report is never edited. Re-auditing an asset later adds a new dated report alongside the old one, so you can watch how a project's situation evolves over time.

What a report answers

• Continuity — can the project survive its current maintainers leaving or losing interest?
• Third-party operability — could an independent successor build, run, and recover it without the creators?
• Evidence — every finding traces to a pinned commit or public source, frozen at a stated cutoff date.

Reports

Asset	Evidence cutoff	Audit
vanityurls.link	2026-07-22	Continuity & third-party operability (deep)

Layout

Every report folder follows the same shape, open index.md to start reading:

audits/
└── <asset>/                        # the audited asset name
    └── <evidence-cutoff>/          # date the evidence was frozen (e.g., cutoff)
        ├── index.md                # START HERE — THE REPORT'S ENTRYPOINT
        ├── manifest.json           # machine-readable metadata
        ├── executive-summary.md    # the reconciled assessment and 30–90 day plan
        ├── controls/               # control-by-control analysis of each safeguard
        ├── evidence/               # evidence ledger and supporting packets
        ├── reviewer-reports/       # findings by review discipline
        └── operator-aids/          # how-to guides for a new operator to rebuild, recover, and monitor

See CONTRIBUTING for the folder conventions and how to add a report.