Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-22 00:39 UTC

theforeman / kafo

A gem for making installations based on puppet user friendly

RubyGPL-3.0★ 57 stars⑂ 43 forkssince Aug 2013View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

theforeman/kafo holds a health index of 62 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (78/100) and lowest on AI Readiness (34/100). It was last updated 56 days ago. A single contributor accounts for most of its recent work.

62
overall / 100
Moderate

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.

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

Ownership

The ForemanOrganization · verified domain
195 followers240 public repossince Feb 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemskafo7.8.0-11999 days ago

Metrics by category

Vitality

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

35Weak · 21% of overall
How it's scored
18/36Push recency — last push 56 days ago
2.8/36Commit cadence — 4/52 weeks with commits
8.6/18Commit volume — 8 commits in the last year
0/10OpenSSF Scorecard: Maintained — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year8
human_commit_share1
days_since_last_push56
active_weeks_last_year4
How it's scored
27/27Ships releases — 1 releases published
0/36Release recency — latest release 2,141 days ago
12.6/27Release cadence — cadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count1
latest_release_tagv6.1.2
releases_from_tagsno
days_since_latest_release2,141
mean_days_between_releases—
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?

55Moderate · 17% of overall
How it's scored
28.4/60Stars — 57 stars
13.5/25Forks — 43 forks
5.6/15Watchers — 11 watchers
Inputs used
forks43
stars57
watchers11
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (GPL-3.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
59/80Total downloads — 472,997 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageskafo
dependents—
ecosystemsrubygems
total_downloads472,997
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?

78Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
9.8/22.5Commit distribution — top contributor authored 56% of commits
13.5/13.5Contributor breadth — 22 contributors
10/10OpenSSF Scorecard: Contributors — project has 23 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled22
top_contributor_share0.565
How it's scored
0/42Issue resolution — no issues or no data
26/30PR acceptance — 335/386 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
13.5/15OpenSSF Scorecard: Code-Review — Found 24/26 approved changesets -- score normalized to 9
Inputs used
merged_prs335
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs51
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
16.5/25Owner reach — 195 followers of theforeman
25/25Track record — 240 public repos, account ~14 yr old
Inputs used
followers195
owner_typeOrganization
is_verifiedyes
owner_logintheforeman
public_repos240
account_age_days5,362

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on rubygems
35/35Publish recency — latest publish 99 days ago
20/20Version history — 119 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageskafo
ecosystemsrubygems
any_deprecatedno
min_days_since_publish99

Engineering Quality

Are baseline engineering and documentation practices in place?

77Good · 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
4/20OpenSSF Scorecard: CI-Tests — 6 out of 25 merged PRs checked by a CI test -- score normalized to 2
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://www.rubydoc.info/gems/kafo/7.8.0
10/10Repository description
10/10Topics — 1 topics
0/10Wiki
Inputs used
topicshacktoberfest
has_wikino
homepage—
docs_sitehttps://www.rubydoc.info/gems/kafo/7.8.0
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

44Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0.5/2.5CI-Tests — 6 out of 25 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
6.8/7.5Code-Review — Found 24/26 approved changesets -- score normalized to 9
2.5/2.5Contributors — project has 23 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
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
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.4
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. 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 instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
20.8/40Legible commit history — 39 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.39
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .rubocop.yml
0/11Static type checking
0/10Reproducible environment
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency 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.01
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/138 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes21,210
source_files_sampled138
oversized_source_files0

Key facts

57GitHub stars
22contributors
8commits, last 12 months
56days since last push
1releases
1bus factor
0open 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 ★ / 43 ⇿
0Stars
43Forks
1Releases

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.

010203040504342013-082020-022026-07
Major 0Minor 0Patch 1

Each point covers 12 days.

OpenSSF Scorecard 4.4 / 10
4.4aggregate

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-10-22 00:39 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
2CI-Tests6 out of 25 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
9Code-ReviewFound 24/26 approved changesets -- score normalized to 9
10Contributorsproject has 23 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained1 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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
RubyGemsjson_pure—Gemfile
RubyGemspuppet—Gemfile
RubyGemspuppet>= 7.0.0Gemfile
RubyGemspuppet-strings>= 1.2.1Gemfile
RubyGemsrdoc< 6.4Gemfile
RubyGemsmetadata-json-lint—Gemfile
RubyGemspuppetlabs_spec_helper—Gemfile
All dependencies 18

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

RegistryPackageVersionRelation
RubyGemsjson_pure—direct
RubyGemsmetadata-json-lint—direct
RubyGemspuppet—direct
RubyGemspuppet-strings—direct
RubyGemspuppetlabs_spec_helper—direct
RubyGemsansi—indirect
RubyGemsbundler—indirect
RubyGemsclamp—indirect
RubyGemshighline—indirect
RubyGemskafo_parsers—indirect
RubyGemskafo_wizards—indirect
RubyGemslogging—indirect
RubyGemsminitest—indirect
RubyGemsminitest-reporters—indirect
RubyGemspowerbar—indirect
RubyGemsrake—indirect
RubyGemsrubocop—indirect
RubyGemssimplecov—indirect
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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — RubyGems.