# SALT19 Dependency Go/No-Go Checker

> SALT19 Dependency Go/No-Go Checker is a paid API for AI agents from api.salt19.com, paid per call via x402, $0.2/call, status unknown (last checked 2026-09-15).

Evaluates an npm/software package and version against vulnerability, license, and activity policies and returns a GO or NO-GO verdict with supporting evidence.

## Facts

- Endpoint: POST https://api.salt19.com/v1/dependency-go-no-go
- Price: $0.2/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-9a442348
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_E2XI1QteM-18bb-QgDwNG

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-9a442348 -d '<json body>'
```

Example prompt: Run a go/no-go dependency check on hono version 4.13.3 — I need to know if it has any vulnerabilities, what its license is, and whether it's been recently maintained.

## When to prefer this

Use this endpoint when you need a structured, policy-backed GO/NO-GO verdict on a software package rather than raw vulnerability data alone. It is ideal for automated dependency gates in CI/CD pipelines, agent-driven code review, or any workflow requiring a single authoritative decision combining vulnerability, license, and maintenance signals under a versioned policy. Prefer this over manually querying OSV or npm registries when you want a normalized, actionable verdict without post-processing.

## Known failure modes

- Unknown or misspelled package name returns an error or NO-GO with no evidence
- Invalid or malformed version string may return a validation error
- Package not found in the vulnerability or registry database may result in incomplete evidence
- Rate limiting or payment failure (x402) results in 402 response and no verdict
- Network timeouts if upstream OSV or registry APIs are slow

## How this service works

SALT19 is an independent applied AI systems lab behind EvoMind governed cognition, the MCP-native Agent Utility Grid, the ARCS research community, AeroClear UAS flight intelligence, and practical software for real-world work.

## Output

A JSON object containing: a 'verdict' field ('GO' or 'NO-GO'), a 'reasons' array explaining the decision (e.g. vulnerability status, license presence, publication activity), an 'evidence' object with the package name, version, resolved license, and vulnerability count, and a 'policy_version' string identifying the policy applied.

## 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-9a442348/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.salt19.com](https://www.zero.xyz/host/api.salt19.com/llms.txt)