Trust Center

Here's what we do. Here's the evidence. Here's how you can check.

What we mean by "trust"

Every public promotion is backed by a receipt A JSON file listing hashed inputs, the generating commit, and timestamps for a specific promotion week. . Receipts show inputs (hashed), decisions, and the commit that generated them. Nothing is promoted in the dark.

Artifacts Hashed 8
Proven Claims 5
Build Commit 5763028
Projects Tracked 101

How promos are chosen

Promotion follows four steps. Automation handles scoring and generation; humans handle queuing and review.

  1. Score. The worthiness rubric A checklist that scores tools on documentation, tests, releases, and other quality signals. rates each tool on objective criteria.
  2. Queue. A human adds qualifying slugs to the promotion queue.
  3. Generate. The pipeline creates press kits, snippets, and proof pages — all hash-verified.
  4. Publish. A human reviews the PR, merges, and the site deploys.

See This Week's Focus 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 promotion or experiment decisions are made until a human unfreezes.

Decisions Active
Experiments Active

Operators can toggle freeze state from the Control Panel.

Decision drift

Each pipeline run compares current promotion 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 promotion week in four steps:

  1. Visit the promotion week page (e.g. /promo/<week>/ ) and copy the verification bundle.
  2. Clone the repo and checkout the commit SHA from the bundle.
  3. Run sha256sum on each input file listed in the bundle.
  4. Compare your computed hashes to the bundle hashes. If they match, the promotion used exactly those inputs.

No promotion weeks available yet. Check back after the next scheduled run.

Machine-readable trust receipt: trust.json · Source: GitHub