How we curate

A directory is only worth reading if you know how it was assembled. This page states the rules this site holds itself to — what gets listed, where the numbers come from, and what money can and cannot buy.

What gets listed

Every entry is added by hand. Nothing is imported in bulk from another list, and nothing is listed because it is popular alone.

  • The source must be published under an OSI-approved licence, or an explicitly documented source-available licence.
  • The project must be directly useful for building or operating AI agents.
  • There must be documentation, or a quick start that actually runs.
  • A project with no commits for 12 months is still listed, but marked, so you learn that from the card rather than from a wasted afternoon.

What does not get listed

Closed-source products, thin wrappers with no independent value, abandoned proofs of concept with no documentation, and anything whose licence cannot be established.

How entries are written

The summary and the "what can you do with this" points are written here, from scratch. They aim to say what a project is good at and where it is a poor fit. A summary with no trade-off in it is usually a summary written without using the thing.

English and Japanese are written independently. The Japanese edition is not machine-translated English.

Why the README is reproduced

Below our own writing, each page reproduces the project's README. It is attributed to the repository, shown under the licence that repository publishes, and linked back to the original. Very long READMEs are shortened, and that is stated on the page.

The reasoning: our judgement is what you came for, so it comes first and it is never replaced by someone else's marketing copy. But once you have decided a project is worth a look, having its own documentation on the same page saves a round trip. The README is reference material underneath an opinion, not a substitute for one.

If you maintain a project listed here and would rather your README were not reproduced, write to hello@agents-oss.com and it will be removed while the entry stays.

Where the numbers come from

Stars, forks, open issues and last-commit dates come from the GitHub API and are refreshed daily. The site stores a snapshot rather than calling GitHub while you read, so the date of the last sync is shown and you can judge the freshness yourself.

Growth figures compare the current star count against the stored history. Until a project has at least two days of history, no growth figure is shown at all rather than an implied zero.

Logos and trademarks

Each entry shows the project's own mark, taken from the icon its website declares or, failing that, from its GitHub organisation avatar. The files are copied into this site rather than hot-linked, so visiting a listing does not report your visit to the project's host.

Those marks remain the property of their respective owners and are shown to identify the project, not to suggest it endorses this site. Any maintainer who would rather their mark were not used here can write to hello@agents-oss.com and it will be removed.

Sponsorship and independence

Paid placements, when they exist, are labelled Sponsored on every surface they appear. Sponsorship buys visibility in a designated slot. It does not buy ranking position, a better description, or the removal of a caveat.

No affiliate links, and no payment is accepted in exchange for editing or deleting an assessment.

Corrections

Every entry shows the date it was last reviewed. If something here is wrong or out of date — a licence change, a transferred repository, a claim that no longer holds — write to hello@agents-oss.com and it will be corrected, with the review date updated.