Method and contact
This site reads public repository pages and nothing else. It does not rank projects by quality and it does not test whether a project runs.
What is read
For each project: the repository record from the GitHub REST API or, for projects hosted elsewhere, the Forgejo API of that host; the latest release object; the whole file tree of the default branch; every license-named file in it (LICENSE, COPYING and variants, outside vendored, font, documentation and test folders); the first part of each of those files; and the first part of the README. Numbers on a page are copied from those responses. Days are counted from the read date, 2026-11-14.
The three checks
License is decided with one rule for every project. A project passes when the whole repository is available under one open-source license (one open-source license), or when the whole code is open source and a commercial license is offered on request as an alternative (dual, for example a project sold both under AGPL and under a commercial license). It fails when any part of the tree sits under a license that is not open source or that needs a subscription or agreement to use in production (split, the open-core pattern: ee/, enterprise/ or proprietary/ folders with their own license file), when the whole repository is source-available (source-available), or when an open-source license has extra terms added (custom). Where we find such a part, the page quotes the sentence from that file and names its path.
Live: the repository is not archived. Active: the latest of the last release date and the last push is within 90 days of the read date. Pushes include the pushes that create tags, so a project that only publishes tags is counted by its push date.
These thresholds are a starting choice, not a standard. Two archived repositories (MinIO, PocketBase) were also opened in a browser and the archive banner read.
What it cannot tell you
The license scan finds separate licenses by file and folder name. A separate license in a file with another name, in a repository outside the one read (a private repository or a git submodule we cannot open), or only described on the project's website is not found. Where the file tree was too large to list in full, the row says so. A repository can have a clean license and still sell a closed edition elsewhere. Install facts are the files present in the repository, not a tested install. README mentions are words in the first part of the README, not a feature test. Star counts are not comparable between forges. Nothing here is legal advice.
Contact
Corrections to a row: [email protected]. Include the project and the line that is out of date.