# Veracode — Code Security & Quality (SAST/SCA)

Veracode by Veracode, Inc. holds a panel rating of 2.5/5 from 6 AI judges (category median 3/5), as of 2026-11-19. Provenance: provenance unknown; sovereignty: 1 of 6 dimensions proven.

- Vendor: Veracode, Inc. (https://www.veracode.com)
- Category: [Code Security & Quality (SAST/SCA)](https://whats-best.ai/software/code-security.md)
- Provenance (editorial classification): provenance unknown
- Canonical page: https://whats-best.ai/software/code-security/veracode
- Alternatives: https://whats-best.ai/software/code-security/veracode/alternatives ([markdown](https://whats-best.ai/software/code-security/veracode/alternatives.md))
- Data as of: 2026-11-21 · evaluated 2026-11-19 · oldest source captured 2026-11-17

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## At a glance

- Vendor: Veracode, Inc.
- Headquarters: Incorporated in the United States [S2]
- Data hosting: Not stated on the vendor’s pages as of 17 Nov 2026
- Free plan: Not stated on the vendor’s pages as of 17 Nov 2026

## The panel's verdict

Veracode's strongest showing is code analysis, where scores cluster at 7: the judges credit an engine that maps every data path where untrusted data reaches critical functions, control-flow modelling across hundreds of frameworks, a Pipeline Scan language list from.NET through COBOL to Kotlin, scans of applications up to 5GB of code, and a published false-positive rate under 1.1 percent. Dependencies and secrets follow at 6-7: the judges credit a malicious-package catalogue of unusual depth — typosquatting, YARA rules, OpenSSF determinations — but the lower scores point to missing evidence on SBOM export and secrets across git history. The weak end is sovereignty at 1-2: the contracting entity is Veracode, Inc., a Delaware corporation under Massachusetts law, and we found no public information on hosting locations, subprocessors or a data processing agreement, only region-specific account domains. Pricing transparency scores sit at 0-1. The remaining splits — developer workflow at 6-7, integration and administration and trust and compliance at 5-6 — turn on evidence the pages do not show: pre-commit checks and scan times, single sign-on, code retention and AI-training questions.

**Speaks for it:**
- Static analysis engine maps every data path where untrusted data reaches critical functions, with control-flow modelling across hundreds of frameworks
- Pipeline Scan lists over twenty languages from COBOL to Kotlin, for applications up to 5GB of code, with a published false-positive rate under 1.1 percent
- Malicious-package detection is documented in unusual depth — typosquatting, YARA rules, OpenSSF determinations — fed by a proprietary threat research feed
- Reachability analysis prioritizes vulnerabilities that are actually exploitable, and licence rules flag GPL and AGPL source-distribution obligations
- FedRAMP Moderate Authority to Operate over an environment implementing over 300 NIST SP 800-53 controls, with audit support for SOC 2 Type II

**Held against it:**
- Sovereignty scores sit at 1-2: the vendor is a Delaware corporation under Massachusetts law, and we found no public information on hosting locations, subprocessors or a data processing agreement
- We found no public information on SBOM export, end-of-life components, or secret scanning across full git history
- We found no public information on single sign-on, SCIM provisioning, audit logs, or export of findings in a standard format
- We found no public information on code retention periods, encryption, or whether customer code trains AI models and how to opt out
- The terms allow changes at any time with or without notice, termination at will, and cap liability at the fees paid

**Best for:**
- You need deep static analysis across many languages and frameworks, backed by a documented triage and mitigation-approval workflow
- Your priority is supply-chain defence — malicious-package detection, reachability and licence compliance — rather than code-quality metrics
- You build audit files against FedRAMP, ISO 27001, PCI DSS, HIPAA, GDPR or DORA and value an independently assessed environment
- Your teams work in GitHub, GitLab, Bitbucket or Azure DevOps and want scans triggered on push and pull requests

**Avoid if:**
- You need a European contracting or processing chain for source code — the vendor is a Delaware corporation under Massachusetts law, and we found no public information on hosting locations or subprocessors
- You need secret scanning across full git history or SBOM export for compliance filings — the documented secret scanning covers containers and infrastructure as code
- Your administration depends on single sign-on, SCIM or a self-hosted edition — we found no public information on these, so verify with the vendor before shortlisting
- You need contractual stability on standard terms — the published terms allow unilateral changes, termination at will, and cap liability at the fees paid

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v1). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The Lead Developer | The Application Security Engineer | The Engineering Manager | The Platform Engineer | The Product Security Officer | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| Code analysis (SAST & code quality) | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Dependencies (SCA), licences & secrets | 3/5 | 3/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Developer workflow, quality gates & fixes | 3/5 | 3/5 | 3.5/5 | 3/5 | 3.5/5 | 3/5 |
| Platforms, deployment & administration | 2.5/5 | 2.5/5 | 3/5 | 2.5/5 | 3/5 | 2.5/5 |
| Source-code handling, security & compliance | 2.5/5 | 3/5 | 2.5/5 | 2.5/5 | 2.5/5 | 2.5/5 |
| European sovereignty | 0.5/5 | 0.5/5 | 0.5/5 | 1/5 | 0.5/5 | 0.5/5 |
| Pricing transparency | n/r | n/r | n/r | n/r | n/r | n/r |
| **Weighted verdict** | **3/5** | **3/5** | **3/5** | **2.5/5** | **2.5/5** | **2.5/5** |

### The judges

- **The Lead Developer** (v1.0): Lead developer at a web agency in Cologne with fourteen developers building Laravel, TypeScript and React Native projects for clients on GitHub and GitLab. Wants every merge request checked for bugs, injection flaws and vulnerable packages before review, comments in the merge request rather than a separate dashboard, the same rules in VS Code and PhpStorm, few false positives, and a bill that does not jump each time a freelancer pushes a commit.
- **The Application Security Engineer** (v1.0): Application security engineer at a payments company in Frankfurt with 120 developers, two of them security champions per team, under PCI DSS and DORA. Wants taint analysis that follows user input across files, reachability so the backlog holds only vulnerable code that is actually called, secrets checked for validity across the whole git history, push protection, custom rules for in-house frameworks, and reports an auditor accepts.
- **The Engineering Manager** (v1.0): Head of engineering at a B2B SaaS company in Munich with six teams and a ten-year-old Java and Kotlin codebase. Wants technical debt and code health shown per team and hotspot, a quality gate on new code that every team keeps, trends to show the board that the rewrite budget worked, findings routed to Jira, single sign-on and roles per team, and to know what the AI-written code the teams now merge does to the numbers.
- **The Platform Engineer** (v1.0): Platform engineer at an insurer in Hanover who runs a self-managed GitLab and Jenkins for 300 developers inside the company network; source code may not leave it. Wants a self-hosted edition or a scanner that runs in the pipeline and sends only results, SAML and SCIM from Entra ID, an API to roll scan settings out to 900 repositories, SARIF output, audit logs, and upgrades that do not break the pipelines.
- **The Product Security Officer** (v1.0): Product security officer at a machine builder in Baden-Württemberg whose controllers and service apps fall under the EU Cyber Resilience Act. Needs an SBOM per release in a standard format, every component's vulnerabilities and licences tracked after shipping, evidence of secure development an auditor can file, and to know where the firmware source code is stored, for how long, and whether any AI model is trained on it.
- **The Skeptic** (v1.0): Has seen "zero false positives" bury a team under four thousand findings on day one, a "free for open source" plan that counted every bot as a contributor, and an "AI autofix" that shipped the repository to a model in the US. Asks how contributors are counted, which languages get real data-flow analysis rather than regular expressions, what happens to the code after a scan, whether the findings export when the contract ends — and what the second year costs.

## European sovereignty — proven facts

Built only from facts on the vendor's own pages; a dimension we could not prove is left open, never scored as zero. Headline: 1 of 6 dimensions proven.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Incorporated in US | 0/2 | [S2] |
| Hosting location | Not determined | — | — |
| Hosting options | Not determined | — | — |
| Open source | Not determined | — | — |
| Data processing agreement | Not determined | — | — |
| Transfer impact assessment | Not determined | — | — |

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Compliance**
- Fedramp moderate ato: yes [S11]
- Nist 800 53 controls: yes · 300 [S11]
- Trust center: yes [S1]

**Hosting**
- Region domains: region-specific domains must be allowlisted; one-way communication on port 443 to REST API domain [S9]

**Integrations**
- Azure devops extension: Static Analysis scanning in pipelines, import findings as work items [S9]
- Azure devops workflow: Repository Scanning with Pipeline Scan (SAST), SCA Agent-based Scan, Container Security scans [S9]
- Bitbucket sca agent: SCA Agent-based Scan in workflows or locally; Veracode-authored [S9]
- Cli integration: Veracode CLI · yes [S9]
- Developer tools: yes [S1]
- Github fix action: automatically resolve SAST flaws with Veracode Fix [S9]
- Github workflow: Repository Scanning with Pipeline Scan (SAST), SCA Agent-based Scan, Container Security scans [S9]
- Gitlab workflow: Repository Scanning with Pipeline Scan (SAST), SCA Agent-based Scan, Container Security scans [S9]
- Integration type: Veracode-authored [S9]
- Languages frameworks: yes [S11]
- Rest API ignore: SAST and DAST flaws · SCA vulnerabilities from SCA Upload and Scan [S7]
- Scan locations: SAST available via IDEs, CI/CD, CLI, Path Analysis [S3]
- Surface: yes [S2]
- Vrm ingest: GitHub · GitLab · Veracode Risk Manager · yes [S9]

**Legal**
- Copyright: 2026 [S2]
- Dmca contact: legal@veracode.com [S2]
- Eligibility age: 18 · 13 [S2]
- Entity: Delaware · Veracode, Inc. · 65 Blue Sky Drive, Burlington, Massachusetts 01803 USA [S2]
- Governing law: Commonwealth of Massachusetts [S2]
- Indemnification: yes [S2]
- Last updated: 2025-06-11 [S2]
- Liability cap: amount paid by user for the applicable services [S2]
- License terms: limited, revocable, non-exclusive, non-transferable, non-sublicensable, personal [S2]
- Notice address: Veracode, Inc., Attn: Legal Department, 65 Blue Sky Drive, Burlington, MA 01803 USA [S2]
- Ownership: Veracode [S1]
- Privacy statement: yes [S2]
- Separate terms: yes [S2]
- Termination: yes [S2]
- Unilateral changes: yes [S2]
- Venue: courts in Middlesex County [S2]

**Product**
- AI code remediation: yes [S11]
- AI generated code: yes [S1]
- API role purpose: API roles are for non-human users such as systems or services [S10]
- Applications scanned: 1500000 [S1]
- Audit ready evidence: Produces audit-ready evidence across applications and software supply chain [S11]
- Binary hybrid scanning: source, binary and hybrid scanning [S3]
- Capabilities: ASPM, AI Code Remediation, SAST, DAST, PTaaS, Container, SCA, VPF, Security Labs, eLearning [S1]
- Cm0001 ip detection: IP detection · CM0001 · Critical [S6]
- Cm0003 landing binary: Landing binary · CM0003 · Critical [S6]
- Cm0007 npm hooks: NPM hooks · CM0007 · Critical [S6]
- Cm0011 hostname detection: Hostname detection · CM0011 · Critical [S6]
- Cm0014 masquerade: Masquerade · CM0014 · Critical [S6]
- Cm0024 remote executable: Remote executable · CM0024 · Critical [S6]
- Cm0037 malware bazaar check: Malware bazaar check · CM0037 · Critical [S6]
- Cm0038 triaged malware: Triaged malware (through threat feed) · CM0038 · Critical [S6]
- Cm0039 depends on malware: Depends on malware · CM0039 · Critical [S6]
- Cm0045 npm security holding: npm security holding package · CM0045 · Critical [S6]
- Cm1002 ossf mal: Malware (via OSSF MAL) · CM1002 · Critical [S6]
- Code to cloud scanning: SAST · DAST · SCA · IaC · container · yes [S12]
- Container iac: Scans vulnerabilities, misconfigurations and embedded secrets in containers and Infrastructure as Code [S12]
- Custom role assignment: Custom roles are assigned to users the same way as standard user roles [S10]
- Custom roles: yes · Identity API [S10]
- Dast: Identifies and addresses runtime vulnerabilities in web apps and APIs through simulated attacks [S12]
- Dast runtime validation: Runtime validation via simulated attacks against PCI DSS and HIPAA mandates [S11]
- Direct source scanning: scan raw source code without compilation [S3]
- Dora support: yes [S11]
- Easm: yes [S11]
- False positive rate: 1.1 [S1]
- Fix AI remediation: AI-powered remediation automates security flaw fixes by generating proprietary reference patches [S12]
- Flaws fixed: 148000000 [S1]
- Forrester recognition: yes · 9 [S3]
- Framework support: framework support for hundreds of frameworks [S3]
- HIPAA GDPR alignment: yes [S11]
- Hm0002 eval blob: Eval blob · HM0002 · High [S6]
- Hm0008 typosquatting: Typosquatting · HM0008 · High [S6]
- Hm0015 encrypted binaries: Encrypted binaries · HM0015 · High [S6]
- Hm0023 strange python imports: Strange Python imports · HM0023 · High [S6]
- Hm0025 env var enumeration: Environment variable enumeration · HM0025 · High [S6]
- Hm0029 obfuscated python: Obfuscated Python · HM0029 · High [S6]
- Hm0032 execute remote URL: Execute on remote URL · HM0032 · High [S6]
- Hm0033 sensitive data enumeration: Sensitive data enumeration · HM0033 · High [S6]
- Hm0036 webhook exfil: Webhook exfil · HM0036 · High [S6]
- Hm0099 js obfuscation: Basic JavaScript obfuscation · HM0099 · High [S6]
- Ignore findings purpose: Ignoring findings mitigates findings you won't resolve [S7]
- Ignore reasons: no manual fix or suggested code patch from Veracode Fix · finding not relevant, potential false positive, or risk accepted [S7]
- Il0022 license mismatch: License mismatch · IL0022 · Minimum · Package has a license mismatch between metadata and files [S5]
- Il0050 license: License · IL0050 · Minimum · License requires source code distribution · AGPL · GPL [S5]
- Im0006 npm donation hooks: NPM hooks (donation hooks) · IM0006 · Minimum [S6]
- Im0007 npm runs after install: NPM hooks (runs software after install) · IM0007 · Minimum [S6]
- Im0009 unicode detection: Unicode detection · IM0009 · Minimum [S6]
- Im0013 dynamic code: Dynamic code · IM0013 · Minimum [S6]
- Im0017 compiled binaries: Compiled binaries · IM0017 · Minimum [S6]
- Im0019 eval calls: Eval function calls · IM0019 · Minimum [S6]
- Im0020 odd dependencies: Odd dependencies · IM0020 · Minimum [S6]
- Im0040 base64 decode: Decodes hardcoded base64 strings · IM0040 · Minimum [S6]
- Im0041 high entropy blobs: High entropy blobs · IM0041 · Minimum [S6]
- Im0042 nuget install scripts: Nuget install scripts · IM0042 · Minimum [S6]
- Im0043 cargo build file: Cargo build file · IM0043 · Minimum [S6]
- Im0044 rubygems install hooks: Rubygems install hooks · IM0044 · Minimum [S6]
- Im0047 python build hook: Python build hook · IM0047 · Minimum [S6]
- Im0051 post request behavior: POST request behavior · IM0051 · Minimum [S6]
- ISO 27001 mapping: Automated assessments with detailed mapping to ISO 27001/27002 controls [S11]
- L0005 noncommercial risk: License · L0005 · Situation-dependent severity · Non-commercial use risk detected · Creative Commons Attribution-NonCommercial (CC BY-NC) [S5]
- Last updated: 2026-07-29 [S6]
- License risk issues purpose: License risk issues identify packages with licensing concerns that may create compliance obligations. [S5]
- M0004 landing binary: Landing binary · M0004 · Situation-dependent [S6]
- M0018 dependency confusion: Dependency confusion · M0018 · Situation-dependent [S6]
- M0028 suspicious URL references: Suspicious URL references · M0028 · Situation-dependent [S6]
- M0031 python setup commands: Suspicious Python setup commands · M0031 · Situation-dependent [S6]
- M0048 compiled python files: Compiled Python files · M0048 · Situation-dependent [S6]
- M0048 yara rule: YARA rule · M0048 · Situation-dependent [S6]
- Malicious code issues definition: Malicious code risk issues identify packages that contain suspicious or harmful code [S6]
- Malicious package defense: yes [S11]
- Max code size: 5 [S3]
- Mitigation approval role: Mitigation Approver · accept · reject [S8]
- Mitigation auto propagation: yes · all matched flaws within the application · copies of the flaw in other sandboxes · latest policy scan [S8]
- Mitigation effect on score and policy: yes [S8]
- Mitigation platform actions: Triage Flaws page · APIs · Static Analysis · Dynamic Analysis [S7]
- Mitigation workflow steps: review flaws with team · comment and track comments · propose mitigating factors · accept or reject mitigations · view mitigated flaws in reports [S8]
- Mm0012 native code: Native code · MM0012 · Medium [S6]
- Mm0024 remote executable reference: Remote executable (references) · MM0024 · Medium [S6]
- Modules: AppSec Analytics & Insights · AppSec Compliance · Cloud Native Architecture · Integrations · Languages and Frameworks · Policy and Reporting · Remediation Guidance · ASPM · AI Code Remediation · SAST · DAST · PTaaS · Container · SCA · VPF… [S2]
- Package firewall: Proactively stops vulnerabilities, malware, and policy violations before they reach development pipelines [S12]
- Path analysis: High-Fidelity Methodology path analysis [S3]
- Pipeline scan languages: .NET, Android, Apex, Apple Platforms, C, C++, COBOL, ColdFusion, Cordova, Groovy, GoLang, IONIC, Java, JavaScript and TypeScript, Kotlin, PhoneGap, PHP, Python, React Native, Ruby on Rails, Scala, Titanium, Xamarin [S4]
- Platform modules: AppSec Analytics & Insights, AppSec Compliance, Cloud Native Architecture, Integrations, Languages and Frameworks, Policy and Reporting, Remediation Guidance [S1]
- Policy driven sdlc: Policy-driven controls across the SDLC [S11]
- Positioning: Application Risk Management Platform across SDLC with automated flaw fixes and governance [S1]
- Predefined roles: yes [S10]
- Reachability analysis: yes [S11]
- Remediation: yes [S1]
- Risk manager: Application Security Posture Management that prioritizes vulnerabilities, pinpoints owner and root cause, and provides next best action for remediation [S12]
- Role types: yes [S10]
- Role view own roles: Users can view their assigned roles via Your Account in the top navigation menu [S10]
- Sast: 60 · yes [S12]
- Sast history: Pioneering SAST for over 20 years with next-generation Adaptable SAST Scanning Service [S3]

**Support**
- Developer resources: Documentation · Developer Community · Developers Training · Contact Support · Technical Support · AppSec Knowledgebase · Vulnerability Database · API Reference [S2]
- Resources: Documentation, Developer Community, Developers Training, Contact Support, Technical Support, AppSec Knowledgebase, Vulnerability Database, API Reference [S1]
- Resources: Documentation · Developer Community · Developers Training · Contact Support · Technical Support · AppSec Knowledgebase · Vulnerability Database · API Reference [S11]

26 more facts on the canonical page: https://whats-best.ai/software/code-security/veracode

## Questions

### Is Veracode European?

Not determined: the vendor’s pages as captured do not say where Veracode is based. Its vendor, Veracode, Inc., is incorporated in the United States, per [the vendor’s page captured 17 Nov 2026](https://whats-best.ai/evidence/26040).

### Where does Veracode store data?

Not stated on the vendor’s pages as of 17 Nov 2026.

### Does Veracode have a free plan?

Not stated on the vendor’s pages as of 17 Nov 2026.

### What are the best alternatives to Veracode?

As of 19 Nov 2026, the panel rates [SonarQube (3.5/5)](https://whats-best.ai/software/code-security/sonarqube), [Aikido Security (3.5/5)](https://whats-best.ai/software/code-security/aikido) and [Endor Labs (3.5/5)](https://whats-best.ai/software/code-security/endor-labs) highest among the other 18 Code Security & Quality (SAST/SCA) products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is [SonarQube](https://whats-best.ai/software/code-security/sonarqube) (EU origin, foreign-owned, Switzerland). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [Veracode alternatives](https://whats-best.ai/software/code-security/veracode/alternatives).

## What this page leaves out

- We found no public information on pricing on the pages we read (veracode.com, veracode.com/terms-of-use, veracode.com/security/static-code-analysis, docs.veracode.com/r/Pipeline_Scan_Supported_Languages, docs.veracode.com/r/License_risk_issues, docs.veracode.com/r/Malicious_code_risk_issues and 6 more). If the vendor publishes it somewhere else, send us the page.
- 11 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.

## Sources

- [S1] Vendor page: https://www.veracode.com (checked 2026-11-17)
- [S2] Terms of service — found from the homepage: https://www.veracode.com/terms-of-use/ (checked 2026-11-17)
- [S3] Code analysis (SAST & code quality) — found from sitemap: https://www.veracode.com/security/static-code-analysis/ (checked 2026-11-17)
- [S4] Code analysis (SAST & code quality) — found from sitemap: https://docs.veracode.com/r/Pipeline_Scan_Supported_Languages (checked 2026-11-17)
- [S5] Dependencies (SCA), licences & secrets — found from sitemap: https://docs.veracode.com/r/License_risk_issues (checked 2026-11-17)
- [S6] Dependencies (SCA), licences & secrets — found from sitemap: https://docs.veracode.com/r/Malicious_code_risk_issues (checked 2026-11-17)
- [S7] Developer workflow, quality gates & fixes — found from sitemap: https://docs.veracode.com/r/Ignore_findings (checked 2026-11-17)
- [S8] Developer workflow, quality gates & fixes — found from sitemap: https://docs.veracode.com/r/Mitigate_flaws_using_the_Triage_Flaws_page (checked 2026-11-17)
- [S9] Platforms, deployment & administration — found from sitemap: https://docs.veracode.com/r/SCM_integrations (checked 2026-11-17)
- [S10] Platforms, deployment & administration — found from sitemap: https://docs.veracode.com/r/User_roles_and_permissions (checked 2026-11-17)
- [S11] Source-code handling, security & compliance — found from sitemap: https://www.veracode.com/application-security-compliance/ (checked 2026-11-17)
- [S12] Source-code handling, security & compliance — found from sitemap: https://www.veracode.com/security/secure-compliance/ (checked 2026-11-17)

---

Cite as: whats-best.ai, "Veracode — Code Security & Quality (SAST/SCA)", AI panel analysis, as of 2026-11-21. https://whats-best.ai/software/code-security/veracode

Corrections: https://whats-best.ai/correct/1940?target=page
