DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to confirm a local rebuild matches the published benchmark with Keystone Bench

Check your rebuilt twins against the hashes the repository publishes, file by file.

  • Research
  • Beginner
  • 30 minutes
  • From the README
  • Any agent

Who it is forA researcher or auditor who wants to cite Keystone results and needs proof that their local copy matches the released data.

The problemThe twins are not shipped in the package, so a reader has no direct way to know their local build matches what was evaluated.

The outcomeA file-by-file match or mismatch report against the published SHA-256 hashes.

What you need first

  • Python with pip to install keystone-bench from PyPI
  • An API key for an OpenAI-compatible endpoint, such as OpenRouter, to run models and a judge from a different vendor
  • Network access so that keystone build can fetch HealthBench from OpenAI's public copy and the label files
  • Enough disk space and time for the local rebuild of the twins, since the release ships span references rather than benchmark prose

Steps

  1. pip install keystone-bench
  2. keystone build
  3. keystone build --check
  4. keystone pairs

Prompt for your agent

Use the keystone-bench package to rebuild the release with keystone build, then run keystone build --check. Report whether every file matches the published hashes and list any file that does not, along with the output of keystone pairs.

Caveat. The rebuild fetches HealthBench from OpenAI's public copy, so the check only confirms a match if that source is also unchanged.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page