Methodology

Repoworthy lists open source repositories that are genuinely useful, and shows the facts you need to decide whether to use one. This page explains exactly where every number and sentence comes from.

How repos are picked

Repos are chosen by Sasa Teguh for being useful to working developers and self-hosters. There is no paid placement: a project cannot buy a listing or a better position. Projects built by Sasa Teguh itself are included sometimes, and always carry a disclosure on their page.

Where the numbers come from

Stars, forks, contributors, licence, language, open issues, latest release and last commit all come straight from the GitHub REST API. They are refreshed every day, and every repo page shows the date it was last checked. Numbers are never typed by hand.

The maintenance signal

The signal is based only on the date of the most recent push to the repository:

A quiet repo is not necessarily abandoned: small, finished tools often need few changes. Treat the signal as a prompt to look closer, not a verdict.

Licence summaries

Licences are detected by GitHub and summarised in plain words, grouped as permissive, weak copyleft, copyleft or network copyleft. Summaries are a starting point, not legal advice. Always read the project's own LICENSE file.

How the descriptions are written

The one-line description, standout capability and "best for" line are drafted with the help of an AI model that is given only the project's README and GitHub description. Each draft is checked automatically before it is published: it must stay within length limits, may not use hype words, and any number it mentions must appear in the README. Drafts that fail are rejected and rewritten.

Corrections

If something is wrong or out of date, email hello@sasateguh.com and it will be fixed. Maintainers can also ask for their project to be removed.

Open data

Everything on this site is available as JSON at /data/repos.json, free to reuse with a link back.