PyPI Scraper: Python Package Details and Stats

PyPI Package Tracker: Metadata + Stats

Snapshot PyPI package metadata using the public pypi.org/pypi/<pkg>/json endpoint. One row per package: version, classifiers, requires_python, maintainers, project URLs, and release count. No authentication required.

---

Example output row

{
  "snapshotAt": "2026-06-03T17:10:00+00:00",
  "name": "requests",
  "latestVersion": "2.32.3",
  "summary": "Python HTTP for Humans.",
  "author": "<author name>",
  "license": "Apache 2.0",
  "homepage": "https://requests.readthedocs.io",
  "projectUrls": {
    "Documentation": "https://requests.readthedocs.io",
    "Source": "https://github.com/psf/requests"
  },
  "requiresPython": ">=3.8",
  "classifiers": [
    "License :: OSI Approved :: Apache Software License",
    "Programming Language :: Python :: 3"
  ],
  "keywords": "http client requests",
  "releaseCount": 142
}

---

How to use

Input schema

Field	Type	Default	Description
packages	string[]	["requests","numpy","pandas"]	PyPI package names to snapshot

Minimal input example

{
  "packages": ["httpx", "pydantic", "fastapi"]
}

Pass any number of package names. Packages that return 404 (deleted or misspelled) are silently skipped: they do not count as a billed row.

---

Pricing

Pay per event. Price per 1,000 events:

Event	Base price	Bronze	Silver	Gold
PyPI package snapshot	$0.20	$0.18	$0.16	$0.14

Bronze, Silver and Gold are the discounts Apify gives users of its paid plans. The Pricing tab always shows the current prices.

---

Buyer

• Python developers tracking dependency metadata across a project's requirements tree.
• Security teams auditing requires_python constraints and classifier flags across an internal package inventory.
• OSS analysts monitoring version cadence and release counts for ecosystem health reports.
• Data engineers building pip-audit pipelines or license-compliance dashboards.
• Researchers collecting classifier and keyword distributions across the PyPI corpus.

---

Run it through the API

Python, with the apify-client package:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("v0iddo/pypi-package-tracker").call(run_input={"packages": ["requests", "numpy", "pandas"]})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

JavaScript, with the apify-client package:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('v0iddo/pypi-package-tracker').call({"packages": ["requests", "numpy", "pandas"]});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

One HTTP call that waits for the run and returns the rows (for runs that finish within 5 minutes):

curl -X POST "https://api.apify.com/v2/acts/v0iddo~pypi-package-tracker/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"packages": ["requests", "numpy", "pandas"]}'

Output fields, real sample rows, the price and this code for Python, JavaScript and cURL are also in the guide to this actor.

Use it from an agent (MCP)

Claude, Cursor, VS Code and other MCP clients can call this actor as a tool through the Apify MCP server. Add it to the client's MCP configuration:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=v0iddo/pypi-package-tracker",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

FAQ

Do I need an account, cookies or an API key?

No. The actor reads public data without logging in. You only need an Apify account to start it.

How am I charged?

Pay per event, at the prices on the Pricing tab for your Apify plan (the Pricing section of this page lists them). The platform usage of the run is included in those prices, and your spending limit for a run is always respected.

Why did my run return no results?

The status message and the log of the run say why: usually nothing matched the input, or the source did not answer for a moment. Check the input against the example above and run it again.

Can I run it on a schedule?

Yes. Save your input as a task and add a schedule in the Apify Console (daily, hourly or with a cron expression). Each run gets its own dataset, so you keep a history.

Which formats can I export?

JSON, CSV, Excel, XML, HTML table and RSS from the Output tab or the API. Integrations send the rows to Google Sheets, Slack, Make, Zapier, n8n or a webhook.

Is collecting this data allowed?

The actor collects data that the source publishes openly, without a login. Public data can still be personal data under laws such as the GDPR, and sources have their own terms: make sure your use of the data follows the rules that apply to you.

What happens when the source changes?

An automated test runs the actor every day on the example input and checks the rows, not only that the run finished. When a check fails, the actor is repaired and rebuilt; the build history on this page shows each update.

Something is missing or wrong. Where do I report it?

Open an issue on the Issues tab of this actor with the run link. Requests for a new field are welcome too.

Related actors

• npm Package Stats Scraper: Metadata and Downloads
• GitHub Trending Scraper: Repos by Language and Period
• GitHub Security Advisories Scraper by Ecosystem
• NVD CVE Scraper: Vulnerabilities by Vendor and Severity
• Chrome Web Store Scraper: Extension Details and Ratings
• Bulk File Downloader and Image Downloader: Web Pages, PDFs

Source

Data is fetched from the official PyPI JSON API:

GET https://pypi.org/pypi/{package}/json

No authentication. Rate-limited to one request every 250 to 600 ms (polite crawler policy). PyPI's terms of service permit programmatic metadata access for non-abusive use.