Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-29 10:44 UTC

acristoffers / tree-sitter-matlab

MATLAB tree-sitter parser

C · JavaScriptMIT★ 44 stars⑂ 13 forkssince Jun 2023View on GitHub ↗

acristoffers/tree-sitter-matlab holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (79/100) and lowest on Security (57/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Álan CrístofferPersonal account
62 followers66 public repossince Aug 2012

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-matlab1.3.111,091153 days agoincrementalmatlabparsingtree-sittertext-editorsparser-implementations
npm@acristoffers/tree-sitter-matlab1.3.04,8374206 days agoincrementalparsingtree-sittermatlab
PyPItree-sitter-matlab1.3.18,721283 days agoincrementalparsingtree-sittermatlab

Metrics by category

Vitality

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

77Good · 21% of overall
How it's scored
36/36Push recencylast push 3 days ago
10.4/36Commit cadence15/52 weeks with commits
17.5/18Commit volume88 commits in the last year
5/10OpenSSF Scorecard: Maintained5 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year88
human_commit_share0.91
days_since_last_push3
active_weeks_last_year15
How it's scored
27/27Ships releases28 releases published
36/36Release recencylatest release 3 days ago
27/27Release cadencea release every ~32.7 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count28
latest_release_tagv1.3.1
releases_from_tagsno
days_since_latest_release3
mean_days_between_releases32.7

Community & Adoption

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

58Moderate · 17% of overall
How it's scored
26.5/60Stars44 stars
9/25Forks13 forks
1.7/15Watchers3 watchers
Inputs used
forks13
stars44
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
58.6/80Monthly downloads24,649 downloads/month across crates, npm, pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagestree-sitter-matlab, @acristoffers/tree-sitter-matlab, tree-sitter-matlab
dependents
ecosystemscrates, npm, pypi
total_downloads46,476
monthly_downloads24,649
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?

64Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
1.3/22.5Commit distributiontop contributor authored 94% of commits
9.5/13.5Contributor breadth7 contributors
10/10OpenSSF Scorecard: Contributorsproject has 11 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled7
top_contributor_share0.942
How it's scored
41.7/42Issue resolution99% of issues closed
25.6/30PR acceptance23/27 decided PRs merged
13/13Newcomer PR acceptance1/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 2/21 approved changesets -- score normalized to 0
Inputs used
merged_prs23
open_issues1
closed_issues139
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.993
closed_unmerged_prs4
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
12.9/25Owner reach62 followers of acristoffers
25/25Track record66 public repos, account ~14 yr old
Inputs used
followers62
owner_typeUser
is_verified
owner_loginacristoffers
public_repos66
account_age_days5,120
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable3 package(s) on crates, npm, pypi
35/35Publish recencylatest publish 3 days ago
20/20Version history28 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagestree-sitter-matlab, @acristoffers/tree-sitter-matlab, tree-sitter-matlab
ecosystemscrates, npm, pypi
any_deprecatedno
min_days_since_publish3

Engineering Quality

Are baseline engineering and documentation practices in place?

79Good · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter config.eslintrc.js
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests10 out of 11 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://docs.rs/tree-sitter-matlab
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_sitehttps://docs.rs/tree-sitter-matlab
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
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.2/2.5CI-Tests10 out of 11 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 2/21 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 11 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
3.8/7.5Maintained5 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
5/5Packagingpackaging workflow detected
0.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6.8/7.5Vulnerabilities1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate4.6

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages50
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 50 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.

70Good · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history91 of 91 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share1
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format config.eslintrc.js
11/11Static type checkingbindings/python/tree_sitter_matlab/py.typed
10/10Reproducible environmentNix, lockfile
2/10Demonstrated agent practice1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance9 of the last 100 commits are automated dependency updates
1/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixyes
has_testsyes
lockfilesCargo.lock, package-lock.json
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configsbindings/python/tree_sitter_matlab/py.typed
agent_commit_share0.01
toolchain_manifestsCargo.toml, go.mod
dependency_bot_commit_share0.09
How it's scored
45/45Type-checkable codeC (statically typed)
52.6/55Manageable file sizes1/23 source files over 60KB
Inputs used
primary_languageC
largest_source_bytes3,207,606
source_files_sampled23
oversized_source_files1

Key facts

44GitHub stars
7contributors
88commits, last 12 months
3days since last push
28releases
1bus factor
1open 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-matlab' from its registry

More detail

Star and fork history 0 ★ / 13 ⇿
0Stars
13Forks
27Releases

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.

03581013151312024-022025-052026-08
Major 1Minor 3Patch 23

Each point covers 3 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-29 10:44 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
9CI-Tests10 out of 11 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 2/21 approved changesets -- score normalized to 0
10Contributorsproject has 11 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
5Maintained5 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
10Packagingpackaging workflow 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
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
crates.iotree-sitter-language0.1Cargo.toml
Gogithub.com/tree-sitter/go-tree-sitterv0.24.0go.mod
npmnode-addon-api^8.2.1package.json
npmnode-gyp-build^4.8.2package.json
All dependencies 52

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

RegistryPackageVersionRelation
crates.iotree-sitter-language0.1.5direct
Gogithub.com/tree-sitter/go-tree-sitter0.24.0direct
npmnode-addon-api8.5.0direct
npmnode-gyp-build4.8.4direct
crates.ioaho-corasick1.1.3indirect
crates.iocc1.2.21indirect
crates.ioequivalent1.0.2indirect
crates.iohashbrown0.15.3indirect
crates.ioindexmap2.9.0indirect
crates.ioitoa1.0.15indirect
crates.iomemchr2.7.4indirect
crates.ioproc-macro21.0.95indirect
crates.ioquote1.0.40indirect
crates.ioregex1.11.1indirect
crates.ioregex-automata0.4.9indirect
crates.ioregex-syntax0.8.5indirect
crates.ioryu1.0.20indirect
crates.ioserde1.0.219indirect
crates.ioserde_derive1.0.219indirect
crates.ioserde_json1.0.140indirect
crates.ioshlex1.3.0indirect
crates.iostreaming-iterator0.1.9indirect
crates.iosyn2.0.101indirect
crates.iotree-sitter0.25.3indirect
crates.iounicode-ident1.0.18indirect
npmbase64-js1.5.1indirect
npmbl4.1.0indirect
npmbuffer5.7.1indirect
npmchownr1.1.4indirect
npmend-of-stream1.4.5indirect
npmfs-constants1.0.0indirect
npmieee7541.2.1indirect
npminherits2.0.4indirect
npmminimist1.2.8indirect
npmmkdirp-classic0.5.3indirect
npmnode-abi3.75.0indirect
npmnpm-run-path3.1.0indirect
npmonce1.4.0indirect
npmpath-key3.1.1indirect
npmprebuildify6.0.1indirect
npmpump3.0.3indirect
npmreadable-stream3.6.2indirect
npmsafe-buffer5.2.1indirect
npmsemver7.7.2indirect
npmstring_decoder1.3.1indirect
npmtar-fs2.1.3indirect
npmtar-stream2.2.0indirect
npmtree-sitter-cli0.25.8indirect
npmutil-deprecate1.0.2indirect
npmwrappy1.0.2indirect
PyPIsetuptoolsindirect
PyPItree-sitterindirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 50 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.3indirecthigh13.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 statisticscrates.io, npm, PyPI.