59/100

Grade D

honojs/hono at ed1d5f7 (main) · README.md
13 checks pass, 10 fail, 5 not checked · 48.6 of 83 points

Scored as CLI tool ·Library ·Full-stack app ·Backend API

Type chosen on this page.

Fix first

FailPrerequisites0/4.2

missing · limit: required for a backend API · line 48
Fix: Add "## Prerequisites" at line 48, before "Documentation". What to install first, with versions (Node.js 22+, Docker), and a command that checks each one.
```
## Prerequisites

What to install first, with versions (Node.js 22+, Docker), and a command that checks each one.
```
FailUsage or commands0/4.2

missing · limit: required for a backend API · line 40
Fix: Add "## Usage" at line 40, before "Features". The commands or calls people use most, each with a one-line example and what it prints.
```
## Usage

The commands or calls people use most, each with a one-line example and what it prints.
```
FailConfiguration0/4.2

missing · limit: required for a backend API · line 40
Fix: Add "## Configuration" at line 40, before "Features". Every setting in a table: name, default, what it changes. Environment variables and config files both.
```
## Configuration

Every setting in a table: name, default, what it changes. Environment variables and config files both.
```
FailTitle near the top0/4

none · limit: within 5 non-empty lines
Fix: Add a title as the first line: "# hono: what it does, in one line".
FailBadges before the first code block0/4

11 · limit: at most 6 · line 9
Fix: Drop 5 of the 11 badges on lines 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, or move them below the first code block.

Sections 12.6/35

FailOverview0/2.8

missing · limit: recommended for a backend API · line 34
Fix: Add "## What is hono?" at line 34, before "Quick Start". Two or three sentences: what hono does, who it is for, and what it replaces.
```
## What is hono?

Two or three sentences: what hono does, who it is for, and what it replaces.
```
PassKey features1.4/1.4

"Features" · limit: nice to have for a backend API · line 40
FailPrerequisites0/4.2

missing · limit: required for a backend API · line 48
Fix: Add "## Prerequisites" at line 48, before "Documentation". What to install first, with versions (Node.js 22+, Docker), and a command that checks each one.
```
## Prerequisites

What to install first, with versions (Node.js 22+, Docker), and a command that checks each one.
```
PassInstallation4.2/4.2

"Quick Start" · limit: required for a backend API · line 34
FailUsage or commands0/4.2

missing · limit: required for a backend API · line 40
Fix: Add "## Usage" at line 40, before "Features". The commands or calls people use most, each with a one-line example and what it prints.
```
## Usage

The commands or calls people use most, each with a one-line example and what it prints.
```
FailConfiguration0/4.2

missing · limit: required for a backend API · line 40
Fix: Add "## Configuration" at line 40, before "Features". Every setting in a table: name, default, what it changes. Environment variables and config files both.
```
## Configuration

Every setting in a table: name, default, what it changes. Environment variables and config files both.
```
FailExamples0/2.8

missing · limit: recommended for a backend API · line 40
Fix: Add "## Examples" at line 40, before "Features". Two or three complete examples a reader can copy and run, or links to them.
```
## Examples

Two or three complete examples a reader can copy and run, or links to them.
```
FailTroubleshooting0/2.8

missing · limit: recommended for a backend API · line 40
Fix: Add "## Troubleshooting" at line 40, before "Features". The three errors people hit most, each with the message they see and the fix.
```
## Troubleshooting

The three errors people hit most, each with the message they see and the fix.
```
FailRoadmap0/1.4

missing · limit: nice to have for a backend API · line 40
Fix: Add "## Roadmap" at line 40, before "Features". What is planned next and what is out of scope, or a link to the issues or project board that tracks it.
```
## Roadmap

What is planned next and what is out of scope, or a link to the issues or project board that tracks it.
```
PassContributing2.8/2.8

"Contributing" · limit: recommended for a backend API · line 60
PassLicense4.2/4.2

"License" · limit: required for a backend API · line 82

First screen 12/20

FailTitle near the top0/4

none · limit: within 5 non-empty lines
Fix: Add a title as the first line: "# hono: what it does, in one line".
PassInstall command4/4

line 37 · limit: within 40 lines · line 37
PassPicture of it working4/4

line 3 · limit: within 20 lines; badges do not count · line 3
FailBadges before the first code block0/4

11 · limit: at most 6 · line 9
Fix: Drop 5 of the 11 badges on lines 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, or move them below the first code block.
PassWords before the first code block4/4

40 · limit: at most 250 · line 25

Readability 6/10

FailFlesch reading ease6/10

48.1 (0% infrastructure words) · limit: 60+ for full points, 30 or below for none
Fix: Shorter sentences and shorter words raise it.

Quickstart 5/5

PassQuickstart block2/2

line 37 · limit: a shell block that installs the project · line 37
PassCommands in the quickstart3/3

1 command · limit: at most 6; a && b is two · line 37
- line 37: npm create hono@latest
Not checkedTranslations give the same commands–

no translated READMEs · limit: 0; folder names may be translated

Links 5/5

PassRelative links resolve5/5

0 of 3 links broken · limit: 0 broken; 1 point off for each
Not checked#anchors match a heading–

no #anchors · limit: 0 broken; 1 point off for each
Fix: Change each anchor listed to a heading's anchor (lower case, spaces as hyphens, punctuation dropped).

Tagline 3/3

PassOne tagline everywhere3/3

1 wording across 2 sources · limit: 1; points by wordings: 3, 1.5, 0
- README.md H1: (none)
- package.json:4: A: package.json description: "Web framework built on Web Standards"
- A: GitHub About description: "Web framework built on Web Standards"
Not checkedOne spelling of the name–

the README has no H1 to take the name from · limit: the H1's spelling

Website: https://hono.dev/ 5/5

Not checkedWebsite headline matches the README–

the README has no H1 · limit: the README H1's wording
Fix: Use one headline: the README H1 says "", the website says "Hono - Web framework built on Web Standards". Change one to the other's wording (the website's <title> and og:title, or the H1).
- <title>: "Hono - Web framework built on Web Standards"
- <h1>: "Hono Web application framework"
PassWebsite description matches the README pitch3/3

93% of the website's key words · limit: 50% of the website's key words · line 21
- Website description: "Web framework built on Web Standards for Cloudflare Workers, Fastly Compute, Deno, Bun, Vercel, Node.js, and others. Fast, but not only fast."
- Only on the website: other
- line 21: Only in the README pitch: mean, flame, japanese, small, simple, ultrafast, work, javascript, runtime, aws, lambda, edge
Not checkedWebsite leads with the README's command–

the README shows no command · limit: the first <name> command the README's quickstart runs · line 37
Fix: Lead with one command in both places: the README's quickstart starts with , the website's first command is import {. Put the same first step first on both, or say on each why there are two ways in.
PassWebsite shows the README's install command2/2

both: npm create hono@latest · limit: the README's first install command · line 37

Badge, API and MCP

[![README score](https://readme.flisk.si/badge/honojs/hono.svg)](https://readme.flisk.si/honojs/hono)
curl 'https://readme.flisk.si/api/score?repo=honojs/hono'
claude mcp add --transport http readme-score https://readme.flisk.si/mcp

Score another

Or paste a README