ESLint
25,000Pluggable JavaScript/TypeScript linter and code-quality enforcer.
Maturity tier details
Computed tier: 2A(raw score 5.26). Effective tier: 2A.
Facets:documented_in=0evaluated_on=0integration_surfaces=1.5paper_citations=0recent_commit=2stars=1.76
Source of truth:pipeline/maturity/score.py
Description
ESLint is the canonical JavaScript and TypeScript linter: it parses source to an AST and runs configurable rule plugins covering logic bugs (unused vars, unreachable code, mistaken equality), style consistency (scope_creep on review), and a growing set of security rules (eslint-plugin-security, no-eval). It runs from the CLI, in pre-commit, in CI, and as a language-server in editors. Configuration lives in `eslint.config.js` or `package.json` `eslintConfig`, which the audit detector now recognises.
Why it's included
Occupies detection × post_generation × fully_autonomous for logic_error, scope_creep, and security_vulnerability in the JS/TS lane. Mature workhorse; missing it leaves the audit detector unable to recognise the single most common JavaScript linting gate present in nearly every modern Node project.
Security notes
Standard dev-tool security posture; ESLint executes plugin code loaded from `node_modules`, so a malicious lint plugin can run with developer privileges — pin plugin versions and prefer audited configurations (e.g. `eslint:recommended`, `@typescript-eslint`).
Addresses failure modes
- Logic error — Correct API use, incorrect logic.
- Scope creep — Actions outside declared task boundary.
- Security vulnerability — Insecure patterns, injection flaws, weak cryptography, secret leakage.