R

Reek

Free#31 of 33 in LintersRuby Static Analysis Tools

Ruby code smell detector

—Not yet scored

Visit Reek

At a glance

• Editor score
  Not yet scored
• Pricing
  Open source
• Best for
  Ruby teams focused on code smells
• Paid from
  None
• CI support
  Yes
• Founded
  2009
• Facts checked
  21 Sep 2026

• Where it wins

  • Detects Ruby smells with configurable detectors and suppressions
  • Supports CLI, CI, Rake, RSpec, editors, and GitHub Actions
  • Exports plain-text, HTML, YAML, JSON, XML, and GitHub reports

• Where it doesn't

  • Supports Ruby rather than multiple programming languages
  • Does not provide autofix
  • Requires configuration for directory-specific rules and suppressions

Our verdict on Reek

Reek is an open-source static analysis tool for Ruby teams that want to identify code smells in classes, modules, methods, and source files. Its detectors cover patterns including Feature Envy, Data Clump, Large Class, Long Parameter List, and Uncommunicative Name. Reek runs from the command line against files, directories, or standard input, making it suitable for developers and teams working with Ruby codebases that want configurable smell analysis rather than broad multi-language linting.

Its strongest feature is the control it provides over analysis. Teams can configure detectors and directory-specific rules through .reek.yml files, while source-code comments can suppress or configure individual warnings. Reek can also generate a todo configuration, which gives teams a way to establish an initial baseline before addressing existing findings. Reports are available in plain text, HTML, YAML, JSON, XML, and GitHub formats. Rake tasks, an RSpec matcher, and a Developer API extend its use beyond a standalone command-line workflow.

Reek also fits several development environments and automation paths, with integrations for Vim, TextMate, Atom, SublimeLinter, VS Code, Emacs, overcommit, pronto-reek, and GitHub Actions. The published model is open source and self-hosted, with an MIT license and no paid tiers described. Its focus is deliberately narrow: Ruby code-smell detection, not multi-language analysis or automatic remediation. Teams that want configurable Ruby smell reporting and established editor, CI, Rake, or RSpec connections should consider Reek. Teams that require autofix or support for more than one language should choose a different tool.

Reek pricing

Reek fact sheet

Reek integrations

Reek lists 12 integrations on its own site.

• Vim
• TextMate
• Atom
• SublimeLinter
• VS Code
• Emacs
• Rake
• RSpec
• overcommit
• ruby-critic
• pronto-reek
• GitHub Actions

Alternatives to Reek

• ESLintA free, extensible JavaScript linter with autofix, plugins, and broad developer-tool integrations.—
• RuffFree Python linting and formatting with more than 900 built-in rules.—
• ShellCheckA free, open-source linter for shell syntax, portability, robustness and security checks.—

See all Reek alternatives →

Also listed in

• Ruby Static Analysis Tools

Used Reek? Be the first to review it

The editor score above is our own research. What this page doesn't have yet is a reader's view — what you used Reek for, what worked and what didn't. No stars are seeded and no review is paid for; an editor reads every one before it appears.

Write a reviewTwo minutes · verified accounts only · read by an editor before it appears

Website

Reviews come only from verified accounts. Sign in or create an account first — your e-mail is never shown.

Your rating

5 stars★4 stars★3 stars★2 stars★1 star★

Title

Your review

0 characters · at least 80, up to 3,000

Pros (optional · one per line)

Cons (optional · one per line)

Your name (shown with your review)

Role (optional)

Company (optional)

How long have you used it?Prefer not to sayLess than a month1–6 months6–12 months1–2 years2+ years

I've used Reek myself and this is my honest opinion — nobody paid or asked me to write it.

Send my reviewPosted from your verified account. Reviews appear after an editor reads them, usually within two working days.

Featured on iTechGuides

Reviewed by iTechGuides Editors · Editorial team · Updated Sep 2026

Advertiser disclosure: iTechGuides is reader-supported. We may earn a commission when you click some links. It never changes a score or a verdict. How we rank.