Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 02:27 UTC

xojs / xo

❤️ JavaScript/TypeScript linter (ESLint wrapper) with great defaults

TypeScriptMIT★ 7,993 stars⑂ 308 forkssince Aug 2015View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

xojs/xo holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (90/100) and lowest on AI Readiness (45/100). It was last updated 29 days ago. 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

XOOrganization
67 followers15 public repossince Jun 2015

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

Package ecosystems

Metrics by category

Vitality

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

80Excellent · 21% of overall
How it's scored
28.8/36Push recencylast push 29 days ago
11.1/36Commit cadence16/52 weeks with commits
16.4/18Commit volume66 commits in the last year
10/10OpenSSF Scorecard: Maintained16 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year66
human_commit_share1
days_since_last_push29
active_weeks_last_year16

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 52 days ago
27/27Release cadencea release every ~39.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv4.0.0
releases_from_tagsno
days_since_latest_release52
mean_days_between_releases39.3
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?

90Excellent · 17% of overall
How it's scored
60/60Stars7,993 stars
20.7/25Forks308 forks
9.5/15Watchers53 watchers
Inputs used
forks308
stars7,993
watchers53
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicescodecov.io, shields.io
has_pull_request_templateno
How it's scored
77.3/80Monthly downloads629,344 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesxo
dependents
ecosystemsnpm
total_downloads
monthly_downloads629,344
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?

66Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
7.4/22.5Commit distributiontop contributor authored 67% of commits
13.5/13.5Contributor breadth94 contributors
10/10OpenSSF Scorecard: Contributorsproject has 53 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled94
top_contributor_share0.673
How it's scored
41.8/42Issue resolution100% of issues closed
22.6/30PR acceptance249/330 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 1/30 approved changesets -- score normalized to 0
Inputs used
merged_prs249
open_issues3
closed_issues550
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.995
closed_unmerged_prs81
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 backingorganization-owned
0/20Verified domain
13.2/25Owner reach67 followers of xojs
20.8/25Track record15 public repos, account ~11 yr old
Inputs used
followers67
owner_typeOrganization
is_verifiedno
owner_loginxojs
public_repos15
account_age_days4,097

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 52 days ago
20/20Version history146 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesxo
ecosystemsnpm
any_deprecatedno
min_days_since_publish52

Engineering Quality

Are baseline engineering and documentation practices in place?

64Moderate · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests1 out of 1 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics11 topics
0/10Wiki
Inputs used
topicseslint, eslint-plugin, eslint-rules, linter, nodejs, shareable-configs, best-practices, unicorns, xo, code-style, style-linter
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?

57Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests1 out of 1 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
0/7.5Code-ReviewFound 1/30 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 53 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained16 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.6
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 advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages397
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:xo@4.0.0 runtime dependency closure — what installing the published package pulls in — 397 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.

45Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://html-eslint.org/llms.txt)
18.1/40Legible commit history34 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://html-eslint.org/llms.txt
legible_history_share0.34
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checkingtsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/25 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes55,926
source_files_sampled25
oversized_source_files0

Key facts

7,993GitHub stars
94contributors
66commits, last 12 months
29days since last push
100releases
1bus factor
3open 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 ★ / 308 ⇿
0Stars
308Forks
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.

012525037530652015-082021-022026-08
Major 4Minor 42Patch 51

Each point covers 11 days.

OpenSSF Scorecard 4.6 / 10
4.6aggregate

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-08-28 02:26 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests1 out of 1 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/30 approved changesets -- score normalized to 0
10Contributorsproject has 53 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained16 commit(s) and 8 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 19
RegistryPackageVersion constraintManifest
npm@sindresorhus/tsconfig^8.1.0package.json
npmarrify^3.0.0package.json
npmcosmiconfig^9.0.2package.json
npmdefine-lazy-prop^3.0.0package.json
npmeslint^10.6.0package.json
npmeslint-config-xo^0.57.0package.json
npmeslint-formatter-pretty^7.1.0package.json
npmfind-cache-directory^6.0.0package.json
npmget-stdin^10.0.0package.json
npmget-tsconfig^4.14.0package.json
npmglobby^16.2.1package.json
npmjiti^2.7.0package.json
npmmeow^14.1.0package.json
npmmicromatch^4.0.8package.json
npmopen-editor^6.0.0package.json
npmpath-exists^5.0.0package.json
npmprettier^3.9.4package.json
npmtype-fest^5.8.0package.json
npmtypescript^6.0.3package.json
All dependencies 27

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

RegistryPackageVersionRelation
npm@sindresorhus/tsconfig^8.1.0direct
npmarrify^3.0.0direct
npmcosmiconfig^9.0.2direct
npmdefine-lazy-prop^3.0.0direct
npmeslint^10.6.0direct
npmeslint-config-xo^0.57.0direct
npmeslint-formatter-pretty^7.1.0direct
npmfind-cache-directory^6.0.0direct
npmget-stdin^10.0.0direct
npmget-tsconfig^4.14.0direct
npmglobby^16.2.1direct
npmjiti^2.7.0direct
npmmeow^14.1.0direct
npmmicromatch^4.0.8direct
npmopen-editor^6.0.0direct
npmpath-exists^5.0.0direct
npmprettier^3.9.4direct
npmtype-fest^5.8.0direct
npmtypescript^6.0.3direct
npm@types/micromatch^4.0.10indirect
npm@types/node^26.1.0indirect
npmdedent^1.7.2indirect
npmeslint-plugin-vue^10.9.2indirect
npmexeca^9.6.1indirect
npmhusky^9.1.7indirect
npmnp^11.2.2indirect
npmtemp-dir^3.0.0indirect
Dependency advisories 0

Installing npm:xo@4.0.0 pulls in 397 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 statisticsnpm.