Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-18 15:37 UTC

thatch-health / grape_sorbet

Sorbet signatures and Tapioca DSL compiler for Grape.

RubyMIT★ 6 stars⑂ 0 forkssince Jun 2024View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

thatch-health/grape_sorbet holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Vitality (83/100) and lowest on Community & Adoption (43/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

ThatchOrganization · verified domain
13 followers5 public repossince Jan 2022

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsgrape_sorbet0.3.0-2164 days ago

Metrics by category

Vitality

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

83Excellent · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
21.5/36Commit cadence — 31/52 weeks with commits
17.6/18Commit volume — 91 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year91
human_commit_share0.4
days_since_last_push2
active_weeks_last_year31
How it's scored
16.2/27Ships releases — 21 version tags (no GitHub releases)
36/36Release recency — latest release 64 days ago
19.8/27Release cadence — a release every ~85.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count21
latest_release_tagv0.3.0
releases_from_tagsyes
days_since_latest_release64
mean_days_between_releases85.2
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?

43Weak · 17% of overall
How it's scored
11.3/60Stars — 6 stars
0/25Forks — 0 forks
0/15Watchers — 1 watchers
Inputs used
forks0
stars6
watchers1
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
13.5/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_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
51.2/80Total downloads — 84,782 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesgrape_sorbet
dependents—
ecosystemsrubygems
total_downloads84,782
monthly_downloads—
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?

52Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.9/22.5Commit distribution — top contributor authored 96% of commits
4.1/13.5Contributor breadth — 3 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.96
How it's scored
0/42Issue resolution — 0% of issues closed
27.5/30PR acceptance — 112/122 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-Review — Found 2/10 approved changesets -- score normalized to 2
Inputs used
merged_prs112
open_issues2
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0
closed_unmerged_prs10
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
20/20Verified domain
8.2/25Owner reach — 13 followers of thatch-health
15.4/25Track record — 5 public repos, account ~4 yr old
Inputs used
followers13
owner_typeOrganization
is_verifiedyes
owner_loginthatch-health
public_repos5
account_age_days1,773

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on rubygems
35/35Publish recency — latest publish 64 days ago
20/20Version history — 21 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgrape_sorbet
ecosystemsrubygems
any_deprecatedno
min_days_since_publish64

Engineering Quality

Are baseline engineering and documentation practices in place?

73Good · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — .rubocop.yml
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 29 out of 30 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

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 6 topics
0/10Wiki
Inputs used
topicsgrape, grape-api, sorbet, tapioca, api, ruby
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?

78Good · 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
2.2/2.5CI-Tests — 29 out of 30 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
1.5/7.5Code-Review — Found 2/10 approved changesets -- score normalized to 2
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
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
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
4/5SAST — SAST tool is not run on all commits -- score normalized to 8
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate7.3
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
advisories0
affected_packages0
assessed_packages73
unassessed_packages3
affected_by_severitynone
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 73 resolved dependencies against OSV. 3 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.

57Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 32 of 40 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.8
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .rubocop.yml
0/11Static type checking
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 6 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 60 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.06
toolchain_manifests—
dependency_bot_commit_share0.6
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/10 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes14,231
source_files_sampled10
oversized_source_files0

Key facts

6GitHub stars
3contributors
91commits, last 12 months
2days since last push
21releases
1bus factor
2open issues
RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

OpenSSF Scorecard 7.3 / 10
7.3aggregate

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-11-18 15:37 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
9CI-Tests29 out of 30 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 2/10 approved changesets -- score normalized to 2
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
8SASTSAST tool is not run on all commits -- score normalized to 8
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
RubyGemsrake~> 13.0Gemfile
All dependencies 76

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

RegistryPackageVersionRelation
RubyGemsrake13.4.2direct
RubyGemsactivesupport—indirect
RubyGemsactivesupport8.1.4.1indirect
RubyGemsansi1.6.0indirect
RubyGemsast2.4.3indirect
RubyGemsbase640.3.0indirect
RubyGemsbenchmark0.5.0indirect
RubyGemsbigdecimal4.1.3indirect
RubyGemsbuilder3.3.0indirect
RubyGemsbundler-audit0.9.3indirect
RubyGemsconcurrent-ruby1.3.8indirect
RubyGemsconnection_pool3.0.2indirect
RubyGemsdrb2.2.3indirect
RubyGemsdry-configurable1.4.0indirect
RubyGemsdry-core1.2.0indirect
RubyGemsdry-inflector1.3.1indirect
RubyGemsdry-logic1.6.0indirect
RubyGemsdry-types1.9.1indirect
RubyGemserb6.0.7indirect
RubyGemserubi1.13.1indirect
RubyGemsgrape—indirect
RubyGemsgrape4.1.0indirect
RubyGemsgrape-entity1.1.0indirect
RubyGemsi18n1.15.2indirect
RubyGemsio-console0.9.5indirect
RubyGemsirb1.19.0indirect
RubyGemsjson3.1.0indirect
RubyGemslanguage_server-protocol3.17.0.6indirect
RubyGemslint_roller1.1.0indirect
RubyGemslogger1.7.0indirect
RubyGemsminitest6.1.0indirect
RubyGemsminitest-reporters1.8.0indirect
RubyGemsmocha3.1.0indirect
RubyGemsmustermann4.0.1indirect
RubyGemsnetrc0.11.0indirect
RubyGemsparallel2.3.0indirect
RubyGemsparser3.3.13.0indirect
RubyGemspp0.6.4indirect
RubyGemsprettyprint0.2.1indirect
RubyGemsprism1.9.0indirect
RubyGemsracc1.8.1indirect
RubyGemsrack3.2.8indirect
RubyGemsrainbow3.1.1indirect
RubyGemsrbi0.5.0indirect
RubyGemsrbs4.2.0indirect
RubyGemsrdoc8.1.0indirect
RubyGemsregexp_parser2.13.1indirect
RubyGemsreline0.7.0indirect
RubyGemsrequire-hooks0.5.1indirect
RubyGemsrexml3.4.4indirect
RubyGemsrubocop1.92.2indirect
RubyGemsrubocop-ast1.50.0indirect
RubyGemsrubocop-minitest0.41.0indirect
RubyGemsrubocop-performance1.27.0indirect
RubyGemsrubocop-rake0.7.1indirect
RubyGemsrubocop-shopify3.1.0indirect
RubyGemsrubocop-sorbet0.17.2indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemsruby2_keywords0.0.5indirect
RubyGemsrubydex0.4.2indirect
RubyGemssecurerandom0.4.1indirect
RubyGemssimplecov1.3.2indirect
RubyGemssorbet0.6.13672indirect
RubyGemssorbet-runtime—indirect
RubyGemssorbet-runtime0.6.13672indirect
RubyGemssorbet-static0.6.13672indirect
RubyGemssorbet-static-and-runtime0.6.13672indirect
RubyGemsspoom1.8.12indirect
RubyGemstapioca0.20.0indirect
RubyGemsthor1.5.0indirect
RubyGemstsort0.2.0indirect
RubyGemstzinfo2.0.6indirect
RubyGemsunicode-display_width3.3.0indirect
RubyGemsunicode-emoji4.3.0indirect
RubyGemsuri1.1.2indirect
RubyGemszeitwerk2.8.3indirect
Dependency advisories 0

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

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 — RubyGems.