Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 02:34 UTC

puppetlabs / puppet

Server automation framework and application

RubyApache-2.0★ 7,923 stars⑂ 2,209 forkssince Sep 2010View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

puppetlabs/puppet holds a health index of 34 out of 100, placing it in the At Risk band. It scores highest on Community & Adoption (94/100) and lowest on Vitality (45/100). It was last updated 21 days ago. 5 contributors account for most of its recent work.

34
overall / 100
At Risk

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.

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

Ownership

PuppetOrganization · verified domain
428 followers723 public repossince Mar 2010

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemspuppet8.10.0-836674 days ago

Metrics by category

Vitality

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

45Weak · 21% of overall
How it's scored
28.8/36Push recencylast push 21 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_share1
days_since_last_push21
active_weeks_last_year0
How it's scored
27/27Ships releases12 releases published
7.2/36Release recencylatest release 674 days ago
27/27Release cadencea release every ~14.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count12
latest_release_tag8.10.0
releases_from_tagsno
days_since_latest_release674
mean_days_between_releases14.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?

94Exceptional · 17% of overall

Popularity & adoption

100Exceptional
How it's scored
60/60Stars7,923 stars
25/25Forks2,209 forks
14.7/15Watchers450 watchers
Inputs used
forks2,209
stars7,923
watchers450
growth_stateorganic
growth_factor_pct100

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_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesbadge.fury.io, github.com
has_pull_request_templateno
How it's scored
77.8/80Total downloads30,625,409 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagespuppet
dependents
ecosystemsrubygems
total_downloads30,625,409
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?

81Excellent · 23% of overall
How it's scored
45.9/54Bus factor5 contributor(s) cover half of all commits
18.4/22.5Commit distributiontop contributor authored 18% of commits
13.5/13.5Contributor breadth100 contributors
10/10OpenSSF Scorecard: Contributorsproject has 35 contributing companies or organizations
Inputs used
bus_factor5
contributors_sampled100
top_contributor_share0.182
How it's scored
23.6/42Issue resolution56% of issues closed
22.4/30PR acceptance7,024/9,392 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
9/15OpenSSF Scorecard: Code-ReviewFound 11/17 approved changesets -- score normalized to 6
Inputs used
merged_prs7,024
open_issues56
closed_issues72
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.562
closed_unmerged_prs2,368
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
18.9/25Owner reach428 followers of puppetlabs
25/25Track record723 public repos, account ~16 yr old
Inputs used
followers428
owner_typeOrganization
is_verifiedyes
owner_loginpuppetlabs
public_repos723
account_age_days5,993
How it's scored
25/25Published & resolvable1 package(s) on rubygems
14/35Publish recencylatest publish 674 days ago
20/20Version history836 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagespuppet
ecosystemsrubygems
any_deprecatedno
min_days_since_publish674

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows5 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 11 merged PRs checked by a CI test -- score normalized to 0
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 sitehttps://puppet.com/open-source/#osp
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepagehttps://puppet.com/open-source/#osp
docs_sitehttps://puppet.com/open-source/#osp
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

51Moderate · 16% of overall
How it's scored
1.5/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionno data
0/2.5CI-Tests0 out of 11 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-ReviewFound 11/17 approved changesets -- score normalized to 6
2.5/2.5Contributorsproject has 35 contributing companies or organizations
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/5SASTSAST tool is not run on all commits -- score normalized to 0
4.5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate3.9
Excluded from scoring (no data or not applicable): Branch-Protection, 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
advisories0
affected_packages0
assessed_packages1
unassessed_packages41
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 1 resolved dependencies against OSV. 41 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.

61Moderate · 4% of overall
How it's scored
45/45Agent instructionsreferences/man/agent.md
0/15Machine-readable docs (llms.txt)
38.4/40Legible commit history72 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.72
agent_instruction_filesreferences/man/agent.md
agent_instruction_max_bytes11,845
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 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
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeRuby without a type-check config
54.6/55Manageable file sizes14/2,158 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes146,680
source_files_sampled2,158
oversized_source_files14
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

7,923GitHub stars
100contributors
0commits, last 12 months
21days since last push
12releases
5bus factor
56open issues
RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-07-21: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 7923 stars today.

More detail

Star and fork history 7,912 ★ / 2,209 ⇿
7,912Stars
2,209Forks
12Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

Star history is shown as collected on 2026-07-21. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

02,0004,0006,0008,0007,9122,209192016-042021-052026-07
Major 0Minor 10Patch 2

Each point covers 10 days.

OpenSSF Scorecard 3.9 / 10
3.9aggregate

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-28 02:34 UTC

2Binary-Artifactsbinaries present in source code
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
0CI-Tests0 out of 11 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 11/17 approved changesets -- score normalized to 6
10Contributorsproject has 35 contributing companies or organizations
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
0SASTSAST tool is not run on all commits -- score normalized to 0
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 51
RegistryPackageVersion constraintManifest
RubyGemsfacterGemfile
RubyGemssemantic_puppetGemfile
RubyGemspuppet-resource_apiGemfile
RubyGemsdiff-lcs~> 1.3Gemfile
RubyGemshieraGemfile
RubyGemshiera-eyamlGemfile
RubyGemshocon~> 1.0Gemfile
RubyGemsminitar~> 0.9Gemfile
RubyGemsmsgpack~> 1.2Gemfile
RubyGemsrdocGemfile
RubyGemspuppetserver-ca~> 2.0Gemfile
RubyGemssyslog~> 0.1.1Gemfile
RubyGemsCFPropertyListGemfile
RubyGemsffi>= 1.15.5Gemfile
RubyGemsjson-schema~> 2.0Gemfile
RubyGemsracc1.5.2Gemfile
RubyGemsrakeGemfile
RubyGemsrspec~> 3.1Gemfile
RubyGemsrspec-expectationsGemfile
RubyGemsrspec-its~> 1.1Gemfile
RubyGemsvcr~> 6.1Gemfile
RubyGemswebmock~> 3.0Gemfile
RubyGemswebrick~> 1.7Gemfile
RubyGemsyardGemfile
RubyGemsrubocop~> 1.0Gemfile
RubyGemsrubocop-i18n~> 3.0Gemfile
RubyGemsrubocop-performance~> 1.0Gemfile
RubyGemsrubocop-rake~> 0.6Gemfile
RubyGemsrubocop-rspec~> 2.0Gemfile
RubyGemsmemory_profilerGemfile
RubyGemspryGemfile
RubyGemsruby-prof>= 0.16.0Gemfile
RubyGemspackagingGemfile
RubyGemsgettext-setup~> 1.0Gemfile
RubyGemsronn~> 0.7.3Gemfile
RubyGemspuppet-stringsGemfile
RubyGemspandoc-rubyGemfile
RubyGemsbeakeracceptance/Gemfile
RubyGemsbeaker-puppetacceptance/Gemfile
RubyGemsbeaker-hostgeneratoracceptance/Gemfile
RubyGemsbeaker-absacceptance/Gemfile
RubyGemsbeaker-vagrantacceptance/Gemfile
RubyGemsbeaker-vmpooleracceptance/Gemfile
RubyGemsbeaker-vcloudacceptance/Gemfile
RubyGemsbeaker-dockeracceptance/Gemfile
RubyGemsbeaker-gkeacceptance/Gemfile
RubyGemsrake>= 12.3.3acceptance/Gemfile
RubyGemshttpartyacceptance/Gemfile
RubyGemsuuidtoolsacceptance/Gemfile
RubyGemsrspec~> 2.14.0acceptance/Gemfile
RubyGemsmocha~> 0.10.5acceptance/Gemfile
All dependencies 42

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

RegistryPackageVersionRelation
RubyGemsCFPropertyListdirect
RubyGemsdiff-lcsdirect
RubyGemsfacterdirect
RubyGemsgettext-setupdirect
RubyGemshocondirect
RubyGemshttpartydirect
RubyGemsjson-schemadirect
RubyGemsmemory_profilerdirect
RubyGemsminitardirect
RubyGemsmochadirect
RubyGemsmsgpackdirect
RubyGemspandoc-rubydirect
RubyGemsprydirect
RubyGemspuppet-resource_apidirect
RubyGemspuppet-stringsdirect
RubyGemspuppetserver-cadirect
RubyGemsracc1.5.2direct
RubyGemsrakedirect
RubyGemsronndirect
RubyGemsrspecdirect
RubyGemsrspec-itsdirect
RubyGemsrubocopdirect
RubyGemsrubocop-i18ndirect
RubyGemsrubocop-performancedirect
RubyGemsrubocop-rakedirect
RubyGemsrubocop-rspecdirect
RubyGemsruby-profdirect
RubyGemssemantic_puppetdirect
RubyGemssyslogdirect
RubyGemsuuidtoolsdirect
RubyGemsvcrdirect
RubyGemswebmockdirect
RubyGemswebrickdirect
RubyGemsyarddirect
RubyGemsconcurrent-rubyindirect
RubyGemsdeep_mergeindirect
RubyGemsfast_gettextindirect
RubyGemsgetoptlongindirect
RubyGemslocaleindirect
RubyGemsmulti_jsonindirect
RubyGemsr10kindirect
RubyGemsscanfindirect
Dependency advisories 0

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: 0 carry known advisories, of which 0 are direct. 41 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 statisticsRubyGems.