01 / Technologies / Testing

Detect k6 in any GitHub repo

k6 is one of the testing technologies Stack Fingerprint recognises automatically when it scans a public repository.

How k6 is detected

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

  • Files or folders: /^k6\.config\.(js|ts)$/, k6.js

k6 README badge

A static badge you can paste anywhere in Markdown:

k6 badge

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

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.