# TypeScript NPM Package Advisory Severity Breakdown

> TypeScript 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-21).

Returns a breakdown of open-source vulnerability advisory severities for a specific version of the npm package 'typescript', sourced from the OSV (Open Source Vulnerabilities) database.

## Facts

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

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 typescript-npm-package-advisory-severity-breakdown-23f8b467 -d '<json body>'
```

Example prompt: Can you pull the OSV advisory severity breakdown for typescript version 5.3.3 from npm so I can see how many critical, high, medium, and low vulnerabilities it has?

## When to prefer this

Choose this endpoint when you need a quick, structured severity summary of vulnerabilities specifically for the 'typescript' npm package from OSV. It is ideal for automated security checks, CI/CD gates, or developer audits focused on TypeScript. Prefer it over raw OSV API calls when you want a pre-scoped, pay-per-call result without managing authentication or query construction.

## Known failure modes

- Invalid version string returns an error or empty result
- Requesting an unpublished or nonexistent typescript version may return no advisories
- Rate limiting or payment failure (x402) blocks the request
- Page token mismatch causes pagination errors
- Network timeout if OSV upstream is slow

## How this service works

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

## Output

Returns a breakdown of security advisories for the specified typescript npm package version, organized by severity level (e.g., critical, high, medium, low), sourced from the OSV database. Includes advisory counts per severity tier and may support pagination for large result sets.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "package": {
   "type": "string",
   "default": "typescript",
   "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/typescript-npm-package-advisory-severity-breakdown-23f8b467/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)