This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
attested
Swap test screenshots for signed receipts on pull requests
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.
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.
No comment highlights available yet. Please check back later!
About attested on Product Hunt
“Swap test screenshots for signed receipts on pull requests”
attested was submitted on Product Hunt and earned 2 upvotes and 1 comments, placing #140 on the daily leaderboard. 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.
attested was featured in Open Source (69.1k followers), Developer Tools (523.2k followers) and GitHub (41.5k followers) on Product Hunt. Together, these topics include over 147.5k products, making this a competitive space to launch in.
Who hunted attested?
attested was hunted by Zachary Lendon. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how attested stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
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.