Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-18 09:14 UTC

puppetlabs / puppet_litmus

Providing a simple command line tool for puppet content creators, to enable simple and complex test deployments.

RubyApache-2.0★ 90 stars⑂ 53 forkssince Sep 2018View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

puppetlabs/puppet_litmus holds a health index of 91 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (93/100) and lowest on AI Readiness (49/100). It was last updated today. 5 contributors account for most of its recent work.

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

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

Ownership

PuppetOrganization
428 followers722 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
RubyGemspuppet_litmus2.8.0-960 days ago

Metrics by category

Vitality

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

80Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
12.5/36Commit cadence18/52 weeks with commits
15.5/18Commit volume52 commits in the last year
10/10OpenSSF Scorecard: Maintained24 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year52
human_commit_share0.99
days_since_last_push0
active_weeks_last_year18
How it's scored
27/27Ships releases35 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~41.9 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count35
latest_release_tagv2.8.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases41.9

Community & Adoption

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

76Good · 17% of overall
How it's scored
31.6/60Stars90 stars
14.3/25Forks53 forks
10.8/15Watchers87 watchers
Inputs used
forks53
stars90
watchers87
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 (Apache-2.0)
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_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesbadge.fury.io, github.com, shields.io
has_pull_request_templateyes
How it's scored
67.3/80Total downloads2,991,876 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagespuppet_litmus
dependents
ecosystemsrubygems
total_downloads2,991,876
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?

93Exceptional · 23% of overall
How it's scored
45.9/54Bus factor5 contributor(s) cover half of all commits
18.7/22.5Commit distributiontop contributor authored 17% of commits
13.5/13.5Contributor breadth45 contributors
10/10OpenSSF Scorecard: Contributorsproject has 17 contributing companies or organizations
Inputs used
bus_factor5
contributors_sampled45
top_contributor_share0.167
How it's scored
38.8/42Issue resolution92% of issues closed
27/30PR acceptance481/534 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs481
open_issues7
closed_issues85
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.924
closed_unmerged_prs53
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
0/20Verified domainverified-domain status not read for this organization
18.9/25Owner reach428 followers of puppetlabs
25/25Track record722 public repos, account ~16 yr old
Inputs used
followers428
owner_typeOrganization
is_verified
owner_loginpuppetlabs
public_repos722
account_age_days5,983
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 0 days ago
20/20Version history96 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagespuppet_litmus
ecosystemsrubygems
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 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
16/20OpenSSF Scorecard: CI-Tests9 out of 11 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics2 topics
0/10Wiki
Inputs used
topicstesting, hacktoberfest
has_wikino
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

56Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2/2.5CI-Tests9 out of 11 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 17 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
7.5/7.5Maintained24 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
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-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.6
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. 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.

49Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
36.1/40Legible commit history67 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.677
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapdocs/md/go.mod (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config.rubocop.yml
0/11Static type checking
0/10Reproducible environment
10/10Demonstrated agent practice10 of the last 100 commits agent-authored or agent-credited
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.1
toolchain_manifestsdocs/md/go.mod
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/19 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes20,825
source_files_sampled19
oversized_source_files0

Key facts

90GitHub stars
45contributors
52commits, last 12 months
0days since last push
35releases
5bus factor
7open issues
RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 53 ⇿
0Stars
53Forks
31Releases

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.

01020304050605352019-032022-082026-01
Major 2Minor 11Patch 17

Each point covers 7 days.

OpenSSF Scorecard 5.6 / 10
5.6aggregate

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-18 09:13 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
8CI-Tests9 out of 11 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 17 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained24 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
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
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
RubyGemsbolt>= 5.0Gemfile
All dependencies 17

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

RegistryPackageVersionRelation
RubyGemsboltdirect
RubyGemsdocker-apiindirect
RubyGemsparallelindirect
RubyGemspryindirect
RubyGemspuppet-modulebuilderindirect
RubyGemsrakeindirect
RubyGemsretryableindirect
RubyGemsrspecindirect
RubyGemsrspec-collection_matchersindirect
RubyGemsrspec-itsindirect
RubyGemsrubocopindirect
RubyGemsrubocop-performanceindirect
RubyGemsrubocop-rspecindirect
RubyGemssimplecovindirect
RubyGemssimplecov-consoleindirect
RubyGemstty-spinnerindirect
RubyGemsyardindirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.31.0 — full methodology · metrics wiki.

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