Reek VS rails_best_practices

Compare Reek vs rails_best_practices and see what are their differences.

Our great sponsors
  • PopRuby - Clothing and Accessories for Ruby Developers
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
Reek rails_best_practices
6 1
3,959 4,131
- -
8.2 0.0
1 day ago about 1 year ago
Ruby Ruby
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

Reek

Posts with mentions or reviews of Reek. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-01-17.

rails_best_practices

Posts with mentions or reviews of rails_best_practices. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-08-06.

What are some alternatives?

When comparing Reek and rails_best_practices you can also consider the following projects:

Rubocop - A Ruby static code analyzer and formatter, based on the community Ruby style guide. [Moved to: https://github.com/rubocop/rubocop]

Rubycritic - A Ruby code quality reporter

Flay - Flay analyzes code for structural similarities. Differences in literal values, variable, class, method names, whitespace, programming style, braces vs do/end, etc are all ignored.

Flog - Flog reports the most tortured code in an easy to read pain report. The higher the score, the more pain the code is in.

Brakeman - A static analysis security vulnerability scanner for Ruby on Rails applications

SimpleCov - Code coverage for Ruby with a powerful configuration library and automatic merging of coverage across test suites

undercover - undercover warns about methods, classes and blocks that were changed without tests, to help you easily find untested code and reduce the number of bugs. It does so by analysing data from git diffs, code structure and SimpleCov coverage reports

Pronto - Quick automated code review of your changes

Fasterer - :zap: Don't make your Rubies go fast. Make them go fasterer ™. :zap:

Coverband - Ruby production code coverage collection and reporting (line of code usage)

bundler-leak - Known-leaky gems verification for bundler: `bundle leak` to check your app and find leaky gems in your Gemfile :gem::droplet: