Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-14 00:58 UTC

package-url / packageurl-ruby

Ruby implementation of the package url spec

RubyMIT★ 11 stars⑂ 4 forkssince Nov 2021View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

package-url/packageurl-ruby holds a health index of 36 out of 100, placing it in the Weak band. It scores highest on Engineering Quality (60/100) and lowest on Vitality (33/100). It was last updated 174 days ago. A single contributor accounts for most of its recent work.

36
overall / 100
Weak

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.

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

Ownership

Package-URLOrganization
92 followers21 public repossince Nov 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemspackageurl-ruby0.2.0-2541 days ago

Metrics by category

Vitality

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

33At Risk · 21% of overall
How it's scored
9.9/36Push recency — last push 174 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share—
days_since_last_push174
active_weeks_last_year0
How it's scored
27/27Ships releases — 2 releases published
7.2/36Release recency — latest release 541 days ago
27/27Release cadence — a release every ~0 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count2
latest_release_tagv0.2.0
releases_from_tagsno
days_since_latest_release541
mean_days_between_releases0
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?

42Weak · 17% of overall
How it's scored
16.2/60Stars — 11 stars
4/25Forks — 4 forks
0/15Watchers — 2 watchers
Inputs used
forks4
stars11
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
52.7/80Total downloads — 117,982 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagespackageurl-ruby
dependents—
ecosystemsrubygems
total_downloads117,982
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?

48Weak · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
2.5/22.5Commit distribution — top contributor authored 89% of commits
2.7/13.5Contributor breadth — 2 contributors
10/10OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.889
How it's scored
25.2/42Issue resolution — 60% of issues closed
7.5/30PR acceptance — 4/16 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 1/9 approved changesets -- score normalized to 1
Inputs used
merged_prs4
open_issues2
closed_issues3
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.6
closed_unmerged_prs12
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
14.2/25Owner reach — 92 followers of package-url
21.8/25Track record — 21 public repos, account ~8 yr old
Inputs used
followers92
owner_typeOrganization
is_verifiedno
owner_loginpackage-url
public_repos21
account_age_days3,231
How it's scored
25/25Published & resolvable — 1 package(s) on rubygems
14/35Publish recency — latest publish 541 days ago
12/20Version history — 2 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagespackageurl-ruby
ecosystemsrubygems
any_deprecatedno
min_days_since_publish541

Engineering Quality

Are baseline engineering and documentation practices in place?

60Moderate · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — .rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 4 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://www.rubydoc.info/gems/packageurl-ruby/0.2.0
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_sitehttps://www.rubydoc.info/gems/packageurl-ruby/0.2.0
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

44Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0/2.5CI-Tests — 0 out of 4 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 1/9 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 5 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
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 — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 10 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate3.6
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
20.2/35Direct dependencies free of known advisories — 1 affected: yard 0.9.37 (moderate 5.3)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
35.3/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 149 days ago
Inputs used
sourceosv
advisories10
affected_packages5
assessed_packages51
unassessed_packages0
affected_by_severityhigh 3, moderate 1, low 1
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 51 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

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.

37Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no 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
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no data
8/8Automated maintenance — 1 of the last 10 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share—
toolchain_manifests—
dependency_bot_commit_share0.1
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/4 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes13,560
source_files_sampled4
oversized_source_files0

Key facts

11GitHub stars
2contributors
0commits, last 12 months
174days since last push
2releases
1bus factor
2open issues
RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 4 ⇿
0Stars
4Forks
2Releases

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.

1223344412022-102024-042025-11
Major 0Minor 2Patch 0

Each point covers 3 days.

OpenSSF Scorecard 3.6 / 10
3.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-09-14 00:58 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
0CI-Tests0 out of 4 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 1/9 approved changesets -- score normalized to 1
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities10 existing vulnerabilities detected
Direct dependencies 8
RegistryPackageVersion constraintManifest
RubyGemsbundler~> 2.0Gemfile
RubyGemsrake~> 13.0Gemfile
RubyGemsrspec~> 3.0Gemfile
RubyGemsrubocop~> 1.74Gemfile
RubyGemsrubocop-rake~> 0.7Gemfile
RubyGemsrubocop-rspec~> 2.19Gemfile
RubyGemssteep~> 1.10.0Gemfile
RubyGemsyard~> 0.9.0Gemfile
All dependencies 51

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

RegistryPackageVersionRelation
RubyGemsrake13.2.1direct
RubyGemsrspec3.13.0direct
RubyGemsrubocop1.74.0direct
RubyGemsrubocop-rake0.7.1direct
RubyGemsrubocop-rspec2.31.0direct
RubyGemssteep1.10.0direct
RubyGemsyard0.9.37direct
RubyGemsactivesupport8.0.2indirect
RubyGemsast2.4.3indirect
RubyGemsbase640.2.0indirect
RubyGemsbenchmark0.4.0indirect
RubyGemsbigdecimal3.1.9indirect
RubyGemsconcurrent-ruby1.3.5indirect
RubyGemsconnection_pool2.5.0indirect
RubyGemscsv3.3.3indirect
RubyGemsdiff-lcs1.6.0indirect
RubyGemsdrb2.2.1indirect
RubyGemsffi1.17.1indirect
RubyGemsfileutils1.7.3indirect
RubyGemsi18n1.14.7indirect
RubyGemsjson2.10.2indirect
RubyGemslanguage_server-protocol3.17.0.4indirect
RubyGemslint_roller1.1.0indirect
RubyGemslisten3.9.0indirect
RubyGemslogger1.6.6indirect
RubyGemsminitest5.25.5indirect
RubyGemsmutex_m0.3.0indirect
RubyGemsparallel1.26.3indirect
RubyGemsparser3.3.7.2indirect
RubyGemsracc1.8.1indirect
RubyGemsrainbow3.1.1indirect
RubyGemsrb-fsevent0.11.2indirect
RubyGemsrb-inotify0.11.1indirect
RubyGemsrbs3.9.0indirect
RubyGemsregexp_parser2.10.0indirect
RubyGemsrspec-core3.13.3indirect
RubyGemsrspec-expectations3.13.3indirect
RubyGemsrspec-mocks3.13.2indirect
RubyGemsrspec-support3.13.2indirect
RubyGemsrubocop-ast1.41.0indirect
RubyGemsrubocop-capybara2.22.1indirect
RubyGemsrubocop-factory_bot2.27.1indirect
RubyGemsrubocop-rspec_rails2.29.1indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemssecurerandom0.4.1indirect
RubyGemsstrscan3.1.2indirect
RubyGemsterminal-table4.0.0indirect
RubyGemstzinfo2.0.6indirect
RubyGemsunicode-display_width3.1.4indirect
RubyGemsunicode-emoji4.0.4indirect
RubyGemsuri1.0.3indirect
Dependency advisories 5

This repository publishes no package the index resolves, so its own dependency graph was assessed — 51 packages, which also include development and test pins that never ship: 5 carry known advisories, of which 1 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
activesupport8.0.2indirecthigh38.1.2.1
concurrent-ruby1.3.5indirecthigh31.3.7
uri1.0.3indirecthigh11.0.4
yard0.9.37directmoderate20.9.44
json2.10.2indirectlow12.19.9

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

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.