For maintainers
A result should help you understand and resolve a problem. You can challenge it.
What we found
Find your repo in browse, open More details, then All the evidence. Check the exact revision, model, OS, operation and transcript. An agent getting stuck can be a documentation, prerequisite or test problem; it is not automatically a bug in your code.
The verified fix and how to get it
A card labeled Works with our fix links its reproduction, before/after proof and downloadable fix.patch. Review the patch against the recorded base revision before applying it to your checkout. A filed patch without the three-fail / three-pass cold proof is labeled separately. A verified patch does not mean upstream has accepted or released it.
Nothing is posted upstream by this workflow. Where older records already have filed links, those remain part of the history; “filed” does not assert a current merge or release status.
Make the first run easier
Write down supported platforms, prerequisites and required accounts. Give one runnable example with real input and expected output. Explain setup, configuration and cleanup. Keep hosted, local, demo and dry-run paths distinct. These instructions help both people and agents.
Static badge and read-only data
Each listed repository has a static SVG status badge and a read-only JSON record. To embed the badge in Markdown, use , replacing OWNER--REPO with the repository slug shown on its Coldpass page. The JSON is available at https://coldpass.dev/api/v1/repos/OWNER--REPO.json. These free static features report the same per-setup public labels shown on the page. Payment never changes a verdict.
Dispute, correct or opt out
Send a review request to Coldpass on its own readtrial repo →
Include your repo URL, the Coldpass result or run ID, the tested revision and the specific correction with reproduction evidence. For opt out, say you maintain the repo and request removal from the public listing and future testing. Do not include credentials or private data in a public request.
Requests are reviewed manually. Intake and the general test queue are currently paused; submitting a request does not trigger a run or immediately remove a listing. There is no automatic dispute or opt-out service.