This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
README Score
Score your README out of 100, with a fix for every miss
Paste a GitHub repo or a README. Get a score out of 100, the sections found and missing, and a fix for each miss, down to the line. 28 fixed rules, no AI: the same README always gets the same score. Free, no signup. API, badge and MCP server included.
I built README Score because READMEs get judged by gut feeling. A README is the first thing anyone reads, yet nobody tells you what’s missing.
How it works: paste a GitHub repo or a README. 28 fixed rules (sections for your kind of project, the first screen, readability, quickstart, links, and whether your website says the same thing) give a score out of 100. Every finding names the line and gives a fix you can paste in. There’s no AI anywhere, so the same README always gets the same score. Every threshold is public on the checks page.
It’s free, has no signup and stores nothing. There’s an API, an SVG badge, and an MCP server for Claude, Cursor or Codex. The code is on GitHub: https://github.com/flisk-sh/readme-score
Flisk’s own README scores 90 and still has five misses, so the tool isn’t flattering anyone.
What would make it more useful for you?
About README Score on Product Hunt
“Score your README out of 100, with a fix for every miss”
README Score was submitted on Product Hunt and earned 2 upvotes and 1 comments, placing #157 on the daily leaderboard. Paste a GitHub repo or a README. Get a score out of 100, the sections found and missing, and a fix for each miss, down to the line. 28 fixed rules, no AI: the same README always gets the same score. Free, no signup. API, badge and MCP server included.
On the analytics side, README Score competes within Open Source, Developer Tools and GitHub — topics that collectively have 633.7k followers on Product Hunt. The dashboard above tracks how README Score performed against the three products that launched closest to it on the same day.
Who hunted README Score?
README Score was hunted by Oleksandr Dykyi. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of README Score including community comment highlights and product details, visit the product overview.
Hi, I’m Oleksandr, one of the makers of Flisk.
I built README Score because READMEs get judged by gut feeling. A README is the first thing anyone reads, yet nobody tells you what’s missing.
How it works: paste a GitHub repo or a README. 28 fixed rules (sections for your kind of project, the first screen, readability, quickstart, links, and whether your website says the same thing) give a score out of 100. Every finding names the line and gives a fix you can paste in. There’s no AI anywhere, so the same README always gets the same score. Every threshold is public on the checks page.
It’s free, has no signup and stores nothing. There’s an API, an SVG badge, and an MCP server for Claude, Cursor or Codex. The code is on GitHub: https://github.com/flisk-sh/readme-score
Flisk’s own README scores 90 and still has five misses, so the tool isn’t flattering anyone.
What would make it more useful for you?