Public record
Software health reportschema 0.16.0 · metrics 2.10.0 · 2026-07-20 14:47 UTC

thekompanee / fuubar

The instafailing RSpec progress bar formatter

RubyMIT★ 963 stars⑂ 67 forkssince Nov 2010View on GitHub ↗

thekompanee/fuubar holds a health index of 51 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (85/100) and lowest on Vitality (10/100). It was last updated 1619 days ago. A single contributor accounts for most of its recent work.

51
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.

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

Ownership

The KompaneeOrganization
2 followers2 public repossince Oct 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsfuubar2.5.1-322027 days ago

Metrics by category

Vitality

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

10Critical · 21% of overall
How it's scored
0/36Push recencylast push 1,619 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 commits in the last year
0/10OpenSSF Scorecard: Maintained0 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_push1,619
active_weeks_last_year0
How it's scored
16.2/27Ships releases2 version tags (no GitHub releases)
0/36Release recencylatest release 4,452 days ago
5.4/27Release cadencea release every ~663.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count2
latest_release_tagv1.3.3
releases_from_tagsyes
days_since_latest_release4,452
mean_days_between_releases663.1
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?

85Excellent · 17% of overall
How it's scored
48.4/60Stars963 stars
15.2/25Forks67 forks
5/15Watchers9 watchers
Inputs used
forks67
stars963
watchers9
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateyes
How it's scored
80/80Total downloads71,667,335 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesfuubar
dependents
ecosystemsrubygems
total_downloads71,667,335
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?

50Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
2.8/22.5Commit distributiontop contributor authored 88% of commits
13.5/13.5Contributor breadth20 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled20
top_contributor_share0.875
How it's scored
40.9/42Issue resolution97% of issues closed
6.9/30PR acceptance11/48 decided PRs merged
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_prs11
open_issues2
closed_issues73
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.973
closed_unmerged_prs37
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
3.4/25Owner reach2 followers of thekompanee
15.5/25Track record2 public repos, account ~9 yr old
Inputs used
followers2
owner_typeOrganization
is_verified
owner_loginthekompanee
public_repos2
account_age_days3,570
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on rubygems
4/35Publish recencylatest publish 2,027 days ago
20/20Version history32 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesfuubar
ecosystemsrubygems
any_deprecatedno
min_days_since_publish2,027

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
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 sitehttp://jeffkreeftmeijer.com/2010/fuubar-the-instafailing-rspec-progress-bar-formatter/
10/10Repository description
10/10Topics3 topics
10/10Wiki
Inputs used
topicsrspec, byebug, pry
has_wikiyes
homepagehttp://jeffkreeftmeijer.com/2010/fuubar-the-instafailing-rspec-progress-bar-formatter/
docs_sitehttp://jeffkreeftmeijer.com/2010/fuubar-the-instafailing-rspec-progress-bar-formatter/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

40Weak · 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
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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-Permissionsdetected GitHub workflow tokens with excessive permissions
2.2/7.5Vulnerabilities7 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate2.5
Excluded from scoring (no data or not applicable): CI-Tests, Packaging, Signed-Releases. 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
advisories7
affected_packages1
assessed_packages26
unassessed_packages3
affected_by_severityhigh 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 26 resolved dependencies against OSV. 3 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.

35Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno 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 environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency 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_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/4 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes8,050
source_files_sampled4
oversized_source_files0

Key facts

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

More detail

OpenSSF Scorecard 2.5 / 10
2.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-07-20 14:46 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
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update 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
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
3Vulnerabilities7 existing vulnerabilities detected
All dependencies 29

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

RegistryPackageVersionRelation
RubyGemsast2.4.1indirect
RubyGemsawesome_print1.8.0indirect
RubyGemsdiff-lcs1.3indirect
RubyGemsdiff-lcs1.4.4indirect
RubyGemsparallel1.20.1indirect
RubyGemsparser2.7.2.0indirect
RubyGemsrainbow3.0.0indirect
RubyGemsregexp_parser2.0.1indirect
RubyGemsrexml3.2.4indirect
RubyGemsrspecindirect
RubyGemsrspec3.10.0indirect
RubyGemsrspec3.8.0indirect
RubyGemsrspec-coreindirect
RubyGemsrspec-core3.10.0indirect
RubyGemsrspec-core3.8.0indirect
RubyGemsrspec-expectations3.10.0indirect
RubyGemsrspec-expectations3.8.3indirect
RubyGemsrspec-mocks3.10.0indirect
RubyGemsrspec-mocks3.8.0indirect
RubyGemsrspec-support3.10.0indirect
RubyGemsrspec-support3.8.0indirect
RubyGemsrubocop1.6.1indirect
RubyGemsrubocop-ast1.3.0indirect
RubyGemsrubocop-performance1.9.1indirect
RubyGemsrubocop-rspec2.1.0indirect
RubyGemsruby-progressbarindirect
RubyGemsruby-progressbar1.10.0indirect
RubyGemsruby-progressbar1.11.0indirect
RubyGemsunicode-display_width1.7.0indirect
Dependency advisories 1

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

PackageVersionRelationSeverityAdvisoriesFixed in
rexml3.2.4indirecthigh73.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.16.0 — full methodology · metrics wiki.

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