PAGES
← all tools
◆ SAST / SCA / Code Security

Mend SAST

Version 26.10.1 (02-November-2026) commercial

Mend SAST is a static application security testingstatic application security testingStatic application security testing, analyzing source code or compiled code for vulnerabilities without running the application. It helps developers find problems before deployment. service that scans source code for vulnerabilities and helps teams prioritize remediation.

Summary

Mend SAST is a commercial static application security testing service that scans source code for vulnerabilities and helps teams prioritize which ones to fix first. It runs through the Mend CLI, invoked as mend code, with scan logs streamed directly to stdout during CI runs so pipeline output shows real-time progress without tailing a separate log file. It sits within the broader Mend AppSecAppSecApplication security: the practice of finding and fixing vulnerabilities in software during design, development, and testing. Cyber tools build on AppSec workflows to shift vulnerability detection earlier in the development lifecycle. Platform alongside Mend SCASCASoftware composition analysis, identifying third-party dependencies and checking them for known vulnerabilities and license issues. It covers software a team uses rather than writes itself. and Mend Container, suggesting it's aimed at organizations consolidating application security tooling under one vendor rather than running point solutions, with findings display built for developers triaging results directly in their IDE. Recent engine work adds detection for CWECWECommon Weakness Enumeration, a catalog of recurring software and hardware weakness types. It describes classes of mistakes, such as injection, rather than individual vulnerability instances.-99 in JavaScript and TypeScript and improves accuracy across eleven CWE categories, alongside a probability risk factor shown next to each data flow for finer-grained triage. With four releases in the tracked window and the last one 26 days ago, development is active.

Mend SAST is a static application security testing service that scans source code for vulnerabilities and helps teams prioritize remediation.

How Mend SAST helps

Which of these findings are real risks worth fixing first?

attaches a probability risk factor to each data flow shown in the finding details, giving a triage signal alongside the raw match

Where in my build process should this scanning happen?

runs through pipeline and developer-platform integrations, including per-branch project scanning on Azure DevOps and Bitbucket Cloud, so results attach to the branch that produced them

Can I clear a finding I've already reviewed without leaving my editor?

offers a suppression action inside the IDE or AI agent workflow, usable singly or in bulk across both SAST and SCA findings

Are secrets or keys hard-coded anywhere in my Rust codebase?

detects CWE-321 hard-coded cryptographic keys and CWE-319 cleartext transmission of sensitive information specifically in Rust source

Is my JavaScript or TypeScript code exposed to injection or redirect flaws missed by older scans?

runs an analysis engine tuned across 11 CWEs including SQL injection, XSS, open redirect, and certificate validation, catching cases the previous accuracy level missed

all 42 features, with the evidence for each →

Languages

Not documented

Features

42 capabilities across 4 capability groups

Built from Mend SAST'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.

Compare with peers →

  • Mend SAST covers 3 of the 8 vulnerability assessment methods capabilities we track.
  • Mend SAST covers 1 of the 3 runtime security capabilities we track.

What Mend SAST offers you

  • Command-line interface4
  • MCP server1
  • REST API1
  • Role-based access control1
  • Scripting language support1
  • Ticketing integration1
Static application security testing 18 features Vulnerability assessment methods since 2024
Enhanced Vulnerability Detection Capabilities shipped Expands detection coverage for specific languages and vulnerability types, including React state XSS, Python mail relay/memcache injection, Angular auto-generated file exclusions, ASP.NET multi-core processing, and HTML/EJS analysis. 22 releases · 1 other source · first seen Jul 2024

Shared capability: Static application security testing

release 22 total

  • New detection for CWE-284 (Improper Access Control / Unsafe Permission Check) in Java Version 26.7.1 (27-July-2026) · Jul 2026 · source · release history
  • New detection for CWE-319 (Cleartext Transmission of Sensitive Information) in Go Version 26.7.1 (27-July-2026) · Jul 2026 · source · release history
  • New detection for CWE-614 (Sensitive Cookie Without Secure Attribute) in Python Version 26.7.1 (27-July-2026) · Jul 2026 · source · release history
  • New detection for CWE-642 (External Control of Critical State Data) in Java Version 26.7.1 (27-July-2026) · Jul 2026 · source · release history
  • Enhances JavaScript analysis by adding local storage as a low-probability source for potential client-side vulnerabilities Version 26.6.1 (29-June-2026) · Jun 2026 · source · release history
  • Improved detection of CWE-79: Cross-site Scripting (XSS) in JavaScript/TypeScript. Version 26.5.2 (15-June-2026) · Jun 2026 · source · release history

example

  • Enable Rust scanning for a new project now that it is GA. n/a (feature enabled via platform settings, not a CLI flag) 26.1.1 · Jan 2026 · source
Exposed Secrets Detection shipped Detects exposed credentials in source code and configuration files via dedicated scanning flags. 17 releases · 1 other source · first seen Jun 2025

Shared capability: Static application security testing

Also counts toward: Command-line interface

release 17 total

  • Improved detection of hard-coded credentials for JavaScript/TypeScript, PL/SQL, and VB.Net. Version 26.5.2 (15-June-2026) · Jun 2026 · source · release history
  • Adds PowerShell scripts (.ps1) to the default set of file types scanned by secret scanning Version 26.5.1 (01-June-2026) · Jun 2026 · source · release history
  • Adds new detection capabilities for hardcoded private keys (.pem, .key) and certificate files (.pfx, .p12) Version 26.5.1 (01-June-2026) · Jun 2026 · source · release history
  • Adds Secret scanning availability in Mend for Visual Studio Code. Version 26.4.2 (04-May-2026) · May 2026 · source · release history
  • Enables incremental scanning for secrets detection to analyze only changed files Version 26.4.1 (20-April-2026) · Apr 2026 · source · release history
  • Enhanced secret scanning to better detect hardcoded database connection strings in code changes Version 26.1.2 (09-February-2026) · Feb 2026 · source · release history

example

  • Scan Xcode projects for exposed secrets in .pbxproj configuration files. n/a (native support, no new flag required) 26.1.1 · Jan 2026 · source
Rust SCA Vulnerability Detection shipped Adds detection for Cleartext Transmission of Sensitive Information (CWE-319) and Use of Hard-coded Cryptographic Key (CWE-321) in Rust projects. 13 releases · first seen Apr 2025

Shared capability: Static application security testing

release 13 total

  • Adds detection for CWE-319 (Cleartext Transmission of Sensitive Information) and CWE-321 (Use of Hard-coded Cryptographic Key) for Rust. Version 26.8.1 (24-August-2026) · Aug 2026 · source · release history
  • Support for CWE-319: Cleartext Transmission of Sensitive Information and CWE-321: Use of Hard-coded Cryptographic Key for Rust. Version 26.8.1 (24-August-2026) · Aug 2026 · source · release history
  • Rust detection is now generally available with expanded CWE coverage 26.1.1 · Jan 2026 · source · release history
  • Makes Mend SAST Rust detection generally available with expanded CWE coverage Version 26.1.1 (26-January-2026) · Jan 2026 · source · release history
  • Added low probability taint sources for file, database, console, and environment variable reads in Rust. Version 25.11.1 (01-December-2025) · Dec 2025 · source · release history
  • Further improved detection accuracy for C/C++ gen 2 , most notably for the following CWEs: CWE-121: Buffer Overflow CWE-369: Divide by Zero CWE-606: Loop Denial of Service CWE-611: XML External Entity (XXE) Injection CWE-789: Uncontrolled Memory Allocation 25.11.1 · Dec 2025 · source · release history
JS/TS Analysis Engine Accuracy Improvement shipped Improves detection accuracy across 11 specific CWEs (including Path Traversal, SQL Injection, and XSS) within the JavaScript and TypeScript analysis engine. 7 releases · 3 other sources · first seen Apr 2024

Shared capability: Static application security testing

release 7 total

  • Adds support for YAML and JSON configuration files as input to the entry point detection engine, enabling automatic identification of API endpoints and mapping to their implementation classes.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Version 26.9.2 (05-October-2026) · Oct 2026 · source · release history
  • Improves JavaScript/TypeScript analysis engine detection accuracy across 11 CWEs: CWE-22 (Path Traversal), CWE-78 (OS Command Injection), CWE-79 (XSS), CWE-89 (SQL Injection), CWE-90 (LDAP Injection), CWE-94 (Code Injection), CWE-117 (Log Neutralization), CWE-295 (Certificate Validation), CWE-601 (Open Redirect),… Version 26.8.2 (07-September-2026) · Sep 2026 · source · release history
  • Increases detection accuracy for Python CWEs (CWE-22, CWE-78, CWE-79, CWE-117) and Java CWE-117 Version 26.6.1 (29-June-2026) · Jun 2026 · source · release history
  • Improves accuracy of Java, JavaScript/TypeScript and Python analysis for CWE-78, CWE-79 and CWE-89 25.11.2 · Dec 2025 · source · release history
  • Python files with BOM encoding can now be scanned. Version 25.4.1 (21-April-2025) · Apr 2025 · source · release history
  • Supports scanning Python files that use BOM (Byte Order Mark) encoding. 25.4.1 · Apr 2025 · source · release history

docs

  • Version 26.9.2 (05-October-2026) Mend SAST now supports additional configuration files, such as YAML and JSON, to improve entry point detection. The engine automatically identifies API endpoints and maps them to their corresponding implementation classes. docs update · Oct 2026 · source
  • Version 26.8.2 (07-September-2026) Improved detection accuracy of JavaScript /TypeScript analysis engine across 11 CWEs. docs update · Sep 2026 · source

example

  • Force the scanner to use the new generation engines for JavaScript and C# during execution. mend-sast scan --js-engine-generation=2 --csharp-engine-generation=2 24.3.2 · Apr 2024 · source
Contract-First Application Entry Point Taint Analysis shipped Automatically marks all generated entry point parameters as tainted in contract-first applications, eliminating the need for manual custom framework configuration. 9 releases · first seen Jun 2024

Shared capability: Static application security testing

release 9 total

  • Supports YAML and JSON configuration files for entry point detection, automatically identifying API endpoints and mapping them to implementation classes for contract-first applications.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ changelog · Oct 2026 · source · release history
  • Automatically marks all generated entry point parameters as tainted, eliminating the need for manual custom framework configuration for contract-first applications. changelog · Oct 2026 · source · release history
  • Automatically marks all generated entry point parameters as tainted for contract-first applications, removing the need for manual custom framework configuration. Version 26.9.2 (05-October-2026) · Oct 2026 · source · release history
  • Added reading from local files as a low probability taint source. Version 25.11.1 (01-December-2025) · Dec 2025 · source · release history
  • Added low probability taint sources for file, database, console, and environment variable reads in Rust, improving analysis accuracy 25.11.1 · Dec 2025 · source · release history
  • Reading from local files has been added as a low probability taint source 25.11.1 · Dec 2025 · source · release history
Advanced Scan Configuration Templates shipped Allows administrators to define and manage code scan configuration templates at the organization level, supporting project-specific defaults, scan profiles (fast/balanced/deep), and exclusion pattern visibility. 6 releases · 1 other source · first seen Jun 2024

Shared capability: Static application security testing

release

  • Control low-probability scan categories individually in the Scan Profile — replacing the previous binary toggle with a configurable selection tree that lets you include or exclude categories such as File Read or Database Read, with a count indicator for selected categories. Version 26.10.1 (02-November-2026) · Nov 2026 · source · release history
  • Custom Code Configuration settings now include a toggle to automatically include newly supported CWE types in scan coverage Version 26.7.1 (27-July-2026) · Jul 2026 · source · release history
  • Improves accuracy of CWE-918 (SSRF) detections for JavaScript and Python. Version 25.3.1 (24-March-2025) · Mar 2025 · source · release history
  • Enables storing Project-specific Code Scan Configurations before the first scan Version 24.10.3 (18-November-2024) · Nov 2024 · source · release history
  • Adds Code scan configuration templates at the organization level to manage code scans across all projects or specific applications. 24.5.3 · Jun 2024 · source · release history
  • Adds the ability to create Code scan configuration templates at the organization level to manage Code scans at scale, serving as defaults or explicit assignments for Applications/Projects. Version 24.5.3 (17-June-2024) · Jun 2024 · source · release history

example

  • Reduce noise for a codebase that has no database access by excluding the Database Read category from the next scan. In the platform UI, go to your Scan Profile > Low-Probability Scan Categories, expand the selection tree, uncheck 'Database Read', and save — the count indicator confirms how many categories remain… Version 26.10.1 (02-November-2026) · Nov 2026 · source
CWE-99 Detection for JS/TS shipped Adds detection capabilities for Improper Control of Resource Identifiers / Client Resource Injection (CWE-99) in JavaScript and TypeScript code. 4 releases · first seen Jul 2025

Shared capability: Static application security testing

Also counts toward: Scripting language support

release

  • Adds detection for CWE-99 (Improper Control of Resource Identifiers / Client Resource Injection) in JavaScript and TypeScript. Version 26.8.1 (24-August-2026) · Aug 2026 · source · release history
  • Detection of CWE-99: Improper Control of Resource Identifiers / Client Resource Injection for JavaScript/TypeScript. Version 26.8.1 (24-August-2026) · Aug 2026 · source · release history
  • Supports reading HTTP Handler Methods from an array as entry points in JavaScript/TypeScript Version 25.10.1 (20-October-2025) · Oct 2025 · source · release history
  • React event-handlers defined in separate files are now picked up as entry points when analyzing JavaScript code. 25.7.1 · Jul 2025 · source · release history
C/C++ Gen 2 Detection Engine shipped Adds a second-generation C and C++ detection engine with improved CWE and framework coverage. 4 releases · first seen Sep 2025

Shared capability: Static application security testing

release

  • SAST detection for Android, Objective-C and Cold Fusion now supports multi-threading to reduce scan time 26.1.1 · Jan 2026 · source · release history
  • Gen 2 C/C++ detection engine with improved CWE and framework coverage 25.10.1 · Oct 2025 · source · release history
  • Introduces the Gen 2 C/C++ detection engine for improved CWE and framework coverage Version 25.10.1 (20-October-2025) · Oct 2025 · source · release history
  • Adds Rust as a supported language for static analysis 25.9.1 · Sep 2025 · source · release history
AI-Generated Code Scanning shipped Enables SAST scanning of code generated by AI tools via MCP server integration, optimized for IDE workflows. 4 releases · first seen Jun 2025

Shared capability: Static application security testing

Also counts toward: MCP server

release

  • Agentic SAST detection now reports all detected findings in the generated code at once instead of just one finding per invocation. Version 25.11.1 (01-December-2025) · Dec 2025 · source · release history
  • Agentic SAST detection now reports all detected findings in the generated code at once instead of just one finding per invocation 25.11.1 · Dec 2025 · source · release history
  • Adds the capability to scan AI-generated code within Windsurf Version 25.8.2 (08-September-2025) · Sep 2025 · source · release history
  • Enables scanning of AI-generated code via the MCP server, with optimized integration for the Cursor IDE to maintain secure coding practices within existing workflows Version 25.5.2-HF1 (23-June-2025) · Jun 2025 · source · release history
Dedicated Project Scanning for SCM shipped Supports scanning into dedicated projects on Azure DevOps and Bitbucket Cloud, allowing security managers to monitor and set policies per branch. 2 releases · 1 other source · first seen Jun 2025

Shared capability: Static application security testing

release

  • Adds support for GitLab Repository Integration to enable automated SAST scanning of base branches and merge requests within the GitLab environment. Version 25.6.1 (30-June-2025) · Jun 2025 · source · release history
  • Adds Mend for GitLab repository integration allowing developers to set automated SAST scans for base branches and merge requests 25.6.1 · Jun 2025 · source · release history

docs

  • Added support for scanning into dedicated projects in the Developer Platform on Azure DevOps and Bitbucket Cloud. This allows security managers to monitor and set policies for each branch individually. docs update · Sep 2026 · source
Custom Scan Timeouts shipped Allows configuring extended scan durations for large repositories via CLI or SCM integrations. 2 releases · 1 other source · first seen May 2025

Shared capability: Static application security testing

Also counts toward: Command-line interface

release

  • Adds support for SAST scanning timeouts exceeding 30 minutes, configurable via CLI and SCM integrations Version 25.4.2 (05-May-2025) · May 2025 · source · release history
  • SAST scanning now supports timeout values exceeding 30 minutes, configurable via both the CLI and SCM integrations. 25.4.2 · May 2025 · source · release history

example

  • Extend scan duration for large repositories by setting a custom timeout via the command line. mend-sast scan --timeout 3600 <path> 25.4.2 · May 2025 · source
Gen 2 Detection Engine for Swift and PHP shipped Introduces a second-generation detection engine for Swift and PHP with improved CWE and framework coverage for more accurate and scalable scans. 1 release · 1 other source · first seen Oct 2026

Shared capability: Static application security testing

release

  • Introduces the Gen 2 detection engine for Swift and PHP, with improved CWE and framework coverage for accurate, scalable scans.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Version 26.9.3 (19-October-2026) · Oct 2026 · source · release history

docs

  • Version 26.9.3 (19-October-2026) Introducing the Gen 2 detection engine for Swift PHP Fixed an issue where HttpServletResponse and ServletResponse parameters were incorrectly treated as taint sources in Java, leading to false-positive Cross-Site Scripting (XSS) findings. docs update · Oct 2026 · source
GitLab Repository Integration shipped Enables automated SAST scanning for base branches and merge requests directly within the GitLab environment. 2 releases · first seen Jun 2025

Shared capability: Static application security testing

release

  • Adds support for GitLab Repository Integration to enable automated SAST scanning of base branches and merge requests within the GitLab environment. Version 25.6.1 (30-June-2025) · Jun 2025 · source · release history
  • Adds Mend for GitLab repository integration allowing developers to set automated SAST scans for base branches and merge requests 25.6.1 · Jun 2025 · source · release history
Custom Node.js Routing Framework Support shipped Parses `routes.json` manifests to identify handler functions as entry points for taint analysis in custom Node.js routing frameworks. 1 release · first seen Nov 2026

Shared capability: Static application security testing

release

  • Support custom Node.js routing frameworks by parsing routes.json manifests to identify handler functions as entry points for taint analysis.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Version 26.10.1 (02-November-2026) · Nov 2026 · source · release history
Java SAST False-Positive Reduction for XSS documented Fixes incorrect treatment of HttpServletResponse and ServletResponse parameters as taint sources in Java, eliminating false-positive XSS findings. 1 other source · first seen Oct 2026

Shared capability: Static application security testing

docs

  • Version 26.9.3 (19-October-2026) Introducing the Gen 2 detection engine for Swift PHP Fixed an issue where HttpServletResponse and ServletResponse parameters were incorrectly treated as taint sources in Java, leading to false-positive Cross-Site Scripting (XSS) findings. docs update · Oct 2026 · source
Python Analysis Engine Accuracy Improvement shipped Improves detection accuracy across multiple common vulnerability types within the Python static analysis engine. 1 release · first seen Oct 2026

Shared capability: Static application security testing

release

  • Improves Python engine detection accuracy across 11 CWEs including CWE-022 Path Traversal, CWE-078 OS Command Injection, CWE-079 XSS, CWE-089 SQL Injection, CWE-094 Code Injection, CWE-209 Error Message Info Exposure, CWE-295 Improper Cert Validation, CWE-532 Sensitive Info in Log, CWE-601 Open Redirect, CWE-918 SSRF,… changelog · Oct 2026 · source · release history
SAST Default Exclusions for macOS Metadata shipped SAST scans via the Mend CLI automatically exclude macOS-generated `/_MACOSX/..*` metadata files across all scan engines, even when default exclusions are otherwise disabled. 1 release · first seen Sep 2026

Shared capability: Static application security testing

release

  • Default exclusions in mend code CLI scans now automatically ignore /_MACOSX/..* metadata files across all SAST scan engines, even when default exclusions are otherwise disabled. Version 26.9.1 (28-September-2026) · Sep 2026 · source · release history
Gen 2 Go Detection Engine shipped Provides a second-generation detection engine for the Go programming language with improved CWE and framework coverage. 1 release · first seen Apr 2026

Shared capability: Static application security testing

release

  • Introduces the Gen 2 Go detection engine for improved CWE and framework coverage Version 26.4.1 (20-April-2026) · Apr 2026 · source · release history
Vulnerability prioritization 2 features Vulnerability assessment methods since 2025
Advanced Risk Factor Prioritization shipped Introduces new risk factors including Probability and Endpoint Access to prioritize high-value findings. 8 releases · first seen Apr 2025

Shared capability: Vulnerability prioritization

release 8 total

  • Probability risk factor is now displayed next to each data flow in finding details within the Mend Platform. Version 26.8.1 (24-August-2026) · Aug 2026 · source · release history
  • The local log file for secret scans now includes a list of all scanned files 25.8.1 · Aug 2025 · source · release history
  • Improves JavaScript/TypeScript analysis performance with substantially reduced duration Version 25.7.2 (11-August-2025) · Aug 2025 · source · release history
  • Code Risk Factors column and workflow condition support allows prioritizing findings by endpoint access or high-probability risk Version 25.5.2 (16-June-2025) · Jun 2025 · source · release history
  • Adds Endpoint Access as a new Risk Factor for findings accessible via API endpoints Version 25.4.3 (19-May-2025) · May 2025 · source · release history
  • Adds new Endpoint Access risk factor to findings accessible through API endpoints to improve prioritization 25.4.3 · May 2025 · source · release history
SAST/DAST Correlation shipped Correlates static analysis findings with dynamic testing results to mark confirmed vulnerabilities as exploitable. 4 releases · first seen Jun 2025

Shared capability: Vulnerability prioritization

release

  • The applications view adds the ability to filter, sort, and group findings by project Version 25.11.2 (15-December-2025) · Dec 2025 · source · release history
  • Adds filtering, sorting, and grouping of findings by project in the applications view 25.11.2 · Dec 2025 · source · release history
  • Correlates SAST findings with dynamic analysis results from the Invicti integration, marking confirmed vulnerabilities with an Exploitable risk factor to prioritize remediation Version 25.5.2-HF1 (23-June-2025) · Jun 2025 · source · release history
  • Correlates SAST findings with Invicti DAST results, marking confirmed vulnerabilities with the Exploitable risk factor 25.5.2 · Jun 2025 · source · release history
Container image vulnerability scanning 1 feature Vulnerability assessment methods since 2026
Chainguard Container Image Detection documented Detects Chainguard image layers and base images, incorporating specific vulnerability data and VEX information for hardened container security. 2 other sources · first seen Aug 2026

Shared capability: Container image vulnerability scanning

docs

  • Version 26.9.2 (04-October-2026) The image scan size limit for Mend Container has been increased from 2GB to 4GB. This update allows for the successful pulling, extraction, and scanning of larger container images across all registry integrations, including ECR. seen Oct 2026 · source
  • Version 26.8.1 (23-August-2026) Chainguard is now supported as part of Mend Container’s hardened image detection , enhancing container security by incorporating Chainguard-specific vulnerability data and VEX information. This update includes the detection of Chainguard image layers and base images. docs update · Aug 2026 · source
Runtime threat detection 1 feature Runtime security since 2024
AI Runtime Protection Multi-Language Support shipped Extends Mend AI Runtime Protection and Guardrails to cover additional widely used programming languages, broadening runtime threat detection coverage. 2 releases · 1 other source · first seen Nov 2024

Shared capability: Runtime threat detection

release

  • Code Scan Configuration control now supports fast, balanced, or deep scan profiles for gen 2 detection engines, optimizing performance or coverage respectively 24.10.3 · Nov 2024 · source · release history
  • Adds a new control in Code Scan Configuration to select fast, balanced, or deep scans for gen 2 detection engines Version 24.10.3 (18-November-2024) · Nov 2024 · source · release history

docs

  • (05-October-2026) Enhanced multi-language support in Mend AI Runtime Protection | Guardrails Languages , expanding runtime threat detection to some of the world's most widely used languages. seen Oct 2026 · source
Other / not yet classified 20 features Features we have not matched to a capability yet. A suggested match is marked.
IDE/AI Agent Finding Suppression shipped Enables developers to suppress or unsuppress findings for all scanning engines directly within their IDE or AI agent workflow, supporting single and bulk actions. 15 releases · 3 other sources · first seen Mar 2025

release 15 total

  • Adds Information Requested state to suppression requests in the UI to allow reviewers to request additional context Version 26.5.1 (01-June-2026) · Jun 2026 · source · release history
  • Suppressions synchronized with GitHub now add a comment to the linked issue containing the suppression reason, extra comments, and the user who performed the suppression. Version 26.2.2 (09-March-2026) · Mar 2026 · source · release history
  • Suppression request tables now display a Reviewed By column showing who approved or rejected each request. Version 26.2.2 (09-March-2026) · Mar 2026 · source · release history
  • Adds support for suppression approval workflows in GitHub repositories to let developers request suppressions while managers retain control Version 26.1.1 (26-January-2026) · Jan 2026 · source · release history
  • Supports suppression approval workflows for Azure DevOps repositories Version 25.12.2 (12-January-2026) · Jan 2026 · source · release history
  • Supports suppression approval workflows for Bitbucket repositories, allowing developers to request suppressions and security managers to approve or reject them. Version 25.12.1 (05-January-2026) · Jan 2026 · source · release history

docs

  • (27-September-2026) The Suppress and Review actions have been extended to the individual finding level. Previously limited to the entity level, users can now triage specific findings within an entity independently. seen Sep 2026 · source
  • Version 26.8.2 (06-September-2026) Introduced a new suppression tool in , enabling developers to effectively manage security findings directly within their IDE or AI agent workflow. This update supports both single and bulk suppression or unsuppression actions across all scanning engines, including SAST and SCA. docs update · Sep 2026 · source

example

  • Audit all pending suppressions across the org and export them for compliance records. In the console, go to Findings --> Suppression Requests, apply filters as needed, then click Export to CSV. 26.3.1 · Mar 2026 · source
Remediation Integration and Automation shipped Provides automated fix suggestions for code findings in the web UI and Jira tickets, and enables end-to-end remediation flows such as updating GitHub feature branches directly from the platform. 14 releases · 1 other source · first seen Sep 2024

Also counts toward: Ticketing integration

release 14 total

  • Adds automated remediation suggestions for Code findings in Rust Version 26.4.1 (20-April-2026) · Apr 2026 · source · release history
  • Adds automated remediation suggestions for Code findings in C and C++ (CWE-22, CWE-79, CWE-89, CWE-117, CWE-601) 26.1.1 · Jan 2026 · source · release history
  • Adds automated remediation suggestions for Code findings in C and C++ covering CWE-22, CWE-79, CWE-89, CWE-117, and CWE-601 Version 26.1.1 (26-January-2026) · Jan 2026 · source · release history
  • Adds mend code import CLI command to import SARIF results from third-party SAST scanners into the Mend AppSec Platform. Version 25.3.2 (07-April-2025) · Apr 2025 · source · release history
  • Adds mend code import CLI command to import third-party SAST results in SARIF format 25.3.2 · Apr 2025 · source · release history
  • Adds support for automated remediation suggestions for CWE-78, CWE-90, CWE-502, CWE-643, and CWE-918 in Java, JavaScript/TypeScript, C#, and Python. Version 25.3.2 (07-April-2025) · Apr 2025 · source · release history

example

  • Review and accept code fix suggestions directly within Bitbucket Cloud pull requests or issues. Steps: Go to your Bitbucket Cloud repository, open a Pull Request containing code findings from Mend SAST. Look for the 'Remediation Suggestions' panel in the Developer Platform integration tab. 25.2.2 · Mar 2025 · source
Unified Vulnerability Remediation Experience shipped Standardizes fix logic and recommendations across the platform, including a Top Fix column in findings tables and consistent metadata for reliable fixes. 6 releases · 3 other sources · first seen Dec 2024

release

  • Adds --print-to-console flag to mend code CLI scans, printing scan logs directly to stdout in real time in addition to the log file.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Version 26.9.1 (28-September-2026) · Sep 2026 · source · release history
  • Code Remediation Suggestions now display exact line numbers in addition to the existing code diff view. 25.7.1 · Jul 2025 · source · release history
  • Renames the Date column to Detected in the Code findings table Version 24.11.2 (16-December-2024) · Dec 2024 · source · release history
  • Adds the CWE Number column to the Code findings table for direct CWE identifier visibility Version 24.11.2 (16-December-2024) · Dec 2024 · source · release history
  • Renames the Type column to CWE Name in the Code findings table Version 24.11.2 (16-December-2024) · Dec 2024 · source · release history
  • Updates the layout of the Code Findings table and the Code Finding Details panel to improve usability 24.11.1 · Dec 2024 · source · release history

docs

  • Version 26.9.1 (28-September-2026) The Mend CLI SAST scan (mend code) now supports a --print-to-console flag that prints the CLI logs directly to the console (stdout) as the scan runs, in addition to writing them to the log file. docs update · Sep 2026 · source
  • Version 26.8.2 (06-September-2026) Introduced a unified vulnerability remediation experience across the Mend Platform by standardizing fix logic and recommendations, adding a Top Fix column in the Findings table, updating the Remediation tab, and ensuring consistent metadata for reliable and clear vulnerability fixes. seen Sep 2026 · source

example

  • Stream scan logs to the console during CI runs so pipeline output captures real-time SAST progress without having to tail a separate log file. mend code --print-to-console Version 26.9.1 (28-September-2026) · Sep 2026 · source
Workflow Violation Conditions shipped Allows compliance standard violations to serve as direct conditions within the platform's workflow engine. 5 releases · first seen Jun 2025

release

  • PCI DSS 4.0 and MISRA standards are now visible in the code findings table and code reports for compliance filtering Version 25.11.2 (15-December-2025) · Dec 2025 · source · release history
  • Adds PCI DSS 4.0 and MISRA as supported compliance standards in code findings table and reports 25.11.2 · Dec 2025 · source · release history
  • Enables repository onboarding via the first pull request when no prior scans exist, causing initial findings to fail the check rather than becoming backlog Version 25.10.1 (20-October-2025) · Oct 2025 · source · release history
  • Adds compliance standard violations as direct conditions in the workflow engine Version 25.6.2 (14-July-2025) · Jul 2025 · source · release history
  • New workflow templates for OWASP Top 10 2021, SANS/CWE Top 25, and PCI DSS standards Version 25.5.2 (16-June-2025) · Jun 2025 · source · release history
AI-Based Project Risk Factor Classification shipped Classifies projects by risk factors using an AI model that analyses code snippets and project details, surfaces the classifications in a risk factors widget on the project summary page and a column in the Applications and Projects lists, and provides an evidence page listing the code signals behind each classification grouped by risk factor and file. 4 releases · first seen Oct 2026

release

  • Mend SAST now shows a risk factors column in the Applications and Projects lists, filterable by group or individual risk factor, to help prioritize remediation across projects.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ changelog · Oct 2026 · source · release history
  • Enable AI-based project risk factors from organization administration — the setting requires AI consent, is off by default, and when on shares code snippets and project details with Mend's AI model to produce classifications. changelog · Oct 2026 · source · release history
  • An evidence page now lists the code signals behind each risk factor classification, grouped by risk factor and file, so teams can see why a project was classified a certain way. changelog · Oct 2026 · source · release history
  • A risk factors widget now appears on the project summary page for at-a-glance visibility into each project's risk profile. changelog · Oct 2026 · source · release history
Bun Package Manager Support documented suggested The Mend CLI and repository integrations support the Bun package manager for JavaScript projects, enabling SCA scanning of Bun-based dependencies. 4 other sources · first seen Sep 2026

Suggested capability: Vulnerability database matching. This is our guess, not confirmed.

Also counts toward: Command-line interface

docs

  • Version 26.9.3 (19-October-2026) The Bun package manager, previously in open beta, is now generally available in the Mend CLI and repository integrations. docs update · Oct 2026 · source
  • Version 26.9.3 (18-October-2026) The Bun package manager, previously in open beta, is now generally available in the Mend CLI and repository integrations. seen Oct 2026 · source
  • Version 26.9.1 (27-September-2026) The Mend CLI and the Mend Repository Integrations now support the Bun package manager for JavaScript projects. seen Sep 2026 · source
  • Version 26.9.1 (28-September-2026) (Open Beta) The Mend CLI now supports the Bun package manager for JavaScript projects. docs update · Sep 2026 · source
Account-Level Global Workflows shipped Allows administrators to define and centrally manage workflows across multiple organizations within an account. 1 release · 3 other sources · first seen Jul 2025

release

  • Adds compliance standard violations as direct conditions in the workflow engine Version 25.6.2 (14-July-2025) · Jul 2025 · source · release history

docs

  • Version 26.9.2 (04-October-2026) Email notification capabilities in have been enhanced, allowing workflow creators to directly control recipients by selecting specific users or groups for scan summary emails. seen Oct 2026 · source
  • Version 26.9.2 (04-October-2026) Email notification capabilities in have been enhanced, allowing workflow creators to directly control recipients by selecting specific users or groups for scan summary emails. docs update · Oct 2026 · source
  • Version 26.8.1 (23-August-2026) Introduced Account-Level (Global) Workflows , enabling administrators to define and manage workflows centrally across multiple organizations. docs update · Aug 2026 · source
Findings Label Filtering shipped Allows filtering code findings by specific labels at the application level to narrow down analysis scope. 2 releases · 1 other source · first seen Jan 2025

release

  • Allows filtering Code Findings by Labels in the Application-level Findings table 24.12.1 · Jan 2025 · source · release history
  • Enables filtering JavaScript Code Findings by Labels at the Application level via the Findings table Version 24.12.1 (06-January-2025) · Jan 2025 · source · release history

example

  • Filter Application-level findings to show only those tagged with a specific label. In the Findings table, open the filter panel and select 'Labels', then choose your target label from the list. 24.12.1 · Jan 2025 · source
CLI stdout log output shipped The `mend code` CLI command supports a `--print-to-console` flag that writes scan logs directly to stdout, enabling real-time monitoring of scan progress and errors without parsing log files. 1 release · 1 other source · first seen Sep 2026

Also counts toward: Command-line interface

release

  • mend code scans now support the --print-to-console flag to print CLI logs directly to stdout. Version 26.9.1 (28-September-2026) · Sep 2026 · source · release history

example

  • Monitor scan progress and errors in real-time without parsing log files or switching terminals. mend code --print-to-console Version 26.9.1 (28-September-2026) · Sep 2026 · source
AI-Assisted Rule Customization shipped Enables sharing project data with the platform's AI engine to generate custom detection rules. 2 releases · first seen May 2025

release

  • Adds ability to share additional project data with Mend.io for AI-assisted detection rule customization Version 25.4.3 (19-May-2025) · May 2025 · source · release history
  • Adds option to share additional project data with Mend.io for AI processing and custom rule candidate generation 25.4.3 · May 2025 · source · release history
Code Report Generation API shipped suggested Exposes code reports through the Mend Platform API (v3), enabling programmatic retrieval and integration of scan results. 2 releases · first seen Dec 2024

Suggested capability: Static application security testing. This is our guess, not confirmed.

Also counts toward: REST API

release

  • Code reports can now be generated through the Platform API (API v3) Version 24.11.1 (02-December-2024) · Dec 2024 · source · release history
  • Adds support for generating Code reports via the Platform API (API v3) 24.11.1 · Dec 2024 · source · release history
AI Bill of Materials (AI-BOM) reporting documented Generates comprehensive reports providing full visibility into an organization's AI footprint. 1 other source · first seen Aug 2026

docs

  • (24-August-2026) Introduced the new AI Bill of Materials (AI-BOM) report , providing full visibility into an organization's AI footprint. docs update · Aug 2026 · source
Enhanced Findings Display shipped suggested Adds columns for Violations, Endpoint Access, and Exploitable status to findings reports for better context. 1 release · first seen Jul 2025

Suggested capability: Vulnerability prioritization. This is our guess, not confirmed.

release

  • Adds Violations, Endpoint Access, and Exploitable data columns to findings reports Version 25.6.2 (14-July-2025) · Jul 2025 · source · release history
Historical Finding Persistence shipped Prevents reappearing of suppressed issues older than 90 days to maintain stable finding states. 1 release · first seen Jul 2025

release

  • Adds historical findings handling to prevent reappearing of suppressed issues older than 90 days Version 25.6.2 (14-July-2025) · Jul 2025 · source · release history
Comprehensive CSP Scanning Support shipped suggested Expands detection coverage for various Common Vulnerabilities and Exposures (CVEs) across Java and other languages. 1 release · first seen Jun 2025

Suggested capability: Published CVE checks. This is our guess, not confirmed.

release

  • Added detection for CWE-208, CWE-256, and CWE-352 in Java Version 25.5.2 (16-June-2025) · Jun 2025 · source · release history
CLI Exclusion Pattern Matching documented Fixes correct application of top-level exclusion patterns in the Mend CLI when the pattern begins with a slash. 1 other source

docs

  • Version 26.9.2 (06-October-2026) Fixed an issue where top-level exclusions were not correctly matched in the CLI when the exclusion pattern started with a slash. seen Oct 2026 · source
Container Image SBOM Report Download Fix documented suggested Fixes an issue where Container Image SBOM reports were downloaded with a .txt extension and a truncated filename despite containing a valid ZIP archive. 1 other source

Suggested capability: Container image vulnerability scanning. This is our guess, not confirmed.

docs

  • Version 26.9.3 (18-October-2026) Fixed an issue where Container Image SBOM reports were downloaded with a .txt extension and a truncated filename, despite containing a valid ZIP archive. seen Oct 2026 · source
Custom Roles documented Provides generally available custom role management, including a role breakdown view and a Create Role wizard for defining and managing user roles with tailored permissions. 1 other source

Also counts toward: Role-based access control

docs

  • Version 26.9.3 (18-October-2026) Custom Roles , previously in closed beta, are now generally available . In this release, the role breakdown and the Create Role wizard are enhanced to provide a more intuitive custom role management experience. seen Oct 2026 · source
EUVD Data Source Integration documented suggested Integrates the European Union Vulnerability Database (EUVD) as a primary source, providing enriched CVSS scores and exploitability data from ENISA. 1 other source

Suggested capability: Vulnerability database matching. This is our guess, not confirmed.

docs

  • Introduced support for the European Union Vulnerability Database (EUVD) as a primary security data source. This integration provides enriched vulnerability data, including dedicated CVSS scores and exploitability information sourced directly from ENISA . seen Sep 2026 · source
OS Vulnerability Detection in Filesystem Scans documented suggested Filesystem scans on RHEL8/Rocky8-based images now correctly surface OS-level CVEs, including those without an available fix from the distribution. 1 other source

Suggested capability: Container image vulnerability scanning. This is our guess, not confirmed.

docs

  • Version 26.9.1 (27-September-2026) Fixed an issue where certain vulnerabilities in RHEL8/Rocky8-based images were not correctly identified during filesystem scans. The scanner now properly surfaces OS-level CVEs even when no official fix is available from the distribution. seen Sep 2026 · source

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.

Command line

4 commands for Mend SAST, each with where it came from. This tool has no source analysis yet, so there is no option reference and no captured run beside them.

Source

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface

Five scores for Mend SAST, 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.

Score cards are part of every paid plan.

See plans →

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 Mend SAST 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.

Checking release-note history…

Explore the full chart →

Commercials

pricing & packaging history · Mend.io vendor page

32 readings of Mend.io's pricing page since May 2022, with 8 relaunches of its plan lineup and 9 changes to what its plans include — each one dated, compared with the reading before it, and explained for someone buying the tool.

Pricing and packaging history is included with Researcher and Business. See how every vendor we track sells, and how that has changed over time, using data we don't publish anywhere else.

See plans →

Website history

mend.io, every change

Mend.io's home page and 40 more pages as they looked each month from May 2022 to October 2026: 53 renders, 4 changes of tagline or palette. Step through them, play them, or put any two months side by side.

Website history is included with Researcher and Business.

See plans →

Coverage

Missing something? Tell us

What Mend SAST connects to, runs on and detects, read from its release notes and docs. So far: 4 updated detections, 3 updated supported platforms, 1 new supported platform.

Show
When

8 changes, tracked since Oct 5, 2026.

  • Oct 202026

    new Bun package manager general availability

    With bun.lock, bun.lockb, package.json

    The Bun package manager, previously in open beta, is now generally available in the Mend CLI and repository integrations. This allows for the automatic detection and reporting of both direct and transitive dependencies in projects using `package.json` alongside `bun.lock` or `bun.lockb` files, ensuring secure and reliable dependency management for the Bun ecosystem.

    Source ↗

  • Oct 202026

    updated Gen 2 detection engine extended to Swift and PHP

    Introducing the Gen 2 detection engine for Swift PHP

    Source ↗

  • Oct 202026

    updated False-positive XSS reduction for Java HttpServletResponse/ServletResponse

    With Cross-Site Scripting (XSS)

    Fixed an issue where `HttpServletResponse` and `ServletResponse` parameters were incorrectly treated as taint sources in Java, leading to false-positive Cross-Site Scripting (XSS) findings.

    Source ↗

  • Oct 202026

    updated False-positive SSRF and NoSQL Injection reduction for JavaScript and TypeScript

    With Server-Side Request Forgery (SSRF)

    Fixed an issue where false-positive findings were reported for JavaScript and TypeScript applications. The engine incorrectly flagged Server-Side Request Forgery (SSRF) on relative in-app paths using React Router's navigate function and NoSQL Injection on Sequelize models even when configured with a PostgreSQL dialect.

    Source ↗

  • Oct 202026

    updated Improved Swagger YAML entry point detection for API definitions

    Fixed an issue where some Swagger YAML entry points were not correctly detected during scans, ensuring more comprehensive coverage and accurate vulnerability reporting for API definitions.

    Source ↗

  • Oct 192026

    updated Gen 2 detection engine for Swift and PHP

    Introducing the Gen 2 detection engine for Swift and PHP , with improved CWE and framework coverage for accurate, scalable scans.

    Version 26.9.3 (19-October-2026) Source ↗

How we count

Read from 8 of 105 release notes and docs updates we hold for Mend SAST. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through Mend SAST'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

105 entries

  1. November 20261
  2. October 202611
  3. September 20268
  4. August 20267
  5. July 20261
  6. June 20263
  7. May 20262
  8. April 20261
  9. March 20262
  10. February 20262
  11. January 20264
  12. December 20254
  13. November 20254
  14. October 20252
  15. September 20253
  16. August 20253
  17. July 20253
  18. June 20255
  19. May 20254
  20. April 20254
  21. March 20254
  22. February 20251
  23. January 20254
  24. December 20243
  25. November 20242
  26. October 20242
  27. September 20244
  28. August 20243
  29. July 20242
  30. June 20244
  31. April 20242
    Show
    Coverage in all entries

    105 entries

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →