01 / Technologies / Linting

Detect ESLint in any GitHub repo

ESLint is the pluggable linter for JavaScript and TypeScript, enforcing code quality and style rules.

Why show ESLint on your README

Linters are flagged as dev-only, so the `prodonly` filter hides them while the `devtools` filter puts them front and centre.

How ESLint is detected

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

  • Files or folders: /^\.eslintrc/, eslint.config.js, eslint.config.mjs, eslint.config.cjs, eslint.config.ts
  • Dependencies in package.json: eslint

ESLint README badge

A static badge you can paste anywhere in Markdown:

ESLint badge

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

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