PyPI Package Metadata Batch Export

Export latest-version metadata for supplied public Python package names, including declared license and Python requirements.

What can this tool do?

Create a Python dependency inventory with latest versions, declared licenses, requirements and release-file recency.

What data does it return?

The default dataset contains JSON rows with these overview fields: id, status, packageName, version, licenseDeclared, requiresPython, dependencies, latestFileUploadedAt, yanked, sourceUrl. RESULTS_CSV contains the rows delivered by this run; OUTPUT records completion, warnings and stop reason. CHECKPOINT supports best-effort resume. A completed checkpoint makes no new source request; use a fresh input without it for a fresh snapshot.

How to use it

Provide the source inputs below. Run it through Apify, then inspect OUTPUT before consuming a partial export. If a result or request cap is reached, reuse CHECKPOINT with the same source inputs; resuming does not repeat rows already acknowledged by this export. Source changes can still move search results between pages, so it is not a historical snapshot guarantee.

{
  "packages": [
    "requests",
    "urllib3"
  ],
  "maxResults": 2,
  "maxRequests": 2
}

Latest-version metadata is publisher supplied and may differ from package files. Unknown license/upload values remain null. There is no download-count estimate, package installation, vulnerability assessment, maintainer contact export or private-index access. Larger lists require a checkpoint after the per-run request cap.

Pricing

Runs can incur Apify charges. Check the current Store pricing and spending limit before starting. Result fees apply to successfully delivered records; package notFound status rows have no result fee, although a startup fee may still apply. No synthetic default-dataset charge is used in addition to the record event.

PyPI JSON endpoints are free; this Actor adds Apify dataset/storage output and bounded checkpoint-based runs.

Is it legal?

Uses the public JSON API, not package execution or website crawling. Project content remains subject to its licenses. No personal-contact export, tokens, spam use or rate-limit avoidance. No affiliation or endorsement is implied.

Source documentation: https://docs.pypi.org/api/json/ Policy/context: https://policies.python.org/pypi.org/Terms-of-Service/

FAQ

Does it retry blocks or bypass authentication? No. Source HTTP errors stop without retries; source hosts are fixed and redirects are not followed.

Are unknown values zero? No. Unavailable fields stay null or cause an explicit source error. Read the source-specific limits above.

Is the data exclusive? No. The official source is public and has a free native alternative.

Feedback

Use the Actor Issues tab with a small reproducible public example and the OUTPUT stop reason. Do not post tokens, personal records or confidential data.