# esbuild npm Package Advisory Severity Breakdown

> esbuild npm Package Advisory Severity Breakdown is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-17).

Returns a breakdown of OSV advisory severities (critical, high, medium, low) for a specific version of the esbuild npm package

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/signal-osv-npm-esbuild-severity?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/esbuild-npm-package-advisory-severity-breakdown-a43781c0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TwhOem1g8KAy0QSkZkZ8u

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 esbuild-npm-package-advisory-severity-breakdown-a43781c0 -d '<json body>'
```

Example prompt: Can you pull the OSV advisory severity breakdown for esbuild version 0.21.5 from the npm registry and tell me how many critical, high, medium, and low vulnerabilities it has?

## When to prefer this

Choose this endpoint when you specifically need OSV-sourced advisory severity counts for the esbuild npm package, particularly when you want a pre-parsed, structured severity breakdown rather than raw advisory text. Prefer this over general vulnerability scanners when the target is specifically esbuild and you need per-severity counts quickly. Not suitable for scanning other npm packages or for full CVE detail retrieval.

## Known failure modes

- Invalid or non-existent version string returns an error or empty result
- Package name overridden with non-esbuild value may yield unexpected results since scope is fixed to esbuild
- Network timeout or upstream OSV data unavailability
- Pagination token (page_token) invalid or expired causing failed continuation

## How this service works

esbuild Advisory severity breakdown: Advisory severity breakdown for npm package esbuild, from OSV. Accepts an exact version; latest resolves the registry version. Scope is the named package only.

## Output

Returns a structured breakdown of OSV security advisories for the specified esbuild npm package version, categorized by severity level (critical, high, medium, low), scoped only to the esbuild package itself. If 'latest' is specified as the version, the endpoint resolves the current registry version automatically.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "package": {
   "type": "string",
   "default": "esbuild",
   "maxLength": 150
  },
  "version": {
   "type": "string",
   "default": "latest",
   "maxLength": 100
  },
  "page_token": {
   "type": "string",
   "maxLength": 4000
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/esbuild-npm-package-advisory-severity-breakdown-a43781c0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from market.datapackvibe.com](https://www.zero.xyz/host/market.datapackvibe.com/llms.txt)