Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-08 12:31 UTC

castle / castle-ruby

Ruby gem for Castle

RubyMIT★ 36 stars⑂ 17 forkssince Sep 2013View on GitHub ↗

castle/castle-ruby holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (84/100) and lowest on Community & Adoption (54/100). It was last updated today. 2 contributors account for most of its recent work.

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

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

Ownership

CastleOrganization · verified domain
17 followers58 public repossince Jul 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemscastle-rb9.3.0-680 days ago

Metrics by category

Vitality

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

60Moderate · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
2.8/36Commit cadence — 4/52 weeks with commits
9/18Commit volume — 9 commits in the last year
2/10OpenSSF Scorecard: Maintained — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Inputs used
commits_last_year9
human_commit_share0.98
days_since_last_push0
active_weeks_last_year4
How it's scored
27/27Ships releases — 39 releases published
36/36Release recency — latest release 0 days ago
12.6/27Release cadence — a release every ~212.3 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count39
latest_release_tagv9.3.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases212.3

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

54Moderate · 17% of overall
How it's scored
25/60Stars — 36 stars
10/25Forks — 17 forks
6.5/15Watchers — 16 watchers
Inputs used
forks17
stars36
watchers16
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
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, github.com
has_pull_request_templateno
How it's scored
63.2/80Total downloads — 1,212,082 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagescastle-rb
dependents—
ecosystemsrubygems
total_downloads1,212,082
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?

84Excellent · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
14.5/22.5Commit distribution — top contributor authored 35% of commits
13.5/13.5Contributor breadth — 27 contributors
10/10OpenSSF Scorecard: Contributors — project has 14 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled27
top_contributor_share0.354
How it's scored
42/42Issue resolution — 100% of issues closed
27.7/30PR acceptance — 249/270 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs249
open_issues0
closed_issues21
prs_merged_7d2
prs_decided_7d2
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio1
closed_unmerged_prs21
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
9/25Owner reach — 17 followers of castle
24.9/25Track record — 58 public repos, account ~13 yr old
Inputs used
followers17
owner_typeOrganization
is_verifiedyes
owner_logincastle
public_repos58
account_age_days4,795

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

68Good · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — .rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
6/20OpenSSF Scorecard: CI-Tests — 8 out of 21 merged PRs checked by a CI test -- score normalized to 3
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://castle.io
10/10Repository description
10/10Topics — 5 topics
0/10Wiki
Inputs used
topicscastle, ruby, sdk, fraud-detection, fraud-prevention
has_wikino
homepagehttps://castle.io
docs_sitehttps://castle.io
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
0/7.5Branch-Protection — no data
0.8/2.5CI-Tests — 8 out of 21 merged PRs checked by a CI test -- score normalized to 3
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 14 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
1.5/7.5Maintained — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
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
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.1
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. 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_packages55
unassessed_packages1
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 55 resolved dependencies against OSV. 1 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.

61Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://castle.io/llms.txt)
37.6/40Legible commit history — 69 of 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://castle.io/llms.txt
legible_history_share0.704
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — mise.toml
22/22Automated tests
11/11Lint / format config — .rubocop.yml
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 2 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, yarn.lock
has_dockerfileno
typed_languageno
bootstrap_filesmise.toml
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.02
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/173 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes5,732
source_files_sampled173
oversized_source_files0

Key facts

36GitHub stars
27contributors
9commits, last 12 months
0days since last push
39releases
2bus factor
0open issues
npm, 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 ★ / 17 ⇿
0Stars
17Forks
34Releases

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.

0481216201722013-112019-052024-10
Major 6Minor 14Patch 14

Each point covers 10 days.

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-09-08 12:31 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
3CI-Tests8 out of 21 merged PRs checked by a CI test -- score normalized to 3
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 14 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
2Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
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
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
RubyGemsrack—Gemfile
RubyGemsrake—Gemfile
All dependencies 56

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

RegistryPackageVersionRelation
RubyGemsrack3.2.7direct
RubyGemsrake13.4.2direct
npm@prettier/plugin-ruby4.0.4indirect
npmprettier3.9.6indirect
RubyGemsaddressable2.9.0indirect
RubyGemsast2.4.3indirect
RubyGemsbase64—indirect
RubyGemsbase640.3.0indirect
RubyGemsbigdecimal4.1.2indirect
RubyGemscrack1.0.1indirect
RubyGemsdate3.5.1indirect
RubyGemsdebug1.11.1indirect
RubyGemsdiff-lcs1.6.2indirect
RubyGemsdocile1.4.1indirect
RubyGemserb6.0.7indirect
RubyGemshashdiff1.2.1indirect
RubyGemsio-console0.9.2indirect
RubyGemsirb1.18.0indirect
RubyGemsjson2.21.2indirect
RubyGemslanguage_server-protocol3.17.0.6indirect
RubyGemslint_roller1.1.0indirect
RubyGemsparallel2.2.0indirect
RubyGemsparser3.3.12.0indirect
RubyGemspp0.6.4indirect
RubyGemsprettier_print1.2.1indirect
RubyGemsprettyprint0.2.0indirect
RubyGemsprism1.9.0indirect
RubyGemspsych5.5.0indirect
RubyGemspublic_suffix7.0.5indirect
RubyGemsracc1.8.1indirect
RubyGemsrainbow3.1.1indirect
RubyGemsrdoc7.2.0indirect
RubyGemsregexp_parser2.12.0indirect
RubyGemsreline0.7.0indirect
RubyGemsrexml3.4.4indirect
RubyGemsrspec3.13.2indirect
RubyGemsrspec-core3.13.6indirect
RubyGemsrspec-expectations3.13.5indirect
RubyGemsrspec-mocks3.13.8indirect
RubyGemsrspec-support3.13.7indirect
RubyGemsrubocop1.90.0indirect
RubyGemsrubocop-ast1.50.0indirect
RubyGemsrubocop-performance1.27.0indirect
RubyGemsrubocop-rake0.7.1indirect
RubyGemsrubocop-rspec3.10.2indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemssimplecov0.22.0indirect
RubyGemssimplecov-html0.13.2indirect
RubyGemssimplecov_json_formatter0.1.4indirect
RubyGemsstringio3.2.0indirect
RubyGemssyntax_tree6.3.0indirect
RubyGemstimecop0.9.11indirect
RubyGemstsort0.2.0indirect
RubyGemsunicode-display_width3.2.0indirect
RubyGemsunicode-emoji4.2.0indirect
RubyGemswebmock3.26.4indirect
Dependency advisories 0

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