# Strale Dependency Audit

> Strale Dependency Audit is a paid API for AI agents from api.strale.io, paid per call via x402, $0.054/call, status unknown (last checked 2026-09-15).

Audits software dependencies from package.json or requirements.txt, returning vulnerabilities and risk data with a cryptographic audit chain record.

## Facts

- Endpoint: GET https://api.strale.io/x402/v2/dependency-audit
- Price: $0.054/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/strale-dependency-audit-f129656a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_R25LDScfGaV8i3A9Js5Ec

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 strale-dependency-audit-f129656a
```

Example prompt: Can you audit the dependencies in my package.json for security vulnerabilities and give me a report? Here are the contents: {paste package.json}

## When to prefer this

Choose this endpoint when you need a verifiable, auditable dependency security scan with a cryptographic chain record — especially in compliance, regulated, or multi-stakeholder environments where proof of audit is as important as the findings themselves. Prefer it over generic vulnerability scanners when you need an immutable audit trail per scan.

## Known failure modes

- Missing or malformed package.json / requirements.txt content returns a validation error
- Empty or unparseable dependency file contents return a parse failure
- No dependencies found in the submitted file returns an empty findings result
- Network or upstream vulnerability database unavailability may cause lookup failures
- Exceeding payload size limits for very large dependency files

## How this service works

Audit npm or Python dependencies. Checks each package against registry for latest version, deprecation, vulnerabilities. Verifiable against actual registries.

## Output

Returns a structured audit report listing dependency vulnerabilities, risk levels, and package-level findings, along with a cryptographic audit record with chain hashing for provenance verification.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "package_json": {
   "type": "string",
   "description": "package.json contents"
  },
  "requirements_txt": {
   "type": "string",
   "description": "requirements.txt contents"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "summary": {
  "type": "object"
 },
 "ecosystem": {
  "type": "string"
 },
 "dependencies": {
  "type": "array"
 },
 "outdated_count": {
  "type": "integer"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/strale-dependency-audit-f129656a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.strale.io](https://www.zero.xyz/host/api.strale.io/llms.txt)