Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-16 23:02 UTC

maedadev / bizside-ruby

RubyMIT★ 2 stars⑂ 8 forkssince Oct 2021View on GitHub ↗
KindLibraryNetwork servicehow this is determined

maedadev/bizside-ruby holds a health index of 53 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (77/100) and lowest on AI Readiness (26/100). It was last updated today. 3 contributors account for most of its recent work.

53
overall / 100
Moderate

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.

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

Ownership

maedadevOrganization
4 followers31 public repossince May 2019

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsbizside3.1.11-590 days ago

Metrics by category

Vitality

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

49Weak · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
5.5/36Commit cadence — 8/52 weeks with commits
10.8/18Commit volume — 15 commits in the last year
1/10OpenSSF Scorecard: Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year15
human_commit_share1
days_since_last_push0
active_weeks_last_year8
How it's scored
27/27Ships releases — 1 releases published
0/36Release recency — latest release 1,034 days ago
12.6/27Release cadence — cadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count1
latest_release_tagv2.3.7
releases_from_tagsno
days_since_latest_release1,034
mean_days_between_releases—
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?

36Weak · 17% of overall
How it's scored
0/60Stars — 2 stars
7/25Forks — 8 forks
0/15Watchers — 1 watchers
Inputs used
forks8
stars2
watchers1
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
49.9/80Total downloads — 63,476 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesbizside
dependents—
ecosystemsrubygems
total_downloads63,476
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?

77Good · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
15.5/22.5Commit distribution — top contributor authored 31% of commits
13.5/13.5Contributor breadth — 15 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor3
contributors_sampled15
top_contributor_share0.309
How it's scored
42/42Issue resolution — 100% of issues closed
27.8/30PR acceptance — 64/69 decided PRs merged
13/13Newcomer PR acceptance — 2/2 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-Review — Found 5/18 approved changesets -- score normalized to 2
Inputs used
merged_prs64
open_issues0
closed_issues4
prs_merged_7d2
prs_decided_7d2
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio1
closed_unmerged_prs5
first_time_authors_30d1
first_time_prs_merged_30d2
first_time_prs_decided_30d2
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
5/25Owner reach — 4 followers of maedadev
23/25Track record — 31 public repos, account ~7 yr old
Inputs used
followers4
owner_typeOrganization
is_verifiedno
owner_loginmaedadev
public_repos31
account_age_days2,743

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://www.rubydoc.info/gems/bizside/3.1.11
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_sitehttps://www.rubydoc.info/gems/bizside/3.1.11
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

41Weak · 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
1/2.5CI-Tests — 2 out of 5 merged PRs checked by a CI test -- score normalized to 4
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-Review — Found 5/18 approved changesets -- score normalized to 2
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0.8/7.5Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
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
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.5
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories — 1 affected: concurrent-ruby 1.3.4 (high 7.5)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
33.7/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 150 days ago
Inputs used
sourceosv
advisories3
affected_packages1
assessed_packages1
unassessed_packages53
affected_by_severityhigh 1
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 1 resolved dependencies against OSV. 53 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.

26At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
15.5/40Legible commit history — 29 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.29
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
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 — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
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 code — Ruby without a type-check config
55/55Manageable file sizes — 0/129 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes12,518
source_files_sampled129
oversized_source_files0

Key facts

2GitHub stars
15contributors
15commits, last 12 months
0days since last push
1releases
3bus factor
0open 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 ★ / 8 ⇿
0Stars
8Forks
1Releases

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.

2345678822021-102024-052026-11
Major 0Minor 0Patch 1

Each point covers 5 days.

OpenSSF Scorecard 3.5 / 10
3.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-11-16 23:02 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
4CI-Tests2 out of 5 merged PRs checked by a CI test -- score normalized to 4
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 5/18 approved changesets -- score normalized to 2
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
1Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 23
RegistryPackageVersion constraintManifest
RubyGemsrails—bizside_test_app/Gemfile
RubyGemsbizside—bizside_test_app/Gemfile
RubyGemsaws-sdk-s3—bizside_test_app/Gemfile
RubyGemscarrierwave—bizside_test_app/Gemfile
RubyGemscoffee-rails~> 4.2bizside_test_app/Gemfile
RubyGemsfog-aws—bizside_test_app/Gemfile
RubyGemsipaddress—bizside_test_app/Gemfile
RubyGemsjbuilder~> 2.5bizside_test_app/Gemfile
RubyGemsjquery-rails—bizside_test_app/Gemfile
RubyGemsmail~> 2.7.1bizside_test_app/Gemfile
RubyGemsmysql2>= 0.4.4bizside_test_app/Gemfile
RubyGemsnokogiri—bizside_test_app/Gemfile
RubyGemsredis~> 4.0bizside_test_app/Gemfile
RubyGemsrequest-log-analyzer—bizside_test_app/Gemfile
RubyGemsresque—bizside_test_app/Gemfile
RubyGemsresque-scheduler~> 4.8.0bizside_test_app/Gemfile
RubyGemsrmagick—bizside_test_app/Gemfile
RubyGemssass-rails~> 5.0bizside_test_app/Gemfile
RubyGemssqlite3>= 1.3bizside_test_app/Gemfile
RubyGemsturbolinks—bizside_test_app/Gemfile
RubyGemsuglifier>= 1.3.0bizside_test_app/Gemfile
RubyGemsconcurrent-ruby1.3.4bizside_test_app/Gemfile
RubyGemsitamae-plugin-recipe-selenium—bizside_test_app/Gemfile
All dependencies 54

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

RegistryPackageVersionRelation
RubyGemsaws-sdk-s3—direct
RubyGemsbizside—direct
RubyGemscarrierwave—direct
RubyGemscoffee-rails—direct
RubyGemsconcurrent-ruby—direct
RubyGemsconcurrent-ruby1.3.4direct
RubyGemsfog-aws—direct
RubyGemsipaddress—direct
RubyGemsitamae-plugin-recipe-selenium—direct
RubyGemsjbuilder—direct
RubyGemsjquery-rails—direct
RubyGemsmail—direct
RubyGemsmysql2—direct
RubyGemsnokogiri—direct
RubyGemsrails—direct
RubyGemsredis—direct
RubyGemsrequest-log-analyzer—direct
RubyGemsresque—direct
RubyGemsresque-scheduler—direct
RubyGemsrmagick—direct
RubyGemssass-rails—direct
RubyGemssqlite3—direct
RubyGemsturbolinks—direct
RubyGemsuglifier—direct
RubyGemsactivesupport—indirect
RubyGemsbenchmark—indirect
RubyGemsbyebug—indirect
RubyGemscapistrano—indirect
RubyGemscapybara—indirect
RubyGemscarrierwave-magic—indirect
RubyGemscsv—indirect
RubyGemscucumber—indirect
RubyGemscucumber-rails—indirect
RubyGemsdatabase_cleaner—indirect
RubyGemsdevise—indirect
RubyGemsfaraday—indirect
RubyGemsffi—indirect
RubyGemsltsv—indirect
RubyGemsmime-types—indirect
RubyGemsmimemagic—indirect
RubyGemsminitest—indirect
RubyGemsminitest-rails—indirect
RubyGemsminitest-reporters—indirect
RubyGemsmulti_json—indirect
RubyGemsmutex_m—indirect
RubyGemsnkf—indirect
RubyGemspuma—indirect
RubyGemsrails-controller-testing—indirect
RubyGemsrake—indirect
RubyGemsRedCloth—indirect
RubyGemssimplecov—indirect
RubyGemsspring—indirect
RubyGemsweb-console—indirect
RubyGemswebmock—indirect
Dependency advisories 1

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

PackageVersionRelationSeverityAdvisoriesFixed in
concurrent-ruby1.3.4directhigh31.3.7

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.