{"id":"io.github.salemalem/npmscan","slug":"io-github-salemalem-npmscan","title":"NPMScan","description":"Detect malicious or vulnerable npm packages: registry search, OSV.dev and GitHub advisory lookups","version":"3.1.2","publisher":{"kind":"github","id":"salemalem","label":"@salemalem on GitHub","url":"https://github.com/salemalem"},"website":"https://npmscan.com","repository":"https://github.com/salemalem/npmscan-mcp-plugin","remotes":[{"type":"streamable-http","url":"https://npmscan.com/api/mcp"}],"packages":[],"published":"2026-10-10","updated":"2026-10-10","status":"online","auth":"","latency_ms":1885,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"search_packages","title":"Search npm packages","description":"Search the npm registry by name or keywords. Each result includes its current weekly/monthly download counts, dependentsCount (how many other npm packages depend on it), topPackagesRank (position among npmscan's own top-100k-by-downloads snapshot — not live, but a second independent popularity signal), and deterministic (not model-generated) popularityTier/maintenanceTier labels — a package matchi","read_only":true},{"name":"get_package","title":"Get npm package details","description":"Fetch npm registry metadata for a package: latest version, install scripts (preinstall/postinstall are a key risk signal), maintainers, license, recent version history, weekly downloads, GitHub stars, TypeScript support, days since last publish, a topPackagesRank (position among npm's ~100k most-downloaded packages, from npmscan's own periodically-refreshed snapshot — not live), and a downloadTren","read_only":true},{"name":"get_package_version","title":"Get a specific npm package version","description":"Fetch registry metadata for one exact version of a package (dependencies, install scripts, tarball) AND check that exact version against OSV.dev for known vulnerabilities — isVulnerable/highestSeverity give a direct answer, and each finding includes severity, a summary, and the fixedVersion to upgrade to. Use this to check a version pinned in a lockfile rather than the latest release. If the OSV.d","read_only":true},{"name":"get_maintainer_profile","title":"Get basic profile info for an npm maintainer","description":"Given an npm username, returns every package npm's own maintainer:<username> search index currently returns for that account (registry.npmjs.org's /-/v1/search — the public registry API has no dedicated 'list packages by maintainer' endpoint otherwise), plus precomputed aggregates: currentlyMaintainsCount (still listed as maintainer right now vs. already-revoked), totalWeeklyDownloads and totalDep","read_only":true},{"name":"query_vulnerabilities","title":"Query known vulnerabilities for a package","description":"Query OSV.dev for known vulnerabilities affecting an npm package, optionally scoped to one exact version (e.g. to check whether a version pinned in a lockfile is safe). Returns isVulnerable and highestSeverity as a direct answer, plus each finding's severity, a plain-language summary, CVE aliases, and the fixedVersion to upgrade to — not a raw advisory dump. Also cross-checks the name/version agai","read_only":true},{"name":"batch_query_vulnerabilities","title":"Batch query known vulnerabilities","description":"Check a whole npm dependency inventory against OSV.dev in one call: pass `packages: [{name, version?}]`, or raw package.json / package-lock / yarn.lock / pnpm-lock / CycloneDX / SPDX content via `content`. Large inventories are chunked automatically. Each finding has severity, summary, CVE aliases, fixedVersion and isMalware, so no per-package follow-up is needed.\n\nBefore calling anything clean, r","read_only":true},{"name":"get_latest_advisories","title":"Get latest npm security advisories","description":"Browse recently published npm security advisories and known-malicious-package findings. Three disjoint sources, selected via type: \"reviewed\" (default) is GitHub's curated, mostly CVE-backed advisories; \"malware\" is GitHub's own known-malicious-package advisories; \"osv\" is OSV.dev's OpenSSF malicious-packages feed, a separate dataset whose entries use MAL-/OSV ids rather than GHSA ids. None of \"ma","read_only":true},{"name":"get_cve","title":"Look up a CVE in the NIST NVD","description":"Look up authoritative NIST NVD data for one exact CVE ID (e.g. \"CVE-2026-2950\"), or browse/search NVD by keyword, CVSS severity, CWE, or a publication-date range. Every result is enriched with CISA KEV status (`kev`, non-null only if this CVE is a confirmed, actively-exploited-in-the-wild vulnerability — treat that as an urgent-patch signal regardless of CVSS score) and FIRST.org EPSS (`epss`, the","read_only":true},{"name":"analyze_install_script","title":"Analyze an npm package install script","description":"Statically scans a package's preinstall/install/postinstall/prepare lifecycle scripts AND the file(s) they reference — fetched directly from the published tarball, not just the command string in package.json — against npmscan's documented red-flags rubric (/docs/red-flags): child_process use, network calls, access to sensitive paths/env (.ssh, .aws, .npmrc, *TOKEN/*KEY), obfuscation, remote binari","read_only":true},{"name":"analyze_transitive_dependencies","title":"Analyze transitive dependencies for vulnerabilities","description":"Walk one or more root packages' dependency trees (e.g. a package.json \"dependencies\" section) up to `maxDepth` levels (default 2, max 3) and check every resolved package@version against OSV.dev, so vulnerabilities several levels down still surface. Read `summary` first; `vulnerablePaths` answers \"which of my dependencies pulled this in\"; `nodes` has the full graph. npm aliases are followed (`actua","read_only":true},{"name":"check_package_provenance","title":"Check an npm package version for publish-provenance red flags","description":"Checks whether a package version was published with npm's own Sigstore-backed publish provenance (`npm publish --provenance`), and cross-checks that provenance against reality rather than just reporting its presence. Three checks: (1) parses the SLSA build attestation (declared source repo, commit, builder identity, GitHub Actions run URL) and flags a builder that isn't GitHub-hosted, or an attest","read_only":true},{"name":"check_maintainer_changes","title":"Check an npm package for maintainer/ownership red flags","description":"Reconstruct who has controlled an npm package and when, straight from the packument (each version records the maintainer list at publish time and who ran `npm publish`). Use it for the 'who controls this package, and did that change recently' question; use get_package/check_package_provenance for general health and publish integrity.\n\nFlags:\n1. a maintainer added recently who then published soon a","read_only":true},{"name":"check_maintainer_blast_radius","title":"Check npm maintainer blast radius","description":"Given an npm username, lists the packages npm's maintainer:<username> search index returns for that account and looks for a tight cluster of packages whose latest version was published within a short rolling window of each other — the shape of a compromised-account supply-chain attack, where a stolen credential is used on every package the account can publish to within hours (e.g. the September 20","read_only":true},{"name":"check_license_compliance","title":"Check a dependency list against a license policy","description":"Given a list of packages (name + optional exact version or semver range — e.g. straight from a package.json \"dependencies\" object) and an optional allow/deny license policy, resolves each package's declared SPDX license and reports a compliance verdict per package. Classifies every license into one of permissive/weak-copyleft/copyleft/network-copyleft/proprietary/public-domain/unknown, and underst","read_only":true},{"name":"diff_dependencies","title":"Diff two package.json/lockfile snapshots","description":"Compare two snapshots of a package.json, package-lock.json (v1-v3), yarn.lock (classic or Berry) or pnpm-lock.yaml (e.g. before/after a PR; formats can differ) and report added, removed and changed packages. Lockfiles cover the full resolved graph, so transitive-only changes are caught; npm aliases are followed (`actualName`). Up to 100 added/changed packages are checked in detail. Ideal for a CI ","read_only":true},{"name":"prioritize_remediation","title":"Rank a batch of flagged vulnerabilities by what to fix first","description":"Rank vulnerability findings other tools already returned (batch_query_vulnerabilities, query_vulnerabilities, analyze_transitive_dependencies, diff_dependencies...) by what to fix first. Pass up to 200 `{packageName, cveId?, severity?, advisoryId?, currentVersion?, fixedVersion?, findingType?}`. Each gets a tier: remove-now / patch-now / patch-soon / scheduled / monitor.\n\nHow the tier is decided:\n","read_only":true},{"name":"simulate_dependency_upgrade","title":"Simulate an npm dependency upgrade","description":"Before running npm install, check whether upgrading a package from a current to a target version is safe. Pass `packageName` + `currentVersion` + `targetVersion` (omit target for \"latest\"), or `packages: [...]` (1-100) to check many in one call; a name that cannot be resolved comes back with `fetchError` instead of failing the batch. A natural follow-up to prioritize_remediation: pass its packageN","read_only":true},{"name":"suggest_alternative","title":"Suggest better-maintained npm alternatives","description":"Given a package that looks deprecated, vulnerable, abandoned, or suspicious, suggest better-maintained alternatives in the same category. This tool first checks the source package's own latest-version health (deprecation, latest-version OSV verdict, popularity/maintenance tiers, typosquat flag), then combines maintainer-provided deprecation hints with deterministic npm search-based category matchi","read_only":true},{"name":"compare_packages","title":"Compare npm packages side-by-side","description":"Compare 2-5 candidate packages for the same job (e.g. \"axios vs got vs node-fetch\") side by side and get a deterministic pick. More than 5 names is rejected, never truncated; duplicate names are rejected. Use search_packages first if you have no shortlist.\n\nPer candidate: downloads and trend, popularity/maintenance tiers, GitHub stars, TypeScript support, license, deprecation, latest-version vulne","read_only":true},{"name":"audit_github_repository","title":"Audit a GitHub repository's npm dependencies","description":"Audit a GitHub repository's npm dependencies from its URL — no pasted files needed. Fetches package.json plus the first lockfile found (pnpm-lock.yaml, then package-lock.json, then yarn.lock) from the default branch (or `ref`), and detects monorepos (package.json workspaces, pnpm-workspace.yaml), merging member dependencies (up to 50 members).\n\nWhat it checks:\n- Every lockfile entry (up to 3,000; ","read_only":true},{"name":"get_remediation_playbook","title":"Get the concrete remediation playbook for a flagged finding","description":"Maps a finding's `rule` value from analyze_install_script, check_maintainer_changes, or check_package_provenance to the matching human-authored incident-response playbook (the same content published at /docs/playbooks) and returns its concrete, ordered steps, severity tier, real-incident references, and prevention tips — not just a link. Pass the exact `rule` string(s) a prior finding already retu","read_only":true},{"name":"generate_sbom","title":"Generate a CycloneDX or SPDX SBOM","description":"Given the same inputs batch_query_vulnerabilities accepts — either a flat {packages:[...]} list, or raw package.json / lockfile / CycloneDX JSON / SPDX JSON content via `content` — emits a spec-valid CycloneDX 1.6 or SPDX 2.3 JSON document (pick with `format`, default 'cyclonedx') with npmscan's own OSV.dev vulnerability findings and registry license data embedded in each spec's native fields: Cyc","read_only":true},{"name":"enrich_npm_audit","title":"Rank raw `npm audit --json` output by what to fix first","description":"Given the raw output of `npm audit --json` (npm 7+'s `{vulnerabilities: {...}}` format, or legacy npm 6's `{advisories: {...}}`), parses it directly — no need to re-paste package.json/lockfile content — and runs it through the same remove-now/patch-now/patch-soon/scheduled/monitor ranking prioritize_remediation exposes for hand-built finding lists (an advisory that is malware — a MAL-* id, or a GH","read_only":true}],"server_info":{"name":"npmscan","version":"3.1.3"},"category":"developer","tags":["security","web-search","data"],"kind":"remote","source":"registry","submitted":{},"first_party":false,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-08-01","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/io-github-salemalem-npmscan/"}