Vigilance vs Socket
Socket. Reads packages from public places like npm and flags a new version that starts running scripts or reaching the internet.
Vigilance. Reads any folder on any computer and says what changed since it last looked.
Side by side
| Question | Socket | Vigilance |
|---|---|---|
| Checks a public npm or PyPI package | Yes | Yes, once it is on disk |
| Blocks a bad package at the pull request | Yes | No |
| Covers software that did not come from a public place | No | Yes |
| Covers a vendor file drop, an installer or a zip | No | Yes |
| Covers your own build output | No | Yes |
| Watches a computer that is already running | No | Yes |
Which one do you need?
These two are the closest match here. Socket guards public packages. Vigilance guards everything else on the machine.
Try it on your own software.
Show it the version you run today and the one you are about to install.