# NPM Package Update Tracker — New Versions & Deprecations (`m_ctim/npm-package-tracker`) Actor

Track new published versions and deprecation warnings for npm packages you depend on. Get the version, publish date, and deprecation status the moment it changes. For engineering and security teams monitoring dependencies without checking npm by hand.

- **URL**: https://apify.com/m\_ctim/npm-package-tracker.md
- **Developed by:** [Timothy Kelvin](https://apify.com/m_ctim) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

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

## 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

## NPM Package Update Tracker — New Versions & Deprecations

Track new published versions and deprecation warnings for npm packages
you depend on. Get the version, publish date, `latest` dist-tag status,
and deprecation message the moment something changes, without checking
npm by hand.

Built for engineering and security teams monitoring dependencies — a
signal `github-release-tracker` can miss, since not every npm publish
corresponds to a tagged GitHub release.

### Input

```json
{
  "packages": ["react", "@babel/core"],
  "daysBack": 30,
  "maxResultsPerPackage": 10
}
```

| Field | Type | Description |
|---|---|---|
| `packages` | array of strings | npm package names, including scoped packages (e.g. `"@babel/core"`). One lookup is billed per package. |
| `daysBack` | number | Only return versions published within this many days of today. Default `30`, max `365`. |
| `maxResultsPerPackage` | number | Max published versions to return per package, most recent first. Default `10`, max `50`. |

### Output

One record per published version:

```json
{
  "packageName": "react",
  "version": "19.2.8",
  "publishedAt": "2026-07-21T15:41:28.716Z",
  "isLatest": true,
  "versionDeprecationMessage": null,
  "packageDeprecationMessage": null,
  "tarballUrl": "https://registry.npmjs.org/react/-/react-19.2.8.tgz"
}
```

A package with no versions published in the requested window returns no
items but is still billed once for the lookup.

### How it works

Direct calls to the official [npm registry API](https://registry.npmjs.org/)
— the same registry `npm install` talks to. No proxy, no key, no scraping.

### Pricing note

Billed per **package checked**, not per version returned — one charge per
package whether it has 0 or 50 matching versions.

### Related products

- [GitHub Release Tracker](https://github.com/timmKal01/github-release-tracker) — new GitHub releases for repos you depend on, a related but distinct signal from npm publishes

# Actor input Schema

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

npm package names, e.g. "react" or a scoped package "@babel/core". One lookup is billed per package.

## `daysBack` (type: `integer`):

Only return versions published within this many days of today.

## `maxResultsPerPackage` (type: `integer`):

Maximum number of published versions to return per package, most recent first.

## Actor input object example

```json
{
  "packages": [
    "react"
  ],
  "daysBack": 30,
  "maxResultsPerPackage": 10
}
```

# Actor output Schema

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

No description

# 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": [
        "react"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("m_ctim/npm-package-tracker").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": ["react"] }

# Run the Actor and wait for it to finish
run = client.actor("m_ctim/npm-package-tracker").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": [
    "react"
  ]
}' |
apify call m_ctim/npm-package-tracker --silent --output-dataset

```

## MCP server setup

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

```

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/yNeHwvozQdG3cSPzs/builds/jjglsQ5XAgprNI5hP/openapi.json