RuboCop
rubocop.org
- Free plan
- Linux
- Self-hosted
6.9 Club score Visit rubocop.org
Plans
Every plan and priceRuboCop
Free
Open source
What the maker publishes
- Autocorrection
- RuboCop can automatically fix many reported problems, with separate options for safe and potentially behavior-changing corrections. source
- Checks
- Its cops check for bugs, style, layout, naming, complexity, and security issues. source
- CI and code scanning
- GitHub-formatted output can annotate pull requests, SARIF can feed code scanning, and JUnit output can be used by CI. source
- Coding agents
- RuboCop supports inspection and autocorrection for coding agents over the Model Context Protocol. source
- Customization
- Teams can configure cop styles in a .rubocop.yml file and inherit settings from a shared configuration. source
- Editors
- The built-in language server provides offenses while typing and format-on-save in VS Code, RubyMine, Emacs, Neovim, Helix, and Zed. source
- Existing codebases
- The --auto-gen-config command records existing offenses in .rubocop_todo.yml so teams can address legacy issues over time. source
- Founded
- 2012 source
- History
- The homepage says RuboCop began in April 2012 and identifies Bozhidar Batsov as its originator. source
- Installation
- RuboCop can be installed with gem install rubocop or added to a Bundler Gemfile as a standalone tool. source
- Maintainers
- The homepage describes RuboCop as free and maintained by a small core team of volunteers with help from thousands of contributors. source
- Plugins
- Plugins extend RuboCop for frameworks and libraries, and the project lists maintained plugins for Rails, RSpec, Minitest, Capybara, and others. source
- Purpose
- RuboCop is a Ruby static code analyzer and formatter based on the community Ruby Style Guide. source
- Runtime support
- The repository README says RuboCop officially supports MRI Ruby 2.7 and later and JRuby 9.4 and later, and targets Ruby 2.0 and later for code analysis. source
- Security disclosure
- The project repository links to a security policy, but the opened pages do not state a security certification or compliance standard. source
- Selective inspection
- The --changed option limits inspection to files that Git reports as changed. source
Checked against the maker's pages on 10 Oct 2026.