Migration Overview

Overview

Qlty is the next generation of Code Climate Quality.

Created in 2011, Code Climate Quality was a pioneer for automated code review, helping developers merge with confidence by bringing maintainability and code coverage metrics into the developer workflow. Now, building on our years of experience with Quality, we’ve decided to reinvest in the product — rebuilding the product from the ground up.

Reflecting our renewed focus on code health, we’ve branched out Qlty into its own new company, Qlty Software. We’re now launching a brand new edition of Quality, available as Qlty Cloud and Qlty CLI.

For users of Code Climate Quality, you’ll notice some meaningful improvements:

• Qlty CLI: The brand new Qlty CLI is designed to provide faster feedback loops by enabling configuration and analysis to be run locally.

• Expanded Language Support: Qlty Cloud supports a broader range of languages, frameworks, and technologies, ensuring that your tools evolve alongside modern development trends.

• Security Scanning: Qlty Cloud includes built-in security scanning for code vulnerabilities, providing integrated checks for SAST, IaC, and SCA—critical for identifying and addressing security risks earlier in your development process.

• Enhanced Code Coverage Support: With improvements to coverage reporting, including diff coverage highlighting directly within the Qlty UI, you can manage coverage more effectively without needing a browser extension.

• Improved Monorepo Support: Qlty offers better handling of monorepos, making it simpler to work across multiple repositories without the complexity traditionally associated with these setups.

• Modernized Plugin Architecture: The new plugin system allows for greater flexibility and faster plugin integration, making it easier to extend Qlty Cloud with the tools your team needs.

While Qlty Cloud is still in beta, it represents the future of Code Climate Quality. We’re now analyzing your existing projects with Qlty Cloud, and we’re excited to see what you think.

Frequently Asked Questions

Setup:

1. I’m ready. How do I get started?

   • For instructions on migrating to Qlty from Code Climate Quality, see our Migration Guide.

2. How much longer will I have access to Code Climate Quality?

   • We haven’t yet established a timeline for shutting down Code Climate Quality, and our current focus is making Qlty Cloud as great as possible to help ease this transition. We’ll provide at least 30 days notice for paying customers.

Features:

1. Does Qlty support all of the features found in Quality?

   • Qlty includes nearly all of the functionality found in Code Climate Quality (and much more). See our Product Comparison for details.

   • Qlty supports most (but not all) of the plugins found in Code Climate Quality. For help with plugins which are no longer supported, please see our guide on Plugin Mapping.

Billing:

1. Is Qlty pricing similar to what I’m paying for Code Climate Quality?

   • The expected pricing for Qlty Cloud will be comparable to Code Climate Quality, with a modest increase.

2. Where can I manage my billing settings?

   • For now, billing is still managed via the Code Climate UI.

Analysis:

1. Do I need to update my analysis configuration?

   • We highly recommend creating a qlty.toml to leverage the full range of Qlty’s functionality. For migrated projects containing a .codeclimate.yml, Qlty attempts to replicate your existing configuration during analysis. For more info, head here.

   • For migrated projects which don’t contain a .codeclimate.yml, Qlty uses an autogenerated configuration. Existing in-app configurations (seen in the Code Climate UI) will not be migrated to Qlty.

2. Do I need to update my coverage reporting configuration?

   • Yes. The existing Code Climate test reporter is not supported in Qlty, so you’ll need to update your CI configuration to implement Qlty’s new coverage reporter. For more information, head see our Migration Guide.

3. Will my historical data be migrated from Code Climate?

   • Historical data (relating to Maintainability and Test Coverage) will not be migrated from Code Climate Quality.

4. Why are my maintainability ratings different in Qlty?

   • It’s expected that maintainability ratings in Qlty may differ from those in Quality. Qlty new checks for Code Smells, Duplication, and Complexity are analagous to Code Climate Maintainability Checks, but with minor differences:
     • Qlty supports a larger number of languages in Qlty than in Code Climate Quality.
     • The default thresholds for Qlty checks may differ from Quality’s default thresholds.
     • Qlty’s default exclusions are broader than Quality’s default exclusions.
     • Qlty is git aware and excludes all files in your .gitignore, whereas Quality is agnostic to the .gitignore file.

See Also

• Product Comparison
• Migration Guide
• Plugin Mappings