Vigilance vs GitHub Advanced Security
Last checked 8 Nov 2026
GitHub sends alerts from security notices that GitHub has reviewed, and new ones can take time to appear. Vigilance reads the files of each new version, so it does not wait for a notice.
GitHub Advanced Security warns about known bugs, committed passwords and mistakes in your code, in repositories on GitHub. Vigilance runs on each computer. It compares each new version with the last good one and reports the file that gained a power, such as reaching the internet or running a program.
Where GitHub Advanced Security Stops
GitHub Advanced Security
- GitHub's docs say Advanced Security is sold as two products.
- GitHub Secret Protection covers secret scanning and push protection.
- GitHub Code Security covers code scanning with CodeQL, Copilot Autofix and dependency review.
- These checks work on repositories on GitHub.
- Dependency review shows what a pull request adds or changes in packages.
- The pages we read state no read of what the new files can do.
Vigilance
- A power is something a file can do, such as reach the internet or run a program.
- Vigilance reports the update that gained one, on each computer.
- On the free trial, Team and Managed, it swaps back to the last good version.
Real case: axios, March 2026
Release 1.14.1
axios is one of the most-installed packages on the internet. This release added a hidden install step to its
package.jsonfile.The step
It downloads software that lets an attacker control the computer. Anyone who installed that release, by hand or through an AI tool, got it. No known-bug entry existed for it, so a list of known bugs had nothing to match.
What Vigilance reports
HEADS UP. 1 file changed.
package.jsonnow runs a program during install and connects to the internet. On the free trial, Team and Managed, it also swaps the computer back to the last good version.
Read the full record: axios npm attack, 2026. See more in the attack library.
For the wider field, read the software supply chain security tools guide or the full list of comparisons.
What GitHub Advanced Security Does Well
Two products
GitHub Secret Protection covers secret scanning and push protection, which stop keys and tokens from entering a repository. GitHub Code Security covers code scanning with CodeQL, Copilot Autofix for scanning alerts, and dependency review. Source: the GitHub docs.
Placement
The strength is placement. The checks sit inside the place where your team already works. A pull request shows the alert next to the code.
Free and paid
Several features are free for public repositories. For private repositories you buy the matching product, and you must be on a GitHub Team or Enterprise plan.
Autofix
When code scanning raises an alert, Copilot Autofix proposes a change, and a developer reviews it in the same pull request.
Feature Comparison
GitHub Advanced Security guards the code in your repositories. Vigilance checks what lands on team computers.
| Question | GitHub Advanced Security | Vigilance |
|---|---|---|
| Warns about a package with a known bug | Yes | No |
| Finds a password committed to a repository | Yes | No |
| Finds a mistake in your own code with CodeQL | Yes | No |
| Shows package changes in a pull request | Yes, with dependency review | No |
| Checks installs that AI tools make on a team computer | Not stated on its public pages | Yes. It checks installs from Claude Code, Cursor, Codex, GitHub Copilot, Devin Desktop and Gemini CLI, and installs a person types |
| Spots an update that gained a harmful power | Not stated on its public pages | Yes |
| Swaps a bad update for the last good version | Not stated on its public pages | Yes, on the trial, Team and Managed |
| Covers software that never touched a GitHub repository | No | Yes |
| Free plan | Free for public repositories only | Free for one person |
The GitHub column comes from the GitHub docs and the GitHub security page. "Not stated on its public pages" means the pages we read are silent.
When GitHub Advanced Security Is the Better Fit
Choose GitHub Advanced Security if
- Your code lives on GitHub and you want checks inside pull requests. It is the shortest path to secret scanning and code scanning.
- You leak secrets. Once a key is in git history, no later tool can fully remove it. Push protection stops the key before it enters.
- You run an open source project. The core features are free on public repositories.
- You want CodeQL. Vigilance does not scan source code for flaws.
Choose Vigilance if
- Your team builds software with AI tools, and you want the installs their AI tools make checked on each computer.
Where GitHub Ends and the Computer Begins
GitHub
- GitHub checks what enters your repository.
Vigilance
- Vigilance checks what lands on each computer.
The reach
An attack can reach a computer without ever touching a GitHub repository.
The install
People on your team who build software with AI tools install packages on their own computers, before any push.
The blind spot
A repository check never sees those installs.
Pricing
GitHub, per active committer
- GitHub Secret ProtectionPer active committer$19 per month
- GitHub Code SecurityPer active committer$30 per month
Both are free for public repositories. You must be on a GitHub Team or GitHub Enterprise plan to buy either one for private repositories. Sources: the GitHub security page and the GitHub docs.
Vigilance, per computer
- SoloOne person on one computer. It checks the code your AI tools download and warns you in plain words if it turns harmfulFree plan
- TeamIf an update turns harmful, it puts back the last good version on its own$49 per month
$490 per year - Managed$2,500 one-time setup per company, or no setup fee on the yearly price. It also checks every app on the computer, and a security person checks each warning before you see it$199 per month
$1,990 per year
Prices are per computer, per month, in US dollars, or in Canadian dollars when the card is from Canada. See the pricing section for the current numbers. The free 14-day trial puts a card on file and charges nothing until you say yes. It works the same as a paid plan. Plan fees have a 60-day refund.
Which One Do You Need?
Use both.
GitHub
GitHub scans the code you write for bugs and secrets.
Vigilance
Vigilance flags the update that gained a power it never had, on each team computer.
Known Risk versus New Risk
A bug or a bad package someone already reported, with a name and a number. Tools with a list of known problems work here.
An update that gained a power its last version never had, before any report covers it. Vigilance works here.
Common Questions
Is Vigilance a GitHub Advanced Security alternative?
Only for the part that checks updates. Vigilance does not scan your code for flaws or find committed secrets.
What does Vigilance do that GitHub Advanced Security does not?
Vigilance checks the installs AI tools make on each computer, including software that never touched a GitHub repository, and reports the update that gained a power.
What does GitHub Advanced Security do that Vigilance does not?
It finds known bugs, committed secrets and flaws in your code through CodeQL, and it reviews package changes in pull requests. Vigilance does none of these.
How much does GitHub Advanced Security cost?
GitHub lists Secret Protection at $19 and Code Security at $30 per active committer per month. Both are free for public repositories.
Does Vigilance need the internet or a cloud account?
Internet: yes. Each computer needs a network connection, because Vigilance checks each new package version on our service. It sends only public package names and versions. Your code and files stay on your computers. Cloud account: you need none of your own. You start with the free 14-day trial or a Vigilance plan.
Try It on Your Own Software.
Install Vigilance on each computer. After 14 days, we show you which packages your team's AI tools installed, and any update that gained a harmful power.
Talk to us
A question, a pilot, or a bigger team? Send a note.