most of codeclimate's metrics come from things you can run locally (eg they blog about this here http://blog.codeclimate.com/blog/2013/08/07/deciphering-ruby-co

most of codeclimate's metrics come from things you can run locally (eg they blog about this here http://blog.codeclimate.com/blog/2013/08/07/deciphering-ruby-code-metrics/ http://blog.codeclimate.com/blog/2013/08/07/deciphering-ruby...): http://ruby.sadi.st/Flog.html http://ruby.sadi.st/Flog.html http://ruby.sadi.st/Flay.html http://ruby.sadi.st/Flay.html http://brakemanscanner.org/ http://brakemanscanner.org/ What makes codeclimate useful is the polish/ease of use on top of these tools. It also makes it easier for me to get projects to adopt new tools - if they're in CC already, and CC start doing bundler-audit reports...we get them for all projects.