The section your link pointed to isn't on Mend Container's page any more, so we've brought you to the top.
Mend Container scans container images for vulnerabilities, licenses, and components, supporting registry integrations, Kubernetes, and SBOMSBOMA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. export formats.
Mend Container is a commercial container-scanning tool that detects vulnerabilities in container images, including the base images and layers that make them up, as part of the wider 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. It runs as a hosted service, with results surfaced in the Mend Platform alongside findings from 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 SASTSASTStatic application security testing, analyzing source code or compiled code for vulnerabilities without running the application. It helps developers find problems before deployment., and findings can be managed from within a developer's IDE or AI agent workflow rather than only through a central dashboard. It is aimed at application security and platform teams who need visibility into what their containers are built from, rather than at developers scanning a single local image. It recognizes Chainguard as a supported source for hardened images, pulling in Chainguard-specific vulnerability and VEXVEXA machine-readable statement from a vendor saying whether a CVE in a component actually affects their product. It is how a scanner is told to stop flagging a vulnerability that is not reachable. data so teams working with hardened base images get posture information directly in the UI. The product is under active development, with three releases in the tracked window and the most recent one 27 days ago.
Mend Container scans container images for vulnerabilities, licenses, and components, supporting registry integrations, Kubernetes, and SBOM export formats.
Which of my container images have known vulnerabilities I don't know about?
scans image layers and base images against vulnerability data and reports findings by image, including which layer introduced the flaw
Which of my base images are already hardened and don't need re-flagging?
detects hardened image sources such as Chainguard layers and cross-references Chainguard-specific vulnerability and VEX data so those images aren't misjudged against generic advisories
Is a flagged vulnerability actually exploitable in my image, or can I dismiss it?
shows Chainguard VEX status directly alongside the finding so the exploitability verdict is visible without leaving the risk factors view
Which findings have my team already reviewed and cleared?
lets developers suppress or unsuppress findings individually or in bulk from within their own IDE or agent workflow, across scanning engines, so cleared results stop resurfacing
What does my organization's AI usage look like across all my scanned assets?
generates an AI Bill of Materials report that gives visibility into where AI components appear across the scanned footprint
Built from Mend Container'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.
+SAST CLI console log outputdocumentedAllows users to print Mend CLI SAST scan logs directly to the console (stdout) in real time via a --print-to-console flag, in addition to the log file.1 other source▸
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.
seen Oct 2026
· source
+SAST entry point and API endpoint detectiondocumentedExpands SAST analysis to use YAML and JSON configuration files for entry point detection, automatically identifying API endpoints and mapping them to their implementation classes.1 other source▸
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.
seen Oct 2026
· source
+Container image scan size limitshippedSupports scanning of container images up to 4 GB across all registry integrations, including ECR, and surfaces a clear error when an image exceeds that limit.5 releases · 1 other source · first seen Oct 2026▸
Raises the image scan size limit from 2 GB to 4 GB, enabling pulling, extraction, and scanning of larger container images across all registry integrations including ECR, with a clear error message for images still exceeding the new limit.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
changelog · Oct 2026
· source
· release history
Increases the maximum scanned image size from 2GB to 4GB across all registry integrations
Version 26.9.2 (04-October-2026) · Oct 2026
· source
· release history
The image scan size limit for Mend Container has been increased from 2GB to 4GB
26.9.2 · Oct 2026
· source
· release history
Raises the container image scan size limit from 2 GB to 4 GB across all registry integrations, including ECR, enabling successful pulling, extraction, and scanning of larger images.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Version 26.9.2 (04-October-2026) · Oct 2026
· source
· release history
Surfaces a clear error message when a scanned image exceeds the new 4 GB limit, instead of failing silently.
Version 26.9.2 (04-October-2026) · Oct 2026
· source
· release history
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
+AI runtime protectiondocumentedProvides runtime threat detection for AI workloads, with support for multiple programming languages.1 other source▸
Shared capability: Runtime threat detection
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. (27-September-2026) The Suppress and Review actions have been extended to the individual finding level.
seen Oct 2026
· source
+Other / not yet classified7 featuresFeatures we have not matched to a capability yet. A suggested match is marked.▸
+IDE/AI agent finding suppressiondocumentedEnables developers to manage security findings directly within their IDE or AI agent workflow, supporting single and bulk suppression actions across all scanning engines.3 other sources · first seen Sep 2026▸
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. (27-September-2026) The Suppress and Review actions have been extended to the individual finding level.
seen Oct 2026
· source
(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 Oct 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
+Account-level workflow managementdocumentedAllows administrators to define and manage workflows centrally across multiple organizations at the account level.2 other sources · first seen Aug 2026▸
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.
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
+Bun package manager supportdocumentedEnables scanning of JavaScript projects that use the Bun package manager via the Mend CLI and Mend Repository Integrations.2 other sources▸
Also counts toward: Command-line interface
docs
Version 26.9.1 (28-September-2026) (Open Beta) The Mend CLI now supports the Bun package manager for JavaScript projects.
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
+AI Bill of Materials (AI-BOM) reportingdocumentedProvides visibility into an organization's AI footprint by generating an AI Bill of Materials report.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
+Container Image SBOM report downloaddocumentedsuggestedGenerates and downloads SBOM reports for container images as valid ZIP archives.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
+OS-level CVE detection in filesystem scansdocumentedSurfaces OS-level CVEs in RHEL8/Rocky8-based container images during filesystem scans, including vulnerabilities with no available fix from the distribution.1 other source▸
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
+Workflow email notification recipient controldocumentedAllows workflow creators to select specific users or groups as recipients for scan summary email notifications.1 other source▸
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
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
5 commands for Mend Container, 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.
View
Source
No command matches.
Score card
Shipping velocityreleases a month, last 12 months
Documentation qualityrelease-notes rubric, 0–100
Breaking-change disciplinehow rarely a release breaks users, and notice given
Maintenance riskquiet time against its own cadence, maintainers
Innovation & surfacenew capabilities, API and MCP surface
Five scores for Mend Container, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Each score is 0–100 on a published rubric, derived from data this site already shows.
A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
Documentation quality — the release-notes rubric published on the analytics page, unchanged.
Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Mend Container 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.
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.
Each offering on the pricing page links to its own page of plans, read at its latest capture.
Plan relaunches
Plans, prices and descriptions are quoted from the vendor's own pricing page as we read it on each date.
A plan missing from a later reading is shown as no longer listed on the page — a statement about the page, not the product.
Readings that failed to show any plans are left out rather than read as a change.
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.