Free pages of public repos

SeeRepo reads popular public repos on GitHub and writes free pages about them. It reads only what's in the code and keeps none of it. AI only helps sort a repo's packages and folders by their names, and never sees its code. Every page has its markdown version for agents: add .md to its address.

The pages

• The repo's page, /r/owner/repo: what the repo is, its free pages and its figures.
• What it's built with, /r/owner/repo/built: each service with the file and line that prove it, and other repos with a similar stack.
• How much of it AI wrote, /r/owner/repo/ai: the share of its commits each AI tool signed.
• Repos written with an AI tool, /written-with/claude-code: the public repos with 20 or more commits signed by that tool.
• Repos that use a technology, /uses/nextjs, or a pair of them, /uses/nextjs+stripe: by stars, with filters by language, framework and AI that don't change the address.
• The best-tested repos of a framework, /best-tested/nextjs: the ones with 10 test files or more and 20 code files or more, by the share of their code files that a test imports directly. It says which files a test reaches, not which lines run.
• Two repos side by side, /compare/owner/repo/vs/owner/repo: stack, size, who writes them, activity and tests, with what they share. It never says which one is better.
• The leaderboard, /leaderboard: which AI tool signed the most commits this month in the public repos in Google, the repos with most commits and those where AI signs most (20 signed commits or more). Each closed month keeps its photo at a fixed address, /leaderboard/2026-10, which doesn't change. People never appear in it.
• The indexes, to find the rest: /uses (every technology with its page), /written-with (every AI tool), /best-tested (every framework) and /repos (every language), each with how many repos, the biggest first. A language's directory, /repos/go, lists its repos in Google, 100 a page by stars (/repos/go/2). You'll find them under Explore, at the bottom of every free page.

Which repos it reads

Popular and active ones: 500 stars or more and a push in the last 6 months. Never a fork, an archived repo or an "awesome" list. It reads the most starred first, and reads a repo again after a push.

When a page enters Google

Only past its minimum. Under it, the page exists but asks not to be in Google.

• What it's built with: its language read and 3 technologies.
• How much AI wrote: 20 commits signed by AI tools.
• A list (written with, uses, best tested): 10 repos. A pair of technologies under it has no page at all.
• A comparison: both repos already in Google, with 3 technologies or more in common.

Repos enter Google in daily batches, the most starred first, so quality is checked before the next batch.

Where each fact comes from

From the repo's code at the commit the page names, as SeeRepo's engine reads it: its package files, its imports and its git history, where AI tools sign their commits. From GitHub: its stars, description and license. Each page says when it was read.

Is it your repo?

Claim it

Connect it to SeeRepo and publish its map: its pages then come from your live map. Connecting alone changes nothing public; your free pages stay until you take them down.

Take its pages down

1. Open Is it your repo? at the bottom of its page, or go to /r/owner/repo/remove.
2. Install the SeeRepo app on that repo (that repo alone is enough). GitHub only lets the people who administer a repo install apps on it.
3. Click Confirm with GitHub. SeeRepo checks with GitHub that you administer the repo and doesn't keep your token.
4. Click Take down the free pages.

Its pages leave Google and their addresses say the repo isn't public; it leaves every list and comparison, and SeeRepo doesn't read it again. You put them back the same way, with Put back the free pages.