# Django PyPI Vulnerability Disclosure Timeline

> Django PyPI Vulnerability Disclosure Timeline 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 the OSV vulnerability disclosure timeline for a specific version of the Django PyPI package, including dates and details of known security issues.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/signal-osv-pypi-django-timeline?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/django-pypi-vulnerability-disclosure-timeline-ac04b9c0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_w7EWes-GoqNzy97UuJnTy

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 django-pypi-vulnerability-disclosure-timeline-ac04b9c0 -d '<json body>'
```

Example prompt: Can you pull up the OSV vulnerability disclosure timeline for Django version 4.2.3 from PyPI so I can see what security issues have been reported against that release?

## When to prefer this

Choose this endpoint when you need structured, OSV-sourced vulnerability disclosure history specifically for the Django PyPI package by exact version. It is ideal for automated security audits, CI/CD pipelines checking dependency safety, or agents that need to verify whether a specific Django release has known CVEs before deployment. Prefer this over generic vulnerability search APIs when you want scoped, per-version data for Django without having to filter a broader dataset.

## Known failure modes

- Invalid or non-existent version string returns empty results or an error
- Package name override to a non-Django package may be rejected or return unexpected results
- 'latest' version resolution may fail if the PyPI registry is temporarily unreachable
- Pagination token mismatch or expiry can cause incomplete result sets
- Rate limiting or payment failure may prevent successful calls

## How this service works

django Vulnerability disclosure timeline: Vulnerability disclosure timeline for PyPI package django, from OSV. Accepts an exact version; latest resolves the registry version. Scope is the named package only.

## Output

Returns a paginated list of OSV vulnerability records for the specified Django version, including vulnerability IDs, disclosure dates, affected version ranges, severity details, and references to upstream security advisories.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "package": {
   "type": "string",
   "default": "django",
   "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/django-pypi-vulnerability-disclosure-timeline-ac04b9c0/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)