Vigilance vs Anchore
Anchore. Open-source tools (Syft and Grype) that list what is in a build and flag parts with known bugs.
Vigilance. Runs on your own machine and names the one file that gained a new power.
Vigilance as an Anchore alternative
Vigilance is an Anchore alternative that runs on your own machine. It names the one file that gained a new power, before you trust an update. Below, a plain table sets the two side by side.
Side by side
| Question | Anchore | Vigilance |
|---|---|---|
| Runs on your own machine | Yes | Yes |
| Finds known bugs in your dependencies | Yes | No |
| Flags a brand-new bad package by what it can do | No | Yes |
| Spots a file that can do more than the version before | No | Yes |
| Looks inside container images | Yes | Yes |
| Works with no internet | With a downloaded database | Pro |
Which one do you need?
Anchore lists parts and their known bugs. Vigilance names the file that gained a power. They cover different risks.
Known risk versus new risk
A bug or a bad package someone already reported, with a name and a number. Most tools work here.
A file that gained a power it never had, that no report covers yet. Vigilance works here.
Common questions
Is Vigilance an Anchore alternative?
Yes, for one job. Vigilance names the file that gained a new power, on your own machine. Many teams run it next to Anchore.
What does Vigilance do that Anchore does not?
Vigilance can spot a file that can do more than the version before, and flag a brand-new bad file by what it can do.
What does Anchore do that Vigilance does not?
Anchore finds known bugs that already have a name and a number. Vigilance does not.
Does Vigilance need the internet or a cloud account?
The Free plan runs online. Pro runs fully offline, with no cloud account.
Try it on your own software.
Show it the version you run today and the one you are about to install.
Talk to us
A question, a pilot, or a bigger fleet? Send a note. It reaches a person.