Detect Bun in any GitHub repo

Bun is an all-in-one JavaScript runtime, bundler, test runner and package manager focused on speed.

Why show Bun on your README

Bun can be used as just a package manager or as the full runtime; the card distinguishes the two from the lockfile and config.

How Bun is detected

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

  • Files or folders: bunfig.toml

Bun README badge

A static badge you can paste anywhere in Markdown:

Bun badge

Markdown
![Bun](https://img.shields.io/badge/Bun-14151A?style=for-the-badge&logo=bun&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 Bun (and everything around it) appears or disappears on its own:

Tech stack card for oven-sh/bun
oven-sh/bun · 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.