# node-fetch OSV Advisory Fixed-Version Boundaries

> node-fetch OSV Advisory Fixed-Version Boundaries 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 the fixed-version boundaries from OSV advisories for the npm package node-fetch, given an exact or latest version.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/signal-osv-npm-node-fetch-fix-versions?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/node-fetch-osv-advisory-fixed-version-boundaries-f395f40e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7EcIrT2ksfF_-mRD5Mcw2

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 node-fetch-osv-advisory-fixed-version-boundaries-f395f40e -d '<json body>'
```

Example prompt: What are the OSV advisory fixed-version boundaries for node-fetch version 2.6.1? I want to know which versions resolve known vulnerabilities for that npm package.

## When to prefer this

Use this endpoint when you specifically need OSV-sourced fixed-version boundary data for the node-fetch npm package. Prefer this over generic vulnerability scanners when you need structured, machine-readable fix-version ranges for automated dependency auditing or CI gating scoped to node-fetch only.

## Known failure modes

- Invalid or unrecognized version string returns an error or empty result
- Package name mismatch (endpoint is scoped solely to node-fetch)
- Network or upstream OSV API unavailability returns a timeout or 5xx error
- Paginated results may require use of page_token for full data retrieval
- 'latest' version resolution may fail if npm registry is unreachable

## How this service works

node-fetch Advisory fixed-version boundaries: Advisory fixed-version boundaries for npm package node-fetch, from OSV. Accepts an exact version; latest resolves the registry version. Scope is the named package only.

## Output

Returns structured advisory records from OSV indicating the version boundaries at which known vulnerabilities in node-fetch are considered fixed, including lower and upper version bounds for each advisory.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "package": {
   "type": "string",
   "default": "node-fetch",
   "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/node-fetch-osv-advisory-fixed-version-boundaries-f395f40e/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)