lint/configured/ruby
A linter is configured
Implements lint/configured for ruby.
| Severity | warning |
| Tiers | 1, 2 |
| Stacks | ruby |
| Scope | each |
| Kind | outcome |
| Source | library v0.5.0 |
| Selected by | fleetlint-recommended@v0.5.0 |
Requirement
RuboCop is configured (.rubocop.yml in the project or a parent directory) or Standard is used (.standard.yml or the standard gem); a .rubocop_todo.yml is the ratchet, not a permanent allowlist.
Why
Ruby’s flexibility is only safe with a linter that holds the line on method length, complexity and swallowed exceptions.
Fix
Add .rubocop.yml and the rubocop gems to the Gemfile’s development group (fleetlint fix --apply does both).
Agent instruction: Add .rubocop.yml from the template, add rubocop with rubocop-performance and rubocop-rspec to the Gemfile, and run rubocop --autocorrect.
fleetlint fix can apply this rule’s fix automatically (2 action(s)).
A finding of this rule points at .rubocop.yml.
Sources
- https://csrc.nist.gov/pubs/sp/800/218/final (standard, PW.7.2: Perform the code review and/or code analysis based on the organization’s secure coding standards)
- https://fleetlint.org/baseline/#static-analysis (convention)
- https://docs.rubocop.org/rubocop/latest/configuration.html (spec)
- https://fleetlint.org/stacks/#ruby
Generated by fleetlint docs from catalog v0.5.0.