Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-16 16:09 UTC

kettle-dev / kettle-test

🍲 Setup a complete multi-core parallelized RSpec test harness, temporal manipulation, silent output testing, block expectations, etc.

Ruby · ShellCustom license★ 1 star⑂ 0 forkssince Aug 2025View on GitHub ↗
KindLibraryhow this is determined
#rspec#ruby#rubygem#testing#testing-tools#parallel-tests

kettle-dev/kettle-test holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Vitality (92/100) and lowest on Community & Adoption (44/100). It was last updated today. A single contributor accounts for most of its recent work.

78
overall / 100
Good

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.

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

Ownership

kettle-devOrganization
6 followers15 public repossince Oct 2023

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemskettle-test2.0.11-230 days ago

Metrics by category

Vitality

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

92Excellent · 21% of overall

Development activity

86Excellent
How it's scored
36/36Push recency — last push 0 days ago
22.2/36Commit cadence — 32/52 weeks with commits
18/18Commit volume — 331 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year331
human_commit_share—
days_since_last_push0
active_weeks_last_year32

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 22 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count22
latest_release_tagv2.0.11
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases5
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?

44Weak · 17% of overall

Popularity & adoption

1Critical
How it's scored
0/60Stars — 1 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars1
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

79Good
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
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

Ecosystem adoption (downloads)

64Moderate
How it's scored
51.2/80Total downloads — 84,338 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageskettle-test
dependents—
ecosystemsrubygems
total_downloads84,338
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?

49Weak · 23% of overall

Maintainer resilience (bus factor)

22At Risk
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.5/22.5Commit distribution — top contributor authored 98% of commits
2.7/13.5Contributor breadth — 2 contributors
10/10OpenSSF Scorecard: Contributors — project has 18 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.979

Issue & PR responsiveness

25At Risk
How it's scored
0/42Issue resolution — no issues or no data
11.4/30PR acceptance — 8/21 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs8
open_issues0
closed_issues0
prs_merged_7d—
prs_decided_7d—
prs_merged_30d—
prs_decided_30d—
issue_closed_ratio—
closed_unmerged_prs13
first_time_authors_30d—
first_time_prs_merged_30d—
first_time_prs_decided_30d—
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

63Moderate
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain — verified-domain status not read for this organization
6.1/25Owner reach — 6 followers of kettle-dev
14.3/25Track record — 15 public repos, account ~2 yr old
Inputs used
followers6
owner_typeOrganization
is_verified—
owner_loginkettle-dev
public_repos15
account_age_days1,004
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

88Excellent · 19% of overall

Engineering practices

80Excellent
How it's scored
24/24CI workflows — 32 workflow(s)
24/24Tests present
16/16Linter config — .rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://kettle-test.galtzo.com/
10/10Repository description
10/10Topics — 6 topics
10/10Wiki
Inputs used
topicsrspec, ruby, rubygem, testing, testing-tools, parallel-tests
has_wikiyes
homepagehttps://kettle-test.galtzo.com/
docs_sitehttps://kettle-test.galtzo.com/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

60Moderate · 16% of overall

Security posture

60Moderate
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 18 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
4.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 9
0/5SAST — no SAST tool detected
5/5Security-Policy — security policy file 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_aggregate6
Excluded from scoring (no data or not applicable): CI-Tests, 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.

75Good · 4% of overall

Agent context & guidance

75Good
How it's scored
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no data
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share—
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes10,617
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.

Verify loop (build / test / typecheck)

83Excellent
How it's scored
18/18One-command bootstrap — mise.toml
22/22Automated tests
11/11Lint / format config — .rubocop.yml
0/11Static type checking
10/10Reproducible environment — devcontainer, lockfile
0/10Demonstrated agent practice — no data
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
9/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 9
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileno
typed_languageno
bootstrap_filesmise.toml
has_devcontaineryes
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.

Code legibility for models

53Moderate
How it's scored
0/45Type-checkable code — Ruby without a type-check config
53.1/55Manageable file sizes — 1/29 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes93,868
source_files_sampled29
oversized_source_files1

Key facts

1GitHub stars
2contributors
331commits, last 12 months
0days since last push
22releases
1bus factor
0open issues
RubyGemspackage ecosystems

More detail

OpenSSF Scorecard 6.0 / 10
6.0aggregate

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-16 16:09 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 18 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
9Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 9
0SASTno SAST tool detected
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
RubyGemsnomono—Gemfile
RubyGemsirb~> 1.17Gemfile
All dependencies 145

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

RegistryPackageVersionRelation
RubyGemsirb1.18.0direct
RubyGemsnomono1.0.8direct
RubyGemsaddressable2.9.0indirect
RubyGemsansi1.6.0indirect
RubyGemsappraisal2—indirect
RubyGemsappraisal23.1.4indirect
RubyGemsappraisal2-rubocop0.2.3indirect
RubyGemsast2.4.3indirect
RubyGemsbackports—indirect
RubyGemsbackports3.25.3indirect
RubyGemsbenchmark0.5.0indirect
RubyGemsbigdecimal4.1.2indirect
RubyGemsbundler-audit—indirect
RubyGemsbundler-audit0.9.3indirect
RubyGemscgi0.5.2indirect
RubyGemscmdparse3.0.7indirect
RubyGemsconcurrent-ruby1.3.7indirect
RubyGemsdate3.5.1indirect
RubyGemsdebug1.11.1indirect
RubyGemsdelegate0.6.1indirect
RubyGemsdiff-lcs1.6.2indirect
RubyGemsdiffy3.4.4indirect
RubyGemsdry-configurable1.4.0indirect
RubyGemsdry-core1.2.0indirect
RubyGemsdry-inflector1.3.1indirect
RubyGemsdry-initializer3.2.0indirect
RubyGemsdry-logic1.6.0indirect
RubyGemsdry-schema1.16.0indirect
RubyGemsdry-types1.9.1indirect
RubyGemsemoji_regex15.0.0indirect
RubyGemserb6.0.4indirect
RubyGemsgem_bench2.0.5indirect
RubyGemsgeom2d0.4.1indirect
RubyGemsgitmoji-regex—indirect
RubyGemsgitmoji-regex2.0.4indirect
RubyGemshexapdf1.9.1indirect
RubyGemsio-console0.8.2indirect
RubyGemsjson2.21.1indirect
RubyGemskettle-dev—indirect
RubyGemskettle-dev2.3.5indirect
RubyGemskettle-rb0.1.2indirect
RubyGemskettle-soup-cover3.0.0indirect
RubyGemskramdown2.5.2indirect
RubyGemskramdown-parser-gfm1.1.0indirect
RubyGemslanguage_server-protocol3.17.0.6indirect
RubyGemslint_roller1.1.0indirect
RubyGemslogger1.7.0indirect
RubyGemsmutex_m0.3.0indirect
RubyGemsnokogiri1.19.4indirect
RubyGemsopenssl4.0.2indirect
RubyGemsostruct0.6.3indirect
RubyGemsparallel1.28.0indirect
RubyGemsparallel_tests5.7.0indirect
RubyGemsparser3.3.12.0indirect
RubyGemspp0.6.4indirect
RubyGemsprettyprint0.2.0indirect
RubyGemsprism1.9.0indirect
RubyGemspsych5.4.0indirect
RubyGemspublic_suffix7.0.5indirect
RubyGemsracc1.8.1indirect
RubyGemsrainbow3.1.1indirect
RubyGemsrake—indirect
RubyGemsrake13.4.2indirect
RubyGemsrbs4.0.3indirect
RubyGemsrdoc6.17.0indirect
RubyGemsreek6.5.0indirect
RubyGemsregexp_parser2.12.0indirect
RubyGemsreline0.6.3indirect
RubyGemsrequire_bench—indirect
RubyGemsrequire_bench1.0.4indirect
RubyGemsrexml3.4.4indirect
RubyGemsrspec—indirect
RubyGemsrspec3.13.2indirect
RubyGemsrspec-block_is_expected—indirect
RubyGemsrspec-block_is_expected1.0.6indirect
RubyGemsrspec-core3.13.6indirect
RubyGemsrspec-expectations3.13.5indirect
RubyGemsrspec-mocks3.13.8indirect
RubyGemsrspec-pending_for—indirect
RubyGemsrspec-pending_for0.1.21indirect
RubyGemsrspec-stubbed_env—indirect
RubyGemsrspec-stubbed_env1.0.6indirect
RubyGemsrspec-support3.13.7indirect
RubyGemsrspec_junit_formatter—indirect
RubyGemsrspec_junit_formatter0.6.0indirect
RubyGemsrubocop1.88.2indirect
RubyGemsrubocop-ast1.50.0indirect
RubyGemsrubocop-capybara2.23.0indirect
RubyGemsrubocop-env0.1.0indirect
RubyGemsrubocop-factory_bot2.28.0indirect
RubyGemsrubocop-gradual0.4.0indirect
RubyGemsrubocop-lts12.3.2indirect
RubyGemsrubocop-lts-rspec1.0.5indirect
RubyGemsrubocop-md2.0.4indirect
RubyGemsrubocop-minitest0.39.1indirect
RubyGemsrubocop-on-rbs2.0.0indirect
RubyGemsrubocop-packaging0.6.0indirect
RubyGemsrubocop-performance1.26.1indirect
RubyGemsrubocop-rake0.7.1indirect
RubyGemsrubocop-rspec3.10.2indirect
RubyGemsrubocop-rspec-extra0.3.0indirect
RubyGemsrubocop-rspec_rails2.32.0indirect
RubyGemsrubocop-ruby2_43.0.6indirect
RubyGemsrubocop-thread_safety0.7.3indirect
RubyGemsruby-progressbar—indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemsruby_engine2.0.3indirect
RubyGemsruby_version1.0.3indirect
RubyGemssilent_stream—indirect
RubyGemssilent_stream1.0.12indirect
RubyGemssimplecov1.0.1indirect
RubyGemssimplecov-cobertura4.0.0indirect
RubyGemssimplecov-console0.9.5indirect
RubyGemssimplecov-rcov0.3.7indirect
RubyGemssimplecov_lcov_formatter0.9.0indirect
RubyGemsstandard1.56.0indirect
RubyGemsstandard-custom1.0.2indirect
RubyGemsstandard-performance1.9.0indirect
RubyGemsstandard-rspec0.5.0indirect
RubyGemsstandard-rubocop-lts2.0.10indirect
RubyGemsstone_checksums—indirect
RubyGemsstone_checksums1.0.6indirect
RubyGemsstringio3.2.0indirect
RubyGemsstrscan3.1.8indirect
RubyGemsterminal-table4.0.0indirect
RubyGemsthor1.5.0indirect
RubyGemstimecop0.9.11indirect
RubyGemstimecop-rspec—indirect
RubyGemstimecop-rspec1.0.3indirect
RubyGemstsort0.2.0indirect
RubyGemsturbo_tests2—indirect
RubyGemsturbo_tests23.1.12indirect
RubyGemsunicode-display_width3.2.0indirect
RubyGemsunicode-emoji4.2.0indirect
RubyGemsversion_gem1.1.14indirect
RubyGemswebrick1.9.2indirect
RubyGemsyaml-converter0.2.3indirect
RubyGemsyard0.9.45indirect
RubyGemsyard-fence0.9.6indirect
RubyGemsyard-junk0.1.0indirect
RubyGemsyard-relative_markdown_links0.6.0indirect
RubyGemsyard-timekeeper0.2.3indirect
RubyGemsyard-yaml0.2.3indirect
RubyGemszeitwerk2.8.2indirect
RubyGemszlib3.2.3indirect
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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with kettle-dev/kettle-test. Read them side by side →

96rubocop/rubocop-rspecCode style checking for RSpec files.Exceptional93DataDog/datadog-ci-rbRuby library for Datadog Test OptimizationExceptional95cucumber/compatibility-kitPlatform-agnostic set of acceptance tests for validating cucumber implementationsExceptional95cucumber/cucumber-expressionsHuman friendly alternative to Regular ExpressionsExceptional93cucumber/tag-expressionsCucumber tag expression parserExceptional92rubocop/rubocop-capybaraCode style checking for Capybara files.Excellent

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

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