Hysen Labs
Open-source project
Arnon-hs/open-source avatar
Arnon-hs

open-source

A living, machine-readable catalog of open-source projects with practical summaries, categories, quality signals and transparent scoring.

72 stars14 forksUnknownMIT
DEEP OPEN-SOURCE ANALYSIS

AtlasRepo catalogs open-source projects for coding agents

AtlasRepo is a machine-readable catalog of thousands of open-source projects with summaries, categories, and transparent scoring meant for agent-driven search.

What the catalog is for

AtlasRepo presents itself as evidence-backed open-source search built for coding agents. The repository turns a fast-moving ecosystem into a browsable and machine-readable decision layer. The stated purpose is to help you discover candidate projects, compare practical fit, and give coding agents a grounded starting point before deeper technical, security, and license review. The README describes the data as a living, auto-curated catalog enriched with practical summaries, categories, quality signals, and transparent scoring. It is not meant to replace hands-on review. Instead it narrows the field so an agent or a human can focus attention where it matters. The authors frame trust as a boundary: the catalog summarizes signals, but the final judgment about security and licensing still belongs to the reviewer. That boundary is written into the project's documentation so users do not treat the scores as a verdict. The README also links a hosted MCP endpoint and an npm package, which tells you the catalog is meant to be queried by software, not only read by a person. For a coding agent asked to pick a library, the catalog offers a ranked shortlist with reasons instead of a blind web search, which is the core use case the project was built around.

Scale and categories

The at-a-glance table lists 33363 projects across 48 categories, with the catalog continuously maintained by something called AtlasRepo Scout. Categories include Misc with 15023 projects, AI/ML with 3265, Mcp with 2529, Orchestration with 2180, and DevTools with 1338, followed by many smaller buckets such as Automation, Frontend, Backend, Crypto, Mobile, DevOps and Infra, Database, and Security. Each category links to a browsable subdirectory. The metadata attached to entries includes repository signals, multilingual summaries, and practical evaluations. The breadth means an agent can ask for, say, a security tool or a database library and receive a ranked shortlist instead of a raw web search. The README also shows a top-projects-by-score view and explains what each entry includes, so the shape of a record is clear before you consume it programmatically. A Trust boundary section is repeated near the data so readers remember the scores are guidance. The number of categories, 48 in total, covers everything from Design and Content-creation down to tiny buckets like Privacy and Agent-memory with only a couple of entries, which shows the catalog tries to stay fine-grained even where the project count is low. A browse link on each row opens the filtered list so you can scan a category without cloning the data.

Installing and using it

Two integration paths are documented. For ChatGPT there is a hosted MCP plugin you can enable without running your own server. For Claude Code the project provides setup so the catalog acts as a tool the agent can query. An npm package named atlasrepo-mcp is also published for developers who want to embed the catalog in their own flow. The README describes a data contract that defines the fields each entry carries, and it restates the trust boundary that scores are signals rather than guarantees. The license section confirms the project is MIT licensed, which matters if you plan to vendor or extend the data. By exposing both a hosted plugin and a code package, AtlasRepo lets teams choose between convenience and control while keeping the same underlying catalog of projects and quality signals. There is also a Skills link in the README pointing to companion material that helps agents use the catalog inside workflows. The combination of a hosted endpoint, an installable package, and a documented schema means you can start with zero setup and later move to self-hosted control without changing how your agents ask questions. That migration path is part of why the project splits the offering the way it does. The community channel is the place to ask when a provider you need is missing. The maintainer-backed paths are the ones to trust for production use.

Editorial conclusion

The catalog is published under the MIT license and ships a hosted MCP plugin plus an npm package named atlasrepo-mcp.

DEEP OPEN-SOURCE ANALYSIS

Official sources

Community notes

Community notes