Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-09 02:55 UTC

eslint-community / eslint-plugin-eslint-plugin

An ESLint plugin for linting ESLint plugins

TypeScriptMIT★ 235 stars⑂ 38 forkssince Dec 2016View on GitHub ↗

eslint-community/eslint-plugin-eslint-plugin holds a health index of 92 out of 100, placing it in the Excellent band. It scores highest on Vitality (87/100) and lowest on AI Readiness (65/100). It was last updated 1 day ago. 2 contributors account for most of its recent work.

overall / 100

Excellent

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.

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)

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 78 is calibrated to 92 on the published index scale (record calibration 2026-08-02).

Ownership

ESLint CommunityOrganization

197 followers16 public repossince Nov 2021

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

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish	Tags
npm	eslint-plugin-eslint-plugin	7.6.2	1,627,799	93	23 days ago	eslint eslintplugin eslint-plugin

Metrics by category

Vitality

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

87Excellent · 21% of overall

Development activity

79Good

How it's scored

36/36	Push recency — last push 1 days ago
15.9/36	Commit cadence — 23/52 weeks with commits
17.2/18	Commit volume — 82 commits in the last year
10/10	OpenSSF Scorecard: Maintained — 24 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10

Inputs used

commits_last_year	82
human_commit_share	0.51
days_since_last_push	1
active_weeks_last_year	23

Release discipline

100Exceptional

How it's scored

27/27	Ships releases — 53 releases published
36/36	Release recency — latest release 23 days ago
27/27	Release cadence — a release every ~20.4 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	53
latest_release_tag	v7.6.2
releases_from_tags	no
days_since_latest_release	23
mean_days_between_releases	20.4

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?

72Good · 17% of overall

Popularity & adoption

55Moderate

How it's scored

38.4/60	Stars — 235 stars
13.1/25	Forks — 38 forks
3.3/15	Watchers — 5 watchers

Inputs used

forks	38
stars	235
watchers	5
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

72Good

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (MIT)
0/18	CONTRIBUTING guide
13.5/13.5	Code of conduct
0/7.2	Issue template
6.3/6.3	PR template

Inputs used

has_readme	yes
has_license	yes
readme_badges	3
has_contributing	no
has_issue_template	no
has_code_of_conduct	yes
readme_badge_services	github.com, shields.io
has_pull_request_template	yes

Ecosystem adoption (downloads)

100Exceptional

How it's scored

80/80	Monthly downloads — 1,627,799 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	eslint-plugin-eslint-plugin
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	1,627,799
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?

77Good · 23% of overall

Maintainer resilience (bus factor)

64Moderate

How it's scored

25.2/54	Bus factor — 2 contributor(s) cover half of all commits
15.2/22.5	Commit distribution — top contributor authored 32% of commits
13.5/13.5	Contributor breadth — 32 contributors
10/10	OpenSSF Scorecard: Contributors — project has 31 contributing companies or organizations

Inputs used

bus_factor	2
contributors_sampled	32
top_contributor_share	0.323

Issue & PR responsiveness

85Excellent

How it's scored

35.2/42	Issue resolution — 84% of issues closed
24.1/30	PR acceptance — 395/492 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15	OpenSSF Scorecard: Code-Review — all changesets reviewed

Inputs used

merged_prs	395
open_issues	26
closed_issues	134
prs_merged_7d	1
prs_decided_7d	1
prs_merged_30d	3
prs_decided_30d	3
issue_closed_ratio	0.838
closed_unmerged_prs	97
first_time_authors_30d	0
first_time_prs_merged_30d	0
first_time_prs_decided_30d	0

Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

65Good

How it's scored

30/30	Ownership backing — organization-owned
0/20	Verified domain
16.5/25	Owner reach — 197 followers of eslint-community
18.6/25	Track record — 16 public repos, account ~4 yr old

Inputs used

followers	197
owner_type	Organization
is_verified	no
owner_login	eslint-community
public_repos	16
account_age_days	1,756

Package maintenance

100Exceptional

How it's scored

25/25	Published & resolvable — 1 package(s) on npm
35/35	Publish recency — latest publish 23 days ago
20/20	Version history — 93 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	eslint-plugin-eslint-plugin
ecosystems	npm
any_deprecated	no
min_days_since_publish	23

Engineering Quality

Are baseline engineering and documentation practices in place?

79Good · 19% of overall

Engineering practices

82Excellent

How it's scored

24/24	CI workflows — 2 workflow(s)
24/24	Tests present
16/16	Linter config — eslint.config.js
0/9.6	Pre-commit hooks
0/6.4	.editorconfig
18/20	OpenSSF Scorecard: CI-Tests — 27 out of 30 merged PRs checked by a CI test -- score normalized to 9

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	no
has_linter_config	yes
has_precommit_config	no

Documentation

75Good

How it's scored

30/30	README
25/25	Documentation directory
0/15	Documentation / homepage site
10/10	Repository description
10/10	Topics — 2 topics
0/10	Wiki

Inputs used

topics	eslint-plugin, eslint
has_wiki	no
homepage	—
docs_site	—
has_readme	yes
has_docs_dir	yes
has_description	yes

Security

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

74Good · 16% of overall

Security posture

67Good

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
0/7.5	Branch-Protection — no data
2.2/2.5	CI-Tests — 27 out of 30 merged PRs checked by a CI test -- score normalized to 9
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
7.5/7.5	Code-Review — all changesets reviewed
2.5/2.5	Contributors — project has 31 contributing companies or organizations
10/10	Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5	Dependency-Update-Tool — update tool detected
0/5	Fuzzing — project is not fuzzed
2.5/2.5	License — license file detected
7.5/7.5	Maintained — 24 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
5/5	Packaging — packaging workflow detected
0/5	Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
3/5	SAST — SAST tool is not run on all commits -- score normalized to 6
5/5	Security-Policy — security policy file detected
0/7.5	Signed-Releases — no data
0/7.5	Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5	Vulnerabilities — 16 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	16
scorecard_version	v5.5.0
checks_inconclusive	2
scorecard_aggregate	6.7

Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional

How it's scored

35/35	Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25	Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40	No advisories left outstanding — no advisory carries a publication date

Inputs used

source	osv
advisories	0
affected_packages	0
assessed_packages	3
unassessed_packages	0
affected_by_severity	none
direct_affected_packages	0

Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:eslint-plugin-eslint-plugin@7.6.2 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.

65Good · 4% of overall

Agent context & guidance

40Weak

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15	Machine-readable docs (llms.txt)
40/40	Legible commit history — 50 of 51 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.98
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

70Good

How it's scored

0/18	One-command bootstrap
22/22	Automated tests
11/11	Lint / format config — eslint.config.js
11/11	Static type checking — e2e/fixtures/all-typed-config/tsconfig.json, tests/lib/fixtures/tsconfig.json, tsconfig.json
10/10	Reproducible environment — lockfile
8/10	Demonstrated agent practice — 4 of the last 100 commits agent-authored or agent-credited
8/8	Automated maintenance — 35 of the last 100 commits are automated dependency updates
0/10	OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0

Inputs used

has_nix	no
has_tests	yes
lockfiles	package-lock.json
has_dockerfile	no
typed_language	yes
bootstrap_files	—
has_devcontainer	no
has_linter_config	yes
typecheck_configs	e2e/fixtures/all-typed-config/tsconfig.json, tests/lib/fixtures/tsconfig.json, tsconfig.json
agent_commit_share	0.04
toolchain_manifests	—
dependency_bot_commit_share	0.35

Code legibility for models

100Exceptional

How it's scored

45/45	Type-checkable code — TypeScript (statically typed)
54.5/55	Manageable file sizes — 1/104 source files over 60KB

Inputs used

primary_language	TypeScript
largest_source_bytes	109,523
source_files_sampled	104
oversized_source_files	1

Key facts

235GitHub stars

32contributors

82commits, last 12 months

1days since last push

53releases

2bus factor

26open 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 ★ / 38 ⇿

0Stars

38Forks

49Releases

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.

Major 4Minor 18Patch 23

Each point covers 9 days.

OpenSSF Scorecard 6.7 / 10

6.7aggregate

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-09-09 02:54 UTC

10	Binary-Artifacts	no binaries found in the repo
n/a	Branch-Protection	internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
9	CI-Tests	27 out of 30 merged PRs checked by a CI test -- score normalized to 9
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
10	Code-Review	all changesets reviewed
10	Contributors	project has 31 contributing companies or organizations
10	Dangerous-Workflow	no dangerous workflow patterns detected
10	Dependency-Update-Tool	update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
10	Maintained	24 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
10	Packaging	packaging workflow detected
0	Pinned-Dependencies	dependency not pinned by hash detected -- score normalized to 0
6	SAST	SAST tool is not run on all commits -- score normalized to 6
10	Security-Policy	security policy file detected
n/a	Signed-Releases	no releases found
0	Token-Permissions	detected GitHub workflow tokens with excessive permissions
0	Vulnerabilities	16 existing vulnerabilities detected

Direct dependencies 2

Registry	Package	Version constraint	Manifest
npm	@eslint-community/eslint-utils	`^4.4.0`	package.json
npm	estraverse	`^5.3.0`	package.json

All dependencies 129

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

Registry	Package	Version	Relation
npm	@eslint-community/eslint-utils	`4.7.0`	direct
npm	@eslint-community/eslint-utils	`^4.4.0`	direct
npm	estraverse	`5.3.0`	direct
npm	estraverse	`^5.3.0`	direct
npm	..	`7.0.0`	indirect
npm	@commitlint/cli	`^20.0.0`	indirect
npm	@commitlint/config-conventional	`^20.0.0`	indirect
npm	@commitlint/types	`^20.0.0`	indirect
npm	@eslint-community/eslint-plugin-eslint-comments	`^4.6.0`	indirect
npm	@eslint-community/regexpp	`4.12.1`	indirect
npm	@eslint/config-array	`0.21.0`	indirect
npm	@eslint/config-helpers	`0.3.1`	indirect
npm	@eslint/core	`0.15.2`	indirect
npm	@eslint/eslintrc	`3.3.1`	indirect
npm	@eslint/eslintrc	`^3.3.5`	indirect
npm	@eslint/js	`9.33.0`	indirect
npm	@eslint/js	`^9.39.4`	indirect
npm	@eslint/markdown	`^7.5.1`	indirect
npm	@eslint/object-schema	`2.1.6`	indirect
npm	@eslint/plugin-kit	`0.3.5`	indirect
npm	@humanfs/core	`0.19.1`	indirect
npm	@humanfs/node	`0.16.6`	indirect
npm	@humanwhocodes/module-importer	`1.0.1`	indirect
npm	@humanwhocodes/retry	`0.3.1`	indirect
npm	@humanwhocodes/retry	`0.4.3`	indirect
npm	@types/eslint-scope	`^8.4.0`	indirect
npm	@types/espree	`^10.1.0`	indirect
npm	@types/estraverse	`^5.1.7`	indirect
npm	@types/estree	`1.0.8`	indirect
npm	@types/estree	`^1.0.8`	indirect
npm	@types/json-schema	`7.0.15`	indirect
npm	@types/lodash	`^4.17.18`	indirect
npm	@types/node	`^24.0.0`	indirect
npm	@typescript-eslint/parser	`8.62.0`	indirect
npm	@typescript-eslint/utils	`8.62.0`	indirect
npm	@vitest/coverage-istanbul	`^4.0.0`	indirect
npm	acorn	`8.15.0`	indirect
npm	acorn-jsx	`5.3.2`	indirect
npm	ajv	`6.12.6`	indirect
npm	ansi-styles	`4.3.0`	indirect
npm	argparse	`2.0.1`	indirect
npm	balanced-match	`1.0.2`	indirect
npm	brace-expansion	`1.1.12`	indirect
npm	callsites	`3.1.0`	indirect
npm	chalk	`4.1.2`	indirect
npm	color-convert	`2.0.1`	indirect
npm	color-name	`1.1.4`	indirect
npm	concat-map	`0.0.1`	indirect
npm	cross-spawn	`7.0.6`	indirect
npm	debug	`4.4.1`	indirect
npm	deep-is	`0.1.4`	indirect
npm	escape-string-regexp	`4.0.0`	indirect
npm	eslint	`9.33.0`	indirect
npm	eslint	`^9.33.0`	indirect
npm	eslint	`^9.39.1`	indirect
npm	eslint-config-not-an-aardvark	`^2.1.0`	indirect
npm	eslint-config-prettier	`^10.1.8`	indirect
npm	eslint-doc-generator	`3.7.0`	indirect
npm	eslint-plugin-n	`^17.21.0`	indirect
npm	eslint-plugin-unicorn	`^62.0.0`	indirect
npm	eslint-remote-tester	`^4.0.3`	indirect
npm	eslint-scope	`8.4.0`	indirect
npm	eslint-scope	`^8.4.0`	indirect
npm	eslint-visitor-keys	`3.4.3`	indirect
npm	eslint-visitor-keys	`4.2.1`	indirect
npm	espree	`10.4.0`	indirect
npm	espree	`^11.2.0`	indirect
npm	esquery	`1.6.0`	indirect
npm	esrecurse	`4.3.0`	indirect
npm	esutils	`2.0.3`	indirect
npm	fast-deep-equal	`3.1.3`	indirect
npm	fast-json-stable-stringify	`2.1.0`	indirect
npm	fast-levenshtein	`2.0.6`	indirect
npm	file-entry-cache	`8.0.0`	indirect
npm	find-up	`5.0.0`	indirect
npm	flat-cache	`4.0.1`	indirect
npm	flatted	`3.3.3`	indirect
npm	glob-parent	`6.0.2`	indirect
npm	globals	`14.0.0`	indirect
npm	has-flag	`4.0.0`	indirect
npm	husky	`^9.1.7`	indirect
npm	ignore	`5.3.2`	indirect
npm	import-fresh	`3.3.1`	indirect
npm	imurmurhash	`0.1.4`	indirect
npm	is-extglob	`2.1.1`	indirect
npm	is-glob	`4.0.3`	indirect
npm	isexe	`2.0.0`	indirect
npm	jiti	`2.5.1`	indirect
npm	jiti	`^2.5.1`	indirect
npm	js-yaml	`4.1.0`	indirect
npm	json-buffer	`3.0.1`	indirect
npm	json-schema-traverse	`0.4.1`	indirect
npm	json-stable-stringify-without-jsonify	`1.0.1`	indirect
npm	keyv	`4.5.4`	indirect
npm	levn	`0.4.1`	indirect
npm	lint-staged	`^16.2.7`	indirect
npm	locate-path	`6.0.0`	indirect
npm	lodash	`^4.17.21`	indirect
npm	lodash.merge	`4.6.2`	indirect
npm	markdownlint-cli	`^0.49.0`	indirect
npm	minimatch	`3.1.2`	indirect
npm	ms	`2.1.3`	indirect
npm	natural-compare	`1.4.0`	indirect
npm	npm-package-json-lint	`^9.0.0`	indirect
npm	npm-run-all2	`^8.0.0`	indirect
npm	optionator	`0.9.4`	indirect
npm	p-limit	`3.1.0`	indirect
npm	p-locate	`5.0.0`	indirect
npm	parent-module	`1.0.1`	indirect
npm	path-exists	`4.0.0`	indirect
npm	path-key	`3.1.1`	indirect
npm	prelude-ls	`1.2.1`	indirect
npm	prettier	`3.9.6`	indirect
npm	punycode	`2.3.1`	indirect
npm	resolve-from	`4.0.0`	indirect
npm	shebang-command	`2.0.0`	indirect
npm	shebang-regex	`3.0.0`	indirect
npm	strip-json-comments	`3.1.1`	indirect
npm	supports-color	`7.2.0`	indirect
npm	tsdown	`^0.21.10`	indirect
npm	type-check	`0.4.0`	indirect
npm	typescript	`5.9.2`	indirect
npm	typescript	`^5.9.2`	indirect
npm	typescript-eslint	`8.62.0`	indirect
npm	uri-js	`4.4.1`	indirect
npm	vitest	`^4.0.0`	indirect
npm	which	`2.0.2`	indirect
npm	word-wrap	`1.2.5`	indirect
npm	yocto-queue	`0.1.0`	indirect

Dependency advisories 0

Installing npm:eslint-plugin-eslint-plugin@7.6.2 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.

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.

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records