Verification, for people who like to double-check.
We publish weekly spotlights. We also know the internet is full of confident nonsense — so when we make a claim, we try to back it with something you can inspect.
What you can verify here
Every spotlight pick is backed by a receipt A JSON file listing hashed inputs, the generating commit, and timestamps for a specific spotlight week. . Receipts show inputs (hashed), decisions, and the commit that generated them. You don't need this page to use the site. It's here for the skeptics (we love skeptics).
How spotlight picks are chosen
Spotlight selection follows four steps. Automation handles scoring and generation; humans handle queuing and review.
- Score. The worthiness rubric A checklist that scores tools on documentation, tests, releases, and other quality signals. rates each tool on objective criteria.
- Queue. A human adds qualifying slugs to the spotlight queue.
- Generate. The pipeline creates press kits, snippets, and proof pages — all hash-verified.
- Publish. A human reviews the PR, merges, and the site deploys.
See This Week's Spotlight for currently featured tools.
Worthiness criteria (minimum score: 3/5):
- License is OSI-approved
- At least 1 release published
- README has install + usage
- Activity within last 90 days
- No known security issues
Freeze modes
Two switches control automated decisions. When frozen A governance state where automated pipeline decisions are paused. Humans must intervene manually. , the pipeline still builds the site, syncs the catalog, and tracks releases — but no new spotlight or experiment decisions are made until a human unfreezes.
Operators can toggle freeze state from the Control Panel.
Decision drift
Each pipeline run compares current spotlight decisions against the previous week's snapshot. Drift Week-over-week change in promotion decisions: new entrants, exits, score deltas, and action changes. detection flags new entrants, exits, score changes, and action flips (e.g. "promote" to "skip").
Drift is expected when a human edits decisions while frozen. It is worth investigating when no known intervention occurred. Details are in the Drift Report.
How to verify a week
Anyone can independently verify a spotlight week in four steps:
-
Visit the spotlight week page (e.g.
/promo/<week>/) and copy the verification bundle. - Clone the repo and checkout the commit SHA from the bundle.
-
Run
sha256sumon each input file listed in the bundle. - Compare your computed hashes to the bundle hashes. If they match, the spotlight used exactly those inputs.
No spotlight weeks available yet. Check back after the next scheduled run.