Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-12 14:39 UTC

testdouble / mocktail

🥃 Take your Ruby, and make it a double!

Ruby · HTMLMIT★ 276 stars⑂ 12 forkssince Sep 2021View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

testdouble/mocktail holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Engineering Quality (76/100) and lowest on AI Readiness (29/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Test DoubleOrganization · verified domain
129 followers166 public repossince Oct 2011

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsmocktail3.0.1-180 days ago

Metrics by category

Vitality

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

62Moderate · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
0.7/36Commit cadence — 1/52 weeks with commits
9.7/18Commit volume — 11 commits in the last year
10/10OpenSSF Scorecard: Maintained — 16 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year11
human_commit_share1
days_since_last_push0
active_weeks_last_year1
How it's scored
16.2/27Ships releases — 18 version tags (no GitHub releases)
36/36Release recency — latest release 0 days ago
12.6/27Release cadence — a release every ~179.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count18
latest_release_tagv3.0.1
releases_from_tagsyes
days_since_latest_release0
mean_days_between_releases179.1
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?

63Moderate · 17% of overall
How it's scored
39.6/60Stars — 276 stars
8.7/25Forks — 12 forks
3.9/15Watchers — 6 watchers
Inputs used
forks12
stars276
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
13.5/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_conductyes
readme_badge_services—
has_pull_request_templateno
How it's scored
61.5/80Total downloads — 829,413 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesmocktail
dependents—
ecosystemsrubygems
total_downloads829,413
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?

71Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.9/22.5Commit distribution — top contributor authored 92% of commits
12.2/13.5Contributor breadth — 9 contributors
10/10OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled9
top_contributor_share0.916
How it's scored
36.8/42Issue resolution — 88% of issues closed
25.2/30PR acceptance — 21/25 decided PRs merged
11.1/13Newcomer PR acceptance — 6/7 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 3/20 approved changesets -- score normalized to 1
Inputs used
merged_prs21
open_issues1
closed_issues7
prs_merged_7d3
prs_decided_7d4
prs_merged_30d6
prs_decided_30d8
issue_closed_ratio0.875
closed_unmerged_prs4
first_time_authors_30d2
first_time_prs_merged_30d6
first_time_prs_decided_30d7
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
15.2/25Owner reach — 129 followers of testdouble
25/25Track record — 166 public repos, account ~14 yr old
Inputs used
followers129
owner_typeOrganization
is_verifiedyes
owner_logintestdouble
public_repos166
account_age_days5,471

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 — 18 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesmocktail
ecosystemsrubygems
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests — 6 out of 10 merged PRs checked by a CI test -- score normalized to 6
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://rubygems.org/gems/mocktail
10/10Repository description
10/10Topics — 4 topics
10/10Wiki
Inputs used
topicsmocking, ruby, test-doubles, testing
has_wikiyes
homepagehttps://rubygems.org/gems/mocktail
docs_sitehttps://rubygems.org/gems/mocktail
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

54Moderate · 16% of overall
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
1.5/2.5CI-Tests — 6 out of 10 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 3/20 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 5 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
7.5/7.5Maintained — 16 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.3
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages46
unassessed_packages2
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 46 resolved dependencies against OSV. 2 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.

29At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
10.7/40Legible commit history — 20 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.2
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
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
lockfilesGemfile.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
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/297 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes17,505
source_files_sampled297
oversized_source_files0

Key facts

276GitHub stars
9contributors
11commits, last 12 months
0days since last push
18releases
1bus factor
1open issues
RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 12 ⇿
0Stars
12Forks
15Releases

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.

0246810121212021-092024-012026-04
Major 2Minor 2Patch 11

Each point covers 5 days.

OpenSSF Scorecard 4.3 / 10
4.3aggregate

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-12 14:39 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
6CI-Tests6 out of 10 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 3/20 approved changesets -- score normalized to 1
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained16 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
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 10
RegistryPackageVersion constraintManifest
RubyGemsrake—Gemfile
RubyGemsminitest~> 5.26Gemfile
RubyGemsstandard—Gemfile
RubyGemsstandard-sorbet—Gemfile
RubyGemssimplecov—Gemfile
RubyGemsm—Gemfile
RubyGemssorbet-static—Gemfile
RubyGemstapioca—Gemfile
RubyGemsspoom—Gemfile
RubyGemsbigdecimal—Gemfile
All dependencies 48

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

RegistryPackageVersionRelation
RubyGemsbigdecimal3.1.9direct
RubyGemsm1.6.2direct
RubyGemsminitest5.27.0direct
RubyGemsrake13.2.1direct
RubyGemssimplecov0.22.0direct
RubyGemssorbet-static0.5.11971direct
RubyGemsspoom1.6.1direct
RubyGemsstandard1.47.0direct
RubyGemsstandard-sorbet0.0.3direct
RubyGemstapioca0.16.11direct
RubyGemsast2.4.3indirect
RubyGemsbenchmark0.4.0indirect
RubyGemsdocile1.4.1indirect
RubyGemserubi1.13.1indirect
RubyGemsjson2.21.2indirect
RubyGemslanguage_server-protocol3.17.0.4indirect
RubyGemslint_roller1.1.0indirect
RubyGemslogger1.7.0indirect
RubyGemsmethod_source1.1.0indirect
RubyGemsnetrc0.11.0indirect
RubyGemsparallel1.26.3indirect
RubyGemsparser3.3.7.4indirect
RubyGemsprism1.4.0indirect
RubyGemsracc1.8.1indirect
RubyGemsrainbow3.1.1indirect
RubyGemsrbi0.3.1indirect
RubyGemsrbs3.9.2indirect
RubyGemsregexp_parser2.10.0indirect
RubyGemsrubocop1.73.2indirect
RubyGemsrubocop-ast1.43.0indirect
RubyGemsrubocop-performance1.24.0indirect
RubyGemsrubocop-sorbet0.9.0indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemssimplecov-html0.13.1indirect
RubyGemssimplecov_json_formatter0.1.4indirect
RubyGemssorbet0.5.11971indirect
RubyGemssorbet-eraser—indirect
RubyGemssorbet-eraser0.3.1indirect
RubyGemssorbet-runtime—indirect
RubyGemssorbet-runtime0.5.11971indirect
RubyGemssorbet-static-and-runtime0.5.11971indirect
RubyGemsstandard-custom1.0.2indirect
RubyGemsstandard-performance1.7.0indirect
RubyGemsthor1.3.2indirect
RubyGemsunicode-display_width3.1.4indirect
RubyGemsunicode-emoji4.2.0indirect
RubyGemsyard0.9.45indirect
RubyGemsyard-sorbet0.9.0indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 46 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 2 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 statistics — RubyGems.