How it works

Publish research with the evidence behind it. Others can search your claims, view earlier versions, and build on your work using the evidence you shared.

Get started

Start with an empty publication repository. You can upload files to it through the website, or connect to a folder on your computer for Git tracking and publishing over time. OpenVersions reviews the claims in your manuscript whenever you publish a new version. You can also search other OpenVersions projects to find relevant claims and methods and access their underlying evidence.

New publication

Already working on GitHub? Publish from an existing GitHub repository and keep pushing updates there. We'll keep track of it.

Claim checks

OpenVersions extracts claims from the manuscript and checks each finding to establish claim support.

Verified
The evidence reviewed supports the claim.
Unverified
The review couldn’t establish whether the evidence supports the claim.
Unsupported
The review found a conflict or a specific problem with the claim’s support.

Open a claim’s status to see the explanation and cited sources.

Build on prior work

Search scientific claims and find relevant repositories with direct links to the paper, code, and data.

SearchAPI docs

To work with a paper and its evidence, download it as a ZIP file or clone it with git. To extend a work, fork the publication repository and push your changes, with credit to the exact version you started from.

Privacy and unpublishing

You control repository privacy. Publish only work you have permission to share. Publishing gives OpenVersions non-exclusive permission to distribute the material and its metadata.

Publish an update or revert a change. Earlier published versions stay readable in Published versions and on their own version pages.

Reset and force-push to a synced GitHub or OpenVersions repository. The next sync or accepted push takes versions dropped from the branch offline and removes them from public history. Their version pages show the commit hash and “This version is no longer available.”

Make a synced GitHub repository private. Imports pause once OpenVersions detects the change. Choose Unpublish to make the publication private on OpenVersions too.

Unpublish the OpenVersions repository. The publication and all its versions become private. GitHub sync pauses, and pushes to an OpenVersions-hosted repository save private commits. Previously public version pages show the commit hash and “This version is no longer available.” Existing forks and downloaded copies are unaffected.