ReproReady

Status, August 2026: The readiness score is implemented. The artifact checker is under development and is not yet publicly available.

The ReproReady checker is a local, offline, deterministic tool for statically checking computational research artifacts.1 It is designed to help researchers understand the manual work required to reproduce reported computational results, rather than predict whether the code will run.

The checker will statically inspect files, code, data, and documentation and report observations, their source locations, and the reason a person may need to review each observation. Like a programming-language linter, it is designed to provide feedback and assist a researcher who is attempting to reproduce results for computational experiments.

Score and checker

ReproReady consists of two components:

  • The readiness score summarizes how much manual reproduction work an artifact appears to remove
  • The static checker will report individual observations without aggregating them into a score or grade

Initial scope

The first checker release is limited to artifacts that primarily use Python. It will inspect eligible Python files and Python notebook code cells without omitting unsupported languages or content.

The checker does not execute artifacts, verify scientific correctness or research quality, determine policy compliance, or certify reproducibility.

Footnotes

  1. Here, a computational research artifact is the supplemental material submitted with a manuscript or an associated code repository. Back to reference