Public record
Software health reportschema 0.26.0 · metrics 2.10.0 · 2026-07-21 23:45 UTC

RubyMoney / money

A Ruby Library for dealing with money and currency conversion.

RubyMIT★ 2,879 stars⑂ 642 forkssince Oct 2008View on GitHub ↗

RubyMoney/money holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (86/100) and lowest on AI Readiness (42/100). It was last updated 29 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

RubyMoneyOrganization
54 followers9 public repossince Aug 2010

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsmoney7.0.2-103223 days ago

Metrics by category

Vitality

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

57Moderate · 21% of overall
How it's scored
28.8/36Push recencylast push 29 days ago
13.2/36Commit cadence19/52 weeks with commits
18/18Commit volume123 commits in the last year
2/10OpenSSF Scorecard: Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Inputs used
commits_last_year123
human_commit_share0.97
days_since_last_push29
active_weeks_last_year19
How it's scored
16.2/27Ships releases69 version tags (no GitHub releases)
16.2/36Release recencylatest release 223 days ago
12.6/27Release cadencea release every ~244.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count69
latest_release_tagv7.0.2
releases_from_tagsyes
days_since_latest_release223
mean_days_between_releases244.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?

86Excellent · 17% of overall
How it's scored
56.1/60Stars2,879 stars
23.4/25Forks642 forks
10.2/15Watchers68 watchers
Inputs used
forks642
stars2,879
watchers68
growth_stateorganic
growth_factor_pct100
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/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_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
80/80Total downloads129,461,623 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesmoney
dependents
ecosystemsrubygems
total_downloads129,461,623
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?

78Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
12.3/22.5Commit distributiontop contributor authored 45% of commits
13.5/13.5Contributor breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 66 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled99
top_contributor_share0.453
How it's scored
41.6/42Issue resolution99% of issues closed
24.8/30PR acceptance598/722 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
12/15OpenSSF Scorecard: Code-ReviewFound 19/22 approved changesets -- score normalized to 8
Inputs used
merged_prs598
open_issues5
closed_issues472
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.99
closed_unmerged_prs124
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
12.5/25Owner reach54 followers of RubyMoney
19.3/25Track record9 public repos, account ~15 yr old
Inputs used
followers54
owner_typeOrganization
is_verified
owner_loginRubyMoney
public_repos9
account_age_days5,832
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on rubygems
26/35Publish recencylatest publish 223 days ago
20/20Version history103 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesmoney
ecosystemsrubygems
any_deprecatedno
min_days_since_publish223

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests23 out of 23 merged PRs checked by a CI test -- score normalized to 10
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 sitehttp://rubymoney.github.io/money
10/10Repository description
10/10Topics3 topics
0/10Wiki
Inputs used
topicsmoney, exchange-rate, ruby
has_wikino
homepagehttp://rubymoney.github.io/money
docs_sitehttp://rubymoney.github.io/money
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

65Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests23 out of 23 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6/7.5Code-ReviewFound 19/22 approved changesets -- score normalized to 8
2.5/2.5Contributorsproject has 66 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
1.5/7.5Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
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
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.5
Excluded from scoring (no data or not applicable): Branch-Protection, 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.

42Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
34.6/40Legible commit history63 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.649
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
0/10Reproducible environment
2/10Demonstrated agent practice1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance3 of the last 100 commits are automated dependency updates
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_configyes
typecheck_configs
agent_commit_share0.01
toolchain_manifests
dependency_bot_commit_share0.03
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/43 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes36,920
source_files_sampled43
oversized_source_files0

Key facts

2,879GitHub stars
99contributors
123commits, last 12 months
29days since last push
69releases
2bus factor
5open issues
RubyGemspackage ecosystems

Data collection warnings

  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 2,879 ★ / 642 ⇿
2,879Stars
642Forks
69Releases

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.

05001,0001,5002,0002,5003,0002,879616162009-012017-102026-07
Major 4Minor 24Patch 41

Each point covers 16 days.

OpenSSF Scorecard 6.5 / 10
6.5aggregate

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-21 23:45 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
10CI-Tests23 out of 23 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 19/22 approved changesets -- score normalized to 8
10Contributorsproject has 66 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
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 13
RegistryPackageVersion constraintManifest
RubyGemspryGemfile
RubyGemsrbsGemfile
RubyGemstypeprofGemfile
RubyGemsrspec~> 3.4Gemfile
RubyGemssimplecovGemfile
RubyGemsrakeGemfile
RubyGemsrubocop~> 1.86.0Gemfile
RubyGemsrubocop-performance~> 1.26.0Gemfile
RubyGemsrubocop-rake~> 0.7.0Gemfile
RubyGemsrubocop-rspec~> 3.8.0Gemfile
RubyGemsyard~> 0.9.38Gemfile
RubyGemsrdocGemfile
RubyGemsredcarpetGemfile
All dependencies 14

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

RegistryPackageVersionRelation
RubyGemsprydirect
RubyGemsrakedirect
RubyGemsrbsdirect
RubyGemsrdocdirect
RubyGemsrspecdirect
RubyGemsrubocopdirect
RubyGemsrubocop-performancedirect
RubyGemsrubocop-rakedirect
RubyGemsrubocop-rspecdirect
RubyGemssimplecovdirect
RubyGemstypeprofdirect
RubyGemsyarddirect
RubyGemsbigdecimalindirect
RubyGemsi18nindirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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

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