Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-21 17:47 UTC

thoughtbot / shoulda

Makes tests easy on the fingers and the eyes

RubyMIT★ 2,204 stars⑂ 183 forkssince Apr 2008View on GitHub ↗

thoughtbot/shoulda holds a health index of 48 out of 100, placing it in the Weak band. It scores highest on Community & Adoption (81/100) and lowest on Vitality (10/100). It was last updated 455 days ago. 2 contributors account for most of its recent work.

48
overall / 100
Weak

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.

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

Ownership

thoughtbot, inc.Organization
895 followers472 public repossince Apr 2008

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsshoulda4.0.0-341246 days ago

Metrics by category

Vitality

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

10Critical · 21% of overall
How it's scored
0/36Push recencylast push 455 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share0.95
days_since_last_push455
active_weeks_last_year0
How it's scored
16.2/27Ships releases30 version tags (no GitHub releases)
0/36Release recencylatest release 2,259 days ago
5.4/27Release cadencea release every ~492.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count30
latest_release_tagv4.0.0
releases_from_tagsyes
days_since_latest_release2,259
mean_days_between_releases492.1
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?

81Excellent · 17% of overall
How it's scored
54.2/60Stars2,204 stars
18.8/25Forks183 forks
9.6/15Watchers54 watchers
Inputs used
forks183
stars2,204
watchers54
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
79.7/80Total downloads46,874,708 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesshoulda
dependents
ecosystemsrubygems
total_downloads46,874,708
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?

75Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
14.5/22.5Commit distributiontop contributor authored 36% of commits
13.5/13.5Contributor breadth56 contributors
10/10OpenSSF Scorecard: Contributorsproject has 42 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled56
top_contributor_share0.357
How it's scored
41.7/42Issue resolution99% of issues closed
20.2/30PR acceptance35/52 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 3/17 approved changesets -- score normalized to 1
Inputs used
merged_prs35
open_issues2
closed_issues236
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.992
closed_unmerged_prs17
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 backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
21.2/25Owner reach895 followers of thoughtbot
25/25Track record472 public repos, account ~18 yr old
Inputs used
followers895
owner_typeOrganization
is_verified
owner_loginthoughtbot
public_repos472
account_age_days6,706
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on rubygems
4/35Publish recencylatest publish 1,246 days ago
20/20Version history34 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesshoulda
ecosystemsrubygems
any_deprecatedno
min_days_since_publish1,246

Engineering Quality

Are baseline engineering and documentation practices in place?

60Moderate · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 15 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttp://www.thoughtbot.com/community
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepagehttp://www.thoughtbot.com/community
docs_sitehttp://www.thoughtbot.com/community
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

51Moderate · 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
0/2.5CI-Tests0 out of 15 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 3/17 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 42 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.9
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 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
advisories0
affected_packages0
assessed_packages1
unassessed_packages14
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 1 resolved dependencies against OSV. 14 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.

33At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
21.9/40Legible commit history39 of 95 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.411
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
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/13 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes17,555
source_files_sampled13
oversized_source_files0

Key facts

2,204GitHub stars
56contributors
0commits, last 12 months
455days since last push
30releases
2bus factor
2open issues
RubyGemspackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 183 ⇿
0Stars
183Forks
29Releases

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.

0408012016020017162008-052017-052026-05
Major 3Minor 9Patch 17

Each point covers 17 days.

OpenSSF Scorecard 3.9 / 10
3.9aggregate

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-21 17:46 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 15 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 3/17 approved changesets -- score normalized to 1
10Contributorsproject has 42 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 13
RegistryPackageVersion constraintManifest
RubyGemsappraisalGemfile
RubyGemsmGemfile
RubyGemsminitest~> 5.0Gemfile
RubyGemsminitest-reporters~> 1.0Gemfile
RubyGemspryGemfile
RubyGemspry-byebugGemfile
RubyGemsrake13.0.1Gemfile
RubyGemsrspec~> 3.9Gemfile
RubyGemsrubocopGemfile
RubyGemsrubocop-packagingGemfile
RubyGemsrubocop-railsGemfile
RubyGemssnowglobeGemfile
RubyGemswarnings_loggerGemfile
All dependencies 15

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

RegistryPackageVersionRelation
RubyGemsappraisaldirect
RubyGemsmdirect
RubyGemsminitestdirect
RubyGemsminitest-reportersdirect
RubyGemsprydirect
RubyGemspry-byebugdirect
RubyGemsrake13.0.1direct
RubyGemsrspecdirect
RubyGemsrubocopdirect
RubyGemsrubocop-packagingdirect
RubyGemsrubocop-railsdirect
RubyGemssnowglobedirect
RubyGemswarnings_loggerdirect
RubyGemsshoulda-contextindirect
RubyGemsshoulda-matchersindirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 1 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 14 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 statisticsRubyGems.