Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 02:16 UTC

thoughtbot / factory_bot

A library for setting up Ruby objects as test data.

RubyMIT★ 8,169 stars⑂ 2,552 forkssince Jun 2008View on GitHub ↗

thoughtbot/factory_bot holds a health index of 90 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (94/100) and lowest on AI Readiness (55/100). It was last updated 6 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

thoughtbot, inc.Organization · verified domain
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
RubyGemsfactory_bot6.6.0-37115 days ago

Metrics by category

Vitality

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

72Good · 21% of overall
How it's scored
36/36Push recency — last push 6 days ago
11.1/36Commit cadence — 16/52 weeks with commits
14.3/18Commit volume — 38 commits in the last year
4/10OpenSSF Scorecard: Maintained — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
Inputs used
commits_last_year38
human_commit_share0.91
days_since_last_push6
active_weeks_last_year16
How it's scored
27/27Ships releases — 33 releases published
27/36Release recency — latest release 115 days ago
19.8/27Release cadence — a release every ~95.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count33
latest_release_tagv6.6.0
releases_from_tagsno
days_since_latest_release115
mean_days_between_releases95.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?

94Exceptional · 17% of overall
How it's scored
60/60Stars — 8,169 stars
25/25Forks — 2,552 forks
11.6/15Watchers — 121 watchers
Inputs used
forks2,552
stars8,169
watchers121
growth_stateorganic
growth_factor_pct100

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateno
How it's scored
80/80Total downloads — 349,995,633 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesfactory_bot
dependents—
ecosystemsrubygems
total_downloads349,995,633
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?

82Excellent · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
13/22.5Commit distribution — top contributor authored 42% of commits
13.5/13.5Contributor breadth — 98 contributors
10/10OpenSSF Scorecard: Contributors — project has 61 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled98
top_contributor_share0.421
How it's scored
39.1/42Issue resolution — 93% of issues closed
15.1/30PR acceptance — 418/830 decided PRs merged
13/13Newcomer PR acceptance — 3/3 first-time contributors' PRs merged in 30d
10.5/15OpenSSF Scorecard: Code-Review — Found 18/23 approved changesets -- score normalized to 7
Inputs used
merged_prs418
open_issues66
closed_issues905
prs_merged_7d3
prs_decided_7d3
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio0.932
closed_unmerged_prs412
first_time_authors_30d3
first_time_prs_merged_30d3
first_time_prs_decided_30d3
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
21.2/25Owner reach — 895 followers of thoughtbot
25/25Track record — 472 public repos, account ~18 yr old
Inputs used
followers895
owner_typeOrganization
is_verifiedyes
owner_loginthoughtbot
public_repos472
account_age_days6,713

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

77Good · 19% of overall
How it's scored
24/24CI workflows — 7 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
14/20OpenSSF Scorecard: CI-Tests — 19 out of 26 merged PRs checked by a CI test -- score normalized to 7
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://thoughtbot.com
10/10Repository description
10/10Topics — 9 topics
10/10Wiki
Inputs used
topicsfactory-girl, ruby, thoughtbot, rubygems, testing, fixtures, factories, rails, factory-bot
has_wikiyes
homepagehttps://thoughtbot.com
docs_sitehttps://thoughtbot.com
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

59Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
1.8/2.5CI-Tests — 19 out of 26 merged PRs checked by a CI test -- score normalized to 7
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
5.2/7.5Code-Review — Found 18/23 approved changesets -- score normalized to 7
2.5/2.5Contributors — project has 61 contributing companies or organizations
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
3/7.5Maintained — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
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
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 12 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.3
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
22.4/35Direct dependencies free of known advisories — 1 affected: sqlite3 2.5.0 (moderate 4.5)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories12
affected_packages5
assessed_packages70
unassessed_packages12
affected_by_severityhigh 3, moderate 2
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 70 resolved dependencies against OSV. 12 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.

55Moderate · 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 — 75 of 91 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.824
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 8 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 4 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.08
toolchain_manifests—
dependency_bot_commit_share0.04
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/144 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes31,477
source_files_sampled144
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — cookbook
Inputs used
example_dirscookbook
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

8,169GitHub stars
98contributors
38commits, last 12 months
6days since last push
33releases
2bus factor
66open issues
RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-07-21: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 8169 stars today.

More detail

Star and fork history 8,182 ★ / 2,552 ⇿
8,182Stars
2,552Forks
26Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

Star history is shown as collected on 2026-07-21. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

1,2502,5003,7505,0006,2507,5008,7508,1822,552142019-072023-022026-08
Major 1Minor 8Patch 17

Each point covers 7 days.

OpenSSF Scorecard 5.3 / 10
5.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-08-28 02:15 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
7CI-Tests19 out of 26 merged PRs checked by a CI test -- score normalized to 7
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 18/23 approved changesets -- score normalized to 7
10Contributorsproject has 61 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
4Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
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
0Vulnerabilities12 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
RubyGemsactiverecord-jdbcsqlite3-adapter—Gemfile
RubyGemssqlite3—Gemfile
All dependencies 82

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

RegistryPackageVersionRelation
RubyGemssqlite32.5.0direct
RubyGemsactivemodel8.0.3indirect
RubyGemsactiverecord—indirect
RubyGemsactiverecord8.0.3indirect
RubyGemsactivesupport—indirect
RubyGemsactivesupport8.0.3indirect
RubyGemsappraisal—indirect
RubyGemsappraisal2.5.0indirect
RubyGemsaruba—indirect
RubyGemsaruba2.3.2indirect
RubyGemsast2.4.3indirect
RubyGemsbase640.3.0indirect
RubyGemsbenchmark0.4.1indirect
RubyGemsbigdecimal3.3.1indirect
RubyGemsbuilder3.3.0indirect
RubyGemsconcurrent-ruby1.3.5indirect
RubyGemsconnection_pool2.5.4indirect
RubyGemscontracts0.17.3indirect
RubyGemscucumber10.1.1indirect
RubyGemscucumber-ci-environment10.0.1indirect
RubyGemscucumber-core15.2.1indirect
RubyGemscucumber-cucumber-expressions18.0.1indirect
RubyGemscucumber-gherkin32.2.0indirect
RubyGemscucumber-html-formatter21.15.1indirect
RubyGemscucumber-messages27.2.0indirect
RubyGemscucumber-tag-expressions6.1.2indirect
RubyGemsdiff-lcs1.6.2indirect
RubyGemsdocile1.4.1indirect
RubyGemsdrb2.2.3indirect
RubyGemsffi1.17.2indirect
RubyGemsi18n1.14.7indirect
RubyGemsjson2.15.1indirect
RubyGemslanguage_server-protocol3.17.0.5indirect
RubyGemslint_roller1.1.0indirect
RubyGemslogger1.7.0indirect
RubyGemsmemoist31.0.0indirect
RubyGemsmini_mime1.1.5indirect
RubyGemsmini_portile22.8.8indirect
RubyGemsminitest6.0.6indirect
RubyGemsmulti_test1.1.0indirect
RubyGemsmutex_m—indirect
RubyGemsmutex_m0.3.0indirect
RubyGemsostruct—indirect
RubyGemsostruct0.6.3indirect
RubyGemsparallel1.27.0indirect
RubyGemsparser3.3.9.0indirect
RubyGemsprism1.5.2indirect
RubyGemsracc1.8.1indirect
RubyGemsrainbow3.1.1indirect
RubyGemsrake—indirect
RubyGemsrake13.3.0indirect
RubyGemsregexp_parser2.11.3indirect
RubyGemsrspec—indirect
RubyGemsrspec3.13.1indirect
RubyGemsrspec-core3.13.5indirect
RubyGemsrspec-expectations3.13.5indirect
RubyGemsrspec-its—indirect
RubyGemsrspec-its2.0.0indirect
RubyGemsrspec-mocks3.13.5indirect
RubyGemsrspec-support3.13.6indirect
RubyGemsrubocop1.80.2indirect
RubyGemsrubocop-ast1.47.1indirect
RubyGemsrubocop-performance1.25.0indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemssecurerandom0.4.1indirect
RubyGemssimplecov—indirect
RubyGemssimplecov0.22.0indirect
RubyGemssimplecov-html0.13.2indirect
RubyGemssimplecov_json_formatter0.1.4indirect
RubyGemsstandard—indirect
RubyGemsstandard1.51.1indirect
RubyGemsstandard-custom1.0.2indirect
RubyGemsstandard-performance1.8.0indirect
RubyGemssys-uname1.4.1indirect
RubyGemsthor1.4.0indirect
RubyGemstimeout0.4.3indirect
RubyGemstzinfo2.0.6indirect
RubyGemsunicode-display_width3.2.0indirect
RubyGemsunicode-emoji4.2.0indirect
RubyGemsuri1.0.4indirect
RubyGemsyard—indirect
RubyGemsyard0.9.37indirect
Dependency advisories 5

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

PackageVersionRelationSeverityAdvisoriesFixed in
activesupport8.0.3indirecthigh38.1.2.1
concurrent-ruby1.3.5indirecthigh31.3.7
json2.15.1indirecthigh22.19.9
sqlite32.5.0directmoderate22.9.5
yard0.9.37indirectmoderate20.9.44

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.