Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-24 07:24 UTC

kwent / pgbouncerhero

A dashboard for your PgBouncers.

Ruby · HTMLMIT★ 289 stars⑂ 13 forkssince Jan 2017View on GitHub ↗
KindLibraryPluginNetwork serviceWeb interfacehow this is determined

kwent/pgbouncerhero holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (86/100) and lowest on Community & Adoption (54/100). It was last updated today. A single contributor accounts for most of its recent work.

83
overall / 100
Excellent

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.

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

Ownership

Quentin RousseauPersonal account
228 followers119 public repossince Jun 2011CTO, Co-Founder at @rootlyhq

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemspgbouncerhero3.2.0-90 days ago

Metrics by category

Vitality

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

75Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
13.8/36Commit cadence — 20/52 weeks with commits
14.8/18Commit volume — 43 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year43
human_commit_share0.69
days_since_last_push0
active_weeks_last_year20
How it's scored
27/27Ships releases — 7 releases published
36/36Release recency — latest release 0 days ago
5.4/27Release cadence — a release every ~513.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count7
latest_release_tagv3.2.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases513.9
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?

54Moderate · 17% of overall
How it's scored
39.9/60Stars — 289 stars
9/25Forks — 13 forks
3.9/15Watchers — 6 watchers
Inputs used
forks13
stars289
watchers6
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_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, github.com, shields.io
has_pull_request_templateno
How it's scored
50.3/80Total downloads — 69,764 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagespgbouncerhero
dependents—
ecosystemsrubygems
total_downloads69,764
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?

64Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.8/22.5Commit distribution — top contributor authored 96% of commits
4.1/13.5Contributor breadth — 3 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.965
How it's scored
42/42Issue resolution — 100% of issues closed
28.4/30PR acceptance — 54/57 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/15 approved changesets -- score normalized to 0
Inputs used
merged_prs54
open_issues0
closed_issues9
prs_merged_7d19
prs_decided_7d19
prs_merged_30d19
prs_decided_30d19
issue_closed_ratio1
closed_unmerged_prs3
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
17/25Owner reach — 228 followers of kwent
25/25Track record — 119 public repos, account ~15 yr old
Inputs used
followers228
owner_typeUser
is_verified—
owner_loginkwent
public_repos119
account_age_days5,536
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

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 — 9 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagespgbouncerhero
ecosystemsrubygems
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — .rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 15 out of 15 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

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://github.com/kwent/pgbouncerhero#readme
10/10Repository description
10/10Topics — 5 topics
0/10Wiki
Inputs used
topicspgbouncer, gui, postgresql, dashboard, engine
has_wikino
homepage—
docs_sitehttps://github.com/kwent/pgbouncerhero#readme
has_readmeyes
has_docs_diryes
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 — 15 out of 15 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/15 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 4 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 0 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 — no data
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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.5
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. 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
advisories0
affected_packages0
assessed_packages68
unassessed_packages14
affected_by_severitynone
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 68 resolved dependencies against OSV. 14 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.

72Good · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
0/15Machine-readable docs (llms.txt)
25.5/40Legible commit history — 33 of 69 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.478
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes5,146
How it's scored
18/18One-command bootstrap — mise.toml
22/22Automated tests
11/11Lint / format config — .rubocop.yml
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 31 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_dockerfileyes
typed_languageno
bootstrap_filesmise.toml
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.31
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/31 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes15,501
source_files_sampled31
oversized_source_files0

Key facts

289GitHub stars
3contributors
43commits, last 12 months
0days since last push
7releases
1bus 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 ★ / 13 ⇿
0Stars
13Forks
4Releases

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.

0246810121222017-042021-122026-08
Major 2Minor 0Patch 2

Each point covers 9 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-08-24 07:24 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests15 out of 15 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/15 approved changesets -- score normalized to 0
10Contributorsproject has 4 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 0 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
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
RubyGemspropshaft—Gemfile
RubyGemspuma—Gemfile
All dependencies 82

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

RegistryPackageVersionRelation
RubyGemspropshaft—direct
RubyGemspropshaft1.3.2direct
RubyGemspuma8.0.2direct
RubyGemsactionpack8.1.3.1indirect
RubyGemsactionview8.1.3.1indirect
RubyGemsactivesupport8.1.3.1indirect
RubyGemsappraisal—indirect
RubyGemsappraisal2.5.0indirect
RubyGemsast2.4.3indirect
RubyGemsbase640.3.0indirect
RubyGemsbigdecimal4.1.2indirect
RubyGemsbuilder3.3.0indirect
RubyGemsconcurrent-ruby1.3.8indirect
RubyGemsconnection_pool—indirect
RubyGemsconnection_pool3.0.2indirect
RubyGemscrass1.0.7indirect
RubyGemsdrb2.2.3indirect
RubyGemserb6.0.6indirect
RubyGemserubi1.13.1indirect
RubyGemsherb—indirect
RubyGemsherb0.10.3indirect
RubyGemsi18n1.15.2indirect
RubyGemsimportmap-rails—indirect
RubyGemsimportmap-rails2.2.3indirect
RubyGemsio-console0.8.2indirect
RubyGemsirb1.18.0indirect
RubyGemsjson2.21.2indirect
RubyGemslanguage_server-protocol3.17.0.6indirect
RubyGemslint_roller1.1.0indirect
RubyGemslogger1.7.0indirect
RubyGemsloofah2.25.2indirect
RubyGemsminitest—indirect
RubyGemsminitest6.0.6indirect
RubyGemsnio4r2.7.5indirect
RubyGemsnokogiri1.19.4indirect
RubyGemsparallel1.28.0indirect
RubyGemsparser3.3.12.0indirect
RubyGemspg—indirect
RubyGemspg1.6.3indirect
RubyGemspp0.6.4indirect
RubyGemsprettyprint0.2.0indirect
RubyGemsprism1.9.0indirect
RubyGemsracc1.8.1indirect
RubyGemsrack3.2.7indirect
RubyGemsrack-session2.1.2indirect
RubyGemsrack-test2.2.0indirect
RubyGemsrackup2.3.1indirect
RubyGemsrails-dom-testing2.3.0indirect
RubyGemsrails-html-sanitizer1.7.1indirect
RubyGemsrailties—indirect
RubyGemsrailties8.1.3.1indirect
RubyGemsrainbow3.1.1indirect
RubyGemsrake—indirect
RubyGemsrake13.4.2indirect
RubyGemsrbs4.1.2indirect
RubyGemsrdoc8.0.0indirect
RubyGemsregexp_parser2.12.0indirect
RubyGemsreline0.6.3indirect
RubyGemsrubocop—indirect
RubyGemsrubocop1.89.0indirect
RubyGemsrubocop-ast1.50.0indirect
RubyGemsrubocop-performance1.26.1indirect
RubyGemsrubocop-rails2.34.3indirect
RubyGemsrubocop-rails-omakase—indirect
RubyGemsrubocop-rails-omakase1.1.0indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemssecurerandom0.4.1indirect
RubyGemsstimulus-rails—indirect
RubyGemsstimulus-rails1.3.4indirect
RubyGemstailwindcss-rails—indirect
RubyGemstailwindcss-rails4.6.0indirect
RubyGemstailwindcss-ruby4.3.3indirect
RubyGemsthor1.5.0indirect
RubyGemstsort0.2.0indirect
RubyGemsturbo-rails—indirect
RubyGemsturbo-rails2.0.23indirect
RubyGemstzinfo2.0.6indirect
RubyGemsunicode-display_width3.2.0indirect
RubyGemsunicode-emoji4.2.0indirect
RubyGemsuri1.1.1indirect
RubyGemsuseragent0.16.11indirect
RubyGemszeitwerk2.8.3indirect
Dependency advisories 0

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

No known advisories affect the assessed dependencies.

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.