Public record
Software health reportschema 0.26.0 · metrics 2.10.0 · 2026-07-22 00:19 UTC

savonrb / savon

Heavy metal SOAP client

RubyMIT★ 2,086 stars⑂ 612 forkssince Jul 2009View on GitHub ↗

savonrb/savon holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (86/100) and lowest on AI Readiness (44/100). It was last updated 15 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

savonrbOrganization
3 followers12 public repossince Sep 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemssavon2.17.4-99343 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
28.8/36Push recencylast push 15 days ago
6.2/36Commit cadence9/52 weeks with commits
17.8/18Commit volume95 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year95
human_commit_share0.92
days_since_last_push15
active_weeks_last_year9
How it's scored
27/27Ships releases16 releases published
36/36Release recencylatest release 18 days ago
19.8/27Release cadencea release every ~96.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count16
latest_release_tagv2.17.4
releases_from_tagsno
days_since_latest_release18
mean_days_between_releases96.7
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
53.8/60Stars2,086 stars
23.2/25Forks612 forks
8.7/15Watchers37 watchers
Inputs used
forks612
stars2,086
watchers37
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
6.3/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_templateyes
How it's scored
80/80Total downloads98,640,558 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagessavon
dependents
ecosystemsrubygems
total_downloads98,640,558
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?

64Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.7/22.5Commit distributiontop contributor authored 79% of commits
13.5/13.5Contributor breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 21 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled99
top_contributor_share0.79
How it's scored
41.6/42Issue resolution99% of issues closed
19.2/30PR acceptance183/286 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/18 approved changesets -- score normalized to 0
Inputs used
merged_prs183
open_issues7
closed_issues754
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.991
closed_unmerged_prs103
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
4.3/25Owner reach3 followers of savonrb
20.1/25Track record12 public repos, account ~13 yr old
Inputs used
followers3
owner_typeOrganization
is_verified
owner_loginsavonrb
public_repos12
account_age_days5,057
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 343 days ago
20/20Version history99 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagessavon
ecosystemsrubygems
any_deprecatedno
min_days_since_publish343

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 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
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://savonrb.com
10/10Repository description
10/10Topics3 topics
0/10Wiki
Inputs used
topicssoap, soap-client, ruby
has_wikino
homepagehttps://savonrb.com
docs_sitehttps://savonrb.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

75Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/18 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 21 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
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
5/5Pinned-Dependenciesall dependencies are pinned
0/5SASTno data
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
6.8/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate7.5
Excluded from scoring (no data or not applicable): CI-Tests, Packaging, SAST, 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.

44Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
16.2/40Legible commit history28 of 92 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.304
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 environmentdevcontainer
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance8 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependenciesall dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontaineryes
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.08
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/64 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes45,722
source_files_sampled64
oversized_source_files0

Key facts

2,086GitHub stars
99contributors
95commits, last 12 months
15days since last push
16releases
1bus factor
7open issues
RubyGemspackage ecosystems

Data collection warnings

  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 2,086 ★ / 612 ⇿
2,086Stars
612Forks
15Releases

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.

04008001,2001,6002,0002,4002,086566162009-122018-032026-07
Major 0Minor 6Patch 7

Each point covers 16 days.

OpenSSF Scorecard 7.5 / 10
7.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-22 00:19 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
n/aCI-Testsinternal error: internal error: Client.Repositories.ListCheckRunsForRef: error during graphqlHandler.setupCheckRuns: Something went wrong while executing your query on 2026-07-22T00:19:35Z. Please include `D8AE:24C918:1241B7F:118E2BC:6A600C95` when reporting this issue.
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/18 approved changesets -- score normalized to 0
10Contributorsproject has 21 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
n/aSASTinternal error: internal error: Client.Checks.ListCheckRunsForRef: error during graphqlHandler.setupCheckRuns: Something went wrong while executing your query on 2026-07-22T00:19:35Z. Please include `D8AE:24C918:1241B7F:118E2BC:6A600C95` when reporting this issue.
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 13
RegistryPackageVersion constraintManifest
RubyGemsfaraday~> 2.14Gemfile
RubyGemsfaraday-digestauth~> 0.4Gemfile
RubyGemsfaraday-follow_redirects~> 0.5Gemfile
RubyGemsfaraday-ntlm_auth~> 0.1Gemfile
RubyGemshttpclient~> 2.7.1Gemfile
RubyGemswebrickGemfile
RubyGemsbundler-audit~> 0.9.3Gemfile
RubyGemsnet-smtpGemfile
RubyGemsrubocop~> 1.86Gemfile
RubyGemsrubocop-rake~> 0.7.1Gemfile
RubyGemsrubocop-rspec~> 3.9Gemfile
RubyGemsruby_audit~> 3.1Gemfile
RubyGemssimplecovGemfile
All dependencies 26

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

RegistryPackageVersionRelation
RubyGemsbundler-auditdirect
RubyGemsfaradaydirect
RubyGemsfaraday-digestauthdirect
RubyGemsfaraday-follow_redirectsdirect
RubyGemshttpclientdirect
RubyGemsrubocopdirect
RubyGemsrubocop-rakedirect
RubyGemsrubocop-rspecdirect
RubyGemssimplecovdirect
RubyGemswebrickdirect
RubyGemsakamiindirect
RubyGemsbuilderindirect
RubyGemsbyebugindirect
RubyGemsgyokuindirect
RubyGemshttpiindirect
RubyGemsjsonindirect
RubyGemsmailindirect
RubyGemsmochaindirect
RubyGemsnokogiriindirect
RubyGemsnoriindirect
RubyGemsostructindirect
RubyGemspumaindirect
RubyGemsrackindirect
RubyGemsrakeindirect
RubyGemsrspecindirect
RubyGemswasabiindirect
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.