Saw a SafeLaunch badge? Check it in seconds.
What a record proves
A promise about one version. Not a blanket one.
One exact version
A record covers one commit, upload or captured page, identified by its fingerprint. Code shipped after it isn't covered, and the record says so.
Signed by SafeLaunch
Each record is signed with an Ed25519 key. The public keys are published, so anyone can check the signature without trusting this page.
Still standing, or not
Records are append-only. If one is withdrawn, replaced by a newer version or overtaken by new code, the record shows it.
How to check one
- 1
Open the record
Paste the link or ID above. Every genuine badge and certificate points to a page on safelaunch.site/verify.
- 2
Read what it covers
The project, the exact version, the rulebook version it was checked against, its score and any exceptions the owner recorded.
- 3
Check the integrity
The record page confirms its digest and signature. Owners can also drop their files on it to confirm they match the fingerprint.
Checking independently? The public keys are at /api/signing-keys. Each record's payload is signed as canonical JSON (sorted keys, no whitespace).
When it isn't genuine
- The badge links anywhere other than safelaunch.site/verify.
- The record page says no such record exists.
- The project name or version doesn't match what you're looking at.
- The record shows as withdrawn, or reports newer code that it doesn't cover.
A record shows what SafeLaunch checked and found. It isn't legal advice or a guarantee of compliance.
Want a record for your own product?
Fix what the scan finds and Launch Fix signs off the exact version you ship, with a badge and certificate that point here.