vuln_fixable
Severity: advise. A library your app uses has a known security hole, and a fixed version exists. Your deploy goes ahead; this is a recommendation, and it usually comes with a ready-made upgrade patch.
What Kaviris saw
A known vulnerability rated above 6.0 (CVSS) in a dependency of your app (from your lockfile, or installed into the app), and the package's maintainers have released a fix. The location names the package, its version and the CVE or GitHub advisory.
Why it doesn't stop your deploy
Which libraries your app uses is your choice, so Kaviris never blocks a deploy over them. It tells you, and does the tedious part of the fix for you. (An organisation can choose stricter rules for its own apps later: see Organisation policies.)
Why it is still worth fixing
Published vulnerabilities are what automated attacks look for first, and the fix is already there.
The fix Kaviris prepares
The refusal's fix has:
| Field | What it is |
|---|---|
package, to |
The package and the version to move to: the lowest version that fixes every known hole in yours, on your current major version when there is one |
command |
The package manager command that does it, such as npm install lodash@4.17.21 or npm update ws |
patch |
When Kaviris could work it out: a ready-made change to your files (a unified diff), for this one package |
The deploy also carries upgrades: one patch that applies every
upgrade that can be made together, plus a list of the ones that could not
(unresolved, each with a note saying why and a command to try). You
find it in get_deploy (MCP), GET /v1/deploys/{id} (API), the deploy
result of kaviris deploy --json, and on the app's card in the portal.
Patches are written for npm (package-lock.json, and package.json when
the version range has to change) and for pip (requirements*.txt pins).
For pnpm, yarn, bun, uv, poetry and Pipfile you get the command only.
Kaviris never changes your code itself. The patch is an offer.
How a coding agent applies it
-
Show the user what would change: the packages, from and to, from
upgrades.packages. Apply nothing unless they agree. -
Save
upgrades.patch(or one refusal'sfix.patch) to a file and apply it in the project folder:git apply --check kaviris-upgrades.patch && git apply kaviris-upgrades.patchIf
git apply --checkfails (the files changed since that deploy), run thecommandinstead. -
For each entry in
upgrades.unresolved, run itscommand, or tell the user what itsnotesays. -
Run the app's tests if it has any, commit, and deploy again.
Without an agent:
npm install lodash@4.17.21 # the fix.command; or pip install -U ...
git commit -am "Upgrade lodash"
kaviris deploy
If the package is not one you use directly, it comes in through another
package: upgrade that one, or use your package manager's override
(overrides in npm, resolutions in yarn, pnpm.overrides).