Public record
Software health reportschema 0.15.0 · metrics 2.10.0 · 2026-07-20 07:35 UTC

voxpupuli / beaker

Puppet Acceptance Testing Harness

RubyApache-2.0★ 371 stars⑂ 335 forkssince Aug 2013View on GitHub ↗

voxpupuli/beaker holds a health index of 96 out of 100, placing it in the Exceptional band. It scores highest on Engineering Quality (90/100) and lowest on AI Readiness (34/100). It was last updated 2 days ago. 4 contributors account for most of its recent work.

96
overall / 100
Exceptional

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.

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

Ownership

Vox PupuliOrganization
200 followers389 public repossince Sep 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsbeaker7.6.0-2476 days ago

Metrics by category

Vitality

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

83Excellent · 21% of overall
How it's scored
36/36Push recencylast push 2 days ago
14.5/36Commit cadence21/52 weeks with commits
18/18Commit volume122 commits in the last year
10/10OpenSSF Scorecard: Maintained27 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year122
human_commit_share
days_since_last_push2
active_weeks_last_year21
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 6 days ago
27/27Release cadencea release every ~36.9 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv7.6.0
releases_from_tagsno
days_since_latest_release6
mean_days_between_releases36.9

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

82Excellent · 17% of overall
How it's scored
41.7/60Stars371 stars
21/25Forks335 forks
12.7/15Watchers197 watchers
Inputs used
forks335
stars371
watchers197
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/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_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
69.7/80Total downloads5,114,190 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesbeaker
dependents
ecosystemsrubygems
total_downloads5,114,190
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?

89Excellent · 23% of overall
How it's scored
43.2/54Bus factor4 contributor(s) cover half of all commits
18.9/22.5Commit distributiontop contributor authored 16% of commits
13.5/13.5Contributor breadth100 contributors
10/10OpenSSF Scorecard: Contributorsproject has 42 contributing companies or organizations
Inputs used
bus_factor4
contributors_sampled100
top_contributor_share0.16
How it's scored
39.6/42Issue resolution94% of issues closed
25.3/30PR acceptance1,554/1,841 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
9/15OpenSSF Scorecard: Code-ReviewFound 6/9 approved changesets -- score normalized to 6
Inputs used
merged_prs1,554
open_issues9
closed_issues151
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.944
closed_unmerged_prs287
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
16.6/25Owner reach200 followers of voxpupuli
25/25Track record389 public repos, account ~11 yr old
Inputs used
followers200
owner_typeOrganization
is_verified
owner_loginvoxpupuli
public_repos389
account_age_days4,332
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 6 days ago
20/20Version history247 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesbeaker
ecosystemsrubygems
any_deprecatedno
min_days_since_publish6

Engineering Quality

Are baseline engineering and documentation practices in place?

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

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://groups.google.com/forum/#!forum/puppet-beaker
10/10Repository description
10/10Topics1 topics
10/10Wiki
Inputs used
topicshacktoberfest
has_wikiyes
homepagehttps://groups.google.com/forum/#!forum/puppet-beaker
docs_sitehttps://groups.google.com/forum/#!forum/puppet-beaker
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

78Good · 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-Tests15 out of 15 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
4.5/7.5Code-ReviewFound 6/9 approved changesets -- score normalized to 6
2.5/2.5Contributorsproject has 42 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained27 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
4/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
3.5/5SASTSAST tool is not run on all commits -- score normalized to 7
4.5/5Security-Policysecurity policy file detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate7.8
Excluded from scoring (no data or not applicable): Branch-Protection. Remaining weights renormalized.

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.

34At Risk · 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
0/10Reproducible environment
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
8/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/201 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes32,462
source_files_sampled201
oversized_source_files0

Key facts

371GitHub stars
100contributors
122commits, last 12 months
2days since last push
100releases
4bus factor
9open issues
RubyGemspackage ecosystems

More detail

OpenSSF Scorecard 7.8 / 10
7.8aggregate

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 07:34 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-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
6Code-ReviewFound 6/9 approved changesets -- score normalized to 6
10Contributorsproject has 42 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained27 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
8Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
7SASTSAST tool is not run on all commits -- score normalized to 7
9Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
RubyGemsfaraday-retry~> 2.1Gemfile
RubyGemsgithub_changelog_generator~> 1.18Gemfile
All dependencies 31

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

RegistryPackageVersionRelation
RubyGemsfaraday-retrydirect
RubyGemsgithub_changelog_generatordirect
RubyGemsbase64indirect
RubyGemsbcrypt_pbkdfindirect
RubyGemsbeaker-hostgeneratorindirect
RubyGemsbeaker-rspecindirect
RubyGemsbenchmarkindirect
RubyGemsed25519indirect
RubyGemsfacterindirect
RubyGemsfakefsindirect
RubyGemshoconindirect
RubyGemsin-parallelindirect
RubyGemsinifileindirect
RubyGemsloggerindirect
RubyGemsminitarindirect
RubyGemsminitestindirect
RubyGemsnet-scpindirect
RubyGemsnet-sshindirect
RubyGemspstoreindirect
RubyGemspuppet-lintindirect
RubyGemspuppetlabs_spec_helperindirect
RubyGemsrakeindirect
RubyGemsreadlineindirect
RubyGemsrexmlindirect
RubyGemsrspecindirect
RubyGemsrspec-githubindirect
RubyGemsrsyncindirect
RubyGemsserverspecindirect
RubyGemsstringify-hashindirect
RubyGemsthorindirect
RubyGemsvoxpupuli-rubocopindirect
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.15.0 — full methodology · metrics wiki.

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