01 / Technologies / Runtime

Detect Deno in any GitHub repo

Deno is a secure-by-default JavaScript and TypeScript runtime with built-in tooling, npm compatibility and a standard library.

Why show Deno on your README

Deno projects look different (deno.json, no node_modules), so flagging the runtime saves contributors a confused first `npm install`.

How Deno is detected

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

  • Files or folders: deno.json, deno.jsonc, deno.lock

Deno README badge

A static badge you can paste anywhere in Markdown:

Deno badge

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

Tech stack card for denoland/fresh
denoland/fresh · 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.