Static badges go stale the moment you swap a dependency. A Stack Fingerprint card is generated from the repo, so TypeScript (and everything around it) appears or disappears on its own:
microsoft/TypeScript · generated live from the repo
Inside the scanner: one recursive Git Trees request, file signals, dependency signals, dev-only tagging, and why every icon has to be inlined as a data URI for GitHub to render it.
Three ways to show what your project is built with: hand-made shields.io badges, a live auto-detected stack card, or a card committed by a GitHub Action. Pros, cons and copy-paste snippets.