pinklone

How grading works

Every grade comes from public GitHub data, gathered automatically each week. It's guidance to help you shortlist, not a code review or security audit.

MIT only. A project only enters the catalog if GitHub reports its license as MIT, and it isn't archived or a fork. We also leave out developer libraries, link lists and anything unsuitable for a general audience.
Two tiers. Established projects have 50 or more GitHub stars. Projects with 20 to 49 stars are labeled Rising: they're often newer or smaller, so give them a closer look before you rely on them. Candidates come from GitHub search and the community-curated awesome-selfhosted list, and every one is checked against the GitHub API before it's listed.

The criteria

Resource use

An estimate of how light the software is to run, from its main language and runtime, its size, and how the project describes itself (for example single binary, SQLite, or Raspberry Pi friendly).

Setup

Hints that installation is straightforward, such as ready-made containers, single-binary downloads or a project homepage with instructions.

Activity

How recently code was pushed. Recently updated projects are more likely to get fixes.

Issue load

Open issues and pull requests compared with the size of the project's audience.

Releases

Whether the project publishes releases, and how recent the latest one is.

Community

How many people follow the project on GitHub.

Letter grades

The criteria combine into a letter grade from A (best fit for modest hardware and small teams) through B and C to D. A low grade doesn't mean a project is bad, only that it's a weaker fit for low-resource use today.

Categories

Limits