Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-01 18:33 UTC

beehiiv / has_state_machine

Simple and flexible state machines for your ActiveRecord classes

RubyMIT★ 15 stars⑂ 1 forksince Sep 2020View on GitHub ↗
KindLibraryNetwork servicehow this is determined

beehiiv/has_state_machine holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Vitality (75/100) and lowest on Community & Adoption (43/100). It was last updated today. 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

beehiivOrganization
35 followers15 public repossince Oct 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemshas_state_machinepoints to another repo — not scored1.3.0-170 days ago

Metrics by category

Vitality

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

75Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
2.1/36Commit cadence — 3/52 weeks with commits
10.8/18Commit volume — 15 commits in the last year
9/10OpenSSF Scorecard: Maintained — 11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
Inputs used
commits_last_year15
human_commit_share0.918
days_since_last_push0
active_weeks_last_year3

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 3 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~39.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count3
latest_release_tagv1.3.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases39.8
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
18.6/60Stars — 15 stars
0/25Forks — 1 forks
4.7/15Watchers — 8 watchers
Inputs used
forks1
stars15
watchers8
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
0/13.5Code of conduct
7.2/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingno
has_issue_templateyes
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes

Sustainability & Governance

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

50Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
9.9/22.5Commit distribution — top contributor authored 56% of commits
5.4/13.5Contributor breadth — 4 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.561
How it's scored
0/42Issue resolution — no issues or no data
20/30PR acceptance — 44/66 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
7.5/15OpenSSF Scorecard: Code-Review — Found 15/29 approved changesets -- score normalized to 5
Inputs used
merged_prs44
open_issues0
closed_issues0
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio—
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): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
11.2/25Owner reach — 35 followers of beehiiv
20.7/25Track record — 15 public repos, account ~5 yr old
Inputs used
followers35
owner_typeOrganization
is_verifiedno
owner_loginbeehiiv
public_repos15
account_age_days2,170

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 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
0/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests — 11 out of 18 merged PRs checked by a CI test -- score normalized to 6
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 3 topics
10/10Wiki
Inputs used
topicsstate-machine, ruby, activerecord
has_wikiyes
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?

61Moderate · 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
1.5/2.5CI-Tests — 11 out of 18 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3.8/7.5Code-Review — Found 15/29 approved changesets -- score normalized to 5
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
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
6.8/7.5Maintained — 11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
5/5Packaging — packaging workflow detected
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 — 17 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.1
Excluded from scoring (no data or not applicable): 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
advisories17
affected_packages5
assessed_packages95
unassessed_packages18
affected_by_severitycritical 1, high 1, moderate 1, low 2
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 95 resolved dependencies against OSV. 18 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.

46Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
31.8/40Legible commit history — 40 of 67 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.597
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
2.7/10Demonstrated agent practice — 1 of the last 73 commits agent-authored or agent-credited
8/8Automated maintenance — 5 of the last 73 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_configyes
typecheck_configs—
agent_commit_share0.014
toolchain_manifests—
dependency_bot_commit_share0.068
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/59 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes27,574
source_files_sampled59
oversized_source_files0

Key facts

15GitHub stars
4contributors
15commits, last 12 months
0days since last push
3releases
1bus factor
0open issues
RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • rubygems package 'has_state_machine' points at a different repository (https://www.github.com/encampment/has_state_machine); excluded from ecosystem scoring

More detail

OpenSSF Scorecard 5.1 / 10
5.1aggregate

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-01 18:32 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
6CI-Tests11 out of 18 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 15/29 approved changesets -- score normalized to 5
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
9Maintained11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
10Packagingpackaging workflow 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
0Vulnerabilities17 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
RubyGemsrails~> 7.2Gemfile
All dependencies 113

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

RegistryPackageVersionRelation
RubyGemsrails—direct
RubyGemsrails7.2.3.1direct
RubyGemsactioncable7.2.3.1indirect
RubyGemsactionmailbox7.2.3.1indirect
RubyGemsactionmailer7.2.3.1indirect
RubyGemsactionpack7.2.3.1indirect
RubyGemsactiontext7.2.3.1indirect
RubyGemsactionview7.2.3.1indirect
RubyGemsactivejob7.2.3.1indirect
RubyGemsactivemodel7.2.3.1indirect
RubyGemsactiverecord7.2.3.1indirect
RubyGemsactivestorage7.2.3.1indirect
RubyGemsactivesupport7.2.3.1indirect
RubyGemsappraisal—indirect
RubyGemsappraisal2.5.0indirect
RubyGemsast2.4.3indirect
RubyGemsbase64—indirect
RubyGemsbase640.3.0indirect
RubyGemsbenchmark0.5.0indirect
RubyGemsbigdecimal—indirect
RubyGemsbigdecimal4.1.2indirect
RubyGemsbuilder3.3.0indirect
RubyGemscgi0.5.2indirect
RubyGemscoderay1.1.3indirect
RubyGemsconcurrent-ruby1.3.7indirect
RubyGemsconnection_pool3.0.2indirect
RubyGemscrass1.0.7indirect
RubyGemsdate3.5.1indirect
RubyGemsdiff-lcs1.6.2indirect
RubyGemsdrb—indirect
RubyGemsdrb2.2.3indirect
RubyGemserb6.0.4indirect
RubyGemserubi1.13.1indirect
RubyGemsglobalid1.4.0indirect
RubyGemsi18n1.15.2indirect
RubyGemsio-console0.8.2indirect
RubyGemsirb1.18.0indirect
RubyGemsjson—indirect
RubyGemsjson2.20.0indirect
RubyGemslanguage_server-protocol3.17.0.5indirect
RubyGemslint_roller1.1.0indirect
RubyGemslogger1.7.0indirect
RubyGemsloofah2.25.1indirect
RubyGemsmail2.9.1indirect
RubyGemsmarcel1.2.1indirect
RubyGemsmethod_source1.1.0indirect
RubyGemsmini_mime1.1.5indirect
RubyGemsmini_portile22.8.9indirect
RubyGemsminitest5.27.0indirect
RubyGemsmutex_m—indirect
RubyGemsmutex_m0.3.0indirect
RubyGemsnet-imap0.6.4.1indirect
RubyGemsnet-pop0.1.2indirect
RubyGemsnet-protocol0.2.2indirect
RubyGemsnet-smtp0.5.1indirect
RubyGemsnio4r2.7.5indirect
RubyGemsnokogiri—indirect
RubyGemsnokogiri1.18.10indirect
RubyGemsparallel—indirect
RubyGemsparallel1.28.0indirect
RubyGemsparser3.3.11.1indirect
RubyGemspp0.6.4indirect
RubyGemsprettyprint0.2.0indirect
RubyGemsprism1.9.0indirect
RubyGemspry—indirect
RubyGemspry0.16.0indirect
RubyGemspry-rails—indirect
RubyGemspry-rails0.3.11indirect
RubyGemsracc1.8.1indirect
RubyGemsrack3.2.6indirect
RubyGemsrack-session2.1.2indirect
RubyGemsrack-test2.2.0indirect
RubyGemsrackup2.3.1indirect
RubyGemsrails-dom-testing2.3.0indirect
RubyGemsrails-html-sanitizer1.7.0indirect
RubyGemsrailties7.2.3.1indirect
RubyGemsrainbow3.1.1indirect
RubyGemsrake13.4.2indirect
RubyGemsrbs4.0.3indirect
RubyGemsrdoc8.0.0indirect
RubyGemsregexp_parser2.12.0indirect
RubyGemsreline0.6.3indirect
RubyGemsrspec-core3.13.6indirect
RubyGemsrspec-expectations3.13.5indirect
RubyGemsrspec-mocks3.13.8indirect
RubyGemsrspec-rails—indirect
RubyGemsrspec-rails7.1.1indirect
RubyGemsrspec-support3.13.7indirect
RubyGemsrubocop—indirect
RubyGemsrubocop1.87.0indirect
RubyGemsrubocop-ast1.49.1indirect
RubyGemsrubocop-performance—indirect
RubyGemsrubocop-performance1.26.1indirect
RubyGemsruby-lsp—indirect
RubyGemsruby-lsp0.26.9indirect
RubyGemsruby-lsp-rails—indirect
RubyGemsruby-lsp-rails0.4.8indirect
RubyGemsruby-lsp-rspec—indirect
RubyGemsruby-lsp-rspec0.1.29indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemssecurerandom0.4.1indirect
RubyGemssqlite3—indirect
RubyGemssqlite32.9.5indirect
RubyGemsthor1.5.0indirect
RubyGemstimeout0.6.1indirect
RubyGemstsort0.2.0indirect
RubyGemstzinfo2.0.6indirect
RubyGemsunicode-display_width3.2.0indirect
RubyGemsunicode-emoji4.2.0indirect
RubyGemsuseragent0.16.11indirect
RubyGemswebsocket-driver0.8.2indirect
RubyGemswebsocket-extensions0.1.5indirect
RubyGemszeitwerk2.8.2indirect
Dependency advisories 5

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

PackageVersionRelationSeverityAdvisoriesFixed in
activestorage7.2.3.1indirectcritical18.1.3.1
nokogiri1.18.10indirecthigh111.19.4
loofah2.25.1indirectmoderate32.25.2
json2.20.0indirectlow12.21.2
rails-html-sanitizer1.7.0indirectlow11.7.1

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.