Add npmguard to MCP Security Servers#161
Open
AyoubTadlaoui wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds npmguard under 💾 MCP Security Servers.
What it is: A native pre-install risk gate for npm packages with an MCP tool for AI coding agents. Single Rust binary, distributed outside the npm ecosystem so it can't be compromised by the thing it's protecting against.
Why it fits the list: It ships as an MCP server specifically so AI coding hosts (Claude Code, Cursor, Windsurf) can ask for a verdict before they run `npm install`. The 2025-2026 wave of npm supply-chain worms (Shai-Hulud, chalk/debug hijack) all spread via lifecycle scripts that an MCP-gated install would have blocked.
What it scores:
Links:
Thanks for maintaining this list!