Great code deserves a great repository.
You put the hard work into the code. But when a recruiter, potential user, or future contributor lands on your repo, they are evaluating the packaging as much as the code itself. A missing README, no install instructions, or no tests are enough to make most people close the tab.
RepoGrade scores what makes a repository worth using and contributing to. The same repo always earns the same score. No opinions, no guesswork, just a fixed set of checks run against a clear standard.
Designed for software projects
RepoGrade is optimized for repositories that contain actual software: Python, JavaScript, TypeScript, Go, Rust, and similar. It is not a great fit for curated lists, wikis, or link collections (think awesome-* repos), which have a different notion of quality. Broader project-type support is on the roadmap.
The code is 90% of the work.
Most developers spend months on the logic and fifteen minutes on the README. But the repo is the first thing anyone sees. A clear README, working CI, and a good screenshot can change how people see your project in a couple of hours of work.
RepoGrade tells you exactly where those hours should go.
What a high score signals
- A screenshot or GIF in the README shows what the project does in two seconds.
- Clear install and run steps mean anyone can get it working on their first try.
- Tests and CI prove the code works today and keeps working as it evolves.
- Issue templates and a contributing guide show that contributions are welcome.
- A license tells people how they are legally allowed to use and build on your work.
- Pinned dependencies and lockfiles make setup reproducible across machines.
The grade scale
- A90–100Portfolio ready. Reproducible, documented, tested, and welcoming to contributors.
- B80–89Strong, with minor gaps. Easy to fix into an A.
- C70–79Functional, but missing the signals that build trust with visitors.
- D60–69Rough. Several fundamentals are absent.
- F0–59Hard to evaluate, reproduce, or trust.
Who it is for
Students and new graduates
Recruiters spend seconds deciding whether to click into a project. A clear README, working tests, and a live demo link can turn a glance into a conversation.
Developers seeking contributors
Good docs and a CONTRIBUTING guide are what convert visitors into actual pull requests. Most projects lose contributors at the setup step.
Teams and open source maintainers
A well-maintained repo signals to users that the project is reliable and that issues will be addressed.
Anyone sharing their work
Whether it is a side project, a library, or a research tool, the repo is what people see first. Make it count.
See where your repo stands.
Grade any public repository in seconds. No account required.