NPMScan icon

NPMScan

blockhacks-io/npmscan · v3.1.2 · Tools & Integrations

by BlockHacks.ioOwner verifiedAwesome AI Plugins

Check npm packages for malware, known vulnerabilities, typosquats and maintainer takeovers before installing, via npmscan.com's free, read-only MCP server (23 tools, no API key).

Follow0
Protect this install with HOL Guard

Guard checks the skills and MCP servers a plugin adds on your machine and asks you before a risky action runs. The scores above are free, and no plan changes them.

Is NPMScan a fit?

From the plugin's manifest and HOL's scan. Anything the plugin does not declare is shown as not declared.

Works with

  • MCP
  • Codex
  • Claude Code
  • Antigravity CLI
  • Kimi Code
  • 5 skills
  • 1 MCP server

Before you install

Sign-in
Asks you to sign in when you install it
Declared access
Interactive, Read
License
MIT

Check before relying on it

  • Some security checks did not finish: Cisco skill scan and Cisco MCP scan. See the evidence

What is NPMScan?

NPMScan is a published tools & integrations plugin for AI coding agents that works with MCP, Codex, Claude Code, Antigravity CLI and Kimi Code, developed by BlockHacks.io and distributed through the HOL AI plugin registry. Check npm packages for malware, known vulnerabilities, typosquats and maintainer takeovers before installing, via npmscan.com's free, read-only MCP server (23 tools, no API key).

Canonical slug
blockhacks-io/npmscan
Version
v3.1.2 · updated Nov 2, 2026

Registry snapshot

Owner verification
Verified on HOL as @salemalem
Marketplace source
.claude-plugin/marketplace.json
Scanner
HOL plugin scanner
Security result
Partial scan
Digest verified
Yes
5 bundled skillsRead, copy or download each SKILL.mdOpen skills

Trust and security

Trust & reputation

On-Chain Verified
84

HOL Trust Score

Per-metric points (0–100 each) combined via a weighted average into the overall score.

Installability
100/100
Maintenance
65/100
MCP server setup
100/100
Plugin Security
97/100
Provenance
80/100
Publisher Quality
100/100

Provenance

Plugin root
.
Source repo
https://github.com/salemalem/npmscan-mcp-plugin
Source commit
efd8dd03e380…
Publisher verified
Yes
Owner verified
@salemalem
Agent Plugins 1.0
Not detected

Continuous scanner CI not detected

This plugin remains listed. Its overall trust score is reduced by 10% because security checks are not maintained in the source repository's CI.

Optional: maintain the scanner in the source repository's CI to receive the full trust score. Listing does not require that change.

README badge not detected

Plugin owners can add the HOL badge to the repository README from Guard Plugins. Distribution, not security evidence. It adds a 2% engagement adjustment to the overall trust score and never changes the security result.

Partial scan
Security result
97
Score from finished checks
0
High findings

Some checks did not finish: Cisco skill scan and Cisco MCP scan. No blocking issue was found in the checks that did finish, but this is not a passed scan.

Provider
codex-plugin-scanner
Grade
A · Excellent
Version
3.24.2
codex:hol-plugin-scanner-FdDOzp / cisco-skill-scanner: failedcodex:hol-plugin-scanner-FdDOzp / cisco-mcp-scanner: unavailable

[claude:.] Claude Plugin

18/18

5 checks

[claude:.] Security

24/24

6 checks

[claude:.] Operational Security

N/A

5 checks · not applicable

[claude:.] Code Quality

10/10

2 checks

[codex:.] Manifest Validation

31/31

9 checks

[codex:.] Security

24/24

9 checks

[codex:.] Operational Security

N/A

5 checks · not applicable

[codex:.] Best Practices

9/12

5 checks

[codex:.] Marketplace

15/15

3 checks

[codex:.] Skill Security

5/5

4 checks

[codex:.] Code Quality

10/10

2 checks

[gemini:.] Gemini Extension

10/10

3 checks

[gemini:.] Security

24/24

6 checks

[gemini:.] Operational Security

N/A

5 checks · not applicable

[gemini:.] Code Quality

10/10

2 checks

[kimi:.] Kimi Plugin

41/45

10 checks

Published advisories

None matched in GitHub security advisories, checked . This covers published advisories only, not problems nobody has reported.

GitHub security advisories are those the source repository has published.

Findings

lowsecurityKIMI_INTERFACE_INVALID

interface must be an object containing string display metadata.

Use string values for Kimi interface metadata.

infobest-practicesCODEXIGNORE_MISSING

A .codexignore file helps prevent accidental inclusion of local artifacts and secrets.

Add a .codexignore file with generated assets, local state, and secret paths.

Install guidance

Install in Claude Code

Install through the Claude Code plugin marketplace.

Claude Code plugin docs

Optional: install HOL Guard for Claude Code first, so it can check this plugin's tools on your machine before Claude Code uses them.

  1. 1

    Add the marketplace

    Run this inside a Claude Code session. It registers the marketplace manifest shipped at the repository root. If the repository ships none, add the generated entry from the Advanced section below first.

    claude code
  2. 2

    Install the plugin

    Installs the npmscan entry from the npmscan marketplace.

    claude code
  3. 3

    Scripted alternative

    Non-interactive equivalent for scripts and CI pipelines. Add --scope project to pin the install to one repository.

    shell
  4. 4

    Check it is installed

    Lists installed plugins. The entry should appear as enabled.

    shell

To remove it later, run claude plugin uninstall npmscan@npmscan.

Did setup work in Claude Code?

No setup reports for Claude Code yet. Self-reported by signed-in visitors. Copying a command is not counted, and most installs are never reported.

Attested installs: Fewer than 10 attested installs of this plugin in week 2026-W44, so no number is shown. Counted from opt-in HOL Guard install reports, once per machine and runtime, and never mixed with the answers above. How install reports work.

Loading reviews

Plugin manifest

{
  "name": "npmscan",
  "version": "3.1.2",
  "description": "Detect malicious, vulnerable, or typosquatted npm packages from a conversation. Search the npm registry, or compare 2-5 candidates side-by-side before adding a new dependency; inspect maintainers, install scripts, and Sigstore publish provenance before installing; audit a whole package.json/lockfile/SBOM/GitHub repo — including transitive dependencies, license compliance, and before/after PR diffs or npm audit output — against OSV.dev / GitHub Security Advisories / NIST NVD (with CISA KEV and FIRST EPSS enrichment); then get a prioritized remediation ranking, concrete incident-response playbooks, a CI-ready PASS/WARN/FAIL merge gate, safer-alternative suggestions, and a generated CycloneDX/SPDX SBOM — via npmscan.com's free, read-only MCP server.",
  "author": {
    "name": "BlockHacks.io",
    "email": "[email protected]",
    "url": "https://npmscan.com"
  },
  "homepage": "https://npmscan.com/docs/mcp",
  "repository": "https://github.com/salemalem/npmscan-mcp-plugin",
  "license": "MIT",
  "keywords": [
    "npm",
    "security",
    "supply-chain",
    "vulnerability",
    "dependency-audit",
    "malware",
    "typosquatting",
    "osv",
    "github-advisories",
    "cve",
    "nvd",
    "provenance",
    "sigstore",
    "license-compliance",
    "sbom",
    "maintainer-takeover",
    "ci-cd",
    "incident-response",
    "remediation"
  ],
  "skills": "./",
  "mcpServers": "./.registry/mcp.json",
  "interface": {
    "displayName": "NPMScan",
    "developerName": "BlockHacks.io",
    "shortDescription": "Detect malicious & vulnerable npm packages",
    "longDescription": "Check npm packages for known vulnerabilities, malware, typosquats, maintainer takeovers, and risky install scripts before you install, upgrade, or ship them. Backed by npmscan.com's free, read-only MCP server (23 tools, no API key): npm registry search and side-by-side comparison, OSV.dev / GitHub Security Advisories / NIST NVD lookups enriched with CISA KEV and FIRST EPSS, Sigstore provenance and maintainer-history checks, whole-repo and transitive-dependency audits, license compliance, PR dependency diffs, npm audit enrichment, remediation ranking, and CycloneDX/SPDX SBOM generation. Bundles five skills: dependency-audit (audit a package.json, lockfile, SBOM, or GitHub repo), package-trust-check (is one package safe or compromised), new-dependency-evaluation (pick between candidate packages), incident-response (concrete playbooks for a flagged package), and ci-pr-gate (a deterministic PASS/WARN/FAIL merge verdict). Official page: https://npmscan.com",
    "category": "Developer Tools",
    "capabilities": [
      "Interactive",
      "Read"
    ],
    "websiteURL": "https://npmscan.com",
    "privacyPolicyURL": "https://npmscan.com/privacy",
    "termsOfServiceURL": "https://npmscan.com/terms",
    "defaultPrompt": [
      "Check if the npm package lodash is safe to install",
      "Audit the package.json in my project for vulnerabilities",
      "Compare axios vs node-fetch before I add a dependency"
    ],
    "composerIcon": "./icon.png",
    "logo": "./assets/logo-400.png",
    "screenshots": [
      "./assets/screenshot-1.png",
      "./assets/screenshot-2.png"
    ],
    "brandColor": "#ef4444"
  },
  "holManifestOrigin": "repository",
  "registryIndexVersion": 9
}

Marketplace source

Repo URL
https://github.com/salemalem/npmscan-mcp-plugin
Marketplace path
.claude-plugin/marketplace.json
Source path
plugins/salemalem/npmscan-mcp-plugin
Install policy
AVAILABLE

Skills

5 SKILL.md files ship with this plugin. Preview, copy, or download each one, then install them with the Skills CLI.

Share
skills-cli
  • ci-pr-gate

    skills/ci-pr-gate/SKILL.md

    Turn a dependency change — a before/after package.json/lockfile snapshot, or one or more named "bump X from A to B" upgrades — into one deterministic PASS/WARN/FAIL verdict formatted for a CI check or PR-comment bot, not a conversational report. Use when the user explicitly wants a mergeable/blocking verdict, a "CI gate," a PR status comment, or asks "should this PR be blocked," "is this safe to merge," "gate this dependency bump." Not for a plain explanation of what changed in a diff (dependency-audit's own snapshot-diff flow already covers that conversationally) and not for a single already-installed package's trust investigation (package-trust-check).

    SKILL.md content is not in this snapshot. Open the raw file to copy it from the source repository.

  • dependency-audit

    skills/dependency-audit/SKILL.md

    Audit a project's npm dependencies for known vulnerabilities and risky install scripts before installing, upgrading, or shipping. Use when the user pastes or attaches a package.json/lockfile, lists dependencies, or asks to check/audit/scan their packages for security issues — including comparing two snapshots (a PR diff) or checking license compliance.

    SKILL.md content is not in this snapshot. Open the raw file to copy it from the source repository.

  • incident-response

    skills/incident-response/SKILL.md

    Turn a flagged npm supply-chain finding — or just a vague, non-technical description of one ("this package looks sketchy," "someone said we got hacked," "npm install did something weird") — into concrete remediation steps. Use whenever the user wants to know what to actually do about a suspicious/compromised/flagged package, however precisely or vaguely they describe it — not for the initial trust/vulnerability investigation itself (see package-trust-check/dependency-audit for that).

    SKILL.md content is not in this snapshot. Open the raw file to copy it from the source repository.

  • new-dependency-evaluation

    skills/new-dependency-evaluation/SKILL.md

    Help decide what to add as a NEW npm dependency — comparing 2-5 named candidates for the same job, evaluating one named candidate against its real peers, or shortlisting candidates from a described need, before anything is installed. Use for "which should we use for X," "axios vs got vs node-fetch," "is X a good pick for Y," "what should we use to do Z," "should we add X or is there something better." Not for auditing packages already in the project (see dependency-audit), not for a deep single-package compromise/trust investigation (see package-trust-check), and not for a plain factual question with no choice being made ("what does X do").

    SKILL.md content is not in this snapshot. Open the raw file to copy it from the source repository.

  • package-trust-check

    skills/package-trust-check/SKILL.md

    Investigate whether one specific npm package is trustworthy — maintainer/ownership takeover signals, publish-provenance mismatches, and risky install scripts. Use when the user asks if a single named package is safe, compromised, hijacked, suspicious, or "can I trust this" — not for auditing a full package.json/lockfile (see dependency-audit) and not for a plain factual question like "what does X do.

    SKILL.md content is not in this snapshot. Open the raw file to copy it from the source repository.

File inventory

.agents/plugins/marketplace.json

file

342 bytes

f597b9a48cd55ba9…

.claude-plugin/marketplace.json

file

1,105 bytes

1d06c9eaeecba97a…

.claude-plugin/plugin.json

file

1,549 bytes

9497ba05b98d4fc9…

.codex-plugin/plugin.json

plugin-manifest

3,057 bytes

34f7791400c16de8…

.mcp.json

file

114 bytes

ecfa1f458a416735…

.registry/mcp.json

mcp-config

78 bytes

c15024eb58bf3276…

assets/logo-400.png

asset

52,724 bytes

a17afe222ac17526…

assets/screenshot-1.png

asset

89,872 bytes

4a8839d8db900a2b…

assets/screenshot-2.png

asset

92,008 bytes

90fa83315a7e4164…

gemini-extension.json

file

385 bytes

e6c79b1112a016b6…

icon.png

file

34,104 bytes

a3854cb0eafa06c7…

kimi.plugin.json

file

4,899 bytes

897a56bfba0691ad…

LICENSE

file

1,428 bytes

309ccffcda86800d…

README.md

file

31,251 bytes

0cdb80ca937976c5…

SECURITY.md

file

1,246 bytes

d08e105abe12693e…

skills/ci-pr-gate/references/test-prompts.md

skill

15,866 bytes

e235ad77cb70524b…

skills/ci-pr-gate/SKILL.md

skill

19,196 bytes

6c9c2ee2d73850fd…

skills/dependency-audit/references/test-prompts.md

skill

23,444 bytes

0c1ddf65b09c5fec…

skills/dependency-audit/SKILL.md

skill

23,900 bytes

275018835f5ee8a2…

skills/incident-response/references/test-prompts.md

skill

12,010 bytes

9cb0d310f373f4d7…

skills/incident-response/SKILL.md

skill

10,834 bytes

d21e2d07fb775c83…

skills/new-dependency-evaluation/references/test-prompts.md

skill

10,495 bytes

e905262cf82d4cd3…

skills/new-dependency-evaluation/SKILL.md

skill

14,908 bytes

0425018cecc31ccc…

skills/package-trust-check/references/test-prompts.md

skill

11,660 bytes

e5038907b868c189…

skills/package-trust-check/SKILL.md

skill

12,072 bytes

971c23747520ac44…

NPMScan — Frequently asked questions

What is NPMScan?
NPMScan is an AI plugin in the HOL registry. Check npm packages for malware, known vulnerabilities, typosquats and maintainer takeovers before installing, via npmscan.com's free, read-only MCP server (23 tools, no API key).
How do I install NPMScan?
Install NPMScan in your harness: Codex — codex plugin marketplace add salemalem/npmscan-mcp-plugin; Claude Code — /plugin marketplace add salemalem/npmscan-mcp-plugin; Antigravity CLI — npx [email protected] add salemalem/npmscan-mcp-plugin. Full step-by-step guidance is on the HOL plugin page.
How do I install NPMScan in HOL Guard?
To install NPMScan in HOL Guard, start with hol-guard plugin install blockhacks-io/npmscan --apply. The complete step-by-step install guide for HOL Guard is on the HOL plugin page.
How do I install NPMScan in Codex?
To install NPMScan in Codex, start with codex plugin marketplace add salemalem/npmscan-mcp-plugin. The complete step-by-step install guide for Codex is on the HOL plugin page.
How do I install NPMScan in Claude Code?
To install NPMScan in Claude Code, start with /plugin marketplace add salemalem/npmscan-mcp-plugin. The complete step-by-step install guide for Claude Code is on the HOL plugin page.
How is the Trust Score for NPMScan computed?
NPMScan has a HOL Trust Score of 84 out of 100. The score is a weighted sum of six components from a static scan of the source, capped for high-severity findings and adjusted by two disclosed policies. Memberships and payments are not inputs, and a scan is not a safety guarantee. Full breakdown: https://hol.org/registry/plugins/blockhacks-io%2Fnpmscan/trust
Who publishes NPMScan?
NPMScan is published by BlockHacks.io and listed on HOL.

Directory acceptance

Listed in 1 of 5 directory lists

Read from the list each directory publishes on GitHub. Being listed means the directory accepted the plugin; it is not a HOL security rating.

Lists last read . HOL re-reads them every day.

Submitting it? Check it against each directory's rules

Install signal

HOL cannot see every install. These are separate signals from different sources, so they are not added together. Counts under each floor show as <N.

Install commands issued here
<5
HOL Guard install commands issued from this listing, last 28 days.
Opt-in install reports
<10
Machines that reported installing it through HOL Guard in week 2026-W44. Reporting is opt-in, so most installs are not counted.
HOL Guard workspaces
<5
Workspaces that approved it or include it in an approved-plugin feed, as of today.

Reviews and similar plugins