Leitir
Verified dependency source for AI agents
Leitir materializes exact library versions from npm, PyPI, crates.io, Go and git hosts, verifies them with checksums and tree validation, and makes them searchable. It exists so a coding agent can read what a library actually does instead of recalling what it probably does.
Why it exists
LLM agents hallucinate library internals. They will confidently describe a function signature that has not existed for three major versions, because the shape of the answer is right even when the answer is not. The fix is not a better prompt. It is giving the agent the real source, pinned to the version actually installed.
What it does
Exact versions, verified
Libraries are materialized at a specific version and checked by checksum and tree validation before anything reads them.
Multi-ecosystem
npm, PyPI, crates.io, Go modules and git hosts.
Citation-ready output
Deterministic results with API extraction and usage examples, so an answer can point at the source it came from.
Offline-capable corpus
An immutable local corpus with fail-closed verification — missing or unverified source is refused, not guessed at.
Where this actually stands
Implementation-complete but explicitly not production ready — the README says so, and so does this page. Design-stage software.
The repository states its own limits before it states its features. If this page and the README ever disagree, the README is right — tell me and I'll fix the page.
How it fits with Ranex
Leitir is planned to fold into Ranex as a feature. Same principle, applied one step earlier: Ranex checks what was produced, Leitir makes sure what goes in is real.
What the Ranex kernel enforcesTry it. Break it. Tell me what broke.
Leitir is early, and the useful feedback right now is where it falls over. If you find a hole, that's a contribution.