Codacy is a commercial appsec platform that centralizes static analysis, linting, and code-quality checks across a codebase, run as a hosted service that repositories connect to rather than a tool installed standalone. It aggregates results from engines like GolangCI-Lint, PHP CS Fixer, Checkov, and ShellCheck, letting teams either configure rules through its UI or defer to config files already committed in the repo, such as .shellcheckrc or .checkov.yaml. Its API spans repository, organization, security, and coding-standards management, plus areas like DASTDASTDynamic application security testing, probing a running application from the outside for vulnerabilities. It checks behavior exposed through the application's interfaces., SBOMSBOMA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue., and gate policies, pointing to application developers and platform teams who need one place to enforce code standards across many repositories rather than per-project tooling. With 17 releases in the tracked window and the last one 81 days ago, it sees steady, ongoing development.
Which files in my repository break the code-quality and style rules my team has agreed on?
runs the configured engines (GolangCI-Lint, PHP CS Fixer, ShellCheck, Oxlint, Checkov, and others) across the codebase and lists violations by file and rule, deferring to config files already committed in the repo when present
Which of my repositories are enforcing a different rule set than the others?
centralizes configuration per organization so every connected repository is judged against the same coding standards, rather than each project carrying its own local setup
Did enabling a new linter just flood my repository with issues that were always there?
flags that newly added engines are off by default on existing repositories, so a sudden spike in reported issues traces back to a manual toggle rather than new code
Is my local ShellCheck or Checkov configuration actually the one being used, or is the UI overriding it?
reads the repository's own configuration file when the corresponding toggle is enabled, and otherwise falls back to whatever rules were set through the UI
Can an AI coding agent catch these issues before I even commit?
lets agents run the same static analysis locally through an installable CLI skill, surfacing the same rule violations before the code reaches a pull request
Which pull requests introduced new issues rather than inheriting existing ones?
tracks analysis results per commit and pull request, so logs and issue counts can be compared against the branch's prior state
40 capabilities
across 3 capability groups
· 10 backed by code, an API document or a real run
Built from Codacy's releases, docs, README and our own runs.
“Seen” marks the month we first spotted a release the vendor didn't date.
Group names and tags are our labels.
+REST API9 featuresInterfaces and integrationssince 2019▸
+REST API — AnalysisverifiedLets users retrieve and update analysis data, including issues and pull-request quality results, through the API.16 releases · 69 other sources · first seen Oct 2020▸
Shared capability: REST API
Also counts toward: REST API
release
16 total
POST /analysis/organizations/{provider}/{remoteOrganizationName}/repositories/{repositoryName}/autoconfig: response schema changed
3.1.0 · Sep 2026
· source
· release history
POST /search/analysis/organizations/{provider}/{remoteOrganizationName}/repositories: response schema changed
3.1.0 · Sep 2026
· source
· release history
GET /analysis/organizations/{provider}/{remoteOrganizationName}/repositories/{repositoryName}: response schema changed
3.1.0 · Sep 2026
· source
· release history
GET /analysis/organizations/{provider}/{remoteOrganizationName}/repositories: response schema changed
3.1.0 · Sep 2026
· source
· release history
GET /analysis/organizations/{provider}/{remoteOrganizationName}/repositories/{repositoryName}/pull-requests: response schema changed
3.1.0 · Aug 2026
· source
· release history
GET /analysis/organizations/{provider}/{remoteOrganizationName}/repositories/{repositoryName}/pull-requests/{pullRequestNumber}: response schema changed
3.1.0 · Aug 2026
· source
· release history
api
69 total
POST /analysis/organizations/{provider}/{remoteOrganizationName}/repositories/{repositoryName}/issues/bulk-ignore
· source
· full API surface
GET /analysis/organizations/{provider}/{remoteOrganizationName}/repositories/{repositoryName}/pull-requests
· source
· full API surface
POST /analysis/organizations/{provider}/{remoteOrganizationName}/repositories/{repositoryName}/pull-requests/{pullRequestNumber}/bypass
· source
· full API surface
GET /analysis/organizations/{provider}/{remoteOrganizationName}/repositories/{repositoryName}/quality-settings
· source
· full API surface
POST /analysis/organizations/{provider}/{remoteOrganizationName}/repositories/{repositoryName}/autoconfig
· source
· full API surface
GET /analysis/organizations/{provider}/{remoteOrganizationName}/repositories/{repositoryName}/tools/{toolUuid}/patterns/{patternId}
· source
· full API surface
+REST API — Organisation managementverifiedLets users manage organisation-level resources, including members, integrations, and settings, through the API.11 releases · 41 other sources · first seen Feb 2019▸
Shared capability: REST API
Also counts toward: REST API, Ticketing integration
release
11 total
New endpoint POST /organizations/{provider}/{remoteOrganizationName}/integrations/webhooks
3.1.0 · Sep 2026
· source
· release history
New endpoint GET /organizations/{provider}/{remoteOrganizationName}/integrations/webhooks
3.1.0 · Sep 2026
· source
· release history
Organization (32 endpoints) — create, read, update, delete
3.1.0 · seen Aug 2026
· source
· release history
Exposes listPeopleFromOrganizationCsv API endpoint to download organization member lists as CSV, available on all plans
Cloud March 2023 · Mar 2023
· source
· release history
Switches the GitHub integration to use a GitHub Apps token instead of a personal one so features continue working if the creator leaves the organization
Cloud August 2022 · Aug 2022
· source
· release history
Streamlines the configuration of Git providers during initial setup
v1.0.0 · May 2020
· source
· release history
example
Re-authorize the Bitbucket integration after the OAuth 2 migration by logging in via the specific endpoint.$ https://www.codacy.com/login-with/bitbucket
Bitbucket changes February 18, 2019 · Feb 2019
· source
api
40 total
GET /organizations/{provider}/{remoteOrganizationName}/integrations/jira
· source
· full API surface
GET /organizations/{provider}/{remoteOrganizationName}/gitProviderAppPermissions
· source
· full API surface
POST /organizations/{provider}/{remoteOrganizationName}/integrations/webhooks
· source
· full API surface
PUT /organizations/{provider}/{remoteOrganizationName}/integrations/slack
· source
· full API surface
POST /organizations/{provider}/{remoteOrganizationName}/settings/sync
· source
· full API surface
POST /organizations/{provider}/{remoteOrganizationName}/integrations/providerSettings/apply
· source
· full API surface
+REST API — Repository managementverifiedLets users create, configure, and remove repositories and their settings within an organisation through the API.13 releases · 31 other sources · first seen Mar 2019▸
Shared capability: REST API
Also counts toward: REST API
release
13 total
New endpoint DELETE /organizations/{provider}/{remoteOrganizationName}/integrations/webhooks/{webhookId}︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
3.1.0 · Sep 2026
· source
· release history
Repository (47 endpoints) — create, read, update, delete
3.1.0 · seen Aug 2026
· source
· release history
Adds Ignore Reason field for ignored issues in repositories and the Security Dashboard (Accepted use, False positive, Not exploitable, Test code, External code)
Cloud December 2025 · Dec 2025
· source
· release history
Adds automatic expiration timeouts for every session for increased security
Cloud June 2024 · Jun 2024
· source
· release history
Display penetration testing results directly in the Codacy app UI
Cloud March 2024 · Mar 2024
· source
· release history
Extends the Analysis configuration permission level from organization Settings > Member privileges to cover pull request reanalysis and last commit reanalysis
Cloud October 2023 · Oct 2023
· source
· release history
api
31 total
GET /organizations/{provider}/{remoteOrganizationName}/repositories/{repositoryName}/settings/quality/commits
· source
· full API surface
POST /organizations/{provider}/{remoteOrganizationName}/repositories/{repositoryName}/integrations/refreshProvider
· source
· full API surface
POST /organizations/{provider}/{remoteOrganizationName}/repositories/{repositoryName}/settings/ssh-repository-key
· source
· full API surface
GET /organizations/{provider}/{remoteOrganizationName}/repositories/{repositoryName}/commits/{commitUuid}/diff
· source
· full API surface
GET /organizations/{provider}/{remoteOrganizationName}/repositories/{repositoryName}/settings/stored-ssh-key
· source
· full API surface
PATCH /organizations/{provider}/{remoteOrganizationName}/repositories/{repositoryName}/integrations/providerSettings
· source
· full API surface
+REST API — SecurityverifiedLets users manage security findings and SLA configuration through the API.13 releases · 22 other sources · first seen Jul 2023▸
Shared capability: REST API
Also counts toward: REST API
release
13 total
New endpoint POST /organizations/{provider}/{remoteOrganizationName}/security/dashboard/remediation/search
3.1.0 · Oct 2026
· source
· release history
New endpoint POST /organizations/{provider}/{remoteOrganizationName}/security/dashboard/remediation/history/search︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
3.1.0 · Oct 2026
· source
· release history
Security (20 endpoints) — create, read, update, delete
3.1.0 · seen Aug 2026
· source
· release history
Security dependency findings now surface affected entrypoint functions reachable from a vulnerable dependency, visible in the Findings card, CLI command output, and public API response fields.
Cloud July 2026 · Jul 2026
· source
· release history
Added text search filter capability within the SRM (Security Risk Management) tab findings view.
Cloud February 2026 · Feb 2026
· source
· release history
Adds the SRM dependencies tab to view dependency lists, distribution across repositories, versions, and associated security findings.
Cloud December 2024 · Dec 2024
· source
· release history
api
22 total
GET /organizations/{provider}/{remoteOrganizationName}/security/items/{srmItemId}
· source
· full API surface
PUT /organizations/{provider}/{remoteOrganizationName}/security/sla
· source
· full API surface
GET /organizations/{provider}/{remoteOrganizationName}/security/sla
· source
· full API surface
POST /organizations/{provider}/{remoteOrganizationName}/security/dashboard
· source
· full API surface
POST /organizations/{provider}/{remoteOrganizationName}/security/items/{srmItemId}/ignore
· source
· full API surface
GET /organizations/{provider}/{remoteOrganizationName}/security/dashboard
· source
· full API surface
+REST API — Coding StandardsverifiedLets users create and manage coding standards and their associated rule patterns through the API.14 releases · 18 other sources · first seen Feb 2021▸
Shared capability: REST API
Also counts toward: REST API
release
14 total
Coding Standards (17 endpoints) — create, read, update, delete
3.1.0 · seen Aug 2026
· source
· release history
Automatic Rule File Updates on Git Load: When the MCP Server is installed, loading a Git repository will now automatically update the rules file.
Cloud May 2025 · May 2025
· source
· release history
CLIv2 configuration files are placed under .codacy/ instead of the repository root
Cloud April 2025 · Apr 2025
· source
· release history
sarif is now supported as the standard output format for cli v2
Cloud April 2025 · Apr 2025
· source
· release history
Jscpd supports new languages: Rust, CoffeeScript, Objective C, Elixir, Groovy, and VisualBasic
Cloud September 2024 · Sep 2024
· source
· release history
Radon now calculates the average complexity of each file in reports.
Cloud August 2024 · Aug 2024
· source
· release history
GET /organizations/{provider}/{remoteOrganizationName}/coding-standards
· source
· full API surface
PATCH /organizations/{provider}/{remoteOrganizationName}/coding-standards/{codingStandardId}/repositories
· source
· full API surface
+REST API — SBOM and AI inventoryverifiedLets users generate and search software bill-of-materials and AI inventory data for repositories and images through the API.7 releases · 17 other sources · first seen Mar 2023▸
Shared capability: REST API
Also counts toward: REST API
release
7 total
21 more areas: Sbom, Admin, Aiinventory, Enterprise, Jira, People, Segments, Tools, Coverage, Dast, Reports, File, Billing, Integrations, Language Settings, App, Configuration, Health, Languages, Session, Version
3.1.0 · seen Aug 2026
· source
· release history
Adds OpenSSF Scorecard report view directly from dependency details to assess open-source component security posture.
Cloud September 2025 · Sep 2025
· source
· release history
Shows license information for every dependency and repository directly in the Security & Risk Management dashboard’s Dependencies tab
Cloud August 2025 · Aug 2025
· source
· release history
Adds support for several new ESLint plugins (eslint-plugin-perfectionist, @ngrx/eslint-plugin, @nx/react, @tanstack/eslint-plugin-query, eslint-plugin-deprecation, eslint-plugin-ember, eslint-plugin-eslint-plugin, eslint-plugin-fp, eslint-plugin-header, eslint-plugin-import-alias,…
Cloud June 2023 · Jun 2023
· source
· release history
Adds support for the stylelint-no-px plugin
Cloud June 2023 · Jun 2023
· source
· release history
Adds eslint-plugin-rxjs, eslint-plugin-markdown, and eslint-plugin-yml to supported ESLint plugins.
Cloud May 2023 · May 2023
· source
· release history
api
17 total
POST /organizations/{provider}/{remoteOrganizationName}/image-sboms
· source
· full API surface
POST /organizations/{provider}/{remoteOrganizationName}/ai-inventory/repositories/summaries/search
· source
· full API surface
POST /organizations/{provider}/{remoteOrganizationName}/sbom/dependencies/search
· source
· full API surface
POST /organizations/{provider}/{remoteOrganizationName}/sbom/repositories/search
· source
· full API surface
GET /organizations/{provider}/{remoteOrganizationName}/ai-risk-checklist
· source
· full API surface
POST /organizations/{provider}/{remoteOrganizationName}/sbom/dependencies/repositories/search
· source
· full API surface
+REST API — MetricsverifiedLets users retrieve metrics data at repository, organisation, and enterprise level through the API.4 releases · 19 other sources · first seen Mar 2021▸
Shared capability: REST API
Also counts toward: REST API
release
Metrics (13 endpoints) — create, read
3.1.0 · seen Aug 2026
· source
· release history
Adds Slack channel notification capability for new critical Security issues detected in the default branch of any repository
Cloud September 2023 · Sep 2023
· source
· release history
The getRepositoryWithAnalysis API endpoint now includes data about coverable and covered lines for a given repository
Cloud August 2023 · Aug 2023
· source
· release history
New getCommitDeltaStatistics API endpoint returns quality metric deltas introduced by a commit.
v3.5.0 · Mar 2021
· source
· release history
api
19 total
POST /organizations/{provider}/{remoteOrganizationName}/metrics/{metricName}/period-grouped
· source
· full API surface
POST /enterprises/{provider}/{enterpriseName}/metrics/{metricName}/period
· source
· full API surface
GET /coverage/organizations/{provider}/{remoteOrganizationName}/repositories/{repositoryName}/pull-requests/{pullRequestNumber}/files
· source
· full API surface
POST /enterprises/{provider}/{enterpriseName}/metrics/{metricName}/latest-grouped
· source
· full API surface
POST /organizations/{provider}/{remoteOrganizationName}/metrics/start
· source
· full API surface
GET /organizations/{provider}/{remoteOrganizationName}/repositories/{repositoryName}/files/{fileId}/duplication
· source
· full API surface
+REST API — Account managementverifiedLets users manage account-level resources through dedicated API endpoints.1 release · 14 other sources▸
Shared capability: REST API
Also counts toward: REST API
release
Account (17 endpoints) — create, read, update, delete
3.1.0 · seen Aug 2026
· source
· release history
+REST API — Gate PoliciesverifiedLets users create and manage quality gate policies through the API.5 releases · 9 other sources · first seen Feb 2022▸
Shared capability: REST API
Also counts toward: REST API
release
Gate Policies (9 endpoints) — create, read, update, delete
3.1.0 · seen Aug 2026
· source
· release history
Quality gates now apply to commits in addition to pull requests.
Cloud May 2023 · May 2023
· source
· release history
Allows defining quality gates using a coverage variation threshold with two-decimal precision
Cloud September 2022 · Sep 2022
· source
· release history
Adds ∅ (not applicable) symbol for diff coverage when a pull request has no coverable lines
Cloud May 2022 · May 2022
· source
· release history
Adds a quality gate rule option for diff coverage to enforce thresholds
Cloud February 2022 · Feb 2022
· source
· release history
api
9 total
PATCH /organizations/{provider}/{remoteOrganizationName}/gate-policies/{gatePolicyId}
· source
· full API surface
POST /organizations/{provider}/{remoteOrganizationName}/gate-policies
· source
· full API surface
GET /organizations/{provider}/{remoteOrganizationName}/gate-policies/{gatePolicyId}
· source
· full API surface
POST /organizations/{provider}/{remoteOrganizationName}/gate-policies/setCodacyDefault
· source
· full API surface
GET /organizations/{provider}/{remoteOrganizationName}/gate-policies
· source
· full API surface
DELETE /organizations/{provider}/{remoteOrganizationName}/gate-policies/{gatePolicyId}
· source
· full API surface
+Static security analysis engine integrationshippedIntegrates specific static analysis engines like Flawfinder for security findings and PSScriptAnalyzer for PowerShell support.8 releases · first seen Nov 2018▸
Adds Semgrep support for PL/SQL rules from Checkmarx.
Cloud August 2024 · Aug 2024
· source
· release history
The Codacy GitHub App requires updated permissions; organization owners must approve these for the feature to work correctly.
Cloud December 2023 · Dec 2023
· source
· release history
Adds support for Semgrep’s open-source engine to perform static application security testing (SAST), with the option to upgrade to Semgrep Pro
Cloud November 2023 · Nov 2023
· source
· release history
Adds support for Trivy to detect committed secrets, IaC misconfigurations, and other security risks
Cloud August 2023 · Aug 2023
· source
· release history
Adds static analysis support for Objective-C with the tool Faux Pas
v3.1.0 · Dec 2020
· source
· release history
Gosec GoLang Security Checker supported as a new client-side tool
v1.5.0 · Jul 2020
· source
· release history
+AI-Driven Development IntegrationshippedEnables AI agents to execute static analysis and code reviews locally via CLI skills and plugin integrations, supporting pre-commit scanning and custom review configurations.5 releases · 2 other sources · first seen Mar 2026▸
Also counts toward: Command-line interface, Plugin system
release
Enables local ruleset sync so the @codacy/analysis-cli checks code against the same standards enforced at the merge gate, when connected to a Codacy account.
announced · Sep 2026
· source
· release history
Installs Codacy Skills into Claude Code via claude plugin marketplace add codacy/codacy-skills and claude plugin install codacy-skills@codacy, with support for the Agent Skills standard across multiple coding agents.
announced · Sep 2026
· source
· release history
Adds the Analysis CLI Skill, installable via npm i -g @codacy/analysis-cli and claude plugin install codacy-skills@codacy, enabling AI agents (Claude Code, OpenAI Codex, GitHub Copilot) to run Codacy static analysis locally before commit — with no Codacy account required.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
announced · Sep 2026
· source
· release history
Supports scoping analysis to specific files, staged changes, a branch, or an open pull request via the @codacy/analysis-cli.
announced · Sep 2026
· source
· release history
AI-generated test coverage suggestions with ready-to-use prompts for coding agents
Cloud March 2026 · Mar 2026
· source
· release history
example
Install the Cloud CLI and authenticate to enable the Code Review Skill, which reviews an open PR against quality gates, coverage, and cloud analysis.$ npm install -g @codacy/codacy-cloud-cli codacy login
announced · Sep 2026
· source
Install the Analysis CLI and Codacy Skills plugin into Claude Code to enable pre-commit scanning with no account needed.$ npm i -g @codacy/analysis-cli claude plugin marketplace add codacy/codacy-skills claude plugin install codacy-skills@codacy
announced · Sep 2026
· source
+File-based Checkov configurationshippedUses a Checkov configuration file already present in the repository to control infrastructure-as-code analysis rather than requiring rules to be set up in the UI.7 releases · 1 other source · first seen Dec 2020▸
Adds support for Checkov configuration files (.checkov.yaml or .checkov.yml) in the repository, enabled via Repository > Code Patterns > Checkov > "Use Checkov configuration file found in the repository".
Adding PHP CS Fixer and support to Checkov configuration files July, 2026 · seen Aug 2026
· source
· release history
Adds support for Checkov configuration files, enabling repository-level Checkov settings to be recognized by Codacy.
Adding PHP CS Fixer and support to Checkov configuration files July, 2026 · seen Jul 2026
· source
· release history
Removed codacy-activities, hotspots-api, and hotspots-worker components and their associated database config keys: activities.*, hotspots-api.*, hotspots-worker.*, global.activitiesdb.*, global.hotspotsdb.*.
v5.0.0 · Dec 2021
· source
· release history
Adds Objective-C support using Clang-Tidy as a client-side tool for code analysis
v4.3.0 · Sep 2021
· source
· release history
PostgreSQL version 10.15 is now required as previous versions reach end-of-life.
v4.0.0 · May 2021
· source
· release history
Enables automatic GitHub fix suggestions for ESLint-identified issues via a new activation setting.
v3.4.0 · Mar 2021
· source
· release history
example
Let Codacy pick up your existing Checkov config instead of managing every check through the UI.$ Repository > Code Patterns > Checkov > enable "Use Checkov configuration file found in the repository"
Adding PHP CS Fixer and support to Checkov configuration files July, 2026 · seen Aug 2026
· source
+Infrastructure as Code analysisshippedAnalyzes infrastructure-as-code files including Terraform, AWS CloudFormation, Kubernetes, Serverless framework, and ARM Templates using Checkov.3 releases · first seen Mar 2021▸
Adds support for the stylelint-no-px linting plugin to detect pixel-based CSS values.
v12.0.0 · Jul 2023
· source
· release history
Drops support for Kubernetes versions 1.19, 1.20, and 1.21.
v11.0.0 · Apr 2023
· source
· release history
Checkov integration extends analysis support for infrastructure-as-code including Terraform, AWS CloudFormation, Kubernetes, Serverless framework, and ARM Templates.
v3.5.0 · Mar 2021
· source
· release history
+Other / not yet classified27 featuresFeatures we have not matched to a capability yet. A suggested match is marked.▸
+Linter engine version updatesshippedMaintains and updates underlying linter engines such as RuboCop, ESLint, and TSLint to ensure current rule sets and compatibility.23 releases · first seen Nov 2018▸
release
23 total
Supports .env, .env.production, .env.prod, and .env.staging files as YAML language so all YAML tools can scan them.
Cloud May 2026 · May 2026
· source
· release history
Adds support for ESLint 9 code analysis engine
Adding ESLint 9 and PMD 7 as new supported tools September, 2024 · Sep 2024
· source
· release history
Adds support for PMD 7 static analysis engine
Adding ESLint 9 and PMD 7 as new supported tools September, 2024 · Sep 2024
· source
· release history
Deprecates CSSLint, Faux Pas, JSHint, Tailor, and TSLint tools; users must enable replacement tools (Stylelint, Clang-Tidy, ESLint, SwiftLint) via code patterns or organization coding standard
v13.0.0 · Nov 2023
· source
· release history
Pylint now supports Python 3.11 syntax
v13.0.0 · Nov 2023
· source
· release history
Deprecated tools bundler-audit, CSSLint, Faux Pas, JSHint, Tailor, and TSLint are no longer active in the platform
Cloud October 2023 · Oct 2023
· source
· release history
+API token managementverifiedLets users create, list, and delete API tokens at both user and repository level.12 releases · 7 other sources · first seen Jan 2022▸
Also counts toward: REST API
release
12 total
POST /organizations/{provider}/{remoteOrganizationName}/repositories/{repositoryName}/tokens: response schema changed
3.1.0 · Aug 2026
· source
· release history
POST /user/tokens: response schema changed
3.1.0 · seen Aug 2026
· source
· release history
POST /organizations/{provider}/{remoteOrganizationName}/repositories/{repositoryName}/tokens: request body changed; response schema changed
3.1.0 · seen Aug 2026
· source
· release history
GET /organizations/{provider}/{remoteOrganizationName}/repositories/{repositoryName}/tokens: response schema changed
3.1.0 · seen Aug 2026
· source
· release history
GET /user/tokens: response schema changed
3.1.0 · seen Aug 2026
· source
· release history
New endpoint POST /organizations/{provider}/{remoteOrganizationName}/repositories/{repositoryName}/tokens/delete
3.1.0 · seen Aug 2026
· source
· release history
api
7 total
GET /organizations/{provider}/{remoteOrganizationName}/repositories/{repositoryName}/tokens
· source
· full API surface
POST /organizations/{provider}/{remoteOrganizationName}/repositories/{repositoryName}/tokens
· source
· full API surface
+Coverage issue reportingshippedDisplays detailed coverage metrics and tooltips for coverage-related issues within the project dashboard.16 releases · first seen Oct 2018▸
release
16 total
Enables GitHub coverage summaries posted directly to pull requests by the new engine.
Rollout of new Coverage engine November 23, 2023 · Nov 2023
· source
· release history
You now get two additional coverage status reports from the new, faster Coverage engine on your Git provider, showing whether your diff coverage and coverage variation are up to standard or not as configured on the quality gate rules for your repository
Cloud November 2023 · Nov 2023
· source
· release history
Adds two new coverage status reports on GitHub (diff coverage and coverage variation) using the new faster Coverage engine
Cloud October 2023 · Oct 2023
· source
· release history
Adds Codacy Visual Studio Code extension to review and manage pull request issues directly within the editor
Cloud September 2023 · Sep 2023
· source
· release history
Enables GitHub coverage status report generation using a new, faster Coverage engine
Cloud September 2023 · Sep 2023
· source
· release history
Adds automatic commit SHA-1 detection on Argo CD for the Coverage Reporter
Cloud January 2023 · Jan 2023
· source
· release history
+Project dashboard customizationshippedProvides visual configurations for the project dashboard, including badge copying, color schemes based on quality settings, and detailed coverage breakdowns.9 releases · 2 other sources · first seen Jul 2018▸
release
9 total
Pull Requests page filter bar lets users search PRs by title and toggle between viewing all target branches or only the current branch.
Cloud July 2026 · Jul 2026
· source
· release history
Launched an Organization Overview Dashboard with metrics for code health, security grade, complexity, duplication, and coverage.
Cloud February 2026 · Feb 2026
· source
· release history
Allows users to select which repositories to follow on Codacy for a cleaner, personalized dashboard view.
Cloud April 2023 · Apr 2023
· source
· release history
Codacy now displays the coverage variation metric with a precision of two decimal places on the Repository Dashboard and Organization Overview, and you can define quality gates with a coverage variation threshold using the same precision.
v10.0.0 · Feb 2023
· source
· release history
Supports reporting a summary of coverage metrics directly on pull requests (GitHub Cloud only)
Cloud January 2023 · Jan 2023
· source
· release history
Adds support for integrating with Bitbucket Server instances configured with custom context paths.
v9.0.0 · Sep 2022
· source
· release history
example
Use the new filter bar on the Pull Requests page to quickly find PRs affecting only the current feature branch.$ In the Codacy web UI, go to the Pull Requests tab and use the new filter bar to toggle the view to 'Current Branch' and search by title.
Cloud July 2026 · Jul 2026
· source
Drill down into specific directories to analyze coverage and complexity without noise from other parts of the repo.$ In the Codacy web UI, navigate to your repository and click on a specific folder in the left-hand navigation panel to view its scoped quality metrics.
Cloud July 2026 · Jul 2026
· source
+Platform support updatesshippedAdds support for new platforms like Kubernetes 1.20 and requires PostgreSQL 10.15.10 releases · first seen Feb 2021▸
Also counts toward: Self-hosted deployment
release
10 total
Codacy Guardrails MCP Server now runs on Windows environments via Windows Subsystem for Linux (WSL).
Cloud May 2025 · May 2025
· source
· release history
Adds platform support for Kubernetes versions 1.24.* and 1.25.* in the self-hosted deployment.
v12.0.0 · Jul 2023
· source
· release history
+Go linting with GolangCI-LintshippedRuns GolangCI-Lint against Go code, either directly on Codacy's servers or by ingesting results uploaded from a local or CI environment.9 releases · first seen Mar 2019▸
release
9 total
GolangCI-Lint is not enabled by default on existing repositories — must be enabled manually in repository settings to avoid a large volume of new issues appearing unexpectedly.
Adding GolangCI-Lint as new supported tool January, 2026 · seen Aug 2026
· source
· release history
Adds GolangCI-Lint as a supported client-side tool for Go projects: run it locally or in CI, then upload results to Codacy for analysis and reporting.
Adding GolangCI-Lint as new supported tool January, 2026 · seen Aug 2026
· source
· release history
Adds GolangCI-Lint as a supported code analysis tool, enabling automated linting for Go projects within Codacy.
Adding GolangCI-Lint as new supported tool January, 2026 · seen Jul 2026
· source
· release history
Codacy now supports GolangCI-Lint results upload. The tool is client-side and disabled by default on existing repos.
Adding GolangCI-Lint as new supported tool – January 2026 · Jan 2026
· source
· release history
Adds a new GolangCI-Lint wrapper that integrates over 100 linters to improve Go code quality checks
Cloud January 2026 · Jan 2026
· source
· release history
Adds GolangCI-Lint 2.7.2 as a new supported tool
Cloud December 2025 · Dec 2025
· source
· release history
+AI-generated fix suggestionsshippedProvides AI-generated context-aware comments and fix suggestions for issues, posted directly into the Git provider.6 releases · 1 other source · first seen Jul 2023▸
release
Allows manual triggering of the Draft PR AI Review via a button on the summary, as it no longer runs automatically for draft PRs.
Cloud May 2026 · May 2026
· source
· release history
Adds context-aware feedback loops for the AI Reviewer on GitHub PRs
Cloud April 2026 · Apr 2026
· source
· release history
AI-generated test coverage suggestions with ready-to-use prompts for coding agents
Cloud March 2026 · Mar 2026
· source
· release history
New Run review button on the Pull Request Summary page for manual AI review triggers
Cloud March 2026 · Mar 2026
· source
· release history
review.md file support to customize AI reviewer output and coding conventions
Cloud March 2026 · Mar 2026
· source
· release history
Adds AI-generated context-aware comments and fix suggestions posted directly into the Git provider for Codacy issues.
Cloud July 2023 · Jul 2023
· source
· release history
example
Observe how AI feedback adapts to conversation history on GitHub PRs.$ View comments from the Codacy AI Reviewer bot in a GitHub Pull Request.
Cloud April 2026 · Apr 2026
· source
+PHP code-style analysis with PHP CS FixershippedRuns PHP CS Fixer to enforce PHP code-style rules, configurable through the Codacy UI or a config file in the repository.7 releases · first seen Jan 2022▸
Also counts toward: Scripting language support
release
7 total
Adds PHP CS Fixer as a new supported Codacy engine for PHP code-style analysis, configurable via the Codacy UI or your repository's own .php-cs-fixer.dist.php or .php-cs-fixer.php file (Codacy-selected patterns take precedence over the repo config file).
Adding PHP CS Fixer and support to Checkov configuration files July, 2026 · seen Aug 2026
· source
· release history
Adds PHP CS Fixer as a supported static analysis tool for PHP code style enforcement.
Adding PHP CS Fixer and support to Checkov configuration files July, 2026 · seen Jul 2026
· source
· release history
Adds the include_paths field to .codacy.yml to explicitly specify files or directories to include in the analysis
Cloud June 2024 · Jun 2024
· source
· release history
Added support for an alternative RuboCop configuration file for Codacy analysis, .rubocop-codacy.yml
Cloud May 2024 · May 2024
· source
· release history
Repositories list page displays a warning icon for repositories with warnings or errors
v7.0.0 · Apr 2022
· source
· release history
Sets default recommended values for all configurable Stylelint code patterns
v5.1.0 · Jan 2022
· source
· release history
+VS Code extensionshippedOffers a Visual Studio Code extension to review and manage pull request issues directly within the editor.5 releases · 1 other source · first seen Sep 2023▸
release
Introduces a dedicated VS Code Setup Section in the extension for streamlined onboarding
Cloud January 2026 · Jan 2026
· source
· release history
Adds a guided walkthrough step-by-step guide within the VS Code extension setup process
Cloud January 2026 · Jan 2026
· source
· release history
Fork and Pull workflows are supported in the Codacy VS Code extension
Cloud April 2025 · Apr 2025
· source
· release history
Codacy Guardrails is available in the VS Code Copilot Agent extension
Cloud April 2025 · Apr 2025
· source
· release history
Adds Codacy Visual Studio Code extension to review and manage pull request issues directly within the editor
Cloud September 2023 · Sep 2023
· source
· release history
example
Use the new dedicated section to configure the Codacy VS Code extension quickly during onboarding.$ In the VS Code extension, navigate to the 'VS Code Setup Section' to begin initial configuration.
Cloud January 2026 · Jan 2026
· source
+Coverage engine updatesshippedEnhances the coverage analysis engine with faster processing, new status report types, and improved precision for coverage metrics.6 releases · first seen Apr 2023▸
release
GitHub coverage summaries and the Codacy app UI diff tabs now pull data from the new Coverage engine.
Cloud December 2023 · Dec 2023
· source
· release history
You now get two additional coverage status reports from the new, faster Coverage engine on your Git provider, showing whether your diff coverage and coverage variation are up to standard or not as configured on the quality gate rules for your repository
Cloud November 2023 · Nov 2023
· source
· release history
Adds two new coverage status reports on GitHub (diff coverage and coverage variation) using the new faster Coverage engine
Cloud October 2023 · Oct 2023
· source
· release history
Enables GitHub coverage status report generation using a new, faster Coverage engine
Cloud September 2023 · Sep 2023
· source
· release history
Updates Codacy Coverage Reporter to version 13.13.1.
v11.0.0 · Apr 2023
· source
· release history
Drops support for Kubernetes versions 1.19, 1.20, and 1.21.
v11.0.0 · Apr 2023
· source
· release history
+Organization-wide coding standardsshippedAllows applying a single coding standard to an organization or group of repositories and automating assignment to new repos.5 releases · first seen Nov 2021▸
release
Adds organization-level default settings configuration for new repository Git provider integrations.
Cloud May 2023 · May 2023
· source
· release history
Supports up to 10 coding standards per organization to optimize and apply quality settings to multiple repositories
Cloud March 2023 · Mar 2023
· source
· release history
Adds the ability to assign a coding standard automatically to new repositories
v5.1.0 · Jan 2022
· source
· release history
Assigns a coding standard automatically to new repositories
Cloud December 2021 · Dec 2021
· source
· release history
New UI feature to use an organization coding standard to apply rules across a group of repositories
Cloud November 2021 · Nov 2021
· source
· release history
+Oxlint Support for JavaScript and TypeScriptshippedIntegrates the Oxlint engine for JavaScript and TypeScript analysis, supporting file-based configuration and standard rule categories.3 releases · 1 other source · first seen Sep 2026▸
Also counts toward: JavaScript scripting support, Scripting language support
release
POST /search/analysis/organizations/{provider}/{remoteOrganizationName}/repositories: response schema changed
3.1.0 · Sep 2026
· source
· release history
Supports repository-level configuration via .oxlintrc.json, .oxlintrc.jsonc, oxlint.config.json, or oxlint.config.jsonc files, which Codacy will detect and apply automatically during analysis.
Adding Oxlint as new supported tool September, 2026 · seen Sep 2026
· source
· release history
Adds Oxlint as a supported Codacy engine for JavaScript and TypeScript, covering correctness, style, and best-practice rule categories including ESLint core rules, typescript-eslint, React ecosystem (react, react-hooks, react-refresh, react-perf), @next/eslint-plugin-next, eslint-plugin-unicorn, testing…
Adding Oxlint as new supported tool September, 2026 · seen Sep 2026
· source
· release history
example
Enable Oxlint analysis in repository settings to start scanning JS/TS code immediately.$ Go to your repository settings in Codacy. Enable Oxlint under the list of supported tools.
Adding Oxlint as new supported tool – September 2026 · Sep 2026
· source
+Dependency Security PostureshippedProvides visibility and assessment of open-source component security through OpenSSF Scorecard integration and Malicious Package Detection.4 releases · first seen Aug 2025▸
Also counts toward: Scheduled jobs
release
Improves dependency chain visibility in the UI to clarify how vulnerable dependencies are introduced
Cloud June 2026 · Jun 2026
· source
· release history
Adds Malicious Package Detection to automatically flag packages identified by OSSF in Pull Requests and nightly scans for clients with SCA enabled.
Cloud November 2025 · Nov 2025
· source
· release history
Adds OpenSSF Scorecard report view directly from dependency details to assess open-source component security posture.
Cloud September 2025 · Sep 2025
· source
· release history
Shows license information for every dependency and repository directly in the Security & Risk Management dashboard’s Dependencies tab
Cloud August 2025 · Aug 2025
· source
· release history
+File-based ShellCheck configurationshippedUses a ShellCheck configuration file in the repository root to control shell-script analysis on a per-repository basis.3 releases · 1 other source▸
release
Adds support for a .shellcheckrc configuration file in the repository root to drive ShellCheck analysis, replacing UI-only configuration.
Support for Shellcheck configuration file - July, 2026 · seen Aug 2026
· source
· release history
Adds a new toggle — "Use Shellcheck configuration file found in the repository" — under Repository > Code Patterns > Shellcheck to activate file-based config.
Support for Shellcheck configuration file - July, 2026 · seen Aug 2026
· source
· release history
Supports ShellCheck configuration files, allowing per-repository ShellCheck rule customization without modifying Codacy settings.
Support for Shellcheck configuration file - July, 2026 · seen Jul 2026
· source
· release history
example
Commit a .shellcheckrc to your repo and enable file-based analysis so ShellCheck rules are version-controlled alongside your code.$ Repository > Code Patterns > Shellcheck > enable "Use Shellcheck configuration file found in the repository"
Support for Shellcheck configuration file - July, 2026 · seen Aug 2026
· source
+C# Unity framework analysisshippedsuggestedAnalyzes C# projects using the Unity framework to detect error-prone patterns and performance issues via Roslyn Analyzers.3 releases · first seen Nov 2022▸
Suggested capability: Static application security testing. This is our guess, not confirmed.
release
Adds PR Reviewer for contextual GitHub Pull Request reviews using security, duplication, complexity, and coverage metrics
Cloud December 2025 · Dec 2025
· source
· release history
Codacy now supports the client-side tool Unity Roslyn Analyzers for reporting error-prone and performance issues on C# projects that use the Unity framework.
v10.0.0 · Feb 2023
· source
· release history
Adds support for the Unity Roslyn Analyzers tool to detect error-prone and performance issues on C# projects using the Unity framework
Cloud November 2022 · Nov 2022
· source
· release history
+Markdown lintingshippedProvides suggested fixes for Markdown issues using markdownlint.3 releases · first seen Jul 2021▸
release
Adds support for additional Markdownlint configuration files.
Cloud October 2025 · Oct 2025
· source
· release history
Adds support for the remarkjs/remark-gfm plugin to enable GitHub Flavored Markdown linting via remark-lint
Cloud November 2022 · Nov 2022
· source
· release history
Adds markdownlint to provide suggested fixes for Markdown issues.
v4.1.0 · Jul 2021
· source
· release history
+Cloud CLI Pull Request ManagementshippedExtends the Cloud CLI with commands to retrieve and filter pull requests, synced with the web UI's search and branch-scope capabilities.2 releases · first seen Jul 2026▸
Also counts toward: Command-line interface
release
New pull-requests list subcommand in the Codacy Cloud CLI to retrieve pull requests backed by new search and branch-scope filter bar on the web UI.
Cloud August 2026 · Aug 2026
· source
· release history
Pull Requests page filter bar lets users search PRs by title and toggle between viewing all target branches or only the current branch.
Cloud July 2026 · Jul 2026
· source
· release history
+Directory-Level Analysis ScopingshippedAllows filtering and analyzing code metrics, issues, and coverage for specific directories or folders within a repository.1 release · 1 other source · first seen Jul 2026▸
release
Folder-Level Metrics now visible by browsing repositories by folder, showing issues, complexity, coverage, and duplication scoped to each directory.
Cloud July 2026 · Jul 2026
· source
· release history
example
Drill down into specific directories to analyze coverage and complexity without noise from other parts of the repo.$ In the Codacy web UI, navigate to your repository and click on a specific folder in the left-hand navigation panel to view its scoped quality metrics.
Cloud July 2026 · Jul 2026
· source
+False Positive Management WorkflowshippedEnables detection and workflow handling of false positives via direct Pull Request comments and dashboard flagging.2 releases · first seen Oct 2025▸
release
Adds a new workflow where False Positive detection leaves a comment directly on the Pull Request for immediate review.
Cloud November 2025 · Nov 2025
· source
· release history
Adds False Positive Detection capability to flag potentially false positive issues on the Business tier.
Cloud October 2025 · Oct 2025
· source
· release history
+Dart/Flutter static analysisshippedRuns Dart analyzer on Dart and Flutter projects to identify syntax errors, style violations, and potential issues.2 releases · first seen Jan 2022▸
release
Adds support for static code analysis of Dart/Flutter projects via dartanalyzer
v6.0.0 · Mar 2022
· source
· release history
Adds static code analysis support for Dart/Flutter projects using dartanalyzer.
Cloud January 2022 · Jan 2022
· source
· release history
+OpenAPI and AsyncAPI lintingshippedLints OpenAPI and AsyncAPI descriptions in YAML or JSON files using Spectral.2 releases · first seen Nov 2021▸
release
Adds support for linting OpenAPI and AsyncAPI descriptions in YAML or JSON using Spectral.
v5.0.0 · Dec 2021
· source
· release history
Spectral is now supported for linting OpenAPI and AsyncAPI descriptions in YAML or JSON files
Cloud November 2021 · Nov 2021
· source
· release history
+CSS and stylesheet linting with StylelintshippedRuns Stylelint on CSS and stylesheet files, including accessibility pattern rules whose IDs carry an `a11y_` prefix, configurable through coding standards and repository code-pattern settings.1 release · first seen Nov 2026▸
release
The 12 Stylelint accessibility pattern IDs are renamed with the a11y_ prefix (e.g. content-property-no-static-value becomes a11y_content-property-no-static-value); any coding standard, repository code-pattern config, or Codacy Analysis CLI setup that references the old IDs must be updated, and the renamed…
Stylelint accessibility patterns renamed – November 2026 · Nov 2026
· source
· release history
+Dependency Entrypoint VisibilityshippedSurfaces the specific entrypoint functions within a repository that are affected by vulnerable dependencies.1 release · first seen Jul 2026▸
Also counts toward: Command-line interface
release
Security dependency findings now surface affected entrypoint functions reachable from a vulnerable dependency, visible in the Findings card, CLI command output, and public API response fields.
Cloud July 2026 · Jul 2026
· source
· release history
+Guardrails Network Proxy SupportshippedAllows the Guardrails component to operate in restricted network environments by configuring an outbound proxy.1 release · first seen Jun 2026▸
release
Adds proxy configuration support to Guardrails for restricted network environments
Cloud June 2026 · Jun 2026
· source
· release history
+Environment File YAML LintingshippedTreats `.env` files as YAML language, enabling existing YAML analysis tools to scan environment configuration files.1 release · first seen May 2026▸
release
Supports .env, .env.production, .env.prod, and .env.staging files as YAML language so all YAML tools can scan them.
Cloud May 2026 · May 2026
· source
· release history
+Organization Overview DashboardshippedProvides a centralized dashboard for organizations to view aggregate metrics on code health, security grade, complexity, duplication, and coverage.1 release · first seen Feb 2026▸
release
Launched an Organization Overview Dashboard with metrics for code health, security grade, complexity, duplication, and coverage.
Cloud February 2026 · Feb 2026
· source
· release history
+Swift code analysisshippedRuns SwiftLint on Swift projects to enforce code style and identify potential issues.1 release · first seen Nov 2018▸
release
Added SwiftLint to Codacy for Swift code analysis.
Cloud November 2, 2018 · Nov 2018
· source
· release history
Lines in monospace are the tool's own words: help text
parsed from its source, or an endpoint from its API document. Under
release, a line is our summary of a dated release. Under
docs, it is quoted from the tool's own documentation or
website. Each links back to the source it came from.
Screenshots
From the release notes, newest first. Click one to see it full size.
Breaking-change disciplinehow rarely a release breaks users, and notice given
Maintenance riskquiet time against its own cadence, maintainers
Innovation & surfacenew capabilities, API and MCP surface
Five scores for Codacy, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Each score is 0–100 on a published rubric, derived from data this site already shows.
A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
Documentation quality — the release-notes rubric published on the analytics page, unchanged.
Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Codacy puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
these 12 patterns didn't check your code. Stylelint didn't recognize their names, so each one reported an issue saying the rule was unknown instead of a real finding. To fix this, the patterns now use the a11y_ prefix, which matches how Stylelint names them.
Stylelint accessibility patterns renamed – November 2026Source ↗
Nothing first seen in this window. That doesn't mean Codacy shipped nothing, only that we found no record of it.
Changes per month New Updated Retired
2026-11
1
How we count
Read from 1 of 122 release notes and docs updates we hold for Codacy. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through Codacy's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
Show
Coverage in all entries
122 entries
No entries match these filters.
November 20261
October 20262
September 20265
August 20268
July 20264
June 20261
May 20261
April 20261
March 20262
February 20261
January 20262
December 20251
November 20251
October 20251
September 20251
August 20251
July 20251
May 20251
April 20252
February 20251
January 20251
December 20241
November 20241
October 20241
September 20242
August 20241
July 20241
June 20242
May 20241
April 20241
March 20241
February 20241
January 20241
December 20231
November 20233
October 20231
September 20231
August 20231
July 20232
June 20231
May 20231
April 20232
March 20231
February 20232
January 20231
December 20222
November 20221
September 20222
August 20221
June 20222
May 20222
April 20222
March 20223
February 20221
January 20222
December 20212
November 20211
September 20212
August 20212
July 20211
May 20211
March 20212
February 20211
December 20202
November 20201
October 20201
August 20201
July 20201
May 20202
February 20201
November 20191
October 20191
September 20191
August 20191
June 20191
May 20191
March 20191
February 20191
January 20191
November 20182
October 20181
July 20181
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can
follow every release here.