> ## Documentation Index
> Fetch the complete documentation index at: https://help.the-meridian.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> These are the public docs of Meridian for Shopify apps: hosting, billing (Plan Builder and the @the-meridian/sdk package), CRM, emails and automations for Shopify app developers.
> Start with these pages: Meridian MCP (https://help.the-meridian.ai/mcp-server.md) to connect a coding agent, AI coding agents (https://help.the-meridian.ai/ai-agents.md) for the agent skill, SDK quickstart (https://help.the-meridian.ai/sdk-quickstart.md), Running your app with the CLI (https://help.the-meridian.ai/cli-dev.md), Deployment (https://help.the-meridian.ai/deployment.md), and Errors (https://help.the-meridian.ai/errors.md) to look up an error code or message.
> Fetch one page at a time as Markdown (the page URL followed by .md), using the index in https://help.the-meridian.ai/llms.txt. llms-full.txt holds every page in one file of about 900 KB, so avoid loading it whole.
> With Meridian MCP connected, search these docs with docs_search and docs_get, and read live facts (feature and event keys, plan ids, environments, deployments, logs) from the MCP tools instead of guessing them.

# Container vulnerability scan after each deploy

> After each production deploy, Meridian scans your container image for known vulnerabilities in OS packages and dependencies: severities, CVEs and fixes.

After each production deploy, Meridian scans your container image for known vulnerabilities in its OS packages and dependencies. You find the results in each app's sidebar as **Vulnerabilities**, under **Deploy**.

## The deployments list

Pick an environment at the top of the page. The list below it has one row per deployment, newest first:

| Column | What it shows |
| :- | :- |
| Deployment | The commit and its branch |
| Scanned | When the scan finished |
| Findings | The critical and high counts, then how many are lower. **No issues** when the image is clean |
| Status | **Completed**, **Scanning** while the scan runs, or **Failed** when the registry could not be read |

Only the newest deployment is flagged with a colored dot, because it is the one serving traffic. Older rows show their counts in plain text. Search by commit or branch to find a deployment.

A deployment that was scanned more than once shows its newest scan. The list covers the environment's 20 most recent scans.

## A deployment's report

Click a row to open its report:

* **Scan results**: the number of critical, high, medium and low vulnerabilities, how many of each have a fix, the package types scanned and the totals.
* **The findings**: every CVE with its package, severity, whether a fix exists and its CVSS score. Select one to read its description, the version that fixes it, the file it was found in and links to the advisories. Search by CVE or package, or filter to findings with or without a fix.
* **Copy for AI**: copies the whole report as Markdown, to paste into an AI assistant for fix guidance.

A result looks like this:

| Severity | CVE | Package | Installed | Fixed in |
| :- | :- | :- | :- | :- |
| Critical | CVE-2024-XXXXX | `openssl` | 3.0.11 | 3.0.13 |
| High | CVE-2024-XXXXX | `libxml2` | 2.9.14 | 2.9.14+dfsg-1.3 |
| Medium | CVE-2024-XXXXX | `curl` | 7.88.1 | 7.88.1-10+deb12u5 |
| Low | CVE-2024-XXXXX | `tar` | 1.34 | No fix yet |

## When scans run

| | Lite | Pro | Enterprise |
| :- | :- | :- | :- |
| After every production deploy or rollback | ✓ | ✓ | ✓ |
| On demand with **Run scan**, on any environment | - | - | ✓ |

Development and staging deploys are not scanned automatically, so their list stays empty until you run a scan. **Run scan** is on the vulnerability check card of the hosting dashboard. On Lite and Pro the button stays visible but disabled. Automatic scans are free and never count against a limit.

## On the hosting dashboard

The summary on the hosting dashboard always describes the **live** deployment, the one serving traffic, and names it: for example *Live deployment 8609eeb · scanned 2 h ago · 98 findings*. A deployment that failed or is still in flight does not replace it there, because the live image is still the one exposed. Until a deployment has gone live, the summary is not shown.

Each row of the deployments table shows its own scan state, such as **Not scanned** or the number of findings. **View report** opens that deployment's report on the Vulnerabilities page.

A scan result describes the known vulnerabilities matched in the image at that time. It is evidence about known vulnerabilities, not proof that the app is secure.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.