repo open metadata protocol

Live public surface

Repository understanding, made reusable.

dotrepo is a trust contract for repository metadata. The important part is not that a .repo file exists. The important part is that hosted answers carry selection reason, provenance, and claim context instead of pretending repository metadata is conflict-free.

See the live trust handoff Explore the public index Read the docs Read the code

Growth and snapshot

613 repositories Published in the current validated export.

613 reviewed or verified 0 records remain imported or inferred.

Rust 58 · TypeScript/JS 178 · Python 182 · Go 72 · Other 123 Primary language-family mix in checked-in index records.

1 accepted claim example Accepted maintainer-owned claim examples in the checked-in index.

2026-07-09 05:38 UTC Snapshot generated at.

2a74819d150a...8a55626696 Snapshot digest 2a74819d150a795c9a6f725d04a13bac74839f3c7b2ea265bc05138a55626696.

Stale after 2026-07-16 05:38 UTC

Two layers of cooperative automation

PageDigest prevents redundant fetching. dotrepo prevents redundant repository interpretation. Together, they are publisher-declared state for automated clients: fetch less, infer less, and preserve provenance.

PageDigest

One manifest tells automated clients what changed before they spend requests on unchanged pages.

dotrepo

One trust-aware record tells automated clients what a repository is, how to use it, and why the answer won.

Together

Fetch less. Re-interpret less. Preserve provenance across repeated machine work.

PageDigest dogfood

dotrepo publishes thousands of small JSON records. PageDigest lets a consumer check the whole covered set first, then fetch only records whose content actually changed. These numbers come from the current export's /v0/stats.json.

2,453 tracked records Records covered by /.well-known/pagedigest.json.

19 needing fetch New or changed records in this export cycle.

2,434 fetches avoided Covered records that a PageDigest-aware consumer can skip.

4.7 MB avoided Payload bytes skipped this cycle out of 4.7 MB covered.

~1.2M tokens avoided Coarse bytes ÷ 4 estimate for agent-context savings.

site_rev 3 Manifest size 658.6 KB; generated 2026-07-09 05:38 UTC.

Trust proof

The strongest live artifact on this site is not a generic field lookup. It is a claim-aware trust response that shows accepted maintainer state, preserved reviewed overlay context, and canonical handoff without silently flattening history away.

ries-rs

github.com/maxwellsantoro/ries-rs

High-performance Rust reimplementation of Robert Munafo’s RIES (RILYBOT Inverse Equation Solver). Given any target number, it discovers elegant algebraic expressions and equations that evaluate exactly to it — now with parallel search, PSLQ integer relations, Python bindings, and WebAssembly support.

claim state: accepted The current exported claim state for the selected record.

handoff: superseded The reviewed overlay remains visible while the accepted maintainer claim points to the canonical source of truth.

confidence: high Provenance: imported, verified

Bootstrapped from `README.md`, `.github/CODEOWNERS`, `.github/SECURITY.md`, and `package.json`. SECURITY.md provided a policy or reporting URL rather than a direct mailbox, so `security_contact` preserves that URL. Impo...

Selection stays explained instead of being reduced to a bare answer.

Summary Trust Query input

What the live trust surface returns

This excerpt comes from the current exported snapshot and keeps the handoff visible. That is the product proof most metadata layers cannot show.

{
  "identity": {
    "host": "github.com",
    "owner": "maxwellsantoro",
    "repo": "ries-rs"
  },
  "selection": {
    "reason": "only_matching_record",
    "recordStatus": "verified",
    "claim": {
      "state": "accepted",
      "handoff": "superseded"
    },
    "trust": {
      "confidence": "high",
      "provenance": [
        "imported",
        "verified"
      ],
      "notes": "Bootstrapped from `README.md`, `.github/CODEOWNERS`, `.github/SECURITY.md`, and `package.json`. SECURITY.md provided a policy or reporting URL rather than a direct mailbox, so `security_contact` preserves that URL. Impo..."
    },
    "artifacts": {
      "reviewPath": "repos/github.com/maxwellsantoro/ries-rs/claims/2026-03-16-maintainer-claim-01/review.md",
      "evidencePath": "repos/github.com/maxwellsantoro/ries-rs/evidence.md"
    }
  },
  "conflicts": []
}

Review path: repos/github.com/maxwellsantoro/ries-rs/claims/2026-03-16-maintainer-claim-01/review.md · Evidence path: repos/github.com/maxwellsantoro/ries-rs/evidence.md

Repo lookup

Paste a repository URL and jump straight to the hosted summary or trust surface. This keeps the human path aligned with the shipped dotrepo.lookup MCP tool instead of inventing a separate browse product.

Paste a repository URL or identity

Open the live hosted summary or trust surface directly from the current public index. The same public origin also powers the MCP dotrepo.lookup tool.

Examples

BurntSushi/ripgrep Defaults to github.com for shorthand input.

github.com/astral-sh/uv Explicit host plus identity segments.

https://github.com/pydantic/pydantic Full repository URL.

https://dotrepo.org/v0/repos/github.com/BurntSushi/ripgrep/index.json Hosted summary or trust URL pasted back into the lookup box.

Why dotrepo

For maintainers

Keep essential repository facts in one trustworthy layer instead of scattering them across README files, CI, platform settings, and tribal knowledge.

For users

Inspect what a project is, how it should be trusted, and where claims came from without cloning the index or reading every supporting file first.

For agents and tools

Query stable JSON and same-origin endpoints directly instead of guessing intent from prose, conventions, and partially structured repository surfaces.

Docs

The public site now keeps the documentation entrypoint on the first-party domain. Detailed working docs still live in the repository, but the navigation no longer treats the site as a thin wrapper around GitHub.

Product and status

Start with the project overview, install guide, and maintainer path before diving into RFC history or operator detail.

Protocol and trust

The trust model, public surface architecture, and roadmap explain how reusable facts remain honest: provenance, precedence, freshness, and visible conflict.

Autonomous index

The roadmap, index rules, and maintainer-claim docs show how evidence-backed overlays scale without confusing generated facts with maintainer authority.

Start at the first-party docs landing page.

Interview-backed priorities

A 9-model, 12-session interview round on dotrepo's current shape converged on three priorities: grow coverage until checking dotrepo is the cheap default, preserve trust and freshness, and keep the core contract focused.

Broaden coverage

Remote lookup has shipped. The next bar is broader ecosystem coverage with measurable field quality.

Automate the conveyor

Deterministic parsers do the common work, unresolved fields escalate through bounded model tiers, and machine gates publish or abstain without a routine human queue.

Keep it small

The trust model, freshness semantics, hosted lookup, and compact schema remain the differentiators. Discovery should be built on profile quality, not used to disguise its absence.

Read the on-site write-up: What the AIs Think About dotrepo. Working repo notes remain in docs/ai-tool-interviews.md.

Writing

Ongoing field reports, launch notes, and research syntheses from the protocol, public surface, and agent-facing product work.

Writing

What the AIs Think About dotrepo

March 18, 2026

A dotrepo-side synthesis of a 9-model, 12-session interview round about repository metadata, trust, adoption, and what AI coding tools actually need.

Read article Companion essay

Public API

Stable entry points

The public surface is export-first. Summary, trust, inventory, freshness, and query responses all come from the same validated snapshot family.

/v0/meta.json Snapshot freshness and digest metadata.

/v0/health.json Machine-checkable origin, snapshot, count, and digest coherence.

/v0/repos/index.json Repository inventory and navigation links.

/v0/repos/<host>/<owner>/<repo>/index.json Per-repository summary surface.

/v0/repos/<host>/<owner>/<repo>/trust.json Selection, provenance, and claim context.

/v0/repos/<host>/<owner>/<repo>/query?path=... Same-origin trust-aware field queries.

read-only / same-origin / claim-aware No mutation API, one canonical host, and trust context stays visible on every query path.

What a query returns

The query route returns the selected value together with selection, trust, and conflict context. This truncated example is derived from the current exported snapshot.

/v0/repos/github.com/0x192/universal-android-debloater/query?path=repo.description Hosted query route for repo.description; static preview data: query-input JSON.

{
  "path": "repo.description",
  "value": "Cross-platform GUI written in Rust using ADB to debloat non-rooted android devices. Improve your privacy, the security and battery life of your device.",
  "selection": {
    "reason": "only_matching_record",
    "recordStatus": "verified",
    "trust": {
      "confidence": "high",
      "provenance": [
        "imported",
        "inferred",
        "verified"
      ],
      "notes": "Bootstrapped from `README.md` and `Cargo.toml`. Inferred `repo.build` from `Cargo.toml`. Inferred `repo.test` from `Cargo.toml`. This is an overlay bootstrap, not a maintainer-controlled canonical record. Preserved prio..."
    },
    "evidencePath": "repos/github.com/0x192/universal-android-debloater/evidence.md"
  },
  "conflicts": []
}

github.com/AlistGo/alist

🗂️A file list/WebDAV program that supports multiple storages, powered by Gin and Solidjs. / 一个支持多存储的文件列表/WebDAV程序，使用 Gin 和 Solidjs。

Summary Trust Query input

Browse all 613 repositories