whitesmith/rubycritic

A Ruby code quality reporter

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 24 minutes ago
Added to GitGenius on September 19th, 2026
Created on October 9th, 2013
Open Issues & Pull Requests: 36 (+0)
GitHub issues: Enabled
Number of forks: 234
Total Stargazers: 3,503 (+0)
Total Subscribers: 44 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 9
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 639 days
Stale 30+ days: 6
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (1)
  • feature (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

RubyCritic is a Ruby code quality reporter that aggregates static analysis tools to provide comprehensive quality metrics and visualizations.

The tool solves the problem of scattered code quality feedback by wrapping multiple static analysis gems—Reek, Flay, and Flog—into a unified reporting interface. It transforms raw analysis output into an organized HTML report that displays project overviews, file-level smell indices, and detailed smell breakdowns. The tool can also leverage your source control system to compare uncommitted changes against the last commit, helping identify quality regressions in new code.

Teams should adopt this tool if they want a centralized dashboard for Ruby code quality without managing multiple analysis tools separately. It suits projects that already use Git, Mercurial, or Perforce and want to track quality trends over time. The tool is particularly useful in CI pipelines where you can set minimum quality scores and enforce thresholds for acceptable score decreases between branches. If you need a single, visually organized report rather than command-line output from individual linters, this consolidation approach eliminates the friction of interpreting multiple tool outputs.

Development activity shows consistent maintenance with regular updates addressing both bug fixes and feature enhancements. The project maintains active engagement with user-reported issues and pull requests, indicating responsive stewardship. Code contributions are regularly reviewed and integrated, suggesting a healthy review process. The maintainers demonstrate commitment to compatibility across Ruby versions and evolving dependencies, keeping the tool functional with modern Ruby ecosystems.