Public record
Software health reportschema 0.26.0 · metrics 2.10.0 · 2026-07-22 15:28 UTC

infrablocks / rake_dependencies

Rake tasks for managing build dependencies.

RubyMIT★ 6 stars⑂ 0 forkssince Jan 2017View on GitHub ↗

infrablocks/rake_dependencies holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Vitality (68/100) and lowest on Community & Adoption (49/100). It was last updated today. 2 contributors account 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

InfraBlocksOrganization
39 followers120 public repossince Mar 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsrake_dependencies3.13.0-8811 days ago

Metrics by category

Vitality

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

68Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
9.7/36Commit cadence14/52 weeks with commits
16.8/18Commit volume73 commits in the last year
10/10OpenSSF Scorecard: Maintained21 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year73
human_commit_share0.58
days_since_last_push0
active_weeks_last_year14
How it's scored
16.2/27Ships releases42 version tags (no GitHub releases)
27/36Release recencylatest release 160 days ago
12.6/27Release cadencea release every ~207.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count42
latest_release_tagv3.13.0
releases_from_tagsyes
days_since_latest_release160
mean_days_between_releases207.4
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?

49Weak · 17% of overall
How it's scored
11.3/60Stars6 stars
0/25Forks0 forks
5.3/15Watchers10 watchers
Inputs used
forks0
stars6
watchers10
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/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_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
61.4/80Total downloads804,782 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesrake_dependencies
dependents
ecosystemsrubygems
total_downloads804,782
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?

67Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
11.3/22.5Commit distributiontop contributor authored 50% of commits
5.4/13.5Contributor breadth4 contributors
10/10OpenSSF Scorecard: Contributorsproject has 5 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled4
top_contributor_share0.498
How it's scored
21/42Issue resolution50% of issues closed
17.6/30PR acceptance131/223 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/3 approved changesets -- score normalized to 0
Inputs used
merged_prs131
open_issues1
closed_issues1
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.5
closed_unmerged_prs92
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
11.5/25Owner reach39 followers of infrablocks
25/25Track record120 public repos, account ~9 yr old
Inputs used
followers39
owner_typeOrganization
is_verified
owner_logininfrablocks
public_repos120
account_age_days3,416
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 11 days ago
20/20Version history88 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesrake_dependencies
ecosystemsrubygems
any_deprecatedno
min_days_since_publish11

Engineering Quality

Are baseline engineering and documentation practices in place?

60Moderate · 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
20/20OpenSSF Scorecard: CI-Tests14 out of 14 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics11 topics
10/10Wiki
Inputs used
topicsrake, ruby, dependencies, download, build, ruby-gem, rubygem, taskset, rake-taskset, rake-task, infrablocks
has_wikiyes
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?

67Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests14 out of 14 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/3 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 5 contributing companies or organizations
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained21 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesno data
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-Permissionsno data
6.8/7.5Vulnerabilities1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate5.9
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages74
unassessed_packages20
affected_by_severitymoderate 1
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 74 resolved dependencies against OSV. 20 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.

51Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
39.5/40Legible commit history43 of 58 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.741
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 environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance42 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.42
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/29 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes33,890
source_files_sampled29
oversized_source_files0

Key facts

6GitHub stars
4contributors
73commits, last 12 months
0days since last push
42releases
2bus factor
1open issues
RubyGemspackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 5.9 / 10
5.9aggregate

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 15:28 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
10CI-Tests14 out of 14 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/3 approved changesets -- score normalized to 0
10Contributorsproject has 5 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained21 commit(s) and 0 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
9Vulnerabilities1 existing vulnerabilities detected
All dependencies 94

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

RegistryPackageVersionRelation
RubyGemsactivesupport7.2.3.1indirect
RubyGemsaddressable2.9.0indirect
RubyGemsast2.4.3indirect
RubyGemsbase640.3.0indirect
RubyGemsbenchmark0.5.0indirect
RubyGemsbigdecimal4.1.2indirect
RubyGemsbundlerindirect
RubyGemschildprocess5.0.0indirect
RubyGemscolored23.1.2indirect
RubyGemsconcurrent-ruby1.3.7indirect
RubyGemsconnection_pool2.5.5indirect
RubyGemsdiff-lcs1.6.2indirect
RubyGemsdocile1.4.0indirect
RubyGemsdownindirect
RubyGemsdown5.5.0indirect
RubyGemsdrb2.2.3indirect
RubyGemsexcon0.111.0indirect
RubyGemsfakefsindirect
RubyGemsfakefs3.0.1indirect
RubyGemsfaraday2.14.3indirect
RubyGemsfaraday-net_http3.4.4indirect
RubyGemsffi1.17.4indirect
RubyGemsgem-releaseindirect
RubyGemsgem-release2.2.4indirect
RubyGemsgit1.19.1indirect
RubyGemshamsterindirect
RubyGemshamster3.0.0indirect
RubyGemsi18n1.15.2indirect
RubyGemsimmutable-struct2.5.0indirect
RubyGemsjson2.20.0indirect
RubyGemslanguage_server-protocol3.17.0.5indirect
RubyGemslino4.1.0indirect
RubyGemslint_roller1.1.0indirect
RubyGemslogger1.7.0indirect
RubyGemsminitarindirect
RubyGemsminitar1.1.0indirect
RubyGemsminitest5.27.0indirect
RubyGemsnet-http0.9.1indirect
RubyGemsoctokit10.0.0indirect
RubyGemsopen41.3.4indirect
RubyGemsparallel1.28.0indirect
RubyGemsparser3.3.11.1indirect
RubyGemsprism1.9.0indirect
RubyGemspublic_suffix6.0.2indirect
RubyGemsracc1.8.1indirect
RubyGemsrainbow3.1.1indirect
RubyGemsrakeindirect
RubyGemsrake13.4.2indirect
RubyGemsrake_circle_ciindirect
RubyGemsrake_circle_ci0.13.0indirect
RubyGemsrake_factoryindirect
RubyGemsrake_factory0.33.0indirect
RubyGemsrake_gitindirect
RubyGemsrake_git0.2.0indirect
RubyGemsrake_git_cryptindirect
RubyGemsrake_git_crypt0.4.0indirect
RubyGemsrake_githubindirect
RubyGemsrake_github0.17.0indirect
RubyGemsrake_gpgindirect
RubyGemsrake_gpg0.20.0indirect
RubyGemsrake_sshindirect
RubyGemsrake_ssh0.12.0indirect
RubyGemsrbnacl7.1.2indirect
RubyGemsrchardet1.8.0indirect
RubyGemsregexp_parser2.12.0indirect
RubyGemsrspecindirect
RubyGemsrspec3.13.2indirect
RubyGemsrspec-core3.13.6indirect
RubyGemsrspec-expectations3.13.5indirect
RubyGemsrspec-mocks3.13.7indirect
RubyGemsrspec-support3.13.7indirect
RubyGemsrubocopindirect
RubyGemsrubocop1.86.1indirect
RubyGemsrubocop-ast1.49.1indirect
RubyGemsrubocop-rakeindirect
RubyGemsrubocop-rake0.7.1indirect
RubyGemsrubocop-rspecindirect
RubyGemsrubocop-rspec3.9.0indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemsruby_git_crypt0.1.0indirect
RubyGemsruby_gpg20.12.0indirect
RubyGemsrubyzipindirect
RubyGemsrubyzip3.4.1indirect
RubyGemssawyer0.9.3indirect
RubyGemssecurerandom0.4.1indirect
RubyGemssimplecovindirect
RubyGemssimplecov0.22.0indirect
RubyGemssimplecov-html0.12.3indirect
RubyGemssimplecov_json_formatter0.1.4indirect
RubyGemssshkey2.0.0indirect
RubyGemstzinfo2.0.6indirect
RubyGemsunicode-display_width3.2.0indirect
RubyGemsunicode-emoji4.2.0indirect
RubyGemsuri1.1.1indirect
Dependency advisories 1

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

PackageVersionRelationSeverityAdvisoriesFixed in
excon0.111.0indirectmoderate11.5.0

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.26.0 — full methodology · metrics wiki.

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