Qlty CLI is a universal code quality tool designed for polyglot development teams, aiming to unify linting, auto-formatting, security scanning, and maintainability checks across 40+ languages and 70+ static analysis tools. It provides a single, fast, and consistent interface for developers to improve code quality and security.

How It Works

Qlty CLI leverages a Rust-based core for high performance and concurrency, integrating with numerous external linters and analysis tools. It operates natively without relying on Docker for linter execution, maximizing speed. The tool is Git-aware, focusing analysis on changes and supporting integration with Git hooks for pre-commit and pre-push workflows. Configuration is managed via a .qlty/qlty.toml file, allowing for version-controlled, flexible setups.

Quick Start & Requirements

• Installation:
  • macOS/Linux: curl https://qlty.sh | bash
  • Windows: powershell -c "iwr https://qlty.sh | iex"
  • Docker image available on GHCR.
• Setup: qlty init within a Git repository.
• Prerequisites: PHP installation required for certain PHP linters.
• Documentation: https://github.com/qltysh/qlty

Highlighted Details

• Supports over 70 static analysis tools for 40+ languages.
• Features auto-fixing capabilities, including AI-generated fixes.
• Provides comprehensive code quality metrics (duplication, complexity, security, coverage).
• Written in Rust for speed and efficiency.

Maintenance & Community

• Community support via GitHub Discussions and Discord chat.
• Feature requests and bug reports are managed through GitHub Issues.
• Contributions are welcomed, with clear guidelines in CONTRIBUTING.md.

Licensing & Compatibility

• Licensed under Fair Source (Business Source License 1.1) with Delayed Open Source Publication (DOSP).
• Free for all uses, including commercial projects, with no contributor limits.

Limitations & Caveats

• Some PHP linters require a pre-installed PHP environment.
• The project is published under a Fair Source license, which may have implications for certain open-source integration scenarios before its transition to open source.