Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 16:09 UTC

sxzz / eslint-config

A opinionated ESLint config preset.

TypeScriptMIT★ 242 stars⑂ 16 forkssince Feb 2023View on GitHub ↗

sxzz/eslint-config holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Vitality (92/100) and lowest on Security (60/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Kevin DengPersonal account
4,837 followers240 public repossince Jan 2014undefined

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npm@sxzz/eslint-config8.7.020,2491929 days ago

Metrics by category

Vitality

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

92Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
22.8/36Commit cadence — 33/52 weeks with commits
18/18Commit volume — 139 commits in the last year
10/10OpenSSF Scorecard: Maintained — 29 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year139
human_commit_share0.86
days_since_last_push0
active_weeks_last_year33

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 9 days ago
27/27Release cadence — a release every ~17.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv8.7.0
releases_from_tagsno
days_since_latest_release9
mean_days_between_releases17.2
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?

69Good · 17% of overall
How it's scored
38.6/60Stars — 242 stars
9.8/25Forks — 16 forks
0/15Watchers — 1 watchers
Inputs used
forks16
stars242
watchers1
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 (MIT)
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_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateyes
How it's scored
57.4/80Monthly downloads — 20,249 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@sxzz/eslint-config
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads20,249
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?

65Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.3/22.5Commit distribution — top contributor authored 99% of commits
8.1/13.5Contributor breadth — 6 contributors
10/10OpenSSF Scorecard: Contributors — project has 25 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled6
top_contributor_share0.988
How it's scored
36/42Issue resolution — 86% of issues closed
25.8/30PR acceptance — 143/166 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/28 approved changesets -- score normalized to 0
Inputs used
merged_prs143
open_issues2
closed_issues12
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.857
closed_unmerged_prs23
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
25/25Owner reach — 4,837 followers of sxzz
25/25Track record — 240 public repos, account ~12 yr old
Inputs used
followers4,837
owner_typeUser
is_verified—
owner_loginsxzz
public_repos240
account_age_days4,652
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 9 days ago
20/20Version history — 192 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@sxzz/eslint-config
ecosystemsnpm
any_deprecatedno
min_days_since_publish9

Engineering Quality

Are baseline engineering and documentation practices in place?

61Moderate · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
0/24Tests present
16/16Linter config — package.json ("prettier")
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests — 2 out of 3 merged PRs checked by a CI test -- score normalized to 6
Inputs used
has_ciyes
has_testsno
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://eslint-config.sxzz.dev
10/10Repository description
10/10Topics — 6 topics
0/10Wiki
Inputs used
topicsconfig, eslint, flat, sxzz, eslint-config, eslint-flat-config
has_wikino
homepagehttps://eslint-config.sxzz.dev
docs_sitehttps://eslint-config.sxzz.dev
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

60Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
1.5/2.5CI-Tests — 2 out of 3 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 1/28 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 25 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 — 29 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
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
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5
Excluded from scoring (no data or not applicable): Packaging, 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 — 1 affected: katex 0.16.47 (low)
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages223
unassessed_packages0
affected_by_severitylow 1
direct_affected_packages0
Matched the npm:@sxzz/eslint-config@8.7.0 runtime dependency closure — what installing the published package pulls in — 223 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.

66Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 86 of 86 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes2,627
How it's scored
0/18One-command bootstrap
0/22Automated tests
11/11Lint / format config — package.json ("prettier")
11/11Static type checking — tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 14 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_testsno
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.14
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
53.4/55Manageable file sizes — 1/35 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes727,691
source_files_sampled35
oversized_source_files1

Key facts

242GitHub stars
6contributors
139commits, last 12 months
0days since last push
100releases
1bus factor
2open 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 ★ / 16 ⇿
0Stars
16Forks
99Releases

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.

04812161622023-032024-122026-09
Major 5Minor 27Patch 65

Each point covers 4 days.

OpenSSF Scorecard 5.0 / 10
5.0aggregate

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-19 16:09 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
6CI-Tests2 out of 3 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/28 approved changesets -- score normalized to 0
10Contributorsproject has 25 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained29 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 27
RegistryPackageVersion constraintManifest
npm@eslint-community/eslint-plugin-eslint-commentscatalog:pluginspackage.json
npm@eslint/jscatalog:package.json
npm@eslint/markdowncatalog:pluginspackage.json
npmeslint-config-flat-gitignorecatalog:pluginspackage.json
npmeslint-config-prettiercatalog:pluginspackage.json
npmeslint-flat-config-utilscatalog:package.json
npmeslint-plugin-antfucatalog:pluginspackage.json
npmeslint-plugin-baseline-jscatalog:pluginspackage.json
npmeslint-plugin-commandcatalog:pluginspackage.json
npmeslint-plugin-de-morgancatalog:pluginspackage.json
npmeslint-plugin-importercatalog:pluginspackage.json
npmeslint-plugin-jsdoccatalog:pluginspackage.json
npmeslint-plugin-jsonccatalog:pluginspackage.json
npmeslint-plugin-ncatalog:pluginspackage.json
npmeslint-plugin-perfectionistcatalog:pluginspackage.json
npmeslint-plugin-pnpmcatalog:pluginspackage.json
npmeslint-plugin-prettiercatalog:pluginspackage.json
npmeslint-plugin-regexpcatalog:pluginspackage.json
npmeslint-plugin-sxzzcatalog:pluginspackage.json
npmeslint-plugin-unicorncatalog:pluginspackage.json
npmeslint-plugin-unused-importscatalog:pluginspackage.json
npmeslint-plugin-vuekitcatalog:pluginspackage.json
npmeslint-plugin-ymlcatalog:pluginspackage.json
npmglobalscatalog:package.json
npmjsonc-eslint-parsercatalog:parserspackage.json
npmtypescript-eslintcatalog:pluginspackage.json
npmvue-eslint-parsercatalog:parserspackage.json
All dependencies 15

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

RegistryPackageVersionRelation
npm@pnpm/exe.android-arm6412.10.1indirect
npm@pnpm/exe.android-x6412.10.1indirect
npm@pnpm/exe.darwin-arm6412.10.1indirect
npm@pnpm/exe.darwin-x6412.10.1indirect
npm@pnpm/exe.freebsd-x6412.10.1indirect
npm@pnpm/exe.linux-arm6412.10.1indirect
npm@pnpm/exe.linux-arm64-musl12.10.1indirect
npm@pnpm/exe.linux-ppc6412.10.1indirect
npm@pnpm/exe.linux-riscv6412.10.1indirect
npm@pnpm/exe.linux-s390x12.10.1indirect
npm@pnpm/exe.linux-x6412.10.1indirect
npm@pnpm/exe.linux-x64-musl12.10.1indirect
npm@pnpm/exe.win32-arm6412.10.1indirect
npm@pnpm/exe.win32-x6412.10.1indirect
npmpnpm12.10.1indirect
Dependency advisories 1

Installing npm:@sxzz/eslint-config@8.7.0 pulls in 223 packages, direct and transitive: 1 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
katex0.16.47indirectlow10.18.2

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.