Where to submit your open-source GitHub project
Every venue worth submitting an open-source project to in 2026, organized by traffic profile, audience, and durability of visibility. Honest tradeoffs for each.
Read more →Blog
Longer-form updates and explainers. For a terse ship log, see Changelog.
The 800-character rule: why long reviews beat thumbs
Why we set the review minimum at 800 characters, what that actually filters out, and the data showing why a higher floor produces better signal than upvotes.
Read more →How to write a code review that helps the maintainer
A practical template for writing peer reviews of open-source projects: what to cover, what to avoid, and how to give honest feedback without being a jerk.
Read more →GitHub stars don’t measure quality. Here’s what does.
Why stars are a lagging vanity metric, what they actually correlate with, and the signals that tell you whether a repo is worth your time.
Read more →How to launch an open-source project in 2026
A pragmatic launch playbook for OSS maintainers: pick the right surfaces, sequence the launches, and keep visibility compounding after week one.
Read more →Topic pages, RSS, and the public API
Ways to browse and syndicate what’s on the RepoRanker board: topic index pages, the RSS feed, and the public JSON API.
Read more →Credits, boosts, and the 48-hour review window
How earning credits after the 48-hour review window, releasing reviews, and spending credits on leaderboard boosts all fit together.
Read more →What is RepoRanker?
A public leaderboard and credit-based review community for open-source GitHub projects. Submit free, earn credits for writing reviews, spend them on visibility.
Read more →