Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 02:14 UTC

eslint / js

Monorepo for the JS language tools.

JavaScriptBSD-2-Clause★ 2,387 stars⑂ 235 forkssince Dec 2014View on GitHub ↗

eslint/js holds a health index of 93 out of 100, placing it in the Exceptional band. It scores highest on Community & Adoption (91/100) and lowest on AI Readiness (54/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.

93
overall / 100
Exceptional

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

93
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 79 is calibrated to 93 on the published index scale (record calibration 2026-08-02).

Ownership

ESLintOrganization · verified domain
1,029 followers37 public repossince Nov 2013

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmespree11.2.0712,878,482103228 days agoastecmascriptjavascriptparsersyntaxacorn
npmeslint-scope9.1.2873,899,97430228 days agoeslint
npmeslint-visitor-keys5.0.11,672,756,07021242 days agoeslint

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

89Excellent · 21% of overall
How it's scored
36/36Push recency — last push 3 days ago
32.5/36Commit cadence — 47/52 weeks with commits
18/18Commit volume — 120 commits in the last year
10/10OpenSSF Scorecard: Maintained — 24 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year120
human_commit_share0.77
days_since_last_push3
active_weeks_last_year47
How it's scored
27/27Ships releases — 100 releases published
16.2/36Release recency — latest release 228 days ago
27/27Release cadence — a release every ~12.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tageslint-scope-v9.1.2
releases_from_tagsno
days_since_latest_release228
mean_days_between_releases12.9
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

91Excellent · 17% of overall
How it's scored
54.8/60Stars — 2,387 stars
19.7/25Forks — 235 forks
9.4/15Watchers — 51 watchers
Inputs used
forks235
stars2,387
watchers51
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (BSD-2-Clause)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesopencollective.com
has_pull_request_templateyes
How it's scored
80/80Monthly downloads — 3,259,534,526 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesespree, eslint-scope, eslint-visitor-keys
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads3,259,534,526
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

75Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
10.3/22.5Commit distribution — top contributor authored 54% of commits
13.5/13.5Contributor breadth — 62 contributors
10/10OpenSSF Scorecard: Contributors — project has 44 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled62
top_contributor_share0.542
How it's scored
41/42Issue resolution — 98% of issues closed
26.7/30PR acceptance — 408/458 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-Review — Found 5/18 approved changesets -- score normalized to 2
Inputs used
merged_prs408
open_issues7
closed_issues300
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.977
closed_unmerged_prs50
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
21.7/25Owner reach — 1,029 followers of eslint
23.5/25Track record — 37 public repos, account ~12 yr old
Inputs used
followers1,029
owner_typeOrganization
is_verifiedyes
owner_logineslint
public_repos37
account_age_days4,714
How it's scored
25/25Published & resolvable — 3 package(s) on npm
26/35Publish recency — latest publish 228 days ago
20/20Version history — 103 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesespree, eslint-scope, eslint-visitor-keys
ecosystemsnpm
any_deprecatedno
min_days_since_publish228

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.js
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 17 out of 17 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

78Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 17 out of 17 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-Review — Found 5/18 approved changesets -- score normalized to 2
2.5/2.5Contributors — project has 44 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 24 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate7.2
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages3
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:espree@11.2.0 runtime dependency closure — what installing the published package pulls in — 3 packages. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

54Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 77 of 77 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.js
11/11Static type checking — packages/eslint-scope/tests/types/tsconfig.json, packages/eslint-scope/tsconfig.json, packages/eslint-visitor-keys/tsconfig.json, packages/espree/tsconfig.json
0/10Reproducible environment
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 23 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configspackages/eslint-scope/tests/types/tsconfig.json, packages/eslint-scope/tsconfig.json, packages/eslint-visitor-keys/tsconfig.json, packages/espree/tsconfig.json
agent_commit_share0.01
toolchain_manifests—
dependency_bot_commit_share0.23
How it's scored
27/45Type-checkable code — JavaScript with type-check config (packages/eslint-scope/tests/types/tsconfig.json, packages/eslint-scope/tsconfig.json, packages/eslint-visitor-keys/tsconfig.json, packages/espree/tsconfig.json)
54.6/55Manageable file sizes — 14/1,920 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes718,772
source_files_sampled1,920
oversized_source_files14

Key facts

2,387GitHub stars
62contributors
120commits, last 12 months
3days since last push
100releases
1bus factor
7open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 235 ⇿
0Stars
235Forks
100Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

0408012016020024022852014-122020-112026-10
Major 9Minor 20Patch 42

Each point covers 11 days.

OpenSSF Scorecard 7.2 / 10
7.2aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-10-21 02:14 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests17 out of 17 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 5/18 approved changesets -- score normalized to 2
10Contributorsproject has 44 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained24 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
npm@types/esrecurse^4.3.1packages/eslint-scope/package.json
npm@types/estree^1.0.8packages/eslint-scope/package.json
npmesrecurse^4.3.0packages/eslint-scope/package.json
npmestraverse^5.2.0packages/eslint-scope/package.json
npmacorn^8.16.0packages/espree/package.json
npmacorn-jsx^5.3.2packages/espree/package.json
npmeslint-visitor-keys^5.0.1packages/espree/package.json
All dependencies 29

Full resolved dependency set from the GitHub dependency graph: 7 direct and 22 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
npm@types/esrecurse^4.3.1direct
npm@types/estree^1.0.8direct
npmacorn^8.16.0direct
npmacorn-jsx^5.3.2direct
npmeslint-visitor-keys^5.0.1direct
npmesrecurse^4.3.0direct
npmestraverse^5.2.0direct
npm@arethetypeswrong/cli^0.18.3indirect
npm@types/node^20.19.0indirect
npm@typescript-eslint/parser^8.60.1indirect
npmc8^12.0.0indirect
npmchai^6.0.0indirect
npmeslint^10.4.0indirect
npmeslint-config-eslint^14.0.0indirect
npmeslint-plugin-chai-friendly^1.0.0indirect
npmeslint-plugin-expect-type^0.7.0indirect
npmespree^11.2.0indirect
npmglobals^17.0.0indirect
npmknip^6.11.0indirect
npmlint-staged^16.0.0indirect
npmmocha^12.0.0indirect
npmnpm-license^0.3.3indirect
npmprettier3.9.10indirect
npmrollup^4.55.2indirect
npmrollup-plugin-dts^6.4.1indirect
npmshelljs^0.10.0indirect
npmtsd^0.33.0indirect
npmtypescript^6.0.3indirect
npmyorkie^2.0.0indirect
Dependency advisories 0

Installing npm:espree@11.2.0 pulls in 3 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.