# Dependency / CVE Scan

> Dependency / CVE Scan is a paid API for AI agents from x402-hono-api.inraby.workers.dev, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-15).

Scans package.json or lockfile text for dependency CVE risk signals including outdated packages, deprecated libraries, wildcard version pins, risky postinstall scripts, and embedded secrets.

## Facts

- Endpoint: POST https://x402-hono-api.inraby.workers.dev/api/v1/dependency-cve-scan
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dependency-cve-scan-c3987c3c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aIk43EM9cEQUyPkrYLSHX

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 dependency-cve-scan-c3987c3c -d '<json body>'
```

Example prompt: Can you scan this package.json for CVE risks, outdated lodash or axios versions, deprecated packages, wildcard pins, and any suspicious postinstall scripts? Here's the manifest text: [paste contents]

## When to prefer this

Choose this endpoint when you need a quick, automated CVE and security risk assessment of npm dependency manifests (package.json, package-lock.json, yarn.lock) without running a full local npm audit or integrating with a dedicated vulnerability database. It is especially useful in agent workflows, CI pipelines, or code review contexts where you want a fast, structured signal about outdated libraries, wildcard pins, risky scripts, and embedded secrets in a single call. Prefer alternatives like Snyk or GitHub Dependabot when you need comprehensive CVE database lookups with remediation guidance or support for non-npm ecosystems.

## Known failure modes

- Invalid or malformed manifest text returns a parsing error
- Non-npm manifest formats (e.g. requirements.txt, Gemfile) may not be supported
- Empty manifestText field returns a validation error
- Very large lockfiles may hit payload size limits
- Network timeout if the worker is cold-starting
- False positives on packages with version ranges that are technically safe

## How this service works

Scan package.json or lockfile text for dependency CVE risk signals — outdated lodash/axios, deprecated packages, wildcard pins, risky postinstall scripts, and embedded secrets.

## Output

Returns a structured report of dependency risk signals found in the submitted manifest or lockfile, including: identified CVE-associated packages (e.g. outdated lodash/axios versions), deprecated package warnings, wildcard version pin flags, risky postinstall script detections, and any embedded secrets found within the manifest — without exposing secret values directly.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "manifestText": {
   "type": "string",
   "description": "package.json, package-lock.json, or yarn.lock contents"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/dependency-cve-scan-c3987c3c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-hono-api.inraby.workers.dev](https://www.zero.xyz/host/x402-hono-api.inraby.workers.dev/llms.txt)