# Mend.io — Code Security & Quality (SAST/SCA)

Mend.io by Mend.io (formerly WhiteSource) holds a panel rating of 3/5 from 6 AI judges (category median 3/5), as of 2026-11-19. Provenance: provenance unknown; sovereignty: 2 of 6 dimensions proven.

- Vendor: Mend.io (formerly WhiteSource) (https://www.mend.io)
- 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/mendio
- Alternatives: https://whats-best.ai/software/code-security/mendio/alternatives ([markdown](https://whats-best.ai/software/code-security/mendio/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: Mend.io (formerly WhiteSource)
- Headquarters: Incorporated in Israel [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

Mend.io is an application-security platform from White Source Ltd. of Givatayim, Israel, with a US subsidiary, covering SAST, SCA, Renovate dependency updates and an LLM-based triage of SAST findings. The bench scores it highest on trust and compliance, 7 from minimum to maximum: judges point to ISO 27001, 27017 and 27701 controls reviewed externally every year, a Schellman-audited SOC 2 Type II report available on request, and findings mapped to PCI DSS, OWASP and the EU Cyber Resilience Act. Code analysis follows at 6-7 on a published CWE table with per-language coverage and findings consolidated by taint sink. The weakest counted area is sovereignty, 2-4: the contracting entity sits in Israel, personal data may be processed in the US, Israel, the UK and other jurisdictions, and the self-hosted option covers only the repository integration, not the platform. Technical scores cluster between 5 and 7 with no flagged disagreements. A pricing page exists; no figures are published.

**Speaks for it:**
- Published CWE rule table with per-language coverage mapped to OWASP Top 10, CAPEC, PCI DSS and SANS TOP 25
- ISO 27001, 27017 and 27701 controls reviewed externally every year, plus a Schellman-audited SOC 2 Type II report available on request
- Developers are notified only when a pull request introduces new findings, and automation workflows can fail builds on policy violations
- Source snippets reach Mend.io's AI model only under a signed AI addendum, and disabling the option stops all code sharing
- Repository integrations for GitHub Enterprise, GitLab and Bitbucket run as self-hosted containers on a monthly release cadence supported for six months

**Held against it:**
- Secret detection is pattern-based, disabled by default, always rated Medium, and detected secrets are not anonymized
- The self-hosted statement covers only the repository integration, while the Mend AppSec Platform itself is Mend-hosted
- The contracting entity is White Source Ltd. in Givatayim, Israel, and the only named subprocessor is ZoomInfo for the website chatbot
- We found no public information on per-team roles, SCIM provisioning, audit logs, portfolio reports across repositories, or export of findings in a standard format
- We found no public information on the provider behind the AI model, a published SLA, a status page, encryption specifics or code-retention periods

**Best for:**
- You need a SAST rule set your auditors can trace, with CWEs mapped to OWASP Top 10, PCI DSS, CAPEC and SANS TOP 25
- You want the repository scanning containers under your own control, as the GitHub Enterprise, GitLab and Bitbucket integration runs self-hosted
- You want AI triage under explicit consent, as snippets are shared only after a signed addendum and turning the feature off stops sharing entirely
- You must file compliance evidence, with an integrated ISO 27001/27017/27701 management system reviewed externally every year and a SOC 2 Type II report through the account team

**Avoid if:**
- Your procurement requires a European contracting entity or a named subprocessor chain, as you would contract with White Source Ltd. in Givatayim, Israel, whose US subsidiary sits in Boston
- You need secret scanning active by default, as it ships disabled, is pattern-based across two weakness categories, always rated Medium, and detected secrets are not anonymized
- You want the entire platform on your own infrastructure, as the self-hosted option covers only the repository integration and the AppSec Platform is otherwise hosted by Mend

## 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 | 3/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Dependencies (SCA), licences & secrets | 3/5 | 3/5 | 2.5/5 | 3.5/5 | 3/5 | 3/5 |
| Developer workflow, quality gates & fixes | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 | 3.5/5 |
| Platforms, deployment & administration | 3/5 | 2.5/5 | 3/5 | 3/5 | 2.5/5 | 2.5/5 |
| Source-code handling, security & compliance | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| European sovereignty | 1/5 | 2/5 | 1.5/5 | 2/5 | 2/5 | 1.5/5 |
| Pricing transparency | n/r | n/r | n/r | n/r | n/r | n/r |
| **Weighted verdict** | **3/5** | **3/5** | **3/5** | **3/5** | **3/5** | **3/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: 2 of 6 dimensions proven.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Incorporated in IL | 0/2 | [S2] |
| Hosting location | Not determined | — | — |
| Hosting options | Self-hostable | 1/1 | [S10] |
| 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**
- Applicable laws last updated: 2025-08 [S2]
- CCPA no sale: no [S2]
- Cookie policy URL: https://www.mend.io/cookies-policy/ [S2]
- Developer email pseudonymization: yes [S11]
- Dispute resolution: Truste (feedback-form.truste.com) · yes [S2]
- Do not track: no [S2]
- GDPR: yes [S11]
- GDPR basis scope: EU Regulation 2016/79 · individuals located in the EU or EEA [S2]
- ISO 27001 17 27701: ISO 27001 · ISO 27017 · ISO 27701 · annually [S11]
- Israel adequacy: yes [S2]
- Israeli law: Israeli Privacy Protection Law, 5741-1981 (as amended) [S2]
- Newsletter tracking pixel: yes [S2]
- No sale 12 months: no [S2]
- Privacy contact: privacy@mend.io [S2]
- Public documents: Compliance & accreditation overview · Information security policy · Request security documents · yes [S11]
- Rights access: yes [S2]
- Rights complaint: Israeli Privacy Protection Authority · EU supervisory authority · UK ICO · yes [S2]
- Rights erasure: yes [S2]
- Rights exercise email: privacy@mend.io [S2]
- Rights objection: yes [S2]
- Rights portability: yes [S2]
- Rights rectification: yes [S2]
- Rights scope: GDPR · UK GDPR · Israeli PPL [S2]
- Rights withdraw consent: yes [S2]
- Sccs: transfers outside EU/EEA or UK without adequacy decision · EU Standard Contractual Clauses · UK Standard Contractual Clauses [S2]
- Security measures: yes [S2]
- Shine the light: no [S2]
- SOC 2 type2: SOC 2 Type II · Schellman · yes [S11]
- Trust page: yes [S1]
- US state privacy laws: Colorado · Connecticut · Delaware · Indiana · Iowa · Montana · Oregon · Tennessee · Texas · Utah · Virginia [S2]

**Data**
- Account deletion: email privacy@mend.io [S2]
- Cookies duration: yes [S2]
- Retention general: no longer reasonably necessary for stated purposes · longer period required by law or Customer · valid deletion request [S2]
- Retention policy URL: https://www.mend.io/data-retention/ [S2]
- Retention website 365: 365 [S2]
- Third party sources: business address · position · work email address · LinkedIn [S2]

**Hosting**
- Customer data choice: Customer’s location and preference · U.S. · EU [S2]
- Data locations: U.S. · Israel · UK · other jurisdictions · EU [S2]
- Self hosted: yes [S10]

**Integrations**
- API v3: 3.0 [S3]
- App health check: Health check API on wss-<integration_type>-app container at port 5678, healthy response code 200 [S9]
- Integration type placeholder: ghe (GitHub Enterprise) · gls (GitLab) · bb (Bitbucket) [S9]
- Languages resources: yes [S1]
- Pending webhooks API: Endpoint returning pending and running webhook counts plus a request token [S9]
- Remediate health check: Remediate container health check on port 8080 returning status OK [S9]
- Scan count all engines: Returns scan counts for SCA and SAST · state · Mend for GitHub Enterprise only [S9]
- Scan count by engine: SCA · SAST · ALL · state · engine · Mend for GitHub Enterprise only [S9]
- Scan state values: pending · scanning · done · pending [S9]
- Scan statistics API: API to track number of scan requests in the scan queue via the app container endpoint [S9]
- Scanner health check: Scanner container health check on port 9393 returning scanner_version · 19.10.1 [S9]
- Scanner health check min version: yes · 19.10.1 [S9]
- Scm support: Available across supported SCM integrations; results appear in Azure DevOps Repos, Bitbucket Cloud, GitHub.com [S7]
- Third party apps: Google · GitHub · GitLab · AWS · Microsoft [S2]

**Legal**
- Address: 53 State Street, Suite 500, 02109 Boston, US [S1]
- Address: 53 State Street, Suite 500, 02109 Boston, US [S11]
- Address: 53 State Street, Suite 500, 02109 Boston, US [S12]
- Controller identity: Mend · Ariel Sharon 4 Street, Givatayim, Israel, 5320047 · WhiteSource Software, Inc. · White Source Ltd. [S2]
- Copyright: 2026 · Mend.io (White Source Ltd.) [S2]
- Copyright entity: 2026 · Mend.io (White Source Ltd.) [S5]
- Copyright entity: Mend.io (White Source Ltd.) [S10]
- Copyright holder: Mend.io (White Source Ltd.) [S3]
- DPA affiliates: yes [S2]
- Entity: White Source Ltd. · 2026 [S1]
- Entity: White Source Ltd. [S11]
- Entity name: White Source Ltd. [S1]
- Entity name: White Source Ltd. [S11]
- Entity name: White Source Ltd. [S12]
- Group companies URL: https://www.mend.io/mend-group-companies/ [S2]
- Headquarters: Israel [S11]

**Pricing**
- Pricing page: yes [S1]

**Product**
- Agentic triage description: AI-based capability using an LLM to assess whether SAST findings are real vulnerabilities or false positives, with plain-language explanations [S7]
- AI bom: Continuously updated AI-BOM and SBOM across code, libraries, containers, dependencies, models, agents, RAGs, and system prompts [S12]
- AI red teaming: yes [S1]
- AI triage requires AI addendum: Requires signed AI addendum (AI Consent); without it the feature cannot be enabled [S7]
- API endpoint indicator: Findings reachable via API endpoints are flagged with an icon and endpoint count in Risk Factors [S8]
- Automated remediation: yes [S10]
- Automatic scan integration: Mend AppSec Platform UI · yes [S6]
- Bulk actions: Bulk actions: Jira issues, suppress/unsuppress, reviewed/unreviewed, change severity, add comments [S8]
- Change severity: yes [S8]
- Claimed metrics: 75 · 3 [S1]
- Code source module: Code Source · yes [S10]
- Comments tab: yes [S8]
- Cwe description tab: CWE Description tab shows CWE description, related Compliance Standard Violations, remediation guidance, further reading [S8]
- Data flow consolidation: Findings consolidated by taint sink; all tainted data flows reaching a sink combined into one finding [S8]
- Data sharing when enabled: Enabling shares source code snippets and finding details with Mend.io's AI model; disabling stops sharing and turns off Agentic Triage [S7]
- Dependency updates: Automated dependency updates at scale [S1]
- Detection accuracy: yes · security research team [S6]
- Differential results: yes [S10]
- Enable locations: Enabled by admin in Mend Platform (Administration → General, Code Findings Triage toggle) and in Code Security section of Developer Platform settings [S7]
- Explanation structure: Structured evidence breakdown including vulnerable location, sanitizer/validator, control-flow coverage, CWE relevance [S7]
- Framework mappings: EU AI Act · EU CRA · EO 14028 · NIST SSDF · NIST AI RMF · OWASP LLM Top 10 · ISO 42001 · ISO 27001 · SOC 2 · PCI DSS [S12]
- Full stack visibility: Full-stack software and AI visibility including packages, AI models, agents, system prompts, shadow dependencies [S1]
- Global configuration: yes [S10]
- High confidence default: yes [S8]
- Iac module: IaC · yes [S10]
- Issue tracker integration: yes · create issues via issue tracker integration (e.g. Jira) [S6]
- Jira issue creation: yes [S8]
- Limitation scope: SAST only [S7]
- Malicious package detection: yes · malicious package detection in Mend SCA [S6]
- Mark reviewed: yes [S8]
- Min age: 18 [S2]
- Modules: Mend AI · Mend AppSec · Mend SCA · Mend SAST · Mend Renovate · DAST · API Security · EOL Support [S1]
- Msc supported registries: npm · RubyGems · PyPi [S6]
- Outcomes advisory: yes [S7]
- Overview: github_app · security vulnerabilities · code weaknesses · IaC · license violations · outdated libraries [S10]
- Platform automation workflows: yes [S3]
- Platform description: security platform for application security and AI security [S11]
- Platform modules: Mend AI · Mend AppSec · Mend SCA · Mend SAST · Mend Renovate · DAST · API Security · EOL Support [S11]
- Platform SSO: yes [S3]
- Positioning: Enterprise AI security and application security platform [S1]
- Prerequisite entitlement: Triage requires Mend Platform access with Code entitlement (SAST) and at least one Code scan performed [S8]
- Release cadence: 6 · 1 [S10]
- Remediation guidance: removal recommended; upgrading unlikely to help; downgrading possible [S6]
- Renovate enterprise: yes [S1]
- Risk factors: SAST findings include Risk Factors based on confidence level, data flow characteristics, and known exploitation patterns [S8]
- Sast: yes [S1]
- Sast beta language marker: C/C++ support is marked Beta in the language lists [S4]
- Sast buffer overflow memory cwes: Stack-based Buffer Overflow (CWE-121) supported [S4]
- Sast cli scanning: yes [S3]
- Sast code scan configuration: yes [S3]
- Sast compliance mapping: CWEs mapped to compliance standards incl. OWASP Top 10, CAPEC, HIPAA, HITRUST, NIST, PCI DSS, SANS TOP25 [S4]
- Sast csrf: CSRF (CWE-352) supported for Java [S4]
- Sast cwe columns: Table columns: CWE-ID, CWE Name, Languages, Compliance Standards, Severity (Low/Medium/High) [S4]
- Sast cwe list purpose: Page documents the CWEs relevant to Mend SAST, sorted by CWE-ID [S4]
- Sast definition: Mend SAST is a Static Application Security Testing product for finding security vulnerabilities in custom code [S3]
- Sast deserialization: Deserialization of Untrusted Data (CWE-502) supported [S4]
- Sast hardcoded credentials: Use of Hard-coded Credentials (CWE-798); language column includes 'Secrets' [S4]
- Sast language support: yes [S3]
- Sast module: SAST · yes [S10]
- Sast os command injection: OS Command Injection (CWE-78) supported [S4]
- Sast password in config: Password in Configuration File (CWE-260) detected via Secrets [S4]
- Sast path traversal: Path Traversal (CWE-22) supported [S4]
- Sast policy violations: yes [S3]
- Sast remediation: yes [S3]
- Sast repository ide integrations: yes [S3]
- Sast sql injection: SQL Injection (CWE-89) supported across many languages [S4]
- Sast ssrf: SSRF (CWE-918) supported [S4]
- Sast third party integrations: yes [S3]
- Sast training resources: yes [S3]
- Sast triage: yes [S3]
- Sast xss: Cross-site Scripting (CWE-79) supported [S4]
- Sbom: yes [S1]
- Sca: yes [S1]
- Sca module: SCA · yes [S10]
- Secret anonymization: no [S5]
- Secret automation workflows: Automation Workflows can trigger policy violations and fail builds on secret detection [S5]
- Secret cli parameter: mend code · --secrets-detection [S5]
- Secret config file types: JSON · XML · .properties · .yaml · .config [S5]

**Subprocessors**
- Zoominfo chatbot: ZoomInfo · chatbot feature [S2]

**Support**
- Docs: yes [S1]

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

## Questions

### Is Mend.io European?

Not determined: the vendor’s pages as captured do not say where Mend.io is based. Its vendor, Mend.io (formerly WhiteSource), is incorporated in Israel, per [the vendor’s page captured 17 Nov 2026](https://whats-best.ai/evidence/26083).

### Where does Mend.io store data?

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

### Does Mend.io have a free plan?

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

### What are the best alternatives to Mend.io?

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: [Mend.io alternatives](https://whats-best.ai/software/code-security/mendio/alternatives).

## What this page leaves out

- 19 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.
- 3 compliance 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.
- 3 legal 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.
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material.
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material.

## Sources

- [S1] Vendor page: https://www.mend.io (checked 2026-11-17)
- [S2] Privacy policy — found from the homepage: https://www.mend.io/privacy-policy/ (checked 2026-11-17)
- [S3] Code analysis (SAST & code quality) — found from sitemap: https://docs.mend.io/platform/latest/mend-sast (checked 2026-11-17)
- [S4] Code analysis (SAST & code quality) — found from sitemap: https://docs.mend.io/platform/latest/sast-cwe-list (checked 2026-11-17)
- [S5] Dependencies (SCA), licences & secrets — found from sitemap: https://docs.mend.io/platform/latest/code-secret-scanning (checked 2026-11-17)
- [S6] Dependencies (SCA), licences & secrets — found from sitemap: https://docs.mend.io/platform/latest/malicious-packages-in-mend-sca (checked 2026-11-17)
- [S7] Developer workflow, quality gates & fixes — found from sitemap: https://docs.mend.io/platform/latest/code-findings-triage (checked 2026-11-17)
- [S8] Developer workflow, quality gates & fixes — found from sitemap: https://docs.mend.io/platform/latest/triage-your-code-security-findings (checked 2026-11-17)
- [S9] Platforms, deployment & administration — found from sitemap: https://docs.mend.io/integrations/latest/api-calls (checked 2026-11-17)
- [S10] Platforms, deployment & administration — found from sitemap: https://docs.mend.io/integrations/latest/mend-for-github-enterprise (checked 2026-11-17)
- [S11] Source-code handling, security & compliance — found from sitemap: https://www.mend.io/trust/ (checked 2026-11-17)
- [S12] Source-code handling, security & compliance — found from sitemap: https://www.mend.io/compliance/ (checked 2026-11-17)

---

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

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