Qlty

Qlty is a code quality platform for GitHub teams, formerly Code Climate Quality: linting, coverage, maintainability grades and security checks on pull requests.

Qlty checks each pull request for lint errors, untested lines, duplicated code and security problems before the change merges. Qlty Software Inc. builds it, and the product began as Code Climate Quality before branching out into a company of its own, announced in December 2024. It comes as two parts under one account. The Qlty CLI is a fair source command-line tool written in Rust, and Qlty Cloud is the hosted service that reads results from GitHub repositories. The CLI runs linters and auto-formatters through plugins, with Semgrep, Bandit and Brakeman for security rules and Trufflehog for secrets. OSV Scanner looks for vulnerable open source packages, while checkov, tflint and trivy cover Terraform, CloudFormation, Kubernetes and Docker files. A qlty.toml file in each repository chooses the plugins and sets how each code smell is treated, and custom checks can be written with AST-Grep. Qlty Cloud assigns a maintainability letter grade based on technical debt and tracks complexity, duplication and test coverage over time. On a pull request it posts the Qlty Gate, Qlty Coverage and Qlty Diff Coverage statuses, comments under the lines where new issues appear, and offers AI autofixes as suggestions that can be committed straight to the branch. The product is built for engineering teams whose code lives on GitHub Cloud and who want quality results inside the pull request. Tech leads use the gate to stop a merge that brings in new issues or lowers coverage. Engineering managers read Workspaces, which roll maintainability, duplication, security and coverage up across many repositories, to see where debt is building. Maintainers of community open source projects are served through a program of their own. Teams that let AI coding agents such as Claude Code or Cursor write code run the CLI as a check on that output. In daily work a developer runs the CLI locally to lint and format before pushing, and the same configuration runs again in CI. Coverage reports go up from GitHub Actions, CircleCI, Buildkite or Jenkins, and Qlty compares each one with the base branch. During review its status checks and comments sit in GitHub alongside the human reviewers' notes. Over months, Trends and hotspots show whether a refactoring lowered complexity or whether one corner of the codebase keeps collecting issues. The job Qlty is hired for is keeping every merge from making the code harder to change.