What would make a README score useful to you?

by•

I'm Oleksandr, one of the makers of README Score.

It reads a GitHub repo or a pasted README and gives a score out of 100, with a fix for every miss, down to the line. There are 28 fixed rules and no AI, so the same README always gets the same score. Every threshold is public:

Flisk's own README scores 90, and it still has five misses. Try it on a repo you know and tell me where the score is wrong.

Three things I'd like to hear:

1. Which check felt unfair or wrong for your project?

2. Which check is missing?

3. Would you rather see this as a badge in your README, a CI check, or an MCP tool inside your editor?

8 views

Add a comment

Replies

Be the first to reply

Have a question or a thought to share? Add a comment above to start the conversation.