# SALT19 Dependency Go/No-Go Checker

> SALT19 Dependency Go/No-Go Checker is a paid API for AI agents from salt19-agent-utility-grid.salt19-llc.workers.dev, paid per call via x402, $0.25/call, status unknown (last checked 2026-09-15).

Evaluates an npm package and version against vulnerability and license policy to return a GO or NO-GO verdict for safe dependency adoption.

## Facts

- Endpoint: POST https://salt19-agent-utility-grid.salt19-llc.workers.dev/v1/dependency-go-no-go
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/salt19-dependency-go-no-go-checker-cc982179
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MR9gx38Gd4JcJ3eSxv7FD

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability salt19-dependency-go-no-go-checker-cc982179 -d '<json body>'
```

Example prompt: Before I add hono version 4.13.3 to my project, can you check if it's safe — look for vulnerabilities and confirm the license is acceptable, then give me a GO or NO-GO?

## When to prefer this

Choose this endpoint when an autonomous agent or CI pipeline needs a structured, policy-backed GO/NO-GO decision on an npm dependency — not just raw vulnerability data. It combines OSV vulnerability scanning and license checking into a single opinionated verdict, making it ideal for automated workflows that need a binary decision rather than raw data to interpret. Prefer it over generic vulnerability scanners when you want a consistent, versioned policy applied and a machine-readable verdict with reasons.

## Known failure modes

- Package not found in registry — may return an error or NO-GO with unknown-package reason
- Version string malformed or not found — validation error on input
- OSV or license data temporarily unavailable — may return indeterminate result or error
- Request body missing required 'package' field — schema validation error
- Payment not processed — x402 payment required error before evaluation runs

## How this service works

Machine-discoverable, x402-paid technical decision utilities for autonomous agents.

## Output

Returns a JSON object with a 'verdict' field ('GO' or 'NO-GO'), a list of 'reasons' explaining the decision, an 'evidence' object containing the package name, version, resolved license, and vulnerability count, and the 'policy_version' string used to evaluate the package.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "package": {
   "type": "string",
   "maxLength": 214,
   "minLength": 1
  },
  "version": {
   "type": "string",
   "maxLength": 64
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/salt19-dependency-go-no-go-checker-cc982179/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from salt19-agent-utility-grid.salt19-llc.workers.dev](https://www.zero.xyz/host/salt19-agent-utility-grid.salt19-llc.workers.dev/llms.txt)