CRITERIA

Inclusion criteria and ranking factors

What gets into the index, what the daily health check reads off each repository, and the six factors the ranking is made of.

WHAT GETS IN

The entry is somebody else’s repository. Nothing Compound Labs builds is in the index, and neither are the model vendors’ own repositories.
The repository exists and has been released. A roadmap, a specification with no implementation, a placeholder and an empty template repository do not go in.
It is an MCP server, a coding-agent harness, an agent framework, or tooling around those. A vector database that tags itself for agents does not go in.
Two independent signals affirmed it, never one. The five signals and what each one means are on how it works, and the people behind them are named on where the entries come from.
One of the accounts posted it. The index is a record of what the accounts published, so it never holds more than they said.

WHAT THE HEALTH CHECK READS

A daily job re-reads every entry’s repository and writes down what it says. Each value carries the URL it was read from, and the entry page prints that URL beside the value. Nothing on this site states a repository fact it did not fetch.

It last read 165 of the 165 entries in the index. The oldest of those reads is from Sep 25, 2026 and the newest is from Sep 25, 2026. 1 repository did not answer on the last read, and those entries are shown as not verified rather than scored.

The job does not run anybody’s code. Where this site says an install command resolved, it means the first install command in the README names a package and that package answered on its registry. It does not mean the tool was run, and no page here says it was.

THE SIX RANKING FACTORS

An entry’s score is the weighted mean of the factors below. A factor whose value could not be read is left out of both the top and the bottom of that mean, so a repository is never ranked down for a fact nobody could check. Stars are not a factor, and neither is the age of the entry.

FACTOR	SHARE	WHAT IT READS	HOW IT SCALES
Last commit	0.22	The pushed_at field on GET /repos/{owner}/{repo}.	A commit today scores 1. A commit 365 days ago or older scores 0.
Commits in 90 days	0.20	The page count of GET /repos/{owner}/{repo}/commits?since=<90 days back>&per_page=1.	30 commits or more scores 1. Zero commits scores 0. The steps between are linear.
Last release	0.18	The published_at field on GET /repos/{owner}/{repo}/releases/latest.	A release in the last 90 days scores 1. A release 730 days old scores 0. A repository with no tagged release scores 0, because a release is the thing being read.
Issue close time	0.15	The median of closed_at minus created_at over the closed issues on GET /repos/{owner}/{repo}/issues?state=closed&per_page=30, pull requests excluded.	A median of 2 days or less scores 1. A median of 60 days or more scores 0. A repository with no closed issues to read is not measurable and is left out of the score.
Licence	0.10	The license.spdx_id field on GET /repos/{owner}/{repo}.	An SPDX identifier scores 1. No identifier scores 0, which includes a repository whose licence file GitHub could not identify.
Install command	0.15	The first install command in the README, and the registry that command names. The registry URL is printed on the entry.	The package resolved on its registry scores 1. The package did not resolve scores 0. A README with no install command to check is not measurable and is left out of the score.

The bands the board filters on are cuts of that score.

Maintained. The score is 0.75 or above.
Active. The score is 0.50 up to 0.75.
Slowing. The score is 0.25 up to 0.50.
Dormant. The score is below 0.25.
Archived. The owner marked the repository archived on GitHub. The score is 0 and no factor is read.
Not verified. The health check has not read this repository yet, or the read failed. Nothing is scored.

DEPLOYMENT MODEL

Installable package. The README’s install command names a package, and that package resolved on its registry.
Container image. The repository root carries a Dockerfile or a compose file.
Clone and build. Neither of the two above was found, so the way the README gives is to clone the repository.

There is no hosted-service model on that list. A repository that declares a homepage is declaring a URL, and a documentation site, a landing page and a hosted product all set the same field. The homepage is printed on the entry as a homepage.

PERMISSION SCOPE

These four are read out of the repository’s own README. The entry prints the phrase that matched, so the claim on this site is about what the README says and never about what the tool does.

Runs commands. The README says the tool runs shell commands or executes code.
Reads or writes files. The README says the tool reads or writes files on the machine it runs on.
Makes outbound requests. The README says the tool fetches pages, searches the web or drives a browser.
Takes a key or token. The README asks the reader to supply an API key, a token or a credential.

WHAT THE PERMISSION FIELD IS NOT

The permission scope is per tool. Five separately permitted calls can still add up to one outcome none of them permits on its own: a tool allowed to read files and a tool allowed to make outbound requests compose into a tool that sends your files somewhere. Nothing on this page measures that.

Cumulative state and blast radius are properties of the agent that runs the tools, not of any tool in the index. Agentwire indexes tools and reads their repositories, so it can say what a README declares and cannot say what happens when four of these run in one loop under one set of credentials.

Read the permission scope as the question to ask the tool, not as an answer about it. An entry with no permission finding is an entry whose README said none of those things, which is a fact about the README.

WHAT IS STILL NOT TESTED

No entry here has been run, benchmarked or reviewed. The health check reads metadata off a repository and a registry. It does not tell you a tool is good or that it works.

To have an entry corrected or taken down, write to hello@thecompound.tech or reply to the post on Bluesky. Corrections to a repository fact are applied at one choke point and reach every page at once.