Public recordModerate
Software health reportschema 0.12.0 · metrics 2.10.0 · 2026-07-17 21:50 UTC
puppetlabs / puppet-data-service
Puppet Data Service - SolArch implementation of the PDS
puppetlabs/puppet-data-service holds a health index of 50 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (77/100) and lowest on Vitality (22/100). It was last updated 1347 days ago. 2 contributors account for most of its recent work.
50
overall / 100Software 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.
50
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)
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 50 is calibrated to 50 on the published index scale (record calibration 2026-08-02).
Ownership
PuppetOrganization
422 followers719 public repossince Mar 2010
This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.
Package ecosystems
| Registry | Package | Version | Downloads / mo | Versions | Last publish |
|---|---|---|---|---|---|
| Go | github.com/puppetlabs/puppet-data-service | v0.1.2 | - | 7 | 1533 days ago |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
22
Development activity
1Critical
How it's scored
| 0/36 | Push recency — last push 1,347 days ago |
| 0/36 | Commit cadence — 0/52 weeks with commits |
| 0/18 | Commit volume — 0 commits in the last year |
| 0/10 | OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
Inputs used
| commits_last_year | 0 |
| human_commit_share | — |
| days_since_last_push | 1,347 |
| active_weeks_last_year | 0 |
Release discipline
54Moderate
How it's scored
| 27/27 | Ships releases — 7 releases published |
| 0/36 | Release recency — latest release 1,533 days ago |
| 27/27 | Release cadence — a release every ~20 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases. |
Inputs used
| releases_count | 7 |
| latest_release_tag | v0.1.2 |
| releases_from_tags | no |
| days_since_latest_release | 1,533 |
| mean_days_between_releases | 20 |
Community & Adoption
Does the project have users, downloads, attention, and a welcoming setup for contributors?
37
Popularity & adoption
16Critical
How it's scored
| 7.7/60 | Stars — 4 stars |
| 5/25 | Forks — 5 forks |
| 3.3/15 | Watchers — 5 watchers |
Inputs used
| forks | 5 |
| stars | 4 |
| watchers | 5 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
60Moderate
How it's scored
| 22.5/22.5 | README |
| 0/22.5 | License — no license file detected |
| 18/18 | CONTRIBUTING guide |
| 13.5/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 0/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | no |
| readme_badges | — |
| has_contributing | yes |
| has_issue_template | no |
| has_code_of_conduct | yes |
| readme_badge_services | — |
| has_pull_request_template | no |
Sustainability & Governance
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
77
Maintainer resilience (bus factor)
55Moderate
How it's scored
| 25.2/54 | Bus factor — 2 contributor(s) cover half of all commits |
| 11.5/22.5 | Commit distribution — top contributor authored 49% of commits |
| 8.1/13.5 | Contributor breadth — 6 contributors |
| 10/10 | OpenSSF Scorecard: Contributors — project has 7 contributing companies or organizations |
Inputs used
| bus_factor | 2 |
| contributors_sampled | 6 |
| top_contributor_share | 0.49 |
Issue & PR responsiveness
96Exceptional
How it's scored
| 42/42 | Issue resolution — 100% of issues closed |
| 29.6/30 | PR acceptance — 73/74 decided PRs merged |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 12/15 | OpenSSF Scorecard: Code-Review — Found 6/7 approved changesets -- score normalized to 8 |
Inputs used
| merged_prs | 73 |
| open_issues | 0 |
| closed_issues | 2 |
| prs_merged_7d | — |
| prs_decided_7d | — |
| prs_merged_30d | — |
| prs_decided_30d | — |
| issue_closed_ratio | 1 |
| closed_unmerged_prs | 1 |
| 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.
Ownership & stewardship
92Excellent
How it's scored
| 30/30 | Ownership backing — organization-owned |
| 0/20 | Verified domain — verified-domain status not read for this organization |
| 18.9/25 | Owner reach — 422 followers of puppetlabs |
| 25/25 | Track record — 719 public repos, account ~16 yr old |
Inputs used
| followers | 422 |
| owner_type | Organization |
| is_verified | — |
| owner_login | puppetlabs |
| public_repos | 719 |
| account_age_days | 5,952 |
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
Package maintenance
69Good
How it's scored
| 25/25 | Published & resolvable — 1 package(s) on go |
| 4/35 | Publish recency — latest publish 1,533 days ago |
| 20/20 | Version history — 7 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | github.com/puppetlabs/puppet-data-service |
| ecosystems | go |
| any_deprecated | no |
| min_days_since_publish | 1,533 |
Engineering Quality
Are baseline engineering and documentation practices in place?
69
Engineering practices
48Weak
How it's scored
| 24/24 | CI workflows — 3 workflow(s) |
| 24/24 | Tests present |
| 0/16 | Linter config |
| 0/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 0/20 | OpenSSF Scorecard: CI-Tests — 0 out of 13 merged PRs checked by a CI test -- score normalized to 0 |
Inputs used
| has_ci | yes |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | no |
| has_precommit_config | no |
Documentation
100Exceptional
How it's scored
| 30/30 | README |
| 25/25 | Documentation directory |
| 15/15 | Documentation / homepage site — https://github.com/puppetlabs/puppet-data-service |
| 10/10 | Repository description |
| 10/10 | Topics — 3 topics |
| 10/10 | Wiki |
Inputs used
| topics | self-service, puppet-data-service, experimental |
| has_wiki | yes |
| homepage | https://github.com/puppetlabs/puppet-data-service |
| docs_site | https://github.com/puppetlabs/puppet-data-service |
| has_readme | yes |
| has_docs_dir | yes |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
41
Security posture
41Weak
How it's scored
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 0/7.5 | Branch-Protection — no data |
| 0/2.5 | CI-Tests — 0 out of 13 merged PRs checked by a CI test -- score normalized to 0 |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 6/7.5 | Code-Review — Found 6/7 approved changesets -- score normalized to 8 |
| 2.5/2.5 | Contributors — project has 7 contributing companies or organizations |
| 10/10 | Dangerous-Workflow — no dangerous workflow patterns detected |
| 7.5/7.5 | Dependency-Update-Tool — update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 0/2.5 | License — license file not detected |
| 0/7.5 | Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| 0/5 | Packaging — no data |
| 0/5 | Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
| 0/5 | SAST — SAST tool is not run on all commits -- score normalized to 0 |
| 4.5/5 | Security-Policy — security policy file detected |
| 0/7.5 | Signed-Releases — Project has not signed or included provenance with any releases. |
| 0/7.5 | Token-Permissions — detected GitHub workflow tokens with excessive permissions |
| 0/7.5 | Vulnerabilities — 53 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 16 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 2 |
| scorecard_aggregate | 4.1 |
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.
39
Agent context & guidance
1Critical
How it's scored
| 0/45 | Agent instructions — no CLAUDE.md / AGENTS.md / editor rules |
| 0/15 | Machine-readable docs (llms.txt) |
| 0/40 | Legible commit history — no data |
Inputs used
| has_llms_txt | no |
| 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.
Verify loop (build / test / typecheck)
61Moderate
How it's scored
| 18/18 | One-command bootstrap — Makefile, golang/pds-cli/Makefile |
| 22/22 | Automated tests |
| 0/11 | Lint / format config |
| 0/11 | Static type checking |
| 10/10 | Reproducible environment — Dockerfile, lockfile |
| 0/10 | Demonstrated agent practice — no data |
| 0/8 | Automated maintenance — no data |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | Gemfile.lock, go.sum |
| has_dockerfile | yes |
| typed_language | no |
| bootstrap_files | Makefile, golang/pds-cli/Makefile |
| has_devcontainer | no |
| has_linter_config | no |
| 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.
Code legibility for models
53Moderate
How it's scored
| 0/45 | Type-checkable code — Ruby without a type-check config |
| 53.3/55 | Manageable file sizes — 1/33 source files over 60KB |
Inputs used
| primary_language | Ruby |
| largest_source_bytes | 68,108 |
| source_files_sampled | 33 |
| oversized_source_files | 1 |
How it's scored
| 40/40 | API schema (OpenAPI/GraphQL/proto) — app/openapi.yaml |
| 0/20 | MCP server |
| 0/40 | Runnable examples |
Inputs used
| example_dirs | — |
| has_mcp_signal | no |
| api_schema_files | app/openapi.yaml |
| interfaces_expected_of | network-service |
Key facts
4GitHub stars
6contributors
0commits, last 12 months
1,347days since last push
7releases
2bus factor
0open issues
Go, RubyGemspackage ecosystems
More detail
OpenSSF Scorecard 4.1 / 10
4.1aggregate
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).
| 10 | Binary-Artifacts | no binaries found in the repo |
| n/a | Branch-Protection | internal 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 |
| 0 | CI-Tests | 0 out of 13 merged PRs checked by a CI test -- score normalized to 0 |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 8 | Code-Review | Found 6/7 approved changesets -- score normalized to 8 |
| 10 | Contributors | project has 7 contributing companies or organizations |
| 10 | Dangerous-Workflow | no dangerous workflow patterns detected |
| 10 | Dependency-Update-Tool | update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 0 | License | license file not detected |
| 0 | Maintained | 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| n/a | Packaging | packaging workflow not detected |
| 0 | Pinned-Dependencies | dependency not pinned by hash detected -- score normalized to 0 |
| 0 | SAST | SAST tool is not run on all commits -- score normalized to 0 |
| 9 | Security-Policy | security policy file detected |
| 0 | Signed-Releases | Project has not signed or included provenance with any releases. |
| 0 | Token-Permissions | detected GitHub workflow tokens with excessive permissions |
| 0 | Vulnerabilities | 53 existing vulnerabilities detected |
Direct dependencies 15
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| RubyGems | webrick | ~> 1.7 | app/Gemfile |
| RubyGems | puma | ~> 5.6 | app/Gemfile |
| RubyGems | sinatra | ~> 2.2 | app/Gemfile |
| RubyGems | sinatra-cross_origin | ~> 0.4 | app/Gemfile |
| RubyGems | sinatra-contrib | ~> 2.2 | app/Gemfile |
| RubyGems | committee | ~> 4.4 | app/Gemfile |
| RubyGems | pg | ~> 1.2 | app/Gemfile |
| RubyGems | rake | ~> 13.0 | app/Gemfile |
| RubyGems | sinatra-activerecord | ~> 2.0 | app/Gemfile |
| RubyGems | activerecord | ~> 6.1 | app/Gemfile |
| RubyGems | composite_primary_keys | ~> 13.0 | app/Gemfile |
| Go | github.com/deepmap/oapi-codegen | v1.12.2 | golang/go.mod |
| Go | github.com/spf13/cobra | v1.6.1 | golang/go.mod |
| Go | github.com/spf13/pflag | v1.0.5 | golang/go.mod |
| Go | github.com/spf13/viper | v1.13.0 | golang/go.mod |
All dependencies 36
Full resolved dependency set from the GitHub dependency graph: 15 direct and 21 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
| Registry | Package | Version | Relation |
|---|---|---|---|
| Go | github.com/deepmap/oapi-codegen | 1.12.2 | direct |
| Go | github.com/spf13/cobra | 1.6.1 | direct |
| Go | github.com/spf13/pflag | 1.0.5 | direct |
| Go | github.com/spf13/viper | 1.13.0 | direct |
| RubyGems | activerecord | 6.1.6.1 | direct |
| RubyGems | committee | 4.4.0 | direct |
| RubyGems | composite_primary_keys | 13.0.3 | direct |
| RubyGems | pg | 1.2.3 | direct |
| RubyGems | puma | 5.6.4 | direct |
| RubyGems | rake | 13.0.6 | direct |
| RubyGems | sinatra | 2.2.0 | direct |
| RubyGems | sinatra-activerecord | 2.0.25 | direct |
| RubyGems | sinatra-contrib | 2.2.0 | direct |
| RubyGems | sinatra-cross_origin | 0.4.0 | direct |
| RubyGems | webrick | 1.7.0 | direct |
| Go | github.com/fsnotify/fsnotify | 1.6.0 | indirect |
| Go | github.com/spf13/afero | 1.9.2 | indirect |
| RubyGems | activemodel | 6.1.6.1 | indirect |
| RubyGems | activesupport | 6.1.6.1 | indirect |
| RubyGems | coderay | 1.1.3 | indirect |
| RubyGems | concurrent-ruby | 1.1.10 | indirect |
| RubyGems | i18n | 1.12.0 | indirect |
| RubyGems | json_schema | 0.21.0 | indirect |
| RubyGems | method_source | 1.0.0 | indirect |
| RubyGems | minitest | 5.16.2 | indirect |
| RubyGems | multi_json | 1.15.0 | indirect |
| RubyGems | mustermann | 1.1.1 | indirect |
| RubyGems | nio4r | 2.5.8 | indirect |
| RubyGems | openapi_parser | 0.15.0 | indirect |
| RubyGems | pry | 0.14.1 | indirect |
| RubyGems | rack | 2.2.3.1 | indirect |
| RubyGems | rack-protection | 2.2.0 | indirect |
| RubyGems | ruby2_keywords | 0.0.5 | indirect |
| RubyGems | tilt | 2.0.10 | indirect |
| RubyGems | tzinfo | 2.0.4 | indirect |
| RubyGems | zeitwerk | 2.6.0 | indirect |
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.
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.12.0 — full methodology · metrics wiki.
How one result sits in the wider record: aggregate statistics — Go.