For users

When Vigilance Swaps or Blocks an Install

Updated 7 Nov 2026

Most of the time you see nothing. Vigilance checks each new package that you or your AI tools install. When an update turns bad, it puts back the last good version, or stops the install and tells you why.

Read the notice for users Install Vigilance

A new install: you see nothing

When you install a package for the first time, the package manager never sees the bad version. It installs the last good one on its own. Your install works as usual.

An install you type: run it again

  1. The install stops

    Your project pins a bad version. The package manager shows a short message: why Vigilance blocked it, for example "This version is a known attack, so Vigilance stopped it."

  2. Vigilance tests the good version

    It tests the last good version in your project. If the test passes, it writes that version into your project files.

  3. Run the install again

    The message says "Vigilance swapped" the package "in this project. Run the install again." Run the same command again.

If no test is possible, the message names the good version to install instead. Install that version. Vigilance never changes the command while it runs.

Inside an AI tool: the Vigilance window

Sometimes Vigilance holds a version that an AI tool tried to add, and a small Vigilance window asks a question. It names the tool and the package, and asks if it can use another version.

  • Press Swap to use the other version.
  • Press Not now to keep the hold. Vigilance asks again after 24 hours.

While a question waits, your company's Portal shows "Vigilance asked you a question" for your computer. Your company can send you a message to answer it.

Other AI tool messages

Your AI tool gets the next step from Vigilance, and tells you in one line. If a package is too new to check, the AI tool uses an established package that does the same job. Vigilance makes no change to a different package without a yes.

Other messages you can see

Your company's Vigilance owner has the details

Vigilance stopped a version and found no good version that works in your app. Your company sees it in the Portal. Carry on with your work.

This version is too new or changed in a way Vigilance must check first

Vigilance holds it until the check is done. Try the install again later.

If this app is live, build and deploy it again

Vigilance swapped a package in an app that is live. The live copy keeps the old version until you build and deploy again.

An editor add-on turned off

Vigilance turned off a bad version of an add-on in your editor, such as Cursor or VS Code. Restart the editor to finish.

A desktop notice

A package already on your computer was later found to be an attack. The notice names it and the good version. Your company sees it too.

What Vigilance asks of you

FAQ

Vigilance blocked my install. What do I do?

Read the message. If it says Vigilance swapped the package in this project, run the install again. If it names a version to install, install that version. If it says your company's Vigilance owner has the details, carry on with your work and tell your company if the package is important to you.

What is the Vigilance window with Swap and Not now?

Vigilance holds a version of a package that an AI tool tried to add, and asks if it can use another version. Press Swap to use it. Press Not now to keep the hold. Vigilance asks again after 24 hours.

Does Vigilance ask for my password?

Only at install and when you remove it. At any other time, Vigilance never asks for a password, and it never asks you to run anything after the first install.

Work as usual. Vigilance checks each install.

When an update turns bad, Vigilance puts back the last good version and tells you the one step to take.

Start the free 14-day trial Troubleshooting