Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 07:04 UTC

tree-sitter / node-tree-sitter

Node.js bindings for tree-sitter

JavaScript · C++MIT★ 879 stars⑂ 175 forkssince Mar 2014View on GitHub ↗

tree-sitter/node-tree-sitter holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (72/100) and lowest on Vitality (37/100). It was last updated 83 days ago. A single contributor accounts for most of its recent work.

63
overall / 100
Moderate

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.

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

Ownership

tree-sitterOrganization
2,747 followers56 public repossince Feb 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmtree-sitter0.25.112,663,34620184 days agoincrementalparsingtree-sitter

Metrics by category

Vitality

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

37Weak · 21% of overall
How it's scored
18/36Push recency — last push 83 days ago
2.1/36Commit cadence — 3/52 weeks with commits
7/18Commit volume — 5 commits in the last year
4/10OpenSSF Scorecard: Maintained — 1 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 4
Inputs used
commits_last_year5
human_commit_share1
days_since_last_push83
active_weeks_last_year3
How it's scored
27/27Ships releases — 54 releases published
7.2/36Release recency — latest release 660 days ago
12.6/27Release cadence — a release every ~130.6 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count54
latest_release_tagv0.22.4
releases_from_tagsno
days_since_latest_release660
mean_days_between_releases130.6

Community & Adoption

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

72Good · 17% of overall
How it's scored
47.7/60Stars — 879 stars
18.7/25Forks — 175 forks
6.4/15Watchers — 15 watchers
Inputs used
forks175
stars879
watchers15
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 12,663,346 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagestree-sitter
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads12,663,346
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?

69Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
5.3/22.5Commit distribution — top contributor authored 77% of commits
13.5/13.5Contributor breadth — 30 contributors
10/10OpenSSF Scorecard: Contributors — project has 17 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled30
top_contributor_share0.766
How it's scored
38.9/42Issue resolution — 93% of issues closed
18.4/30PR acceptance — 84/137 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 8/25 approved changesets -- score normalized to 3
Inputs used
merged_prs84
open_issues10
closed_issues125
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.926
closed_unmerged_prs53
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
0/20Verified domain
24.7/25Owner reach — 2,747 followers of tree-sitter
24.8/25Track record — 56 public repos, account ~10 yr old
Inputs used
followers2,747
owner_typeOrganization
is_verifiedno
owner_logintree-sitter
public_repos56
account_age_days3,903

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 84 days ago
20/20Version history — 201 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagestree-sitter
ecosystemsnpm
any_deprecatedno
min_days_since_publish84

Engineering Quality

Are baseline engineering and documentation practices in place?

68Good · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests — 5 out of 10 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://www.npmjs.com/package/tree-sitter
10/10Repository description
10/10Topics — 4 topics
10/10Wiki
Inputs used
topicstree-sitter, nodejs, binding, javascript
has_wikiyes
homepagehttps://www.npmjs.com/package/tree-sitter
docs_sitehttps://www.npmjs.com/package/tree-sitter
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

53Moderate · 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
1.2/2.5CI-Tests — 5 out of 10 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-Review — Found 8/25 approved changesets -- score normalized to 3
2.5/2.5Contributors — project has 17 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
3/7.5Maintained — 1 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 4
0/5Packaging — no data
0.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
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 — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 41 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.1
Excluded from scoring (no data or not applicable): Packaging. 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_packages2
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:tree-sitter@0.25.1 runtime dependency closure — what installing the published package pulls in — 2 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.

51Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
37.9/40Legible commit history — 71 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.71
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 checking — tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
1/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — JavaScript with type-check config (tsconfig.json)
55/55Manageable file sizes — 0/27 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes37,692
source_files_sampled27
oversized_source_files0

Key facts

879GitHub stars
30contributors
5commits, last 12 months
83days since last push
54releases
1bus factor
10open 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 ★ / 175 ⇿
0Stars
175Forks
54Releases

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.

0408012016015932015-122021-052026-10
Major 0Minor 8Patch 46

Each point covers 10 days.

OpenSSF Scorecard 4.1 / 10
4.1aggregate

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 07:03 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
5CI-Tests5 out of 10 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 8/25 approved changesets -- score normalized to 3
10Contributorsproject has 17 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
4Maintained1 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 4
n/aPackagingpackaging workflow not detected
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities41 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmnode-addon-api^8.5.0package.json
npmnode-gyp-build^4.8.4package.json
All dependencies 121

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

RegistryPackageVersionRelation
npmnode-addon-api8.5.0direct
npmnode-gyp-build4.8.4direct
npm@gerrit0/mini-shiki3.20.0indirect
npm@isaacs/balanced-match4.0.1indirect
npm@isaacs/brace-expansion5.0.0indirect
npm@isaacs/fs-minipass4.0.1indirect
npm@npmcli/agent4.0.0indirect
npm@npmcli/fs5.0.0indirect
npm@shikijs/engine-oniguruma3.20.0indirect
npm@shikijs/langs3.20.0indirect
npm@shikijs/themes3.20.0indirect
npm@shikijs/types3.20.0indirect
npm@shikijs/vscode-textmate10.0.2indirect
npm@types/hast3.0.4indirect
npm@types/node25.0.3indirect
npm@types/tmp0.2.6indirect
npm@types/unist3.0.3indirect
npmabbrev4.0.0indirect
npmagent-base7.1.4indirect
npmargparse2.0.1indirect
npmbalanced-match1.0.2indirect
npmbase64-js1.5.1indirect
npmbl4.1.0indirect
npmbrace-expansion2.0.2indirect
npmbuffer5.7.1indirect
npmcacache20.0.3indirect
npmcamelcase8.0.0indirect
npmchownr1.1.4indirect
npmchownr3.0.0indirect
npmdebug4.4.3indirect
npmencoding0.1.13indirect
npmend-of-stream1.4.4indirect
npmentities4.5.0indirect
npmenv-paths2.2.1indirect
npmerr-code2.0.3indirect
npmexponential-backoff3.1.1indirect
npmfdir6.5.0indirect
npmfs-constants1.0.0indirect
npmfs-minipass3.0.3indirect
npmglob13.0.0indirect
npmgraceful-fs4.2.11indirect
npmhttp-cache-semantics4.2.0indirect
npmhttp-proxy-agent7.0.2indirect
npmhttps-proxy-agent7.0.6indirect
npmiconv-lite0.6.3indirect
npmieee7541.2.1indirect
npmimurmurhash0.1.4indirect
npminherits2.0.4indirect
npmip-address10.1.0indirect
npmisexe3.1.1indirect
npmlinkify-it5.0.0indirect
npmlru-cache11.2.4indirect
npmlunr2.3.9indirect
npmmake-fetch-happen15.0.3indirect
npmmarkdown-it14.1.0indirect
npmmdurl2.0.0indirect
npmminimatch10.1.1indirect
npmminimatch9.0.5indirect
npmminimist1.2.8indirect
npmminipass3.3.6indirect
npmminipass7.1.2indirect
npmminipass-collect2.0.1indirect
npmminipass-fetch5.0.0indirect
npmminipass-flush1.0.5indirect
npmminipass-pipeline1.2.4indirect
npmminipass-sized1.0.3indirect
npmminizlib3.1.0indirect
npmmkdirp-classic0.5.3indirect
npmms2.1.3indirect
npmnegotiator1.0.0indirect
npmnode-abi3.71.0indirect
npmnode-gyp12.1.0indirect
npmnopt9.0.0indirect
npmnpm-run-path3.1.0indirect
npmonce1.4.0indirect
npmp-map7.0.4indirect
npmpath-key3.1.1indirect
npmpath-scurry2.0.0indirect
npmpicomatch4.0.3indirect
npmprebuildify6.0.1indirect
npmproc-log6.1.0indirect
npmpromise-retry2.0.1indirect
npmpump3.0.2indirect
npmpunycode.js2.3.1indirect
npmreadable-stream3.6.2indirect
npmretry0.12.0indirect
npmsafe-buffer5.2.1indirect
npmsafer-buffer2.1.2indirect
npmsemver7.6.3indirect
npmsmart-buffer4.2.0indirect
npmsocks2.8.7indirect
npmsocks-proxy-agent8.0.5indirect
npmssri13.0.0indirect
npmstring_decoder1.3.0indirect
npmtar7.5.2indirect
npmtar-fs2.1.4indirect
npmtar-stream2.2.0indirect
npmtinyglobby0.2.15indirect
npmtmp0.2.5indirect
npmtree-sitter-c0.24.1indirect
npmtree-sitter-embedded-template0.25.0indirect
npmtree-sitter-html0.23.2indirect
npmtree-sitter-java0.23.5indirect
npmtree-sitter-javascript0.25.0indirect
npmtree-sitter-json0.24.8indirect
npmtree-sitter-python0.25.0indirect
npmtree-sitter-ruby0.23.1indirect
npmtree-sitter-rust0.24.0indirect
npmtypedoc0.28.15indirect
npmtypedoc-plugin-rename-defaults0.7.3indirect
npmtypescript5.9.3indirect
npmuc.micro2.1.0indirect
npmundici-types7.16.0indirect
npmunique-filename5.0.0indirect
npmunique-slug6.0.0indirect
npmutil-deprecate1.0.2indirect
npmwhich6.0.0indirect
npmwrappy1.0.2indirect
npmyallist4.0.0indirect
npmyallist5.0.0indirect
npmyaml2.8.2indirect
Dependency advisories 0

Installing npm:tree-sitter@0.25.1 pulls in 2 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.