Latest, never best
The badge cannot cherry-pick a passing result. It always follows the most recent run and turns grey after 30 days.
- Latest run only
- Stale after 30 days
- 20-point score trend
- Publishing is reversible
Verifiable public proof
Publish a privacy result others can verify.
Turn the latest AgentLeak run into a public trust page and README badge. Visitors see the score, verdict, measurement date, detection tiers and trend—never the findings or sensitive values behind them.
AgentLeak privacy92 · passing
LATEST RESULT92Privacy score
- Verdict
- Passing
- Measured
- Today
- Tiers
- Pattern · Context
The strength of the check is visible
A pattern-only pass is narrower than a full pipeline pass. The page names the tiers that ran, and a degraded run can never display the passing colour.
- Detection tiers named
- Degraded state disclosed
- Verdict and score dated
- Plain-language caveats
Evidence stays private
Public proof confirms that a measurement happened and how strong it was. It never exposes the findings, trace contents or sensitive values.
- No public findings
- No trace contents
- Self-contained page and badge
- Works on hosted and self-hosted installs
The mental model
A trust badge is useful only when it refuses to flatter the product.
A static badge can outlive the code it describes. AgentLeak binds the public claim to a dated latest run, makes weak or degraded detection visible and removes the passing state when the evidence becomes stale.
Before
A badge is a permanent marketing claim.
With AgentLeak
A badge is a link to a current, qualified measurement.
- Staleness replaces the score after 30 days
- Degraded detection cannot appear as passing
- Publishing is explicit, opt-in and reversible
How it works
From private evidence to qualified public proof.
1
Run the audit
Create the result you want the public claim to follow. The latest run will remain the source of truth.
2
Choose the slug
Publish explicitly for the project; recording a run never makes anything public by itself.
3
Place the badge
Use the generated Markdown in a README, documentation site or release page.
4
Keep measuring
Every new run refreshes the claim. Remove the slug at any time to withdraw the page and badge.
Publish and link the latest result
curl -X POST https://www.agentleak.org/api/projects/<id>/publish \
-H 'content-type: application/json' \
-d '{"slug":"support-bot"}'
[]
(https://www.agentleak.org/a/support-bot)FAQ
Questions, answered.
Ready when you are
Test the path, not only the answer.
Create a local workspace, run a bundled scenario, then wire AgentLeak into CI or let your agent onboard itself.