# npm & PyPI Package Data API: Versions, License, Downloads (`lepidata/package-registry`) Actor

Look up npm and PyPI packages via the official public registry JSON APIs: latest version, license, repo links, publish dates and npm download counts. No author or maintainer emails.

- **URL**: https://apify.com/lepidata/package-registry.md
- **Developed by:** [Lepi Data](https://apify.com/lepidata) (community)
- **Categories:** Developer tools, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.20 / 1,000 package rows

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## npm & PyPI Package Data API: Versions, License, Downloads

**What it does.** Looks up npm and PyPI packages through the official public registry JSON APIs and returns one row per package: latest version, license, description, keywords, homepage, repository and issue links, version count, dependency count, publish dates and (npm) weekly/monthly downloads.

**Input**

- `packages`: names, one per line; prefix `npm:` or `pypi:` per name, or set `ecosystem` (npm, pypi, both). Scoped npm names (`@types/node`) work.
- `includeDownloads` (default on): npm download counts from api.npmjs.org.
- `maxItems`: up to 5,000.

**Output fields**
`ecosystem`, `name`, `latestVersion`, `description`, `license`, `keywords`, `homepage`, `repositoryUrl`, `bugsUrl`, `versionsCount`, `dependenciesCount`, `requiresPython`, `nodeEngine`, `deprecated`, `createdAt`, `latestPublishedAt`, `modifiedAt`, `downloadsLastWeek`, `downloadsLastMonth`, `packageUrl`
Free status rows (not charged): `no-results` (package not found), `invalid-input`, `api-error`, `free-plan-limit`, `charge-limit-reached`.
PyPI's JSON API publishes no download counts, so download fields are empty for PyPI rows.

**Example** (the build's prefill): `{"packages":["npm:lodash","pypi:requests"]}`

**Data source and compliance**

- Data from the npm public registry (registry.npmjs.org, api.npmjs.org) and the Python Package Index JSON API (pypi.org). Official JSON APIs only; no website pages are scraped.
- **Privacy:** author and maintainer names and email addresses are dropped entirely. Only a fixed list of package fields is returned.
- Independent Lepi Data tool, **not affiliated with or endorsed by npm, Inc., GitHub, the Python Software Foundation or PyPI**. No logos are used. npm is a trademark of npm, Inc.; "PyPI" and "Python" are trademarks of the PSF.
- About one request per second, with back-off on errors.
- Free-plan accounts get up to 100 results per run.

**Pricing.** Pay per package row, flat on every plan, no start fee. Free status rows are never charged.

# Actor input Schema

## `packages` (type: `array`):

Package names, one per line. Prefix with npm: or pypi: to pick the registry per name (e.g. pypi:requests); names without a prefix use Ecosystem. Scoped npm names like @types/node work.

## `ecosystem` (type: `string`):

Registry for names without an npm:/pypi: prefix. 'both' looks each name up on npm and on PyPI.

## `includeDownloads` (type: `boolean`):

Adds last-week and last-month downloads from the official npm downloads API. PyPI's JSON API publishes no download counts, so these stay empty for PyPI.

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

Maximum package rows to return (up to 5,000).

## Actor input object example

```json
{
  "packages": [
    "npm:lodash",
    "pypi:requests"
  ],
  "ecosystem": "npm",
  "includeDownloads": true,
  "maxItems": 100
}
```

# Actor output Schema

## `items` (type: `string`):

All rows from this run.

# 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 = {
    "packages": [
        "npm:lodash",
        "pypi:requests"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("lepidata/package-registry").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 = { "packages": [
        "npm:lodash",
        "pypi:requests",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("lepidata/package-registry").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 '{
  "packages": [
    "npm:lodash",
    "pypi:requests"
  ]
}' |
apify call lepidata/package-registry --silent --output-dataset

```

## MCP server setup

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

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/Gtt0coqr02KdgButE/builds/RJOS8rjGXFZ8NO2Ry/openapi.json