Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 01:22 UTC

thoughtbot / appraisal

A Ruby library for testing your library against different versions of dependencies.

RubyMIT★ 1,324 stars⑂ 114 forkssince Nov 2010View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

thoughtbot/appraisal holds a health index of 57 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (84/100) and lowest on Vitality (20/100). It was last updated 311 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

thoughtbot, inc.Organization
889 followers469 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
RubyGemsappraisal2.5.0-30629 days ago

Metrics by category

Vitality

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

20At Risk · 21% of overall
How it's scored
3.6/36Push recencylast push 311 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_share
days_since_last_push311
active_weeks_last_year0
How it's scored
27/27Ships releases13 releases published
7.2/36Release recencylatest release 629 days ago
5.4/27Release cadencea release every ~387.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count13
latest_release_tagv3.0.0.rc1
releases_from_tagsno
days_since_latest_release629
mean_days_between_releases387.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?

84Excellent · 17% of overall
How it's scored
50.6/60Stars1,324 stars
17.1/25Forks114 forks
8.9/15Watchers41 watchers
Inputs used
forks114
stars1,324
watchers41
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
74.5/80Total downloads14,797,926 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesappraisal
dependents
ecosystemsrubygems
total_downloads14,797,926
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?

77Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
11.4/22.5Commit distributiontop contributor authored 49% of commits
13.5/13.5Contributor breadth60 contributors
10/10OpenSSF Scorecard: Contributorsproject has 23 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled60
top_contributor_share0.492
How it's scored
38.6/42Issue resolution92% of issues closed
17.8/30PR acceptance76/128 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
12/15OpenSSF Scorecard: Code-ReviewFound 24/28 approved changesets -- score normalized to 8
Inputs used
merged_prs76
open_issues10
closed_issues113
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.919
closed_unmerged_prs52
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
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 reach889 followers of thoughtbot
25/25Track record469 public repos, account ~18 yr old
Inputs used
followers889
owner_typeOrganization
is_verified
owner_loginthoughtbot
public_repos469
account_age_days6,671
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on rubygems
14/35Publish recencylatest publish 629 days ago
20/20Version history30 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesappraisal
ecosystemsrubygems
any_deprecatedno
min_days_since_publish629

Engineering Quality

Are baseline engineering and documentation practices in place?

55Moderate · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 28 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://thoughtbot.com
10/10Repository description
10/10Topics6 topics
0/10Wiki
Inputs used
topicsruby, thoughtbot, appraisal, rubygems, testing, gemfile
has_wikino
homepagehttps://thoughtbot.com
docs_sitehttps://thoughtbot.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

44Weak · 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 28 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
6/7.5Code-ReviewFound 24/28 approved changesets -- score normalized to 8
2.5/2.5Contributorsproject has 23 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_aggregate4.4
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.

23At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
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_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/45 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes10,122
source_files_sampled45
oversized_source_files0

Key facts

1,324GitHub stars
60contributors
0commits, last 12 months
311days since last push
13releases
2bus factor
10open issues
RubyGemspackage ecosystems

More detail

OpenSSF Scorecard 4.4 / 10
4.4aggregate

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-07-17 01:22 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 28 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 24/28 approved changesets -- score normalized to 8
10Contributorsproject has 23 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 1
RegistryPackageVersion constraintManifest
RubyGemsthor~> 0.14.0Gemfile
All dependencies 5

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

RegistryPackageVersionRelation
RubyGemsthordirect
RubyGemsactivesupportindirect
RubyGemsbundlerindirect
RubyGemsrakeindirect
RubyGemsrspecindirect
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.11.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsRubyGems.