npm why (who installs this package)
MCPB · NPM-WHY-1.0.0.MCPB · 2 COMPONENTS
Why a package is in node_modules, which versions, who pulls it in: npm explain from package-lock.
Available components
Last scanned (14 hours ago)
Scores higher than 72% of MCPB servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 709 tokens (~354/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 39
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed mcpb/https://github.com/Lawatch/10aday/releases/download/npm-why-v1.0.0/npm-why-1.0.0.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
npm_duplicates Which npm packages are installed in several versions? ~221
Lists the packages that package-lock.json installs in more than one version (e.g. 4 versions of chalk), with how many copies, where, and which package asks for each version. Use it to shrink node_modules or a bundle, to understand "two copies of React" or "instanceof fails" bugs, and to know what `npm dedupe` or an upgrade could remove.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum packages to list, worst first (default 30). |
| lockfile | object|string | – | Or: the content of package-lock.json (object or JSON text), lockfileVersion 2 or 3. |
| lockfile_path | string | – | Path to package-lock.json / npm-shrinkwrap.json, or to the project folder (the package.json next to it is read too, for "overrides"). Easiest when the server runs on your machine. |
| package_json | object|string | – | Optional: the root package.json (object or JSON text), used for "overrides". Read automatically with lockfile_path. |
| Name | Type | Req | Description |
|---|---|---|---|
| duplicated_packages | integer | – | – |
| duplicates | array | yes | – |
| extra_copies | integer | – | – |
| packages_in_lockfile | integer | – | – |
| summary | string | yes | – |
No examples provided.
why_npm_package Why is this npm package installed? ~390
Answers "why is X in my node_modules, which version, and who pulls it in?" from package-lock.json, exactly like `npm explain X` but without node_modules: every installed copy of the package (version and folder), whether it is a direct dependency, dev-only or optional, the packages that require it with their version ranges, and the full chains from your package.json (your project › express@4.21.2 › debug@2.6.9). Give a version range (e.g. "<4.17.21") to find only the vulnerable copies after a security alert, and see which top-level dependency to upgrade. Handles workspaces, aliases (npm:), overrides, bundled and peer dependencies. Use it instead of reading the lockfile yourself: lockfiles are thousands of lines and the nested node_modules rules decide which copy each package gets.
| Name | Type | Req | Description |
|---|---|---|---|
| lockfile | object|string | – | Or: the content of package-lock.json (object or JSON text), lockfileVersion 2 or 3. |
| lockfile_path | string | – | Path to package-lock.json / npm-shrinkwrap.json, or to the project folder (the package.json next to it is read too, for "overrides"). Easiest when the server runs on your machine. |
| max_paths | integer | – | Chains to show per copy, shortest first (default 5). |
| package | string | – | Package name, e.g. "debug" or "@babel/core". |
| package_json | object|string | – | Optional: the root package.json (object or JSON text), used for "overrides". Read automatically with lockfile_path. |
| packages | array | – | Or several package names at once. |
| version | string | – | Optional semver range: only copies whose version matches (e.g. "<4.17.21" for a vulnerability, "^7"). |
| Name | Type | Req | Description |
|---|---|---|---|
| lockfile | string | – | – |
| results | array | yes | – |
No examples provided.
How do I install the npm why (who installs this package) MCP server?
npm why (who installs this package) ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 10ae92afe77c256afad4dc27af918c5f66810c0202bf37653704278af7a5f69d; the commands to do that are on this page. If it does not match, do not open it.
mcpb · npm-why-1.0.0.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
10ae92afe77c256afad4dc27af918c5f66810c0202bf37653704278af7a5f69d
macOS / Linux
echo "10ae92afe77c256afad4dc27af918c5f66810c0202bf37653704278af7a5f69d npm-why-1.0.0.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\npm-why-1.0.0.mcpb).Hash -eq "10ae92afe77c256afad4dc27af918c5f66810c0202bf37653704278af7a5f69d"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the npm why (who installs this package) MCP server?
npm why (who installs this package) is an MCP server listed in the public MCP registry as io.github.Lawatch/npm-why. Why a package is in node_modules, which versions, who pulls it in: npm explain from package-lock. This page covers its MCPB bundle (https://github.com/Lawatch/10aday/releases/download/npm-why-v1.0.0/npm-why-1.0.0.mcpb).
Is the npm why (who installs this package) MCP server safe to use?
npm why (who installs this package) scores 41 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the npm why (who installs this package) MCP server expose?
npm why (who installs this package) exposes 2 tools: why_npm_package, npm_duplicates. Their descriptions and schemas cost roughly 611 tokens of context every time the server is loaded.
What licence is the npm why (who installs this package) MCP server under?
npm why (who installs this package) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the npm why (who installs this package) MCP server?
VerifyMCP ran 12 checks on npm why (who installs this package), covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about npm why (who installs this package): Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.