Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 15:04 UTC

RND-SOFT / bbk-utils

[MIRROR] Common classes and helpers for BBK library stack.

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

RND-SOFT/bbk-utils holds a health index of 7 out of 100, placing it in the Critical band. It scores highest on Engineering Quality (48/100) and lowest on Security (23/100). It was last updated today. A single contributor accounts for most of its recent work.

7
overall / 100
Critical

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.

7
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 40 is calibrated to 35 on the published index scale (record calibration 2026-08-02). High-Risk Jurisdiction Policy applies a 20% multiplier to weighted overall health and gives it an At Risk ceiling of 34.

Ownership

RNDSOFTOrganization · verified domain
9 followers50 public repossince Sep 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsbbk-utils1.1.6.409139-471 day ago

Metrics by category

Vitality

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

39Weak · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
8.3/36Commit cadence12/52 weeks with commits
15.6/18Commit volume53 commits in the last year
5/10OpenSSF Scorecard: Maintained7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year53
human_commit_share1
days_since_last_push0
active_weeks_last_year12
How it's scored
0/27Ships releasesno releases published
0/36Release recencyno releases
0/27Release cadenceno releases
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count0
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?

41Weak · 17% of overall
How it's scored
0/60Stars0 stars
0/25Forks0 forks
2.7/15Watchers4 watchers
Inputs used
forks0
stars0
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, shields.io
has_pull_request_templateno
How it's scored
48.9/80Total downloads51,308 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesbbk-utils
dependents
ecosystemsrubygems
total_downloads51,308
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?

46Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.5/22.5Commit distributiontop contributor authored 98% of commits
2.7/13.5Contributor breadth2 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.978
How it's scored
0/42Issue resolutionno issues or no data
0/30PR acceptanceno decided pull requests or no data
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
7.2/25Owner reach9 followers of RND-SOFT
24.4/25Track record50 public repos, account ~11 yr old
Inputs used
followers9
owner_typeOrganization
is_verifiedyes
owner_loginRND-SOFT
public_repos50
account_age_days4,032

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on rubygems
35/35Publish recencylatest publish 1 days ago
20/20Version history47 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesbbk-utils
ecosystemsrubygems
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

48Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://br.rnds.pro/ruby/bbk/utils
10/10Repository description
10/10Topics4 topics
10/10Wiki
Inputs used
topicsruby, gem, bbk, ruby-gem
has_wikiyes
homepagehttps://br.rnds.pro/ruby/bbk/utils
docs_sitehttps://br.rnds.pro/ruby/bbk/utils
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

23At Risk · 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
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
3.8/7.5Maintained7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
0/7.5Vulnerabilities13 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate2.1
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier20
security_posture_after_multiplier4
security_posture_before_jurisdiction21
Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Signed-Releases, Token-Permissions. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 20% multiplier and gives Security posture an At risk ceiling of 34.

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
advisories13
affected_packages4
assessed_packages66
unassessed_packages19
affected_by_severityhigh 4
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 66 resolved dependencies against OSV. 19 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.

25At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
1.6/40Legible commit history3 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.03
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/28 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes35,034
source_files_sampled28
oversized_source_files0

Key facts

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

More detail

OpenSSF Scorecard 2.1 / 10
2.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-09-18 15:04 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
5Maintained7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities13 existing vulnerabilities detected
All dependencies 85

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

RegistryPackageVersionRelation
RubyGemsactivesupportindirect
RubyGemsactivesupport7.1.6indirect
RubyGemsaddressable2.8.0indirect
RubyGemsansi1.5.0indirect
RubyGemsast2.4.2indirect
RubyGemsaxiom-types0.1.1indirect
RubyGemsbase640.3.0indirect
RubyGemsbenchmark0.5.0indirect
RubyGemsbigdecimal4.0.1indirect
RubyGemsbundlerindirect
RubyGemsbyebugindirect
RubyGemsbyebug11.1.3indirect
RubyGemscoercible1.0.0indirect
RubyGemsconcurrent-ruby1.2.2indirect
RubyGemsconnection_pool3.0.2indirect
RubyGemsdescendants_tracker0.0.4indirect
RubyGemsdiff-lcs1.6.0indirect
RubyGemsdocile1.4.0indirect
RubyGemsdrb2.2.3indirect
RubyGemsequalizer0.0.11indirect
RubyGemserubis2.7.0indirect
RubyGemsfakerindirect
RubyGemsfaker2.19.0indirect
RubyGemsflay2.12.1indirect
RubyGemsflog4.6.4indirect
RubyGemsi18n1.14.1indirect
RubyGemsice_nine0.11.2indirect
RubyGemskwalify0.7.2indirect
RubyGemslaunchy2.5.0indirect
RubyGemslogger1.7.0indirect
RubyGemsminitest6.0.2indirect
RubyGemsmock_redisindirect
RubyGemsmutex_m0.3.0indirect
RubyGemsostructindirect
RubyGemsostruct0.6.3indirect
RubyGemsparallel1.21.0indirect
RubyGemsparser3.0.3.1indirect
RubyGemspath_expander1.1.0indirect
RubyGemsprism1.9.0indirect
RubyGemspublic_suffix4.0.6indirect
RubyGemsraccindirect
RubyGemsracc1.8.1indirect
RubyGemsrainbow3.0.0indirect
RubyGemsrakeindirect
RubyGemsrake12.3.3indirect
RubyGemsredisindirect
RubyGemsreek6.0.6indirect
RubyGemsregexp_parser2.2.0indirect
RubyGemsrexml3.2.5indirect
RubyGemsrspecindirect
RubyGemsrspec3.13.0indirect
RubyGemsrspec-core3.13.3indirect
RubyGemsrspec-expectations3.13.3indirect
RubyGemsrspec-mocks3.13.2indirect
RubyGemsrspec-support3.13.2indirect
RubyGemsrspec_junit_formatterindirect
RubyGemsrspec_junit_formatter0.4.1indirect
RubyGemsrubocopindirect
RubyGemsrubocop1.22.3indirect
RubyGemsrubocop-ast1.13.0indirect
RubyGemsrubocop-rspecindirect
RubyGemsrubocop-rspec2.6.0indirect
RubyGemsruby-progressbar1.11.0indirect
RubyGemsruby_parser3.22.0indirect
RubyGemsrubycriticindirect
RubyGemsrubycritic4.6.1indirect
RubyGemsrussianindirect
RubyGemsrussian0.6.0indirect
RubyGemssecurerandom0.4.1indirect
RubyGemssexp_processor4.17.5indirect
RubyGemssimplecovindirect
RubyGemssimplecov0.21.2indirect
RubyGemssimplecov-coberturaindirect
RubyGemssimplecov-cobertura2.1.0indirect
RubyGemssimplecov-consoleindirect
RubyGemssimplecov-console0.9.1indirect
RubyGemssimplecov-html0.12.3indirect
RubyGemssimplecov_json_formatter0.1.3indirect
RubyGemsterminal-tableindirect
RubyGemsterminal-table3.0.2indirect
RubyGemsthread_safe0.3.6indirect
RubyGemstty-which0.4.2indirect
RubyGemstzinfo2.0.6indirect
RubyGemsunicode-display_width2.1.0indirect
RubyGemsvirtus1.0.5indirect
Dependency advisories 4

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

PackageVersionRelationSeverityAdvisoriesFixed in
activesupport7.1.6indirecthigh38.1.2.1
addressable2.8.0indirecthigh12.9.0
concurrent-ruby1.2.2indirecthigh31.3.7
rexml3.2.5indirecthigh63.3.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 statisticsRubyGems.