I built a tool that turns any GitHub repo into a tech‑stack card - Discover Stack Fingerprint

Description and use

The tool automatically generates a tech‑stack card for any GitHub repository, eliminating manual badge updates and enhancing security by embedding all icons in a self‑contained SVG.

Problem

README badges become stale and require manual updates, making it hard to reflect the current tech stack of a repository.

Outcome

The tool automatically generates an up‑to‑date tech‑stack card for any GitHub repository, eliminating manual badge maintenance, reducing supply‑chain risk, and providing customizable filtering and monorepo support.

Workflow

• 1. Point the tool at a repo via the API URL or embed the Markdown snippet in the README.
• 2. The scanner makes a single GitHub Git Trees API call with recursive=1 to retrieve the entire file tree.
• 3. Run two detection passes: file signals (regex on file paths) and manifest signals (parse package.json, pyproject.toml, Gemfile, composer.json).
• 4. Map detected dependencies to technology signals, tagging dev‑only dependencies.
• 5. Generate a self‑contained SVG card with base64‑encoded icons from simple‑icons, avoiding external image requests.
• 6. Optionally use the web builder to preview and customize themes, layouts, sizes, and icon styles.
• 7. Optionally add a .stackfingerprint.json config file to ignore, pin, or relabel technologies and target a sub‑directory in monorepos.
• 8. Optionally deploy a GitHub Action that generates the SVG on every push and commits it to the repo, eliminating runtime dependency on the author’s server.

Evidence

Every README has the same section: a wall of hand‑picked shields.io badges, half of them out of date.

Source

The scanner makes one call to the GitHub Git Trees API with recursive=1, which returns the entire file tree flattened.

Source

It also remembers where each dependency came from. Anything that only shows up in devDependencies gets tagged as dev‑only.

Source

The SVG must be fully self‑contained.

Source

Drop a .stackfingerprint.json in your repo for full control.

Source