Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 08:35 UTC

troessner / reek

Code smell detector for Ruby

Ruby · GherkinMIT★ 4,129 stars⑂ 281 forkssince Sep 2008View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

troessner/reek holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (86/100) and lowest on AI Readiness (56/100). It was last updated 11 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

Timo RößnerPersonal account
181 followers8 public repossince May 2010

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsreek6.5.0-146521 days ago

Metrics by category

Vitality

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

56Moderate · 21% of overall
How it's scored
28.8/36Push recencylast push 11 days ago
13.8/36Commit cadence20/52 weeks with commits
15.5/18Commit volume52 commits in the last year
9/10OpenSSF Scorecard: Maintained11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
Inputs used
commits_last_year52
human_commit_share0.97
days_since_last_push11
active_weeks_last_year20
How it's scored
16.2/27Ships releases96 version tags (no GitHub releases)
7.2/36Release recencylatest release 521 days ago
12.6/27Release cadencea release every ~146.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count96
latest_release_tagv6.5.0
releases_from_tagsyes
days_since_latest_release521
mean_days_between_releases146.7
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?

84Excellent · 17% of overall
How it's scored
58.7/60Stars4,129 stars
20.4/25Forks281 forks
8.9/15Watchers41 watchers
Inputs used
forks281
stars4,129
watchers41
growth_stateorganic
growth_factor_pct100
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, github.com, shields.io
has_pull_request_templateno
How it's scored
78.9/80Total downloads39,100,724 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesreek
dependents
ecosystemsrubygems
total_downloads39,100,724
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?

68Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
14/22.5Commit distributiontop contributor authored 38% of commits
13.5/13.5Contributor breadth97 contributors
10/10OpenSSF Scorecard: Contributorsproject has 58 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled97
top_contributor_share0.378
How it's scored
38.8/42Issue resolution92% of issues closed
26.8/30PR acceptance1,074/1,201 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 3/12 approved changesets -- score normalized to 2
Inputs used
merged_prs1,074
open_issues49
closed_issues584
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d2
issue_closed_ratio0.923
closed_unmerged_prs127
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
16.2/25Owner reach181 followers of troessner
18.9/25Track record8 public repos, account ~16 yr old
Inputs used
followers181
owner_typeUser
is_verified
owner_logintroessner
public_repos8
account_age_days5,955
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on rubygems
14/35Publish recencylatest publish 521 days ago
20/20Version history146 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesreek
ecosystemsrubygems
any_deprecatedno
min_days_since_publish521

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
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 sitehttps://github.com/troessner/reek
10/10Repository description
10/10Topics8 topics
0/10Wiki
Inputs used
topicssmell, ruby, smell-warnings, smell-detector, static-analysis, linters, quality, parsing
has_wikino
homepagehttps://github.com/troessner/reek
docs_sitehttps://github.com/troessner/reek
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

57Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-ReviewFound 3/12 approved changesets -- score normalized to 2
2.5/2.5Contributorsproject has 58 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
6.8/7.5Maintained11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
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
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.7
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.

56Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://docs.docker.com/llms.txt)
26.9/40Legible commit history49 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.docker.com/llms.txt
legible_history_share0.505
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
10/10Reproducible environmentDockerfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance3 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.03
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/240 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes47,967
source_files_sampled240
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplessamples
Inputs used
example_dirssamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

4,129GitHub stars
97contributors
52commits, last 12 months
11days since last push
96releases
2bus factor
49open issues
RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-07-20: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 4129 stars today.
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 4,130 ★ / 281 ⇿
4,130Stars
281Forks
96Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

Star history is shown as collected on 2026-07-20. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

01,0002,0003,0004,0005,0004,130280522008-102017-082026-07
Major 4Minor 30Patch 62

Each point covers 17 days.

OpenSSF Scorecard 5.7 / 10
5.7aggregate

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-28 08:35 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
10CI-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 3/12 approved changesets -- score normalized to 2
10Contributorsproject has 58 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
9Maintained11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
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 12
RegistryPackageVersion constraintManifest
RubyGemsaruba~> 2.3Gemfile
RubyGemscodeclimate-engine-rb~> 0.4.0Gemfile
RubyGemscucumberGemfile
RubyGemsrake~> 13.0Gemfile
RubyGemsrspec~> 3.0Gemfile
RubyGemsrspec-benchmark~> 0.6.0Gemfile
RubyGemsrubocop~> 1.89.0Gemfile
RubyGemsrubocop-performance~> 1.26.0Gemfile
RubyGemsrubocop-rspec~> 3.10.2Gemfile
RubyGemssimplecov~> 0.22.0Gemfile
RubyGemsyard~> 0.9.5Gemfile
RubyGemsredcarpet~> 3.4Gemfile
All dependencies 16

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

RegistryPackageVersionRelation
RubyGemsarubadirect
RubyGemscodeclimate-engine-rbdirect
RubyGemsrakedirect
RubyGemsredcarpetdirect
RubyGemsrspecdirect
RubyGemsrspec-benchmarkdirect
RubyGemsrubocopdirect
RubyGemsrubocop-performancedirect
RubyGemsrubocop-rspecdirect
RubyGemssimplecovdirect
RubyGemsyarddirect
RubyGemsdry-schemaindirect
RubyGemsloggerindirect
RubyGemsparserindirect
RubyGemsrainbowindirect
RubyGemsrexmlindirect
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 statisticsRubyGems.