Skip to the card

2026-10-22 issue

Observed arrival · 2026-10-22

Ledgerlight asks whether the safety test actually ran

ledgerlight.dev Visit website
Editorial interest 79/100 Selection signal · not a rating of the site

Ledgerlight compares a Markdown loss ledger with test reports to show, loss by loss, whether the cited checks ran and passed.

Landing page captured for the 2026-10-22 issue.
For
Teams tracking software safety tests in CI
Worth noticing
A missing report is explicitly NO-REPORT, never a pass; the CLI distinguishes that from a test file missing from a supplied report.

Field notes

The CLI takes the ledger and test reports as separate inputs, so the ledger cannot certify its own claims. Its examples cover Vitest and Playwright JSON, and the page says there is no config file or runtime dependency. A missing project report yields NO-REPORT, while skipped or todo cases receive a distinct verdict; the documented exit codes also let a CI job fail on dark or unclaimed losses.

Observed signals

Read the marks

Editorial observations of this landing page, not a rating.

○OpenPublic substance visible
✦PrettyNotable craft visible
●ProPolished or operationally mature
◎NicheUnusually specific use

One card from the complete issue

Longitude Takes Time

459,427 arrived 1,000 judged 979 catalogued Enter the complete issue
ledgerlight.dev

Landing page observed 2026-10-22. The live site may have changed.