dependency-go-no-go

Dependency approval decision for coding agents: decide whether an npm dependency or package is safe to install or adopt and return GO, WARN, or BLOCK using vulnerabilities, security, license, maintenance, deprecation, and package metadata.

Price: $0.20 USDC equivalent
Endpoint: POST /v1/dependency-go-no-go
Network: Base mainnet · eip155:8453
Asset: USDC
MCP tool: dependency-go-no-go
External payability: PASS · 2026-10-08T19:55:01.298Z

When an agent should use it

should I install this npm dependency
decide whether this package is safe to adopt
dependency approval decision for a coding agent
check vulnerabilities maintenance and license before adding a dependency

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

{
  "verdict": "GO",
  "reasons": [
    "No OSV vulnerabilities returned",
    "License declared",
    "Recent publication activity"
  ],
  "evidence": {
    "package": "hono",
    "version": "4.13.3",
    "license": "MIT",
    "vulnerabilities": 0
  },
  "policy_version": "salt19-dependency-policy-v1"
}

x402 flow

POST /v1/dependency-go-no-go
→ 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.