# Official Codacy sources

Verify these pages again before implementation.

- Client-side tools: `https://docs.codacy.com/repositories-configure/local-analysis/client-side-tools/`
- Codacy Cloud CLI and Skills: `https://docs.codacy.com/codacy-cloud-cli/`
- Guardrails getting started: `https://docs.codacy.com/codacy-guardrails/codacy-guardrails-getting-started/`
- Guardrails usage: `https://docs.codacy.com/codacy-guardrails/codacy-guardrails-how-to-use/`
- Guardrails limitations: `https://docs.codacy.com/codacy-guardrails/codacy-guardrails-limitations/`
- Guardrails rule configuration: `https://docs.codacy.com/codacy-guardrails/codacy-guardrails-how-to-configure-rules/`
- Guardrails troubleshooting: `https://docs.codacy.com/codacy-guardrails/codacy-guardrails-troubleshooting/`
- Guardrails FAQ: `https://docs.codacy.com/codacy-guardrails/codacy-guardrails-faq/`

## Verified behavior on 2026-07-15

- Client-side tools can be containerized through Codacy Analysis CLI or standalone tools whose output is converted and uploaded.
- GitHub users are directed to evaluate the official Codacy Analysis CLI GitHub Action for containerized tools.
- Cloud CLI installs from `@codacy/codacy-cloud-cli`, uses `codacy login` interactively, supports `CODACY_API_TOKEN` in CI, and supports `--output json`.
- Official Codacy Skills are installed separately from the Cloud CLI and may expose write operations.
- Guardrails requires Git, Node.js with working `npx`, and curl for the documented VS Code-based flow.
- Guardrails supports macOS and Linux; Windows support requires WSL and is limited to VS Code-based IDEs in the current limitation page.
- The documented built-in scanners include Trivy, Semgrep, ESLint, Pylint, PMD, dartanalyzer, Lizard, and Revive.
- With no API token, Guardrails uses a predefined recommended ruleset. With an API token, it retrieves repository rule configuration.
- Rule configuration can come from supported scanner configuration files or the Codacy UI.
- Local scanning can work offline; API-backed metrics and Cloud features require connectivity.
- Guardrails local scanning is free according to the current FAQ; centralized policy and broader Cloud features depend on paid plans.

Treat these statements as dated observations, not permanent platform guarantees.
