Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-14 19:53 UTC

samvera / valkyrie

A Data Mapper library to enable multiple backends for storage of files and metadata in Samvera

RubyCustom license★ 35 stars⑂ 21 forkssince Aug 2016View on GitHub ↗
KindLibraryCommand-line toolPluginhow this is determined

samvera/valkyrie holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (71/100) and lowest on AI Readiness (36/100). It was last updated 46 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Samvera CommunityOrganization
64 followers26 public repossince Jul 2009

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsvalkyrie3.6.1-6046 days ago

Metrics by category

Vitality

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

55Moderate · 21% of overall
How it's scored
18/36Push recency — last push 46 days ago
8.3/36Commit cadence — 12/52 weeks with commits
14.5/18Commit volume — 40 commits in the last year
10/10OpenSSF Scorecard: Maintained — 19 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year40
human_commit_share1
days_since_last_push46
active_weeks_last_year12
How it's scored
27/27Ships releases — 23 releases published
16.2/36Release recency — latest release 240 days ago
12.6/27Release cadence — a release every ~244.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count23
latest_release_tagv3.5.1
releases_from_tagsno
days_since_latest_release240
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?

64Moderate · 17% of overall
How it's scored
24.8/60Stars — 35 stars
10.8/25Forks — 21 forks
10.3/15Watchers — 71 watchers
Inputs used
forks21
stars35
watchers71
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesbadge.fury.io, circleci.com, shields.io
has_pull_request_templateno
How it's scored
56.9/80Total downloads — 302,158 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesvalkyrie
dependents—
ecosystemsrubygems
total_downloads302,158
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?

71Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
11/22.5Commit distribution — top contributor authored 51% of commits
13.5/13.5Contributor breadth — 43 contributors
10/10OpenSSF Scorecard: Contributors — project has 43 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled43
top_contributor_share0.513
How it's scored
34.7/42Issue resolution — 83% of issues closed
26.6/30PR acceptance — 541/610 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
13.5/15OpenSSF Scorecard: Code-Review — Found 9/10 approved changesets -- score normalized to 9
Inputs used
merged_prs541
open_issues68
closed_issues322
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.826
closed_unmerged_prs69
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
13/25Owner reach — 64 followers of samvera
22.4/25Track record — 26 public repos, account ~17 yr old
Inputs used
followers64
owner_typeOrganization
is_verifiedno
owner_loginsamvera
public_repos26
account_age_days6,257

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on rubygems
35/35Publish recency — latest publish 46 days ago
20/20Version history — 60 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesvalkyrie
ecosystemsrubygems
any_deprecatedno
min_days_since_publish46

Engineering Quality

Are baseline engineering and documentation practices in place?

65Good · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config — .rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 9 out of 10 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://www.rubydoc.info/gems/valkyrie/3.6.1
10/10Repository description
10/10Topics — 2 topics
10/10Wiki
Inputs used
topicscore-components, samvera-community
has_wikiyes
homepage—
docs_sitehttps://www.rubydoc.info/gems/valkyrie/3.6.1
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

58Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.2/2.5CI-Tests — 9 out of 10 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
6.8/7.5Code-Review — Found 9/10 approved changesets -- score normalized to 9
2.5/2.5Contributors — project has 43 contributing companies or organizations
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 19 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
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 — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate5.8
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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.

36Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
25.6/40Legible commit history — 48 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.48
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
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/138 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes26,145
source_files_sampled138
oversized_source_files0

Key facts

35GitHub stars
43contributors
40commits, last 12 months
46days since last push
23releases
1bus factor
68open issues
RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 21 ⇿
0Stars
21Forks
23Releases

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.

0481216202022017-032021-092026-04
Major 3Minor 8Patch 6

Each point covers 9 days.

OpenSSF Scorecard 5.8 / 10
5.8aggregate

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-09-14 19:52 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
9CI-Tests9 out of 10 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
9Code-ReviewFound 9/10 approved changesets -- score normalized to 9
10Contributorsproject has 43 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained19 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
RubyGemsactiverecord—Gemfile
RubyGemsldp—Gemfile
RubyGemspg—Gemfile
RubyGemsrsolr—Gemfile
All dependencies 30

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

RegistryPackageVersionRelation
RubyGemsactiverecord—direct
RubyGemsldp—direct
RubyGemspg—direct
RubyGemsrsolr—direct
RubyGemsactivemodel—indirect
RubyGemsactivesupport—indirect
RubyGemsappraisal—indirect
RubyGemsbixby—indirect
RubyGemsbundler—indirect
RubyGemsdatabase_cleaner—indirect
RubyGemsdry-struct—indirect
RubyGemsdry-types—indirect
RubyGemsfaraday-multipart—indirect
RubyGemsfcrepo_wrapper—indirect
RubyGemsjson—indirect
RubyGemsjson-ld—indirect
RubyGemspry—indirect
RubyGemspry-byebug—indirect
RubyGemsrailties—indirect
RubyGemsrake—indirect
RubyGemsrdf—indirect
RubyGemsrdf-vocab—indirect
RubyGemsreform—indirect
RubyGemsreform-rails—indirect
RubyGemsrspec—indirect
RubyGemssimplecov—indirect
RubyGemssolr_wrapper—indirect
RubyGemstimecop—indirect
RubyGemswebmock—indirect
RubyGemsyard—indirect
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.34.0 — full methodology · metrics wiki.

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