npm why (who installs this package)
Why a package is in node_modules, which versions, who pulls it in: npm explain from package-lock.
Open the source (opens github.com) https://github.com/lawatch/10aday
Before you use it
- Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
What it is
MCP servers from io.github.Lawatch.
The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.
How to get it
oci package (stdio)
ghcr.io/lawatch/npm-why:1.0.0
From the server's entry in the official MCP Registry
mcpb package (stdio)
https://github.com/Lawatch/10aday/releases/download/npm-why-v1.0.0/npm-why-1.0.0.mcpb
From the server's entry in the official MCP Registry
Related
-
npm
MCP serversStructured npm/pnpm operations (install, audit, outdated, list) as typed JSON.
@paretools/npm@0.8.0 -
pare-npm
MCP serversPare npm ג€” Structured npm/pnpm operations (install, audit, outdated, list, run) as typed JSON.
@paretools/npm@0.8.1 -
npm Supply Chain Audit
MCP serversCheck npm packages for typosquats, hallucinated names, install scripts and risky new releases.
-
ScriptProbe MCP
MCP serversScriptProbe: Check npm install scripts and publisher changes before installing.
scriptprobe-mcp@0.1.0 -
Upgrade X-Ray: npm & PyPI dependency update diff
MCP serversDiff two npm/PyPI versions or lockfiles: new install scripts, network/shell/eval calls, new deps.
-
import-guardian
MCP serversCatch AI-hallucinated (slopsquatted) npm imports in generated code before npm install.
import-guardian-mcp@0.3.0