# Package Registry Monitor - npm, PyPI, crates.io (`sbr35/package-registry-monitor`) Actor

Input: packages as npm:react, pypi:requests or crates:serde. Output: latest version, release date, licence, maintainers, dependency count and an abandonment flag. Use when you need to check whether a dependency is current, maintained or stale.

- **URL**: https://apify.com/sbr35/package-registry-monitor.md
- **Developed by:** [Alexandre de La Fayette](https://apify.com/sbr35) (community)
- **Categories:** Developer tools, Automation, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 packages

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Package Registry Monitor

Track open-source packages across **npm, PyPI and crates.io** with one schema and one run.

Reads each registry's official public JSON API — documented, unauthenticated endpoints built
for exactly this. No scraping, no API keys, no rate-limit games.

### What you get

One row per package:

| Field | Description |
|---|---|
| `name` / `registry` | Package name and which registry it came from |
| `latestVersion` | Current published version |
| `releasedAt` | When that version shipped |
| `firstReleasedAt` | When the package first appeared |
| `daysSinceRelease` | Days since the newest release |
| `isStale` | True if it has not shipped inside your threshold |
| `license` | Declared licence |
| `repository` / `homepage` | Normalised source and project links |
| `maintainers` / `maintainerCount` | Who publishes it — bus-factor signal |
| `dependencies` | Direct dependency count |
| `versionCount` | Total released versions |
| `deprecated` | Registry-flagged deprecation |
| `keywords` | Declared keywords |
| `versionHistory` | Last 10 releases with dates (optional) |
| `downloads` | Total and recent downloads (crates.io) |

### Input

```json
{
  "packages": ["npm:react", "pypi:requests", "crates:serde"],
  "includeVersionHistory": true,
  "staleAfterDays": 365
}
```

| Option | Default | What it does |
|---|---|---|
| `packages` | required | `registry:name`. Aliases accepted: `node`→npm, `pip`/`python`→pypi, `rust`→crates |
| `includeVersionHistory` | `true` | Attach the last 10 releases with dates |
| `staleAfterDays` | 365 | Days before a package is flagged stale |

Scoped npm packages work as-is: `npm:@types/node`.

### Who this is for

- **Security and platform teams** auditing dependencies for abandonment. `isStale`,
  `maintainerCount` and `deprecated` together are a decent bus-factor signal.
- **Engineering managers** tracking whether critical dependencies are still maintained.
- **Investors and analysts** measuring release cadence across an ecosystem.
- **Developer-tool companies** monitoring competitor packages.
- **Anyone** who wants npm, PyPI and crates.io in one schema instead of three APIs.

### Honest limits

- `dependencies` counts **direct** dependencies only, not the full transitive tree.
- crates.io does not expose maintainers through this endpoint, so `maintainers` is empty there.
- PyPI licence data is inconsistent across packages — it falls back to classifiers, but some
  projects declare neither.
- Download counts are only available from crates.io. npm and PyPI serve those from separate
  endpoints not included here.

### Pricing

Pay per event. Charged per package successfully resolved. A failed lookup costs nothing.

### Changelog

**1.0** — First release. npm, PyPI and crates.io with staleness detection.

# Actor input Schema

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

Packages to look up, as registry:name. Supported registries: npm, pypi, crates. Examples: npm:react, pypi:requests, crates:serde

## `includeVersionHistory` (type: `boolean`):

Add the last 10 released versions with their dates, useful for tracking release cadence.

## `staleAfterDays` (type: `integer`):

Mark a package as stale if its newest release is older than this many days. Useful for spotting abandoned dependencies.

## Actor input object example

```json
{
  "packages": [
    "npm:react",
    "pypi:requests",
    "crates:serde"
  ],
  "includeVersionHistory": true,
  "staleAfterDays": 365
}
```

# Actor output Schema

## `packages` (type: `string`):

Version, licence, maintainers, dependencies and staleness for each package.

## `packagesCsv` (type: `string`):

The same data as a spreadsheet-ready CSV.

# 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:react",
        "pypi:requests",
        "crates:serde"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("sbr35/package-registry-monitor").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:react",
        "pypi:requests",
        "crates:serde",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("sbr35/package-registry-monitor").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:react",
    "pypi:requests",
    "crates:serde"
  ]
}' |
apify call sbr35/package-registry-monitor --silent --output-dataset

```

## MCP server setup

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

```

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/71ne1omI542csGiGY/builds/fOyHNv0h2kdO8yGxx/openapi.json