Numbers · 02

Container verification attempts recorded, and how many passed

28 / 68

runs

Stage

deploy_verification_runs

Method

one row per (slug, ran_at, lane) from the weekly verifier

Sample

68

As of

2026-09-07

Note

A failing run names the rung it failed on; the queue retries failures after 28 days (--retry-failed-after). A credentials rung means the spec needs a secret the harness does not hold, not that the install is broken.

select count(*) filter (where ok), count(*) from deploy_verification_runs;

A number from Sato Hub's own tables and public sources. It is never summed across venues, chains or stages; a sample under 20 is shown but is not a finding; “unknown” means the measurement could not be taken, never zero. Data CC-BY-4.0 — attribution: data by satohub.ai.

Sato Hub. "Sato Hub — Container verification attempts recorded, and how many passed." Sato Hub, updated 2026-09-07, accessed 2026-09-08. https://satohub.ai/numbers/container-verification-attempts-recorded-and-how-many-passed