Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-16 11:35 UTC

not-an-aardvark / eslint-plugin-eslint-plugin

An ESLint plugin for linting ESLint plugins

TypeScriptMIT★ 234 stars⑂ 37 forkssince Dec 2016View on GitHub ↗

not-an-aardvark/eslint-plugin-eslint-plugin holds a health index of 89 out of 100, placing it in the Excellent band. It scores highest on Vitality (87/100) and lowest on AI Readiness (49/100). It was last updated today. 2 contributors account for most of its recent work.

89
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.

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

Ownership

ESLint CommunityOrganization
191 followers16 public repossince Nov 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmeslint-plugin-eslint-pluginpoints to another repo — not scored7.5.01,538,066900 days agoeslinteslintplugineslint-plugin

Metrics by category

Vitality

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

87Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
14.5/36Commit cadence21/52 weeks with commits
17.3/18Commit volume83 commits in the last year
10/10OpenSSF Scorecard: Maintained28 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year83
human_commit_share
days_since_last_push0
active_weeks_last_year21

Release discipline

100Exceptional
How it's scored
27/27Ships releases50 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~29.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count50
latest_release_tagv7.5.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases29.5
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?

63Moderate · 17% of overall
How it's scored
38.4/60Stars234 stars
13/25Forks37 forks
3.3/15Watchers5 watchers
Inputs used
forks37
stars234
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateyes

Sustainability & Governance

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

76Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
16.4/22.5Commit distributiontop contributor authored 27% of commits
13.5/13.5Contributor breadth34 contributors
10/10OpenSSF Scorecard: Contributorsproject has 34 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled34
top_contributor_share0.272
How it's scored
34.9/42Issue resolution83% of issues closed
24/30PR acceptance384/481 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs384
open_issues26
closed_issues129
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.832
closed_unmerged_prs97
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
16.4/25Owner reach191 followers of eslint-community
18.3/25Track record16 public repos, account ~4 yr old
Inputs used
followers191
owner_typeOrganization
is_verified
owner_logineslint-community
public_repos16
account_age_days1,701
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter configeslint.config.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics2 topics
0/10Wiki
Inputs used
topicseslint-plugin, eslint
has_wikino
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

69Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 34 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained28 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
3.5/5SASTSAST tool is not run on all commits -- score normalized to 7
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0.8/7.5Vulnerabilities9 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.9
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.

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.

49Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configeslint.config.js
11/11Static type checkinge2e/fixtures/all-typed-config/tsconfig.json, tests/lib/fixtures/tsconfig.json, tsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configse2e/fixtures/all-typed-config/tsconfig.json, tests/lib/fixtures/tsconfig.json, tsconfig.json
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
54.4/55Manageable file sizes1/98 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes81,830
source_files_sampled98
oversized_source_files1

Key facts

234GitHub stars
34contributors
83commits, last 12 months
0days since last push
50releases
2bus factor
26open issues
npmpackage ecosystems

Data collection warnings

  • npm package 'eslint-plugin-eslint-plugin' points at a different repository (git+https://github.com/eslint-community/eslint-plugin-eslint-plugin.git); excluded from ecosystem scoring

More detail

OpenSSF Scorecard 6.9 / 10
6.9aggregate

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-07-16 11:35 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal 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
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 34 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained28 commit(s) and 4 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
7SASTSAST tool is not run on all commits -- score normalized to 7
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
1Vulnerabilities9 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npm@eslint-community/eslint-utils^4.4.0package.json
npmestraverse^5.3.0package.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.

RegistryPackageVersionRelation
npm@eslint-community/eslint-utils4.7.0direct
npm@eslint-community/eslint-utils^4.4.0direct
npmestraverse5.3.0direct
npmestraverse^5.3.0direct
npm..7.0.0indirect
npm@commitlint/cli^20.0.0indirect
npm@commitlint/config-conventional^20.0.0indirect
npm@commitlint/types^20.0.0indirect
npm@eslint-community/eslint-plugin-eslint-comments^4.6.0indirect
npm@eslint-community/regexpp4.12.1indirect
npm@eslint/config-array0.21.0indirect
npm@eslint/config-helpers0.3.1indirect
npm@eslint/core0.15.2indirect
npm@eslint/eslintrc3.3.1indirect
npm@eslint/eslintrc^3.3.5indirect
npm@eslint/js9.33.0indirect
npm@eslint/js^9.39.4indirect
npm@eslint/markdown^7.5.1indirect
npm@eslint/object-schema2.1.6indirect
npm@eslint/plugin-kit0.3.5indirect
npm@humanfs/core0.19.1indirect
npm@humanfs/node0.16.6indirect
npm@humanwhocodes/module-importer1.0.1indirect
npm@humanwhocodes/retry0.3.1indirect
npm@humanwhocodes/retry0.4.3indirect
npm@types/eslint-scope^8.4.0indirect
npm@types/espree^10.1.0indirect
npm@types/estraverse^5.1.7indirect
npm@types/estree1.0.8indirect
npm@types/estree^1.0.8indirect
npm@types/json-schema7.0.15indirect
npm@types/lodash^4.17.18indirect
npm@types/node^24.0.0indirect
npm@typescript-eslint/parser8.62.0indirect
npm@typescript-eslint/utils8.62.0indirect
npm@vitest/coverage-istanbul^4.0.0indirect
npmacorn8.15.0indirect
npmacorn-jsx5.3.2indirect
npmajv6.12.6indirect
npmansi-styles4.3.0indirect
npmargparse2.0.1indirect
npmbalanced-match1.0.2indirect
npmbrace-expansion1.1.12indirect
npmcallsites3.1.0indirect
npmchalk4.1.2indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmconcat-map0.0.1indirect
npmcross-spawn7.0.6indirect
npmdebug4.4.1indirect
npmdeep-is0.1.4indirect
npmescape-string-regexp4.0.0indirect
npmeslint9.33.0indirect
npmeslint^9.33.0indirect
npmeslint^9.39.1indirect
npmeslint-config-not-an-aardvark^2.1.0indirect
npmeslint-config-prettier^10.1.8indirect
npmeslint-doc-generator3.6.0indirect
npmeslint-plugin-n^17.21.0indirect
npmeslint-plugin-unicorn^62.0.0indirect
npmeslint-remote-tester^4.0.3indirect
npmeslint-scope8.4.0indirect
npmeslint-scope^8.4.0indirect
npmeslint-visitor-keys3.4.3indirect
npmeslint-visitor-keys4.2.1indirect
npmespree10.4.0indirect
npmespree^11.2.0indirect
npmesquery1.6.0indirect
npmesrecurse4.3.0indirect
npmesutils2.0.3indirect
npmfast-deep-equal3.1.3indirect
npmfast-json-stable-stringify2.1.0indirect
npmfast-levenshtein2.0.6indirect
npmfile-entry-cache8.0.0indirect
npmfind-up5.0.0indirect
npmflat-cache4.0.1indirect
npmflatted3.3.3indirect
npmglob-parent6.0.2indirect
npmglobals14.0.0indirect
npmhas-flag4.0.0indirect
npmhusky^9.1.7indirect
npmignore5.3.2indirect
npmimport-fresh3.3.1indirect
npmimurmurhash0.1.4indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmisexe2.0.0indirect
npmjiti2.5.1indirect
npmjiti^2.5.1indirect
npmjs-yaml4.1.0indirect
npmjson-buffer3.0.1indirect
npmjson-schema-traverse0.4.1indirect
npmjson-stable-stringify-without-jsonify1.0.1indirect
npmkeyv4.5.4indirect
npmlevn0.4.1indirect
npmlint-staged^16.2.7indirect
npmlocate-path6.0.0indirect
npmlodash^4.17.21indirect
npmlodash.merge4.6.2indirect
npmmarkdownlint-cli^0.49.0indirect
npmminimatch3.1.2indirect
npmms2.1.3indirect
npmnatural-compare1.4.0indirect
npmnpm-package-json-lint^9.0.0indirect
npmnpm-run-all2^8.0.0indirect
npmoptionator0.9.4indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmparent-module1.0.1indirect
npmpath-exists4.0.0indirect
npmpath-key3.1.1indirect
npmprelude-ls1.2.1indirect
npmprettier3.9.4indirect
npmpunycode2.3.1indirect
npmresolve-from4.0.0indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmstrip-json-comments3.1.1indirect
npmsupports-color7.2.0indirect
npmtsdown^0.21.10indirect
npmtype-check0.4.0indirect
npmtypescript5.9.2indirect
npmtypescript^5.9.2indirect
npmtypescript-eslint8.62.0indirect
npmuri-js4.4.1indirect
npmvitest^4.0.0indirect
npmwhich2.0.2indirect
npmword-wrap1.2.5indirect
npmyocto-queue0.1.0indirect
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.11.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.