npm Supply Chain Audit

io.github.tylerscomic-labv1.1.0Updated Oct 2, 2026

Check npm packages for typosquats, hallucinated names, install scripts and risky new releases.

VerifiedStreamable HTTPWeb executableSecurity & MonitoringDeveloper Tools

Overview

AI-generated overview

Audits npm package.json files for typosquatted names, risky install scripts, unpinned versions, and suspicious live registry entries.

What it does
This server exposes tools that inspect npm dependency manifests for supply-chain risks rather than generic CVEs. audit_package_json runs a full audit of a package.json, check_package_name performs a focused typosquat check on one name, and the newer inspect_package_live and audit_dependencies_live look packages up on the live npm registry. It flags names within 1-2 character edit distance of heavily depended-on packages, install hooks that pipe remote downloads into a shell or decode base64 payloads, and dependencies pinned to * or latest. Live lookups also flag nonexistent, brand-new low-traffic, deprecated, or typosquatted packages.
When to use it
Use it when reviewing a JavaScript project's dependencies before installing or merging, when checking whether a package name an assistant suggested actually exists, or when triaging a dependency tree after a supply-chain scare. It is aimed at npm-specific risks such as typosquatting and install scripts, not at general vulnerability scanning.
Requirements
The hosted option is a remote streamable HTTP endpoint; the README also describes self-hosting by installing dependencies and running node server.js, which requires Node.js. The manifest declares no authentication, environment variables, or headers. Live registry tools need network access to the npm registry. The README mentions a free tier and a paid Pro plan.
Before you install
The live tools send package names to the public npm registry. The README mentions a paid Pro tier, so check pricing before relying on the hosted endpoint. Audit results are heuristic flags, not proof of malice, so verify findings before acting on them.

Installation

In SourceWeft

  1. Open npm Supply Chain Audit in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "npm-supply-chain-audit-mcp": {
      "type": "http",
      "url": "https://npm-supply-chain-audit-mcp.mcpize.run/mcp"
    }
  }
}

README

npm-supply-chain-audit-mcp

[License: MIT] [Live on MCPize]

An MCP server that audits package.json for the real mechanisms behind actual npm supply-chain incidents — typosquatting and malicious install scripts — not a generic vulnerability-database lookup.

What it catches

Typosquatting. Dependency names within 1-2 character edit distance of one of the npm registry's most-depended-on packages (lodash, express, react, axios, and ~90 others) — the actual real targets of typosquat campaigns, since attackers go after the packages with the largest install base. lodahs, expres, reqeust all flag; an unrelated, genuinely distinct package name doesn't.

Malicious install scripts. preinstall/install/postinstall hooks run automatically on npm install, before any of the package's own code is ever reviewed — the actual delivery mechanism behind real incidents (event-stream 2018, ua-parser-js 2021, and others since). Flags scripts that pipe a remote download directly into a shell, and scripts that decode an obfuscated base64 payload before running it.

Unpinned versions. Dependencies on * or latest pull in whatever gets published next, silently, with no diff in your repo to explain why your dependency tree changed.

Tools

audit_package_json

Full audit of a package.json file.

check_package_name

Focused typosquat check on a single package name.

Use it

Hosted (recommended): MCPize — free tier, $7/mo Pro.

Self-host:

bash
npm installnode server.js

Part of a small suite

secrets-leak-audit-mcp, mcp-trust-audit-mcp, github-actions-audit-mcp, dockerfile-audit-mcp.

License

MIT

Update 1.1.0 (2026-10-01)

  • New tools inspect_package_live and audit_dependencies_live: look packages up on the live npm registry. Flags names that do not exist (hallucinated or mistyped), brand-new low-traffic packages, install scripts, deprecated releases and typosquats.

Source: README.md at commit d9bebba

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.1.0LatestOct 2, 2026