PyPI Package Release Monitor - Versions & Yanked Files

SOURCE COVERAGE & PRACTICAL LIMITS

Full product guide

Documentation captured from build 1.0.1. Example outputs retain their original sample context; they are not live results.

PyPI Package Release Monitor - Versions & Yanked Files

Compare versions, declared Python requirements and exact file hashes while retaining per-file yanked flags.

Track current PyPI releases, Python requirements, distribution hashes and yanked-file flags. Saved comparisons and readable reports for package watchlists. No packages downloaded or executed.

Start in under a minute

1. Paste python packages into the first input field, or use the included sample.
2. Keep the five-result limit for your first run and choose Start.
3. Open Observations, Scope and diagnostics, or the Readable run report in Output. Export CSV or JSON from the dataset.

{
  "packages": [
    "requests"
  ],
  "maxResults": 5
}

No source account, API key, paid proxy or extra subscription is required for these public endpoints. Source availability and rate limits still apply.

Who this helps

Python teams and AI tooling maintainers watching release and compatibility metadata.

What you receive

One row per unique confirmed observation. Every row includes a stable recordId, title, source URL and observation time.

Saved comparisons

Enable Compare with saved observations, choose a snapshot name, and reuse the same input scope. The first run establishes history; it cannot report changes before that point. Enable Save only new or changed observations for later runs if you want a change-only export. An unchanged run can correctly save zero rows.

Only confirmed saved rows advance history. A bounded or failed run never establishes that a missing record was deleted. History is stored in a named key-value store in the running user's account. Use one writer per snapshot: do not overlap runs against the same snapshot. Change the snapshot name when starting a new independent workflow.

Scope and limitations

Current release returned by PyPI JSON, not every historic release. Yanked flags are per distribution file. Metadata is not a security audit, dependency resolver or download-count estimate.

At most ten input values and thirty saved rows per run. Each input performs one bounded public API request. Responses are capped at 8 MiB and share the run deadline. No authentication bypass, image/package download or code execution is performed. HTTP 429 stops further requests; Stack Exchange backoff/quota signals are respected. Source failures appear in SUMMARY and the HTML report, never as paid data rows.

Pricing

The configured base price is $0.001 per saved observation, plus $0.00005 per start at the default memory. Five observations cost $0.00505 at that base rate. Applicable plan discounts and the Store pricing panel govern actual charges. Set a maximum charge in Run options. Diagnostics, reports and unchanged skipped rows are not dataset result events.

Make it recurring

Save an Actor task with your inputs, then attach an Apify Schedule. For change detection, keep the same snapshot and avoid overlapping runs. Add an integration to deliver results to your own spreadsheet or workflow. No external delivery is enabled automatically.

Examples

1. Python packages: requests — A bounded requests observation sample. Review source evidence and export rows or compare them in a later run.
2. Python packages: fastapi — A bounded fastapi observation sample. Review source evidence and export rows or compare them in a later run.
3. Python packages: pydantic — A bounded pydantic observation sample. Review source evidence and export rows or compare them in a later run.

Source and support

Official source documentation. This independent Mayd IT tool is not affiliated with the source platform. Open an Actor issue with the run ID and expected result, or contact bmay@mayd-it.com. Never include credentials.