npm-package-intel

Check whether an npm package is deprecated or vulnerable before installing it, including vulnerabilities, license, maintenance, freshness, dependency health, and package.json risk signals.

Price: $0.03 USDC equivalent
Endpoint: POST /v1/npm-package-intel
Network: Base mainnet · eip155:8453
Asset: USDC
MCP tool: npm-package-intel
External payability: PASS · 2026-10-08T19:55:01.298Z

When an agent should use it

check an npm package before installing it
npm vulnerability license and maintenance check
is this npm package deprecated or vulnerable
inspect npm dependency health

Input schema

{
  "type": "object",
  "properties": {
    "package": {
      "type": "string",
      "minLength": 1,
      "maxLength": 214
    },
    "version": {
      "type": "string",
      "maxLength": 64
    }
  },
  "required": [
    "package"
  ],
  "additionalProperties": false
}

Example request

{
  "package": "hono",
  "version": "4.13.3"
}

Example output

{
  "package": "hono",
  "version": "4.13.3",
  "license": "MIT",
  "deprecated": false,
  "vulnerabilities": 0,
  "published_at": "2026-08-19T00:00:00.000Z"
}

x402 flow

POST /v1/npm-package-intel
→ HTTP 402 + PAYMENT-REQUIRED
→ buyer authorizes locally
→ retry same request with PAYMENT-SIGNATURE
→ one governed execution + machine-readable JSON

Discovery: OpenAPI · x402 · llms.txt

A valid 402/payability probe is operational evidence, not proof of independent demand, future settlement, or semantic correctness.