Coverage

Tools Vigilance Does Not Check

Updated 7 Nov 2026

Vigilance checks the installs that people and AI tools run with npm, pnpm, yarn, bun, pip and uv. It does not check cargo, go, gem, composer, maven, gradle or nuget yet. When a computer uses one of them, your Portal names it in a note. This page says what to do about each.

Start the free 14-day trial See the full coverage

What the Portal shows

Each computer tells Vigilance which of these seven tools it uses. It sends only the tool name from a fixed list. It never sends a project, a path or a file name.

The Portal shows each one as a note under "Notes. These do not change your status."

Example note

"Raj's ThinkPad also gets code with cargo, a tool for Rust. Vigilance does not check cargo. Ask your IT person if your users need it."

One rule for every tool

  1. Ask if it is needed

    Ask your IT person if your users need the tool. Remove it where nobody uses it.

  2. Lock the versions

    Commit the lock file of the tool, so each install gets the same version as before.

  3. Install from the lock

    Use the setting that fails when the lock does not match, so a new version needs a review.

What to do about each tool

ToolWhat it installsWhat to do
cargoRust packagesCommit Cargo.lock. Build and install with --locked, so cargo stops if the lock is out of date.
goGo modulesCommit go.mod and go.sum. Keep the Go checksum database on, so each module matches the copy everyone else got.
gemRuby gemsCommit Gemfile.lock. Install with Bundler in frozen mode, so it stops if the lock does not match.
composerPHP packagesCommit composer.lock. Use composer install, not composer update, outside a review. Add --no-scripts where no package needs its scripts.
mavenJava packagesPin an exact version for each dependency and plugin. Do not use version ranges. Run with --strict-checksums.
gradleJava and Android packagesTurn on dependency locking and dependency verification, so Gradle checks each file against the checksums in your project.
nuget.NET packagesTurn on packages.lock.json and restore with dotnet restore --locked-mode.

These settings belong to each tool, not to Vigilance. Check them with the tool's own documentation before you change a build. See also the nine prevention controls.

Other installs Vigilance does not check

The full list is in the Technical Overview, section 12.

FAQ

Which package tools does Vigilance check?

npm, pnpm, yarn, bun, pip and uv, for installs that people and AI tools run on Mac, Windows and Linux computers that joined.

Does an unchecked tool change my status in the Portal?

No. It shows as a note, for example "Raj's ThinkPad also gets code with cargo, a tool for Rust. Vigilance does not check cargo." Your status stays the same.

What do I do about a tool Vigilance does not check?

Ask your IT person if your users need it. If they do, lock the versions the tool installs and install only from that lock, so a new version never arrives without a review.

Check what your AI tools install.

Vigilance checks each install from npm, pnpm, yarn, bun, pip and uv, and puts back the last good version of a bad update.

Start the free 14-day trial What each status means