Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-09 08:12 UTC

rubysec / bundler-audit

Patch-level verification for Bundler

RubyGPL-3.0★ 2,757 stars⑂ 249 forkssince Feb 2013View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

rubysec/bundler-audit holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Security (72/100) and lowest on AI Readiness (49/100). It was last updated 4 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

RubySecOrganization
31 followers6 public repossince Feb 2013

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

Metrics by category

Vitality

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

64Moderate · 21% of overall
How it's scored
36/36Push recency — last push 4 days ago
11.8/36Commit cadence — 17/52 weeks with commits
16.7/18Commit volume — 72 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year72
human_commit_share0.8
days_since_last_push4
active_weeks_last_year17
How it's scored
27/27Ships releases — 2 releases published
16.2/36Release recency — latest release 284 days ago
5.4/27Release cadence — a release every ~463 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count2
latest_release_tagv0.9.3
releases_from_tagsno
days_since_latest_release284
mean_days_between_releases463

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

69Good · 17% of overall
How it's scored
55.8/60Stars — 2,757 stars
20/25Forks — 249 forks
8.8/15Watchers — 40 watchers
Inputs used
forks249
stars2,757
watchers40
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (GPL-3.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, github.com
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

55Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
5.2/22.5Commit distribution — top contributor authored 77% of commits
13.5/13.5Contributor breadth — 62 contributors
10/10OpenSSF Scorecard: Contributors — project has 26 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled62
top_contributor_share0.767
How it's scored
36.2/42Issue resolution — 86% of issues closed
16.2/30PR acceptance — 138/255 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
9/15OpenSSF Scorecard: Code-Review — Found 3/5 approved changesets -- score normalized to 6
Inputs used
merged_prs138
open_issues24
closed_issues149
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.861
closed_unmerged_prs117
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
10.8/25Owner reach — 31 followers of rubysec
18.2/25Track record — 6 public repos, account ~13 yr old
Inputs used
followers31
owner_typeOrganization
is_verifiedno
owner_loginrubysec
public_repos6
account_age_days4,957

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 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
20/20OpenSSF Scorecard: CI-Tests — 16 out of 16 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

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 8 topics
0/10Wiki
Inputs used
topicsbundler-audit, ruby-advisory-db, ruby, dependency-checker, patch-management, security, security-tools, security-audit
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?

72Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 16 out of 16 merged PRs checked by a CI test -- score normalized to 10
0.5/2.5CII-Best-Practices — badge detected: InProgress
4.5/7.5Code-Review — Found 3/5 approved changesets -- score normalized to 6
2.5/2.5Contributors — project has 26 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
7.5/7.5Maintained — 30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
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 — Project has not signed or included provenance with any releases.
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate6.5
Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories139
affected_packages26
assessed_packages94
unassessed_packages9
affected_by_severitycritical 5, high 15, moderate 4, low 2
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 94 resolved dependencies against OSV. 9 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

49Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
26/40Legible commit history — 39 of 80 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.487
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 environment — lockfile
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 20 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.01
toolchain_manifests—
dependency_bot_commit_share0.2
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/37 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes11,323
source_files_sampled37
oversized_source_files0

Key facts

2,757GitHub stars
62contributors
72commits, last 12 months
4days since last push
2releases
1bus factor
24open 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 ★ / 249 ⇿
0Stars
249Forks
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.

05010015020025024352013-022019-112026-07
Major 0Minor 0Patch 2

Each point covers 13 days.

OpenSSF Scorecard 6.5 / 10
6.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-09-09 08:11 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests16 out of 16 merged PRs checked by a CI test -- score normalized to 10
2CII-Best-Practicesbadge detected: InProgress
6Code-ReviewFound 3/5 approved changesets -- score normalized to 6
10Contributorsproject has 26 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 4 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 103

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

RegistryPackageVersionRelation
RubyGemsactioncable5.2.8indirect
RubyGemsactioncable6.1.3.2indirect
RubyGemsactionmailbox6.1.3.2indirect
RubyGemsactionmailer5.2.8indirect
RubyGemsactionmailer6.1.3.2indirect
RubyGemsactionpack5.2.8indirect
RubyGemsactionpack6.1.3.2indirect
RubyGemsactiontext6.1.3.2indirect
RubyGemsactionview5.2.8indirect
RubyGemsactionview6.1.3.2indirect
RubyGemsactivejob5.2.8indirect
RubyGemsactivejob6.1.3.2indirect
RubyGemsactivemodel3.2.10indirect
RubyGemsactivemodel5.2.8indirect
RubyGemsactivemodel6.1.3.2indirect
RubyGemsactiverecord3.2.10indirect
RubyGemsactiverecord5.2.8indirect
RubyGemsactiverecord6.1.3.2indirect
RubyGemsactivestorage5.2.8indirect
RubyGemsactivestorage6.1.3.2indirect
RubyGemsactivesupport3.2.10indirect
RubyGemsactivesupport5.2.8indirect
RubyGemsactivesupport6.1.3.2indirect
RubyGemsarel3.0.3indirect
RubyGemsarel9.0.0indirect
RubyGemsbase640.3.0indirect
RubyGemsbuilder3.0.4indirect
RubyGemsbuilder3.2.4indirect
RubyGemsconcurrent-ruby1.1.10indirect
RubyGemsconcurrent-ruby1.1.7indirect
RubyGemsconcurrent-ruby1.1.8indirect
RubyGemsconcurrent-ruby1.3.7indirect
RubyGemscrass1.0.6indirect
RubyGemscrass1.0.7indirect
RubyGemsdate3.5.1indirect
RubyGemserubi1.10.0indirect
RubyGemsglobalid0.4.2indirect
RubyGemsglobalid1.0.1indirect
RubyGemsi18n0.9.5indirect
RubyGemsi18n1.12.0indirect
RubyGemsi18n1.8.10indirect
RubyGemskramdown—indirect
RubyGemslogger1.7.0indirect
RubyGemsloofah2.19.1indirect
RubyGemsloofah2.25.2indirect
RubyGemsmail2.7.1indirect
RubyGemsmail2.9.1indirect
RubyGemsmarcel1.0.1indirect
RubyGemsmarcel1.0.2indirect
RubyGemsmethod_source1.0.0indirect
RubyGemsmini_mime1.0.3indirect
RubyGemsmini_mime1.1.5indirect
RubyGemsmini_portile22.8.0indirect
RubyGemsmini_portile22.8.9indirect
RubyGemsminitest5.14.4indirect
RubyGemsminitest5.17.0indirect
RubyGemsmulti_json1.15.0indirect
RubyGemsnet-imap0.6.6indirect
RubyGemsnet-pop0.1.2indirect
RubyGemsnet-protocol0.3.0indirect
RubyGemsnet-smtp0.5.1indirect
RubyGemsnio4r2.5.7indirect
RubyGemsnio4r2.5.8indirect
RubyGemsnokogiri1.13.10indirect
RubyGemsnokogiri1.19.4indirect
RubyGemsracc1.6.1indirect
RubyGemsracc1.8.1indirect
RubyGemsrack2.2.23indirect
RubyGemsrack2.2.6.3indirect
RubyGemsrack-test1.1.0indirect
RubyGemsrails5.2.8indirect
RubyGemsrails6.1.3.2indirect
RubyGemsrails-dom-testing2.0.3indirect
RubyGemsrails-html-sanitizer1.4.4indirect
RubyGemsrails-html-sanitizer1.7.1indirect
RubyGemsrailties5.2.8indirect
RubyGemsrailties6.1.3.2indirect
RubyGemsrake—indirect
RubyGemsrake13.0.3indirect
RubyGemsrake13.0.6indirect
RubyGemsredcarpet—indirect
RubyGemsrspec—indirect
RubyGemsrubocop—indirect
RubyGemsrubygems-tasks—indirect
RubyGemssimplecov—indirect
RubyGemssprockets4.0.2indirect
RubyGemssprockets4.0.3indirect
RubyGemssprockets-rails3.2.2indirect
RubyGemssprockets-rails3.4.2indirect
RubyGemsthor1.1.0indirect
RubyGemsthor1.2.1indirect
RubyGemsthread_safe0.3.6indirect
RubyGemstimeout0.6.1indirect
RubyGemstzinfo0.3.58indirect
RubyGemstzinfo0.3.61indirect
RubyGemstzinfo1.2.10indirect
RubyGemstzinfo2.0.4indirect
RubyGemswebsocket-driver0.7.4indirect
RubyGemswebsocket-driver0.8.2indirect
RubyGemswebsocket-extensions0.1.5indirect
RubyGemsyard—indirect
RubyGemsyard-spellcheck—indirect
RubyGemszeitwerk2.4.2indirect
Dependency advisories 26

This repository publishes no package the index resolves, so its own dependency graph was assessed — 94 packages, which also include development and test pins that never ship: 26 carry known advisories, of which 0 are direct. 9 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
activerecord3.2.10indirectcritical98.0.2.1
activerecord5.2.8indirectcritical38.0.2.1
activerecord6.1.3.2indirectcritical48.0.2.1
activestorage5.2.8indirectcritical88.1.3.1
activestorage6.1.3.2indirectcritical98.1.3.1
actionmailer5.2.8indirecthigh17.2.1.1
actionmailer6.1.3.2indirecthigh17.2.1.1
actionpack5.2.8indirecthigh68.0.0.1
actionpack6.1.3.2indirecthigh118.0.0.1
actiontext6.1.3.2indirecthigh17.2.1.1
activesupport3.2.10indirecthigh78.1.2.1
activesupport5.2.8indirecthigh68.1.2.1
activesupport6.1.3.2indirecthigh68.1.2.1
concurrent-ruby1.1.10indirecthigh31.3.7
concurrent-ruby1.1.7indirecthigh31.3.7
concurrent-ruby1.1.8indirecthigh31.3.7
nokogiri1.13.10indirecthigh181.19.4
rack2.2.6.3indirecthigh263.2.6
tzinfo0.3.58indirecthigh11.2.10
websocket-driver0.7.4indirecthigh40.8.2
actionview5.2.8indirectmoderate28.1.2.1
actionview6.1.3.2indirectmoderate38.1.2.1
loofah2.19.1indirectmoderate12.25.2
mail2.7.1indirectmoderate12.9.1
globalid0.4.2indirectlow11.0.1
rails-html-sanitizer1.4.4indirectlow11.7.1

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.