Repowise / Code Climate / Qlty
Repowise vs Code Climate / Qlty: the decision is not a checklist.
Choose between a focused managed maintainability workflow and a broader self-hostable repository intelligence layer.
Qlty is the direct successor for teams that used Code Climate for maintainability and coverage. Repowise adds architecture, git history, recorded decisions and agent access around its code-health findings.
- Category
- Maintainability and test coverage
- Reading rule
- Different product philosophies are explained before individual capabilities are compared.
01 / Category framing
What each product is built to do.
- Repowise
- A persistent codebase-intelligence layer that combines structure, git history, decisions, code health, generated documentation, and MCP retrieval for both people and coding agents.
- Code Climate / Qlty
- Cloud maintainability and coverage analysis, with metrics and issue workflows for engineering teams.
How it works
What happened to Code Climate Quality?
On November 11, 2024, Code Climate announced that its Quality product had been spun out into a separate company, Qlty Software. Code Climate itself now sells only Velocity, an engineering-metrics product built on delivery data such as cycle time and deploy frequency.
Existing Code Climate Quality organizations were migrated to Qlty on a scheduled date, and their old GitHub integrations (commit statuses, PR comments) were switched off. The old Code Climate API was disabled on July 18, 2025, so CI jobs still uploading coverage with cc-test-reporter now fail. So if you are looking for a Code Climate alternative for maintainability and test coverage, Qlty is the direct successor, and the question is whether you want that product or something different.
02 / Overlap and difference
Where the workflows meet, and where they diverge.
Genuine overlap
- Both expose maintainability evidence to help prioritize engineering work.
- Both connect repository analysis to team review workflows.
- Starting point
- Qlty centers on managed maintainability and coverage metrics. In Repowise, code health is one view in an index that also covers architecture, history and decisions.
- Operating model
- Qlty documents a cloud product and CLI workflow. Repowise supports hosted use and open-source self-hosting.
- Evidence boundary
- No controlled head-to-head benchmark is claimed on this page. Product descriptions come from the linked primary documentation.
03 / Concise comparison
Compare the operating questions.
Text carries every distinction. Color and icons are not required to understand this table.
Scroll sideways to read both products and the caveat column.
| Buying question | Repowise | Code Climate / Qlty | Boundary |
|---|---|---|---|
| What does it check? | Code health markers per file (defect, maintainability and performance risk), dead code, hotspots, ownership and co-change from git. | Linting and formatting, maintainability metrics (complexity, duplication, code smells), coverage, and security scanning (SAST/IaC), focused on newly introduced issues. | Qlty runs linters; Repowise does not replace your linters. |
| Languages and tools | 16 languages parsed to a full syntax tree, 11 at the Full tier. | The Qlty CLI lists 40+ languages and technologies and 60+ linter plugins with over 20,000 rules. | Qlty's linter coverage is much wider. |
| Test coverage | Ingests coverage reports (LCOV, Cobertura, JaCoCo and others) to flag hotspots that lack tests; the PR bot can fail a pull request below a patch coverage minimum. | Coverage tracking is a core feature of every plan, including Free. | Qlty is the fuller coverage product. |
| Uses git history? | Yes. It mines hotspots, ownership, bus factor, co-change and bug-fix history from git, using the full history on paid plans. | Hotspots are listed as an Enterprise plan feature; trends keep one year of history on Pro. | History-based ranking is Repowise's default view. |
| Coding agents | MCP server with 10 tools (answers, search, context, symbols, rationale, risk, health), usable from Claude Code, Cursor, Claude.ai and other MCP clients. | AI autofixes are metered per plan. No MCP server is described in the Qlty pages checked. | Verify Qlty's current agent integrations before buying. |
| Where it runs | Open source under AGPL-3.0 and self-hostable, or hosted at repowise.dev. | Qlty Cloud, plus the Qlty CLI published under a Fair Source license (Business Source License 1.1) that you can run locally and in CI. | Qlty documents about five minutes of setup with no CI changes for Cloud. |
| Price | Free for public repositories (git analysis on the last 500 commits). Pro $15/month, Teams $20/seat/month. Self-hosting is free. | Free: 1,000 analysis minutes and 100 AI autofixes a month. Pro $20/contributor/month. Enterprise $30/contributor/month. Free for open source projects. | Prices from qlty.sh/pricing on the verification date. |
04 / Repowise evidence
Inspect the product, not a scorecard.
The links below open current output for the named Repowise repository. Measured claims, when relevant to this decision, come directly from the benchmark fact registry and keep their sample and caveat attached.
One result you can check
Repowise's index of ollama/ollama (1,089 files) flags 154 hotspots, files that change often and are complex, and lists server/routes.go first. A maintainability grade alone treats a messy file nobody touches the same as one that changes every week; ranking by change history puts the second one on top. We did not run Qlty on ollama for this page.
Open the ollama hotspot list05 / Fit
Choose Repowise when...
- You want code health joined to git history, architecture, decisions, and generated documentation.
- You want a self-hostable context layer usable by people and MCP clients.
Honest trade-off
Choose Code Climate / Qlty when...
- You want a managed maintainability and coverage workflow with Qlty's integrations.
- Continuity with Code Climate concepts is important to the team.
06 / Verification notes
What this brief does not claim.
- No controlled head-to-head performance or quality result is claimed between these products.
- Competitor capabilities, packaging, deployment terms, and prices can change after the verification date.
- A product-category comparison is not a security, compliance, procurement, or legal assessment.
- Repowise evidence links show current product output; they are demonstrations, not proof that every repository will produce the same findings.
External facts checked October 6, 2026
- Code Climate / QltyOfficial maintainability metrics and cloud workflow documentation.Read Qlty documentation
- Code Climate / QltyCode Climate Quality is now Qlty Software; Code Climate focuses on Velocity.Code Climate announcement
- Code Climate / QltyMigration of Code Climate Quality organizations; Code Climate API disabled July 18, 2025.Qlty migration guide
- Code Climate / QltyFree, Pro $20 and Enterprise $30 per contributor per month; free for open source.Qlty pricing
- Code Climate / QltyFair Source license, 40+ languages, 60+ linter plugins, over 20,000 rules.Qlty CLI source
Common questions
Everything people ask before they try it.
Is Code Climate still available?
Code Climate Quality is not. It was spun out as Qlty Software in November 2024, existing organizations were migrated, and the old Code Climate API was disabled on July 18, 2025. Code Climate, Inc. still sells Velocity, which is an engineering-metrics product, not code quality analysis.
What is the best Code Climate alternative?
For the same maintainability and coverage workflow, Qlty is the direct successor. SonarQube and Codacy are the other common rule-based options. Repowise fits when you want files ranked by git history and code health together, with architecture, decisions and an MCP server for coding agents.
Is Qlty free?
Qlty Cloud has a free plan with 1,000 analysis minutes and 100 AI autofixes a month, and it is free for open source projects. The Qlty CLI is free to use under a Fair Source license.
Does Repowise track test coverage like Code Climate did?
Repowise covers part of it. It ingests coverage reports, uses them to find hotspots without tests, and its PR bot can fail a pull request below a patch coverage minimum. It does not offer Qlty's coverage trends and dashboards, so if coverage reporting is the main need, Qlty is the closer replacement.
Can I use Qlty and Repowise together?
Yes. Qlty runs linters and coverage in CI; Repowise indexes the repository for health, history, architecture and agent context. They do not compete for the same step in the pipeline.
Start with a real repository.
Browse Repowise output before you make the product decision. No account is required for public repositories.