# PyPI Package Metadata — Version, Licence and Requires-Python (`alaudinburki/pypi-packages`) Actor

A Python package's metadata from PyPI as a flat row — latest version, summary, licence, the Python versions it supports, homepage and repository, and how many releases it has. Free public PyPI API, no key.

- **URL**: https://apify.com/alaudinburki/pypi-packages.md
- **Developed by:** [alaudin burki](https://apify.com/alaudinburki) (community)
- **Categories:** Developer tools
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## PyPI Package Metadata — Version, Licence and Requires-Python

Source: the Python Package Index. Free, no key. Built 2026-10-18 for Phase 37, from the open doors in `plan/ACTOR-BUILD-PROGRAM.md` and the unbuilt rows of `plan/MASTER-TRACKER.md`.

### What you get

`name`, `latestVersion`, `summary`, `author`, `authorEmail`, `licence`, `requiresPython`, `homepage`, `keywords`, `classifiers`, `sourceUrl`, `documentationUrl`, `isYanked`, `requires`, `releaseCount`, `newestFileName`, `newestSizeBytes`, `newestUploadedAt`, `id`.

### Sample output

```json
{ "id": "pypi:requests", "name": "requests", "latestVersion": "2.34.2",
  "licence": "Apache-2.0", "requiresPython": ">=3.8", "isYanked": false,
  "releaseCount": 160 }
```

### Limitations — read before buying

- **One package per run**, by design: PyPI's document is per project, and flattening its `releases` map would produce many rows with nothing to tell them apart. Batch by running it over a list.
- **The LATEST version only**, which is not always the one you should pin — `releaseCount` and `isYanked` are there so that judgement is possible.
- **`isYanked` matters more than it looks.** A yanked release is not deleted, so a naive version check still sees it; this flag is the only thing that says it is unusable.
- **`licence` is free text from the package metadata**, frequently `null` or a classifier-only value. The authoritative licence is in the classifiers list.
- **`requires` is the declared dependency list**, joined. It is what the package ASKS for, not the resolved lock file.
- **`requiresPython` is an expression string** (`>=3.8`), returned as written rather than parsed.

### Pricing

Pay per result — charged for rows returned, not for the run.

### Fields

| Field | Type | What it holds |
|---|---|---|
| `name` | string | Display name as the source writes it. |
| `latestVersion` | string | Most recent version published upstream. |
| `summary` | string | Short human-readable summary of this row. |
| `author` | string | Display name of the reviewer. A display name, not a verified identity. |
| `authorEmail` | string | Author email as the package declares it. Often the maintainer's, and sometimes absent. |
| `licence` | string | Licence the source publishes under, as written by the source. Not a legal opinion. |
| `requiresPython` | string | The Python versions the package declares support for, as an expression string, e.g. >=3.8. Returned as written rather than parsed. |
| `homepage` | string | Homepage of the organisation or project. |
| `keywords` | string | Keywords, joined into one string. |
| `classifiers` | string | The package's classifier list as published, joined. It is where Development Status and the supported Python versions are actually stated. |
| `sourceUrl` | string | The page or endpoint this row was read from. |
| `documentationUrl` | string | Link to the package's documentation, where the source declares one. |
| `isYanked` | boolean | Whether the maintainer yanked this release. A yanked version is NOT deleted, so a naive version check still sees it — this flag is the only thing that says it is unusable. |
| `requires` | string | The runtime dependencies as declared, joined. What the package ASKS for, not a resolved lock file. |
| `releaseCount` | number | How many releases the project publishes. |
| `newestFileName` | string | Filename of the newest uploaded artefact — what a plain install actually fetches. |
| `newestSizeBytes` | number | Size of the newest uploaded artefact, in BYTES. |
| `newestUploadedAt` | string | When the newest artefact was uploaded, as ISO-8601. |

### What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in
an answer or a comparison.

- PyPI Package Metadata — Version, Licence and Requires-Python declares all 18 of its output fields in its dataset schema, each with a type, a written description and an example value.
- The output fields of PyPI Package Metadata include name, latestVersion, summary, author, authorEmail and licence.
- PyPI Package Metadata needs no API key, login or account of any kind before its first run.
- Every one of PyPI Package Metadata's 3 inputs is optional, so it runs with no configuration at all.
- PyPI Package Metadata documents `summary` as: Short human-readable summary of this row.
- Every number published about PyPI Package Metadata is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
- PyPI Package Metadata is filed under business and developer tools so that it is found by the people looking for that job, not by its internal name.

### FAQ

**What does PyPI Package Metadata return?**

It returns 18 documented output fields — `name`, `latestVersion`, `summary`, `author`, `authorEmail`, `licence`, `requiresPython` and `homepage` — each with a declared type and a written description. The full schema is below.

**What does PyPI Package Metadata require to run?**

Nothing. All 3 inputs are optional and ship with working defaults.

**Does PyPI Package Metadata need an API key?**

No. It reads only public data and asks for no account.

**How is PyPI Package Metadata billed?**

Per result returned, on Apify. A run that returns nothing costs nothing. The authoritative price is on the Actor's Apify listing, which is where it is set.

# Actor input Schema

## `package` (type: `string`):

The distribution name on PyPI, e.g. requests.

## `maxItems` (type: `integer`):

Stop after this many rows.

## `maxPages` (type: `integer`):

Stop after this many pages.

## Actor input object example

```json
{
  "maxItems": 1000,
  "maxPages": 10
}
```

# Actor output Schema

## `results` (type: `string`):

One row per item, with the 18 fields listed under Views.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "maxItems": 1000,
    "maxPages": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("alaudinburki/pypi-packages").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "maxItems": 1000,
    "maxPages": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("alaudinburki/pypi-packages").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "maxItems": 1000,
  "maxPages": 10
}' |
apify call alaudinburki/pypi-packages --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,alaudinburki/pypi-packages"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/tmzBJWUKMSIMxuiKS/builds/i5MMGwZH3zmp8O4j9/openapi.json