Detect Hono in any GitHub repo

Hono is a small, fast web framework built on Web Standards that runs on Cloudflare Workers, Deno, Bun, Node and other edge runtimes.

Why show Hono on your README

Hono apps usually target a specific runtime; the card shows Hono together with Bun, Deno or Cloudflare when they're present.

How Hono is detected

Stack Fingerprint reads the repo's full file tree in one GitHub API call and flags Hono when it finds any of these:

  • Files or folders: hono.config.ts, hono.config.js
  • Dependencies in package.json: hono

Hono README badge

A static badge you can paste anywhere in Markdown:

Hono badge

Markdown
![Hono](https://img.shields.io/badge/Hono-E36002?style=for-the-badge&logo=hono&logoColor=white)

Or let the repo describe itself

Static badges go stale the moment you swap a dependency. A Stack Fingerprint card is generated from the repo, so Hono (and everything around it) appears or disappears on its own:

Tech stack card for honojs/hono
honojs/hono · generated live from the repo
README.md
[![Stack Fingerprint](https://stackfingerprint.vercel.app/api/card?repo=OWNER/REPO)](https://stackfingerprint.vercel.app/?repo=OWNER/REPO)

Replace OWNER/REPO with your repository, or open the builder to pick a theme and layout.