How it works
From curiosity to commit.
Four steps, all built on open data and the people who maintain it.
step 01
Scout
Forkpad queries GitHub’s search API by the window a project was born in, its language and topics. The default view shows projects created in the last seven days, ranked by stars.
step 02
Inspect
Each project page pulls the repository, its languages, contributors, latest commits, releases and community profile, then turns them into four plain signals: momentum, maintenance, community and openness.
step 03
Shortlist
Bookmarks live in your browser. There’s no account and no tracking. Compare your saved projects in one table.
step 04
Ship
Drafting a launch checks that the repository exists and reads its forkpad.json. If the maintainers have opted out, the draft is refused.
Questions
Where does the data come from?
Everything comes from the public GitHub REST API, cached for a few minutes on the server. Forkpad never touches private repositories.
What do the signals mean?
They’re simple heuristics such as stars per day, days since the last push, contributor count and license presence. Use them to decide where to look closer, not as a verdict on anyone’s work.
Why can’t I launch for some projects?
Their maintainers published a forkpad.json with launches set to disallow. Forkpad treats that as final.
Is any of this financial advice?
No. Forkpad helps you discover and research open-source projects. It doesn’t evaluate tokens or tell anyone what to buy.