Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 11:01 UTC

bearcove / arborium

An opinionated tree-sitter + tree-sitter-highlight + grammars bundle

JavaScript · C · RustApache-2.0★ 507 stars⑂ 43 forkssince Nov 2025View on GitHub ↗

bearcove/arborium holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (85/100) and lowest on Security (30/100). It was last updated 53 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

bearcoveOrganization
458 followers124 public repossince Aug 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.ioxtaskpoints to another repo — not scored0.1.42755113 days agoautomationmacosreleasecodesignxtaskcommand-line-utilities

Metrics by category

Vitality

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

65Good · 21% of overall
How it's scored
18/36Push recency — last push 53 days ago
11.8/36Commit cadence — 17/52 weeks with commits
18/18Commit volume — 424 commits in the last year
1/10OpenSSF Scorecard: Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year424
human_commit_share0.99
days_since_last_push53
active_weeks_last_year17
How it's scored
16.2/27Ships releases — 78 version tags (no GitHub releases)
36/36Release recency — latest release 53 days ago
27/27Release cadence — a release every ~24.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count78
latest_release_tagv2.18.2
releases_from_tagsyes
days_since_latest_release53
mean_days_between_releases24.7
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?

55Moderate · 17% of overall
How it's scored
43.9/60Stars — 507 stars
13.5/25Forks — 43 forks
1.7/15Watchers — 3 watchers
Inputs used
forks43
stars507
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

53Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.7/22.5Commit distribution — top contributor authored 97% of commits
13.5/13.5Contributor breadth — 10 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled10
top_contributor_share0.967
How it's scored
29.6/42Issue resolution — 70% of issues closed
23.5/30PR acceptance — 80/102 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 5/30 approved changesets -- score normalized to 1
Inputs used
merged_prs80
open_issues32
closed_issues76
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.704
closed_unmerged_prs22
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
19.1/25Owner reach — 458 followers of bearcove
23.3/25Track record — 124 public repos, account ~5 yr old
Inputs used
followers458
owner_typeOrganization
is_verifiedno
owner_loginbearcove
public_repos124
account_age_days1,887

Engineering Quality

Are baseline engineering and documentation practices in place?

85Excellent · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — clippy.toml, eslint.config.mjs
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 21 out of 22 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://arborium.bearcove.eu/
10/10Repository description
10/10Topics — 4 topics
0/10Wiki
Inputs used
topicshighlighting, rust, syntax, tree-sitter
has_wikino
homepagehttps://arborium.bearcove.eu/
docs_sitehttps://arborium.bearcove.eu/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

30At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.2/2.5CI-Tests — 21 out of 22 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 5/30 approved changesets -- score normalized to 1
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
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
0.8/7.5Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
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
0/7.5Vulnerabilities — 54 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

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.

80Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
37.2/40Legible commit history — 69 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.697
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes1,306
How it's scored
18/18One-command bootstrap — justfile, langs/group-maple/just/def/samples/Justfile, langs/group-maple/make/def/samples/Makefile
22/22Automated tests
11/11Lint / format config — clippy.toml, eslint.config.mjs
11/11Static type checking — crates/arborium-tree-sitter/binding_web/tsconfig.json, langs/group-acorn/json/def/samples/tsconfig.json, packages/arborium/tsconfig.json
10/10Reproducible environment — Dockerfile, Nix, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixyes
has_testsyes
lockfilesCargo.lock, package-lock.json, pnpm-lock.yaml
has_dockerfileyes
typed_languageno
bootstrap_filesjustfile, langs/group-maple/just/def/samples/Justfile, langs/group-maple/make/def/samples/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configscrates/arborium-tree-sitter/binding_web/tsconfig.json, langs/group-acorn/json/def/samples/tsconfig.json, packages/arborium/tsconfig.json
agent_commit_share0
toolchain_manifestsexamples/arborium-example-json/Cargo.toml, examples/wasm-browser/Cargo.toml, langs/group-acorn/xml/def/samples/pom.xml, xtask/Cargo.toml
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — JavaScript with type-check config (crates/arborium-tree-sitter/binding_web/tsconfig.json, langs/group-acorn/json/def/samples/tsconfig.json, packages/arborium/tsconfig.json)
52.6/55Manageable file sizes — 23/529 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes247,261
source_files_sampled529
oversized_source_files23
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — demo/samples/graphql.graphql, demo/samples/proto.proto, langs/group-maple/graphql/def/samples/starwars_schema.graphql, langs/group-pine/proto/def/samples/addressbook.proto
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples, samples
Inputs used
example_dirsexamples, samples
has_mcp_signalno
api_schema_filesdemo/samples/graphql.graphql, demo/samples/proto.proto, langs/group-maple/graphql/def/samples/starwars_schema.graphql, langs/group-pine/proto/def/samples/addressbook.proto
interfaces_expected_of—
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

507GitHub stars
10contributors
424commits, last 12 months
53days since last push
78releases
1bus factor
32open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • crates package 'xtask' points at a different repository (https://github.com/arcboxlabs/xtask); excluded from ecosystem scoring
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 43 ⇿
0Stars
43Forks
78Releases

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.

010203040504332025-122026-052026-10
Major 2Minor 42Patch 34
OpenSSF Scorecard 3.0 / 10
3.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-21 11:00 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
9CI-Tests21 out of 22 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 5/30 approved changesets -- score normalized to 1
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
1Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
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
0Vulnerabilities54 existing vulnerabilities detected
Direct dependencies 36
RegistryPackageVersion constraintManifest
crates.iocamino1xtask/Cargo.toml
crates.iochrono0.4xtask/Cargo.toml
crates.iofs-err3xtask/Cargo.toml
crates.iowhich7xtask/Cargo.toml
crates.iofacet—xtask/Cargo.toml
crates.iofacet-value—xtask/Cargo.toml
crates.iofacet-args—xtask/Cargo.toml
crates.iofacet-json—xtask/Cargo.toml
crates.iofacet-yaml—xtask/Cargo.toml
crates.iofacet-pretty—xtask/Cargo.toml
crates.iofacet-diff—xtask/Cargo.toml
crates.iofacet-toml—xtask/Cargo.toml
crates.ioindexmap2xtask/Cargo.toml
crates.iothiserror2xtask/Cargo.toml
crates.iostructstruck0.4xtask/Cargo.toml
crates.iorootcause0.10xtask/Cargo.toml
crates.iotiny_http0.12xtask/Cargo.toml
crates.ioindicatif0.17xtask/Cargo.toml
crates.ioowo-colors4xtask/Cargo.toml
crates.iorayon1.10xtask/Cargo.toml
crates.iotempfile3xtask/Cargo.toml
crates.ioregex1xtask/Cargo.toml
crates.ioblake31xtask/Cargo.toml
crates.ioignore0.4xtask/Cargo.toml
crates.iotracing-subscriber0.3.22xtask/Cargo.toml
crates.iosailfish0.10xtask/Cargo.toml
crates.iorand0.9.2xtask/Cargo.toml
crates.iotoml0.8xtask/Cargo.toml
crates.iowalkdir2xtask/Cargo.toml
crates.ioflate21xtask/Cargo.toml
crates.iotar0.4xtask/Cargo.toml
crates.iobrotli7xtask/Cargo.toml
crates.iotoml_edit0.23.9xtask/Cargo.toml
crates.ioserde_json1.0.145xtask/Cargo.toml
crates.iowalrus0.20xtask/Cargo.toml
crates.iopetgraph0.7xtask/Cargo.toml
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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.