Public record
Software health reportschema 0.15.0 · metrics 2.10.0 · 2026-07-20 14:08 UTC

dry-rb / dry-validation

Validation library with type-safe schemas and rules

RubyMIT★ 1,422 stars⑂ 196 forkssince Jul 2015View on GitHub ↗

dry-rb/dry-validation holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Community & Adoption (86/100) and lowest on AI Readiness (43/100). It was last updated 71 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

DryOrganization
382 followers41 public repossince Mar 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsdry-validation1.11.1-70545 days ago

Metrics by category

Vitality

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

51Moderate · 21% of overall
How it's scored
18/36Push recencylast push 71 days ago
11.1/36Commit cadence16/52 weeks with commits
15.1/18Commit volume47 commits in the last year
6/10OpenSSF Scorecard: Maintained7 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 6
Inputs used
commits_last_year47
human_commit_share
days_since_last_push71
active_weeks_last_year16
How it's scored
27/27Ships releases37 releases published
7.2/36Release recencylatest release 545 days ago
12.6/27Release cadencea release every ~177.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count37
latest_release_tagv1.11.1
releases_from_tagsno
days_since_latest_release545
mean_days_between_releases177.9
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
51.1/60Stars1,422 stars
19.1/25Forks196 forks
8/15Watchers29 watchers
Inputs used
forks196
stars1,422
watchers29
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/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_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
80/80Total downloads115,453,872 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesdry-validation
dependents
ecosystemsrubygems
total_downloads115,453,872
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?

68Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
5.9/22.5Commit distributiontop contributor authored 74% of commits
13.5/13.5Contributor breadth65 contributors
10/10OpenSSF Scorecard: Contributorsproject has 35 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled65
top_contributor_share0.738
How it's scored
39.3/42Issue resolution94% of issues closed
24.7/30PR acceptance227/276 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/29 approved changesets -- score normalized to 0
Inputs used
merged_prs227
open_issues28
closed_issues402
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.935
closed_unmerged_prs49
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
18.6/25Owner reach382 followers of dry-rb
23.8/25Track record41 public repos, account ~11 yr old
Inputs used
followers382
owner_typeOrganization
is_verified
owner_logindry-rb
public_repos41
account_age_days4,157
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on rubygems
14/35Publish recencylatest publish 545 days ago
20/20Version history70 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesdry-validation
ecosystemsrubygems
any_deprecatedno
min_days_since_publish545

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows5 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests1 out of 1 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 sitehttps://dry-rb.org/gems/dry-validation
10/10Repository description
10/10Topics8 topics
0/10Wiki
Inputs used
topicsdry-rb, validation, ruby, data-validation, type-safety, coercion, rubygem, gem
has_wikino
homepagehttps://dry-rb.org/gems/dry-validation
docs_sitehttps://dry-rb.org/gems/dry-validation
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

51Moderate · 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-Tests1 out of 1 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
0/7.5Code-ReviewFound 0/29 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 35 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
4.5/7.5Maintained7 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 6
0/5Packagingno data
3.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
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
6.8/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.1
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)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.rubocop.yml
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
7/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/71 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes10,472
source_files_sampled71
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

1,422GitHub stars
65contributors
47commits, last 12 months
71days since last push
37releases
1bus factor
28open issues
RubyGemspackage ecosystems

More detail

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-07-20 14:08 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests1 out of 1 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/29 approved changesets -- score normalized to 0
10Contributorsproject has 35 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
6Maintained7 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 6
n/aPackagingpackaging workflow not detected
7Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 8
RegistryPackageVersion constraintManifest
RubyGemsactionpackGemfile
RubyGemsactivemodelGemfile
RubyGemsactiverecordGemfile
RubyGemsbenchmark-ipsGemfile
RubyGemssqlite3Gemfile
RubyGemsjdbc-sqlite3Gemfile
RubyGemsactiverecord-jdbc-adapterGemfile
RubyGemsvirtusGemfile
All dependencies 18

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

RegistryPackageVersionRelation
RubyGemsactionpackdirect
RubyGemsactivemodeldirect
RubyGemsactiverecorddirect
RubyGemsactiverecord-jdbc-adapterdirect
RubyGemsbenchmark-ipsdirect
RubyGemsjdbc-sqlite3direct
RubyGemssqlite3direct
RubyGemsvirtusdirect
RubyGemsbundlerindirect
RubyGemsconcurrent-rubyindirect
RubyGemsdry-coreindirect
RubyGemsdry-initializerindirect
RubyGemsdry-monadsindirect
RubyGemsdry-schemaindirect
RubyGemsi18nindirect
RubyGemsrakeindirect
RubyGemsrspecindirect
RubyGemszeitwerkindirect
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.15.0 — full methodology · metrics wiki.

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