Skip to content

Go to the docs contents

Dependency vulnerabilities

Each version of your app is checked against known vulnerabilities, at build time and then every day. A serious vulnerability to fix wakes your agent.

Updated November 21, 2026.

View as Markdown

Dependency vulnerability scanning at every build and every day: the magnifying glass finds the cracked block and a serious flaw wakes your AI

You, to your AI: Are there vulnerabilities to fix before the production deployment?

When to use it

The inventory is always there: each version is checked against the known vulnerabilities, and your agent reads them before production, with get_app_status { include: ["vulnerabilities"] }.

How it works

Each version built by while has the list of components of its whole image, system packages included, checked against the known vulnerabilities at its build and then every day. A serious vulnerability to fix opens the “Serious vulnerabilities” incident, which wakes your agent.

Each vulnerability is reported only once. A deployment’s response lists the serious vulnerabilities the new version brings, with what to change, such as “upgrade lodash to 4.18.0 in package.json”. It waits up to 20 seconds for their check; if the check is not finished, it says so.

On the app’s Versions page, the version that brought a serious vulnerability shows it until the vulnerability is fixed, with what to do and a sentence to give your agent. A vulnerability known later, about what is already live, is attached to the live version. The version that fixes a vulnerability says so.

Without a Dockerfile, while chooses the app’s base image, and its vulnerabilities are while’s business: they are not reported to you. As soon as the fixed image is published, while rebuilds the app on it, with the same code and the usual deployment (health probe, automatic rollback). The Versions page records it.

With your own Dockerfile, you choose the base image. while reads the image of your FROM and says what to do: deploy again if the published image already has the fix, or add the line that updates the package.

What to know

get_app_status { include: ["vulnerabilities"] } lists them, checked by UpdateFOMO. A provided image (image:) is only inventoried if it carries its list of components (docker buildx build —sbom=true). The vulnerabilities of an embedded tool (esbuild…) or without a published fix are shown without opening an incident.

For the app’s runtime (Python, Node.js, Ruby, PHP, Go), a vulnerability fixed only in a more recent branch stays to be watched, even high: the advice is to migrate (change branch, then test), not to update. Actively exploited (KEV list), it opens the incident anyway.

Your agent’s MCP tools

Your agent handles it with the get_app_status tool.

Give your AI the message, and it takes care of the rest

Give this to your AI

Read while.sh/agents and help me get started with while.

Copy the message

In 3 minutes, with no sign-up, the tool has its own address. To keep it, create your account.

For a company project, write to the while team: hello@while.sh