Public record
Software health reportschema 0.27.0 · metrics 2.10.0 · 2026-07-30 14:47 UTC

pay-rails / pay

Payments for Ruby on Rails apps

RubyMIT★ 2,249 stars⑂ 355 forkssince Feb 2017View on GitHub ↗
KindLibraryhow this is determined
#subscription#stripe#pay#engine#rails#payment-provider#braintree#sca#paddle#payments#hacktoberfest

pay-rails/pay holds a health index of 89 out of 100, placing it in the Excellent band. It scores highest on Vitality (89/100) and lowest on AI Readiness (38/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

PayOrganization
26 followers1 public reposince Aug 2019

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemspay11.7.0-1570 days ago

Metrics by category

Vitality

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

89Excellent · 21% of overall

Development activity

81Excellent
How it's scored
36/36Push recency — last push 0 days ago
17.3/36Commit cadence — 25/52 weeks with commits
17.5/18Commit volume — 87 commits in the last year
10/10OpenSSF Scorecard: Maintained — 18 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year87
human_commit_share1
days_since_last_push0
active_weeks_last_year25

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 70 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~39 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count70
latest_release_tagv11.7.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases39
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?

74Good · 17% of overall

Popularity & adoption

83Excellent
How it's scored
54.4/60Stars — 2,249 stars
21.2/25Forks — 355 forks
7.8/15Watchers — 26 watchers
Inputs used
forks355
stars2,249
watchers26
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

57Moderate
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
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges—
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateyes

Ecosystem adoption (downloads)

82Excellent
How it's scored
65.2/80Total downloads — 1,892,301 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagespay
dependents—
ecosystemsrubygems
total_downloads1,892,301
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?

67Good · 23% of overall

Maintainer resilience (bus factor)

37Weak
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
4.9/22.5Commit distribution — top contributor authored 78% of commits
13.5/13.5Contributor breadth — 98 contributors
10/10OpenSSF Scorecard: Contributors — project has 20 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled98
top_contributor_share0.784

Issue & PR responsiveness

77Good
How it's scored
42/42Issue resolution — 100% of issues closed
21.9/30PR acceptance — 489/670 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-Review — Found 6/26 approved changesets -- score normalized to 2
Inputs used
merged_prs489
open_issues0
closed_issues385
prs_merged_7d—
prs_decided_7d—
prs_merged_30d—
prs_decided_30d—
issue_closed_ratio1
closed_unmerged_prs181
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.

Ownership & stewardship

68Good
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain — verified-domain status not read for this organization
10.3/25Owner reach — 26 followers of pay-rails
14.2/25Track record — 1 public repos, account ~6 yr old
Inputs used
followers26
owner_typeOrganization
is_verified—
owner_loginpay-rails
public_repos1
account_age_days2,535
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

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 — 157 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagespay
ecosystemsrubygems
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

88Excellent · 19% of overall

Engineering practices

80Excellent
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
16/20OpenSSF Scorecard: CI-Tests — 6 out of 7 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://github.com/pay-rails/pay
10/10Repository description
10/10Topics — 11 topics
10/10Wiki
Inputs used
topicssubscription, stripe, pay, engine, rails, payment-provider, braintree, sca, paddle, payments, hacktoberfest
has_wikiyes
homepagehttps://github.com/pay-rails/pay
docs_sitehttps://github.com/pay-rails/pay
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

62Moderate · 16% of overall

Security posture

52Moderate
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2/2.5CI-Tests — 6 out of 7 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-Review — Found 6/26 approved changesets -- score normalized to 2
2.5/2.5Contributors — project has 20 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
7.5/7.5Maintained — 18 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
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 — no data
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.2
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 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_packages118
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 118 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.

38Weak · 4% of overall

Agent context & guidance

14Critical
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
13.9/40Legible commit history — 26 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.26
agent_instruction_files—
agent_instruction_max_bytes—

Verify loop (build / test / typecheck)

50Moderate
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .rubocop.yml
0/11Static type checking
10/10Reproducible environment — devcontainer, Dockerfile, lockfile
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontaineryes
has_linter_configyes
typecheck_configs—
agent_commit_share0.01
toolchain_manifests—
dependency_bot_commit_share0

Code legibility for models

55Moderate
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/258 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes20,680
source_files_sampled258
oversized_source_files0

Key facts

2,249GitHub stars
98contributors
87commits, last 12 months
0days since last push
70releases
1bus factor
0open 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 ★ / 355 ⇿
0Stars
355Forks
68Releases

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.

012525037533962017-072022-012026-07
Major 7Minor 18Patch 43

Each point covers 9 days.

OpenSSF Scorecard 5.2 / 10
5.2aggregate

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-30 14:47 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
8CI-Tests6 out of 7 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 6/26 approved changesets -- score normalized to 2
10Contributorsproject has 20 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained18 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
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
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 20
RegistryPackageVersion constraintManifest
RubyGemsappraisal—Gemfile
RubyGemsmocha—Gemfile
RubyGemsstandard—Gemfile
RubyGemsvcr—Gemfile
RubyGemswebmock—Gemfile
RubyGemsbraintree>= 2.92.0Gemfile
RubyGemslemonsqueezy~> 1.0Gemfile
RubyGemspaddle~> 2.6Gemfile
RubyGemsstripe~> 19.0Gemfile
RubyGemsprawn—Gemfile
RubyGemsreceipts—Gemfile
RubyGemsmysql2—Gemfile
RubyGemspg—Gemfile
RubyGemssqlite3—Gemfile
RubyGemspuma—Gemfile
RubyGemsimportmap-rails—Gemfile
RubyGemssprockets-rails—Gemfile
RubyGemsstimulus-rails—Gemfile
RubyGemsturbo-rails—Gemfile
RubyGemsminitest< 6.0.0Gemfile
All dependencies 119

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

RegistryPackageVersionRelation
RubyGemsappraisal3.0.0.rc1direct
RubyGemsbraintree4.39.0direct
RubyGemsimportmap-rails2.2.3direct
RubyGemslemonsqueezy1.1.0direct
RubyGemsminitest5.27.0direct
RubyGemsmocha3.1.0direct
RubyGemsmysql20.5.7direct
RubyGemspaddle2.10direct
RubyGemspg1.6.3direct
RubyGemsprawn2.5.0direct
RubyGemspuma8.0.2direct
RubyGemsreceipts2.4.0direct
RubyGemssprockets-rails3.5.2direct
RubyGemssqlite32.9.5direct
RubyGemsstandard1.56.0direct
RubyGemsstimulus-rails1.3.4direct
RubyGemsstripe19.4.0direct
RubyGemsturbo-rails2.0.23direct
RubyGemsvcr6.4.0direct
RubyGemswebmock3.26.2direct
RubyGemsaction_text-trix2.1.19indirect
RubyGemsactioncable8.1.3.1indirect
RubyGemsactionmailbox8.1.3.1indirect
RubyGemsactionmailer8.1.3.1indirect
RubyGemsactionpack8.1.3.1indirect
RubyGemsactiontext8.1.3.1indirect
RubyGemsactionview8.1.3.1indirect
RubyGemsactivejob8.1.3.1indirect
RubyGemsactivemodel8.1.3.1indirect
RubyGemsactiverecord8.1.3.1indirect
RubyGemsactivestorage8.1.3.1indirect
RubyGemsactivesupport8.1.3.1indirect
RubyGemsaddressable2.9.0indirect
RubyGemsast2.4.3indirect
RubyGemsbase640.3.0indirect
RubyGemsbigdecimal3.3.1indirect
RubyGemsbindex0.8.1indirect
RubyGemsbuilder3.3.0indirect
RubyGemscgi0.5.2indirect
RubyGemsconcurrent-ruby1.3.8indirect
RubyGemsconnection_pool3.0.2indirect
RubyGemscrack1.0.1indirect
RubyGemscrass1.0.7indirect
RubyGemsdate3.5.1indirect
RubyGemsdrb2.2.3indirect
RubyGemserb6.0.6indirect
RubyGemserubi1.13.1indirect
RubyGemsfaraday2.14.3indirect
RubyGemsfaraday-net_http3.4.4indirect
RubyGemsglobalid1.4.0indirect
RubyGemshashdiff1.2.1indirect
RubyGemsi18n1.15.2indirect
RubyGemsio-console0.8.2indirect
RubyGemsirb1.18.0indirect
RubyGemsjson2.21.1indirect
RubyGemslanguage_server-protocol3.17.0.6indirect
RubyGemslint_roller1.1.0indirect
RubyGemslogger1.7.0indirect
RubyGemsloofah2.25.2indirect
RubyGemsmail2.9.1indirect
RubyGemsmarcel1.2.1indirect
RubyGemsmatrix0.4.3indirect
RubyGemsmini_mime1.1.5indirect
RubyGemsmini_portile22.8.9indirect
RubyGemsnet-http0.9.1indirect
RubyGemsnet-imap0.6.6indirect
RubyGemsnet-pop0.1.2indirect
RubyGemsnet-protocol0.2.2indirect
RubyGemsnet-smtp0.5.1indirect
RubyGemsnio4r2.7.5indirect
RubyGemsnokogiri1.19.4indirect
RubyGemsostruct0.6.3indirect
RubyGemsparallel2.1.0indirect
RubyGemsparser3.3.12.0indirect
RubyGemspdf-core0.10.0indirect
RubyGemspp0.6.4indirect
RubyGemsprawn-table0.2.2indirect
RubyGemsprettyprint0.2.0indirect
RubyGemsprism1.9.0indirect
RubyGemspublic_suffix7.0.5indirect
RubyGemsracc1.8.1indirect
RubyGemsrack3.2.6indirect
RubyGemsrack-session2.1.2indirect
RubyGemsrack-test2.2.0indirect
RubyGemsrackup2.3.1indirect
RubyGemsrails—indirect
RubyGemsrails8.1.3.1indirect
RubyGemsrails-dom-testing2.3.0indirect
RubyGemsrails-html-sanitizer1.7.1indirect
RubyGemsrailties8.1.3.1indirect
RubyGemsrainbow3.1.1indirect
RubyGemsrake13.4.2indirect
RubyGemsrbs4.1.1indirect
RubyGemsrdoc8.0.0indirect
RubyGemsregexp_parser2.12.0indirect
RubyGemsreline0.6.3indirect
RubyGemsrexml3.4.4indirect
RubyGemsrubocop1.88.2indirect
RubyGemsrubocop-ast1.50.0indirect
RubyGemsrubocop-performance1.26.1indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemsruby2_keywords0.0.5indirect
RubyGemssecurerandom0.4.1indirect
RubyGemssprockets4.2.2indirect
RubyGemsstandard-custom1.0.2indirect
RubyGemsstandard-performance1.9.0indirect
RubyGemsthor1.5.0indirect
RubyGemstimeout0.6.1indirect
RubyGemstsort0.2.0indirect
RubyGemsttfunk1.8.0indirect
RubyGemstzinfo2.0.6indirect
RubyGemsunicode-display_width3.2.0indirect
RubyGemsunicode-emoji4.2.0indirect
RubyGemsuri1.1.1indirect
RubyGemsuseragent0.16.11indirect
RubyGemsweb-console4.3.0indirect
RubyGemswebsocket-driver0.8.2indirect
RubyGemswebsocket-extensions0.1.5indirect
RubyGemszeitwerk2.8.2indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 118 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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with pay-rails/pay. Read them side by side →

98juspay/hyperswitchOpen source, composable payments platform | PCI compliant | SaaS and Self-host options | Enables connectivity to multiple payment, payout, fraud, vault and tokenization providers | Uplifts authorization with intelligent routing and revenue recovery | Reduce payment processing costs with cost observability | Reduces payment ops with reconciliationExceptional99stripe/stripe-react-nativeReact Native library for Stripe.Exceptional96avo-hq/avoThe Essential Toolkit for building Internal Tools and admin panels with Ruby on RailsExceptional99stripe/stripe-pythonPython library for the Stripe API. Exceptional99open-telemetry/opentelemetry-rubyOpenTelemetry Ruby API & SDK, and related gemsExceptional99newrelic/newrelic-ruby-agentNew Relic RPM Ruby AgentExceptional

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.27.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — RubyGems.