Verify a repository's provenance.
Paste a GitHub repository URL. Aletheia recomputes its canonical repoHash — the same keccak256 anyone can derive — and reads the registry straight from Monad to tell you whether the repo is sealed, and where to find its proof.
1 · Hash
The repo URL is reduced to github.com/owner/repo and keccak256-hashed — the deterministic key the registry stores under.
2 · Read chain
projectByRepo(repoHash) is read directly from Monad. A non-zero id means the build history is sealed on-chain.
3 · Re-verify
Run npx aletheia-verify <id> to recompute every commit and tree hash from a fresh clone — zero trust in this site.
Two layers of trust
This page proves registration and timing — that a repository was bound to the chain and when. Full re-verification of the commit and tree hashes is the CLI's job, and it needs nothing from Aletheia but the public registry. Read the registry yourself on the block explorer.