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

How to verify a paper's metrics by running its code in a sandbox with Veri Repro

Run a paper's repository in the Docker boundary and get a PASS, FAIL, or PARTIAL verdict.

  • Research
  • Advanced
  • 1 hour
  • From the README
  • Any agent

Remote script. This runs third-party experiment code from the paper's repository, so use disposable infrastructure if the repository might be hostile, since Docker is not a formal sandbox proof.

Who it is forA reproducibility engineer or lab member who needs a grounded verdict on whether a paper's reported numbers can be reproduced.

The problemA script exiting successfully does not show the paper's scientific result was reproduced, and manual comparison of metrics is error-prone.

The outcomeA verdict in report.json and report.md, with metrics, figures, tables, and stdout and stderr logs preserved in the workspace.

What you need first

  • Python with pip to install the verirepro package from PyPI
  • A pinned arXiv ID, DOI, PDF URL, or local PDF of the paper
  • Docker, only if you want third-party experiment code to execute
  • An OpenAI-compatible model endpoint, only if you want model-assisted analysis

Steps

  1. Install the package with python -m pip install verirepro.
  2. Confirm the sandbox prerequisites with verirepro doctor --strict before any third-party code runs.
  3. Run the reproduction of the target paper with verirepro reproduce <paper-id>, adding --allow-network or --allow-gpu only when you have decided to grant those authorities. (inferred, check the README)
  4. Read the verdict in report.json and check the metric comparisons and the experiment.stdout.log and experiment.stderr.log files before you trust the result.

Prompt for your agent

Using the VeriRepro repo (XiantingWu/VeriRepro), run `verirepro doctor --strict` and then `verirepro reproduce <paper-id>` for the paper <paper-id>. Expected output is a workspace with report.json and a PASS, FAIL, or PARTIAL status. Verify that any PASS is backed by evidence-authorized scalar comparisons and not just a zero exit code.

Caveat. Veri Repro states that Docker is an execution boundary, not a formal sandbox proof, and that a PARTIAL verdict is intentional when evidence is insufficient.

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