ESLint
27,642Pluggable JavaScript/TypeScript linter and code-quality enforcer.
Activity band details
Activity band A to F: a bin of a score that adds GitHub stars (log scale), a push to the upstream repository in the 12 months before `as_of`, the number of declared integration surfaces and, where the catalogue records them, citing papers and benchmark evaluations. It measures popularity and activity. It is not a level of evidence: no band means a paper cites the tool or that it was measured. Recency is judged as of 2026-11-22.
Computed band: C
(raw score 5.28).
Shown band: C
.
Facets:
documented_in=0evaluated_on=0integration_surfaces=1.5paper_citations=0recent_push=2stars=1.78
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, 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 in the JS/TS lane. Tag basis (2026-11-20 tag audit, research/fm_tag_audit/final_table.csv): logic_error from the core 'possible problems' rules such as no-unreachable; security_vulnerability from no-eval and related rules (wider coverage needs third-party plugins); fabrication from no-undef, which flags names that do not exist; incomplete_execution from no-warning-comments, which flags TODO / FIXME and is off by default. The audit removed scope_creep: a linter has no notion of a task boundary. 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
These tags are the catalog's claim about what ESLint is built to catch or prevent. A tag is not a test result. SAICA-Bench has not measured ESLint, so none of these tags is tested here.
- Logic error — Correct API use, incorrect logic.
- Security vulnerability — Insecure patterns, injection flaws, weak cryptography, secret leakage.
- Fabrication — Generating reference to non-existent APIs, packages, or symbols.
- Incomplete execution — Agent claims completion while subtasks are skipped, stubbed, or silently dropped.