# Package Dependency Risk Scanner: npm & PyPI Vulnerabilities (`centorprat/package-dependency-risk-scanner`) Actor

Give it npm or PyPI package names. For each it reads the registry metadata and latest version (and npm download counts) and queries OSV.dev for known security advisories, then composes a risk brief: known vulnerabilities, deprecation, staleness and a signal. Keyless, agent-callable.

- **URL**: https://apify.com/centorprat/package-dependency-risk-scanner.md
- **Developed by:** [Centor Prat](https://apify.com/centorprat) (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 $17.00 / 1,000 package scanneds

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

## Package Dependency Risk Scanner: npm & PyPI Vulnerabilities

**Check a software package for problems before you depend on it.** Give npm or PyPI package names; for
each it reads the registry metadata (latest version, last publish, license, deprecation, npm weekly
downloads) and queries **OSV.dev** for known security advisories, then composes a risk brief with a clear
signal. Keyless, agent-callable, built to answer *"is this dependency vulnerable, deprecated, or
abandoned?"*

> 📋 **Advisories, not a verdict.** Vulnerabilities come from **OSV.dev** (official GHSA/CVE data) and are
> reported verbatim — a signal to review and verify against the source, not a judgement that a package is
> unsafe or advice not to use it.

### ⚡ Why it's useful

One call turns a dependency name into the three things that actually bite: **known CVEs/GHSAs**, whether
it's **deprecated**, and whether it's **stale/abandoned** — the answer, not raw registry JSON.

### 📋 What each brief contains

| Field | Meaning |
|---|---|
| `signal` | `known-vulnerabilities--review` / `deprecated` / `stale--check-maintenance` / `no-known-issues` |
| `vulnerabilities` | OSV advisories affecting the checked version: `id` (GHSA), `aliases` (CVE), `severity` (CVSS), `summary` |
| `vulnerabilityCount` | How many advisories affect the checked version |
| `checkedVersion` / `latestVersion` | The version queried (your version or latest) and the registry latest |
| `ageDaysSinceLastPublish` | Staleness signal |
| `deprecated` / `deprecatedReason` | Registry deprecation (npm) or yank (PyPI) |
| `weeklyDownloads` / `license` | npm weekly downloads and the declared license |

### 📥 Input

```json
{ "packages": ["lodash", "express@4.18.0", "pypi:requests", "npm:@babel/core"], "ecosystem": "npm" }
```

Prefix a name with `npm:` or `pypi:` to pick the ecosystem; add `@version` (npm) or `==version` (PyPI) to
check a specific version. One brief per package.

### 📤 Example output (real run, trimmed)

```json
{
  "ecosystem": "npm", "name": "lodash", "checkedVersion": "4.17.4", "latestVersion": "4.17.21",
  "signal": "known-vulnerabilities--review", "vulnerabilityCount": 10, "weeklyDownloads": 162267012,
  "vulnerabilities": [
    {"id": "GHSA-29mw-wpgm-hmr9", "severity": "CVSS:3.1/.../A:L", "summary": "Regular Expression Denial of Service (ReDoS) in lodash"},
    {"id": "GHSA-35jh-r3h4-6jhm", "severity": "CVSS:3.1/.../A:H", "summary": "Command Injection in lodash"}
  ]
}
```

In the same run `express` and `pypi:requests` returned `no-known-issues`, and `left-pad` came back
`deprecated` (last published ~8 years ago).

### 💰 Pricing (pay-per-event)

- **Package scanned — $0.02** per package found. Packages that don't resolve are free.

### 💡 Use cases

- **Developers / security / platform teams:** vet a dependency (or a list) for CVEs, deprecation and abandonment.
- **Due diligence / audits:** a fast risk read across a company's stated dependencies.
- **CI / agents:** callable as an MCP tool — feed package names, get back a risk signal.

### 🔑 Keyless & agent-callable

No API keys, no accounts, no paid child Actors — just the public npm registry, PyPI, and OSV.dev.

### 🚀 Ready-made tasks (one click)

- [npm Package Vulnerability Check - CVEs & Health](https://apify.com/centorprat/package-dependency-risk-scanner/examples/npm-package-vulnerability-check)

### 🤖 For AI agents (MCP)

```
https://mcp.apify.com/?tools=actors,docs,centorprat/package-dependency-risk-scanner
```

Loads as `centorprat--package-dependency-risk-scanner`. Claude Code:

```
claude mcp add apify -- npx -y @apify/actors-mcp-server --actors centorprat/package-dependency-risk-scanner
```

# Actor input Schema

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

e.g. \["lodash", "express@4.18.0", "pypi:requests", "npm:@babel/core"]. Prefix with npm: or pypi: to pick the ecosystem (else the default below); add @version (npm) or ==version (PyPI) to check a specific version. One brief per package.

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

Used for package names without an npm:/pypi: prefix.

## `webhookUrl` (type: `string`):

If set, the briefs are POSTed here as JSON when the run finishes.

## Actor input object example

```json
{
  "packages": [
    "lodash",
    "pypi:requests"
  ],
  "ecosystem": "npm"
}
```

# Actor output Schema

## `briefs` (type: `string`):

One brief per package: ecosystem, name, latest and checked version, last-publish date and age, license, deprecation, npm weekly downloads, the known vulnerabilities from OSV.dev (id, aliases, severity, summary), and a signal. Advisories reported verbatim.

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

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

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

```

## MCP server setup

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

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/P6QyvGwHJwWktxPr8/builds/rEws3GLcfdfbUfvW8/openapi.json