Accepted
Everything passed — build, tests, security, and proofs on your exact source.
FalseGreen Report
Proof of work.
Every FalseGreen Job ends in a report that anyone can verify offline.
The verdict
Three outcomes. Each one is final.
Failed
Something was demonstrably wrong — the report names it and states the fix.
Insufficient Evidence
The verification could not finish correctly - never a silent pass.
What's inside
Six sections, in every report.
The verdict
Accepted, Failed, or Insufficient — one word that settles it, decided on your exact source.
HTML · PDF · JSONThe evidence
For every requirement: what was run, what it returned, when.
HTML · PDF · JSONSecurity findings
Vulnerable packages with severity and the fixed version, secrets, undeclared components, licence terms.
HTML · PDF · JSONThe proofs
The claim the tools discharged and the result, quoted verbatim.
HTML · PDF · JSONThe environment
The exact toolchain the verification ran on.
HTML · PDF · JSONThe signature
Ed25519, embedded in the JSON. A changed byte fails the check.
JSONThe JSON
HTML and PDF are for humans. The JSON is the artifact.
Full SBOM + VEX exports
The machine-readable inventory and vulnerability posture of the exact build.
JSONCounterexample traces
For a violated proof, the input that breaks the rule — reproducible.
JSONPer-attempt history
Every attempt in the Job, with its own source and outcome.
JSONReal reports
Both verdicts, from runs that really happened.
Accepted Report
The open-source FalseGreen Ledger: every requirement green on the first attempt, with two machine proofs of its core rule.
Open →Critical ReportThe same project, blocked by a vulnerable dependency: the fix is named in the report, the attempts ran out, and the Job was never accepted.
Open →The program these runs certified is open source:GitHub.
Every report, three addresses
HTML — falsegreen.com/report/<job_id>
PDF — falsegreen.com/report/<job_id>/pdf
JSON — falsegreen.com/report/<job_id>/json
The HTML view links the PDF and the JSON. The JSON is the version the FalseGreen client checks.
Certification and audits
When an auditor asks you for evidence, give them the report.
An agreed spec
The requirement was agreed to and frozen before anyone was graded — and it is quoted in the report.
A verified program
The verdict is bound to one exact source snapshot, hashed — not to a version range or a claim.
An independent reviewer
FalseGreen decided it, the evidence is embedded, and the signature checks offline.
Verify it yourself
Verify the report offline, on your local machine.
Offline verification
1 cargo install falsegreen
↓ save the JSON (add /json to any report's address)
2 falsegreen verify-report ./report.json
↓ no account, no network
3 VERIFIED — the report is exactly what our key signed