01 / Technologies / Linting

Detect commitlint in any GitHub repo

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

How commitlint is detected

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

  • Files or folders: /^commitlint\.config\.(js|ts|cjs|mjs)$/, .commitlintrc

commitlint README badge

A static badge you can paste anywhere in Markdown:

commitlint badge

Markdown
![commitlint](https://img.shields.io/badge/commitlint-000000?style=for-the-badge&logo=commitlint&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 commitlint (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.