RepoProof.THE EVIDENCE WORKSPACE

Put a repo to the test.

See what a project claims, how it’s tested, and what actually happens
when the code runs. Real evidence you can inspect. A conclusion you can challenge.

Illustrative replay · No repository was executed

This is a synthetic example. Evidence is fictional.

illustrative/route-kita1b2c3d (example)

RUN RESULT

Contradicted

The answer never changes.

Two different inputs returned the same answer.

THIS BROWSER ONLY

Return to the evidence.

Only reports owned by this browser session appear here. Opening one reads stored evidence; it does not inspect source, approve a plan or rerun code. Telegram and MCP reports belong to their separate sessions.

ILLUSTRATIVE REPLAYS

Follow a different claim.

Synthetic examples. No repository code was run.

CLAIM → CHECK → OBSERVATION

Inspect the evidence

Run this pinned plan.

These commands execute downloaded code in an isolated offline job: 0.5 CPU, 256 MiB RAM, 64 tasks and at most 15 seconds per check. Dependencies that are unavailable offline will fail or remain blocked. A passing command does not prove every project claim.

Continue the investigation.

Checking Telegram availability.

Web and Telegram keep separate private investigations. The web evidence remains available here.

QUOTATION → CRITERION → RECEIPT

Cross-check one claim.

Choose an exact source quotation and a narrow command criterion. You select the relationship; RepoProof reports only the observed exit, not whether the tests validate the quotation. This does not run code or change consent.