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

ruby / psych

A libyaml wrapper for Ruby

Ruby · C · JavaMIT★ 596 stars⑂ 221 forkssince Sep 2009View on GitHub ↗

ruby/psych holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Vitality (90/100) and lowest on AI Readiness (43/100). It was last updated 1 day ago. 2 contributors account 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

2,077 followers190 public repossince Feb 2010

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemspsych5.4.0-15549 days ago

Metrics by category

Vitality

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

90Excellent · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
23.5/36Commit cadence34/52 weeks with commits
18/18Commit volume109 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year109
human_commit_share0.75
days_since_last_push1
active_weeks_last_year34
How it's scored
27/27Ships releases87 releases published
36/36Release recencylatest release 18 days ago
19.8/27Release cadencea release every ~67 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count87
latest_release_tagv5.4.0
releases_from_tagsno
days_since_latest_release18
mean_days_between_releases67
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?

79Good · 17% of overall
How it's scored
45/60Stars596 stars
19.5/25Forks221 forks
9/15Watchers42 watchers
Inputs used
forks221
stars596
watchers42
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 downloads230,157,691 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagespsych
dependents
ecosystemsrubygems
total_downloads230,157,691
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?

82Excellent · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
14/22.5Commit distributiontop contributor authored 38% of commits
13.5/13.5Contributor breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 84 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled99
top_contributor_share0.377
How it's scored
33.6/42Issue resolution80% of issues closed
25.8/30PR acceptance338/393 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 2/5 approved changesets -- score normalized to 4
Inputs used
merged_prs338
open_issues76
closed_issues305
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.801
closed_unmerged_prs55
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
23.9/25Owner reach2,077 followers of ruby
25/25Track record190 public repos, account ~16 yr old
Inputs used
followers2,077
owner_typeOrganization
is_verified
owner_loginruby
public_repos190
account_age_days5,990
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on rubygems
35/35Publish recencylatest publish 49 days ago
20/20Version history155 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagespsych
ecosystemsrubygems
any_deprecatedno
min_days_since_publish49

Engineering Quality

Are baseline engineering and documentation practices in place?

61Moderate · 19% of overall
How it's scored
24/24CI workflows5 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests8 out of 8 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics7 topics
0/10Wiki
Inputs used
topicspsych, libyaml, c, yaml-parser, java, ruby, hacktoberfest
has_wikino
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?

56Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests8 out of 8 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
3/7.5Code-ReviewFound 2/5 approved changesets -- score normalized to 4
2.5/2.5Contributorsproject has 84 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 10 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
1/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
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
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.6
Excluded from scoring (no data or not applicable): 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.

43Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
38.4/40Legible commit history54 of 75 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.72
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
10/10Demonstrated agent practice26 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance25 of the last 100 commits are automated dependency updates
2/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.26
toolchain_manifests
dependency_bot_commit_share0.25
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/105 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes37,659
source_files_sampled105
oversized_source_files0

Key facts

596GitHub stars
99contributors
109commits, last 12 months
1days since last push
87releases
2bus factor
76open issues
RubyGemspackage ecosystems

Data collection warnings

  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 596 ★ / 221 ⇿
596Stars
221Forks
87Releases

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.

0100200300400500600595215922009-092018-022026-07
Major 4Minor 11Patch 54

Each point covers 16 days.

OpenSSF Scorecard 5.6 / 10
5.6aggregate

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

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests8 out of 8 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 2/5 approved changesets -- score normalized to 4
10Contributorsproject has 84 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 10 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
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
All dependencies 7

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

RegistryPackageVersionRelation
RubyGemsdateindirect
RubyGemsjar-dependenciesindirect
RubyGemsrake-compilerindirect
RubyGemsruby-mavenindirect
RubyGemsstringioindirect
RubyGemstest-unitindirect
RubyGemstest-unit-ruby-coreindirect
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.