Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-12 23:57 UTC

6cdh / tree-sitter-scheme

Scheme parser for tree-sitter

JavaScript · Tree-sitter Query · CMIT★ 52 stars⑂ 14 forkssince Apr 2022View on GitHub ↗

6cdh/tree-sitter-scheme holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Engineering Quality (84/100) and lowest on Security (53/100). It was last updated today. A single contributor accounts for most of its recent work.

73
overall / 100
Good

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.

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

Ownership

Ren XZPersonal account
30 followers14 public repossince May 2018

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 publishTags
crates.iotree-sitter-scheme0.25.031,93430 days agoincrementalparsingschemetree-sittertext-editors
npm@6cdh/tree-sitter-scheme0.25.011320 days ago—

Metrics by category

Vitality

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

68Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
4.8/36Commit cadence — 7/52 weeks with commits
14.5/18Commit volume — 40 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year40
human_commit_share1
days_since_last_push0
active_weeks_last_year7
How it's scored
16.2/27Ships releases — 11 version tags (no GitHub releases)
36/36Release recency — latest release 0 days ago
12.6/27Release cadence — a release every ~179.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count11
latest_release_tagv0.25.0
releases_from_tagsyes
days_since_latest_release0
mean_days_between_releases179.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?

60Moderate · 17% of overall
How it's scored
27.7/60Stars — 52 stars
9.3/25Forks — 14 forks
3.9/15Watchers — 6 watchers
Inputs used
forks14
stars52
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/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_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
60.1/80Monthly downloads — 31,934 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagestree-sitter-scheme
dependents—
ecosystemscrates
total_downloads148,424
monthly_downloads31,934
unverified_packages_excluded@6cdh/tree-sitter-scheme
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?

55Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.1/22.5Commit distribution — top contributor authored 95% of commits
8.1/13.5Contributor breadth — 6 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled6
top_contributor_share0.953
How it's scored
31.5/42Issue resolution — 75% of issues closed
30/30PR acceptance — 6/6 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/7 approved changesets -- score normalized to 0
Inputs used
merged_prs6
open_issues4
closed_issues12
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.75
closed_unmerged_prs0
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
10.7/25Owner reach — 30 followers of 6cdh
20.6/25Track record — 14 public repos, account ~8 yr old
Inputs used
followers30
owner_typeUser
is_verified—
owner_login6cdh
public_repos14
account_age_days3,082
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable — 2 package(s) on crates, npm
35/35Publish recency — latest publish 0 days ago
12/20Version history — 3 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagestree-sitter-scheme, @6cdh/tree-sitter-scheme
ecosystemscrates, npm
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 1 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

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://docs.rs/tree-sitter-scheme
10/10Repository description
10/10Topics — 2 topics
10/10Wiki
Inputs used
topicstree-sitter, scheme
has_wikiyes
homepage—
docs_sitehttps://docs.rs/tree-sitter-scheme
has_readmeyes
has_docs_diryes
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
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 1 out of 1 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/7 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
3/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 6
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
5.2/7.5Vulnerabilities — 3 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.1
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
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories3
affected_packages1
assessed_packages57
unassessed_packages2
affected_by_severityhigh 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 57 resolved dependencies against OSV. 2 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

71Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
26.1/40Legible commit history — 49 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.49
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes898
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
0/11Lint / format config
11/11Static type checking — bindings/python/tree_sitter_scheme/py.typed
10/10Reproducible environment — Nix, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
6/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 6
Inputs used
has_nixyes
has_testsyes
lockfilesCargo.lock, package-lock.json, pnpm-lock.yaml
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configsbindings/python/tree_sitter_scheme/py.typed
agent_commit_share0
toolchain_manifestsCargo.toml, go.mod
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — JavaScript with type-check config (bindings/python/tree_sitter_scheme/py.typed)
53.8/55Manageable file sizes — 1/46 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes328,122
source_files_sampled46
oversized_source_files1

Key facts

52GitHub stars
6contributors
40commits, last 12 months
0days since last push
11releases
1bus factor
4open issues
crates.io, Go, npm, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch go package 'github.com/tree-sitter/tree-sitter-scheme' from its registry
  • Could not fetch pypi package 'tree-sitter-scheme' from its registry
  • deps.dev does not index crates:tree-sitter-scheme@0.25.0; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 14 ⇿
0Stars
14Forks
8Releases

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.

03581013151412022-092024-092026-09
Major 0Minor 5Patch 1

Each point covers 4 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-12 23:57 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/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 0/7 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
6Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 6
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
7Vulnerabilities3 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
crates.iotree-sitter-language0.1Cargo.toml
Gogithub.com/tree-sitter/go-tree-sitterv0.25.0go.mod
npmnode-addon-api^8.0.0package.json
npmnode-gyp-build^4.8.1package.json
All dependencies 59

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

RegistryPackageVersionRelation
crates.iotree-sitter-language0.1.6direct
Gogithub.com/tree-sitter/go-tree-sitterv0.25.0direct
npmnode-addon-api8.1.0direct
npmnode-addon-api8.9.2direct
npmnode-gyp-build4.8.2direct
npmnode-gyp-build4.8.4direct
crates.ioaho-corasick1.1.4indirect
crates.iocc1.2.49indirect
crates.ioequivalent1.0.2indirect
crates.iofind-msvc-tools0.1.5indirect
crates.iohashbrown0.17.1indirect
crates.ioindexmap2.14.2indirect
crates.ioitoa1.0.18indirect
crates.iomemchr2.7.6indirect
crates.ioproc-macro21.0.107indirect
crates.ioquote1.0.47indirect
crates.ioregex1.12.2indirect
crates.ioregex-automata0.4.13indirect
crates.ioregex-syntax0.8.8indirect
crates.ioserde1.0.229indirect
crates.ioserde_core1.0.229indirect
crates.ioserde_derive1.0.229indirect
crates.ioserde_json1.0.151indirect
crates.ioshlex1.3.0indirect
crates.iostreaming-iterator0.1.9indirect
crates.iosyn3.0.6indirect
crates.iotree-sitter0.26.13indirect
crates.iounicode-ident1.0.26indirect
crates.iozmij1.0.23indirect
npmbase64-js1.5.1indirect
npmbl4.1.0indirect
npmbuffer5.7.1indirect
npmchownr1.1.4indirect
npmend-of-stream1.4.4indirect
npmfs-constants1.0.0indirect
npmieee7541.2.1indirect
npminherits2.0.4indirect
npmminimist1.2.8indirect
npmmkdirp-classic0.5.3indirect
npmnode-abi3.67.0indirect
npmnpm-run-path3.1.0indirect
npmonce1.4.0indirect
npmpath-key3.1.1indirect
npmprebuildify6.0.1indirect
npmpump3.0.0indirect
npmreadable-stream3.6.2indirect
npmsafe-buffer5.2.1indirect
npmsemver7.6.3indirect
npmstring_decoder1.3.0indirect
npmtar-fs2.1.1indirect
npmtar-stream2.2.0indirect
npmtree-sitter0.21.1indirect
npmtree-sitter0.25.1indirect
npmtree-sitter-cli0.24.7indirect
npmtree-sitter-cli0.26.13indirect
npmutil-deprecate1.0.2indirect
npmwrappy1.0.2indirect
PyPIsetuptools—indirect
PyPItree-sitter—indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 57 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct. 2 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
tar-fs2.1.1indirecthigh33.1.1

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 — crates.io, npm.