Source
Certification page (SOC 2) — Codacy
Checked for Codacy on 6 Nov 2026
- Page
- https://www.codacy.com/soc-2
- Checked
- 6 Nov 2026, 04:58 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:573fc7c261097ae1acecc9c95efbd47f60c1f4c721086014ed54c0a5a6162465
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
SOC 2 type2 Report an error
“Codacy is SOC 2 Type II certified”
-
SOC 2 cc8 1 change management Report an error
“Codacy's quality gate blocks the merge until checks pass and a reviewer approves. The check result and the approval are recorded against the pull request, including changes written by AI coding agents.”
-
SOC 2 cc7 1 vulnerability detection Report an error
“Codacy records severity-ranked SAST and dependency findings on every commit, with the date each was identified and resolved. Periodic penetration testing covers what code scanning cannot reach.”
-
SOC 2 cc6 1 credential protection Report an error
“Codacy flags hardcoded secrets, keys and tokens in the pull request, before they reach the main branch. Each detection is recorded with the commit and the resolution.”
-
SOC 2 cc6 6 external threats Report an error
“Penetration testing exercises the running application against external attack. SAST identifies injection, access-control and cryptographic flaws in code before release.”
-
SOC 2 cc6 8 malicious software Report an error
“Codacy inventories open-source dependencies and versions, and flags packages with known vulnerabilities before they are merged.”
-
SOC 2 cc4 1 monitoring Report an error
“One dashboard shows security and quality status across every repository, filterable by severity, age and status, exportable for an auditor. Pentest reports provide the periodic evaluation.”
-
Merge gates Report an error
“Set the checks a pull request has to pass before it can merge. Each gate produces a timestamped record of what was tested, what the outcome was, and who approved the change. When an auditor samples pull requests, you export those records.”
-
AI reviewer Report an error
“Code review on every pull request, with fix suggestions and PR summaries.”
-
Evidence reporting Report an error
“Security and quality status across your Git organization in a single view. Filter by severity, age and status, and export the result.”
-
Sast Report an error
“Injection flaws, cryptographic misuse, access-control gaps and other high-risk classes, identified before merge.”
-
Dependency scanning Report an error
“Which packages and versions you depend on, and which carry known vulnerabilities.”
-
Finding age status Report an error
“Each finding shows when it was identified and whether it has been resolved.”
-
Enforced coding standards Report an error
“Configure a rule set once. It is applied at every commit across every repository.”
-
Coverage gates Report an error
“Set a coverage threshold and enforce it as a merge condition.”
-
Pipeline Report an error
“Works with your pipeline Major agents, IDEs and Git providers. Issues sync to Jira, alerts to Slack.”
-
Merge blocking depends on provider Report an error
“Yes, when Codacy status checks are configured as required checks in your Git provider. Your branch protection settings determine whether a failing check prevents a merge.”
-
SOC 2 scope limitation Report an error
“Codacy focuses on code quality and application security. Use it within your wider SOC 2 program, alongside your policies, operational controls, and audit process.”
-
Setup speed Report an error
“Connect your Git organisation in two clicks. First evidence report the same day.”
-
GDPR Report an error
“GDPR Compliant”
-
Customer scale Report an error
“Trusted by 15,000+ organizations and 200,000+ developers worldwide”
-
AI inventory guardrails Report an error
“AI Inventory AI Guardrails AI Risk Hub”
1 fact read from this page is not shown because it could not be confirmed on the page as captured.
Scores citing this record
- The Application Security Engineer Dependencies (SCA), licences & secrets
- The Application Security Engineer Source-code handling, security & compliance
- The Application Security Engineer European sovereignty
- The Engineering Manager Source-code handling, security & compliance
- The Lead Developer Dependencies (SCA), licences & secrets
- The Lead Developer Source-code handling, security & compliance
- The Platform Engineer Developer workflow, quality gates & fixes
- The Platform Engineer Source-code handling, security & compliance
- The Product Security Officer Dependencies (SCA), licences & secrets
- The Product Security Officer Developer workflow, quality gates & fixes
- The Product Security Officer Source-code handling, security & compliance
- The Product Security Officer European sovereignty
- The Skeptic Source-code handling, security & compliance