Launching today
attested
Swap test screenshots for signed receipts on pull requests
2 followers
Swap test screenshots for signed receipts on pull requests
2 followers
Your tests already record proof. attested keeps it in your CI and gives the pull request a signed receipt instead: the result on this exact commit, every file fingerprinted, and a required check can block the merge without one. Free and open source.
Free
Launch Team / Built With
AWS Startup AdvisorPersonalized AWS guidance that meets you where you’re already building
Promoted
Hi Product Hunt, I’m Zach, CTO at PRAXSO.
Coding agents now open pull requests on their own, and they show their work the way people do: by pasting test screenshots into the PR, or posting them somewhere they can link to. That goes wrong in public. Glow Labs’ PixelLeak research, reported by Help Net Security, found more than 13,000 internal screenshots that coding agents had pushed to public GitHub, across 900+ repositories and 300+ organizations. A screenshot also can’t tell you which commit produced it or which tests ran.
attested swaps the screenshot for a receipt. Your tests (Playwright, or anything that writes a CTRF report) run as usual; the proof stays in your CI run; the pull request gets a signed receipt: pass or fail on this exact commit, a sha256 of every screenshot, video and trace, and one command to fetch the originals. A required check can block the merge without a passing receipt. When a test fails, your agent gets a short failure packet (emails and tokens masked) through the MCP server for Claude Code, Codex or Cursor, so it can fix and rerun instead of guessing.
What it doesn’t prove: that the change is correct. A PR can still weaken its own tests, so review test changes.
Try it: npx @praxso/attested run -- npx playwright test. Apache-2.0.
I’d love to hear how you show your agents’ work today.