dependency-evaluator vs NPMScan
dependency-evaluator is a plugin bundle for AI coding tools published by apart-tech. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). NPMScan is an MCP server published by salemalem. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  dependency-evaluator |  NPMScan |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 3.1.2 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | dependency-evaluator | NPMScan |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (npmscan.com/api/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/apart-tech/plugins | github.com/salemalem/npmscan-mcp-plugin |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
dependency-evaluator
Evaluate npm and Python packages before adding them as dependencies. Automatically gathers package metadata, analyzes source complexity, checks security and maintenance health, and produces a structured USE / EXTRACT / BUILD verdict. Auto-triggers when your agent is about to install a new package, or run on-demand with /evaluating-dependencies <package> [function]. Catches supply chain red flags like .pth injection, typosquatting, and stale maintainership.
NPMScan
Detect malicious or vulnerable npm packages: registry search, OSV.dev and GitHub advisory lookups
How to run each
dependency-evaluator As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install dependency-evaluator@claude-communityNPMScan As a remote MCP server
claude mcp add --transport http npmscan https://npmscan.com/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: dependency-evaluator · What it can do: NPMScan · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.