
README Score
ClaimedBy Flisk
Score your README and get a fix for every missing section
Free, no paid tierFree Documentation
Tracked since 2026
The Bottom Line
- Best for
- Open-source maintainers who want a README that readers can follow
- Price
- Free, no paid tier. Compare plans
Key facts
- Scores any README out of 100 with fixed rules and no AI model, so the same README always gets the same score
- Every finding links the exact line and gives a concrete fix: the heading to add, the command to move, the link to correct
- Free web app, JSON API, score badge and MCP tool, none needing a key
Pros
- Deterministic: the same README always gets the same score
- Each miss names the line to change and how to fix it
- No signup or API key: web app, JSON API, badge and MCP tool
Cons
- Static checks only: it does not run the setup commands to prove they work
- Reads public GitHub repositories or pasted text only, not private repos
What is README Score?
Enter a GitHub repo or paste a README: a score out of 100, the sections found and missing, and a fix for each miss. No AI: same README, same score.
Available on: Web
Preview
Key Features
- Scores README files out of 100
- Lists sections found and missing
- Provides a fix for each finding with a line reference
- Detects CLI, library, full-stack app, and backend API projects
- Checks readability, quickstart instructions, and links
Pricing
Free
README Score is completely free to use with no hidden costs.
Is README Score worth the price?
Good value
This tool currently offers no paid tiers, meaning it is effectively free.
That is an excellent deal for individual developers or small teams who need automated README checks without any budget. It is best for users who want immediate, no-cost value.
Reviews

$99 Free with your review
Write the first review Write the first README Score review, get a free AI guide
Share your experience and we will send you Improve Your Thinking Patterns Using ChatGPT, free.
Explore More
README Score FAQ
How does README Score help a developer improve a GitHub repository's README?
You can enter a GitHub repository or paste a README directly, and README Score returns a score out of 100, a list of sections found, a list of missing sections, and a fix for each missing section. This gives you a concrete checklist of documentation gaps and actionable next steps.
Which limitation should a user keep in mind when relying on README Score?
README Score does not use AI, so it evaluates the presence of expected sections rather than the nuance, tone, or subjective quality of the writing. Because the scoring is deterministic, the same README always receives the same score, which is useful for tracking changes but may not capture every factor a human reviewer would notice.
What kind of user benefits most from README Score?
Developers and documentation-focused teams who maintain GitHub repositories benefit most, because README Score turns README improvement into a simple checklist of missing sections with suggested fixes. It is especially helpful for users who want a fast, objective, and repeatable documentation review without relying on an AI-generated opinion.
How is README Score priced?
README Score is free to use, and no paid plan is required. There are no subscription tiers or hidden costs for accessing the scoring and fix suggestions.
Can README Score analyze a README without linking a GitHub repo?
Yes, you can paste a README directly into README Score, or you can enter a GitHub repository to have it analyzed. This makes it easy to check a draft README before committing it to a repository.
Does README Score provide actionable guidance for missing sections?
Yes, README Score identifies which expected sections are present and which are missing, and it provides a fix for every missing section. This turns the score into a direct improvement plan rather than just a rating.
Why does README Score give the same README the same score every time?
README Score intentionally does not use AI, so its scoring logic is fully deterministic. Given the same README input, it will always produce the same score, the same list of found and missing sections, and the same suggested fixes, making the results consistent and reproducible.
Source: readme.flisk.si