# Malicious Package Watch — npm/PyPI Supply Chain Alerts (`0xgollum/malicious-package-watch`) Actor

Watch the open-source packages your codebase depends on and get alerted the moment a new security advisory (including typosquat/malicious package takedowns) is published for one - built on the free OSV.dev vulnerability database. Only new advisories are reported after the first baseline check.

- **URL**: https://apify.com/0xgollum/malicious-package-watch.md
- **Developed by:** [0xGollum](https://apify.com/0xgollum) (community)
- **Categories:** Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$20.00 / 1,000 new advisories

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/platform/actors/running/actors-in-store#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

## Malicious Package Watch — npm/PyPI Supply Chain Alerts

Watch the open-source packages your codebase depends on and get alerted the moment a new
security advisory is published for one — including typosquat and malicious-package takedowns,
not just ordinary CVEs. Run on a schedule; only advisories new since the last check are
reported, never the full advisory history dumped as "alerts" on the very first run.

### How it works

Consumes the free, no-auth public API of [OSV.dev](https://osv.dev) — Google's open-source
vulnerability database, which already aggregates advisories from GitHub Security Advisories,
PyPA, npm, RustSec, and other ecosystem-specific sources — and adds the part it doesn't offer:
a per-package watchlist with alert-only-on-new-advisory logic across scheduled runs. Verified
live against the real API (`api.osv.dev/v1/querybatch`) before shipping.

Checked against Apify Store before building (08/08/2026): no existing competitor does
scheduled diff-based monitoring of package advisories — the few related tools are one-off
scanners, not watch-and-alert.

### Input

- **Packages** (required) — list of `{"name": ..., "ecosystem": ...}` objects. Ecosystem:
  `npm`, `PyPI`, `Go`, `crates.io`, `Packagist`, `RubyGems`, `Maven`, or `NuGet`.
- **Request timeout**.

### Output

One row per newly published advisory: `package`, `vuln_id`, `summary`, `severity`,
`published`, `checked_at`.

### Known constraints

- Coverage depends entirely on what OSV.dev aggregates — it's broad but not exhaustive across
  every ecosystem.
- First-ever check for a package establishes a silent baseline (no rows) rather than dumping
  its historical advisories as if they just happened — alerts start from the second run onward.

# Actor input Schema

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

List of {"name": ..., "ecosystem": ...} objects. Ecosystem: npm, PyPI, Go, crates.io, Packagist, RubyGems, Maven, or NuGet. Run on a schedule - only advisories new since the last check are reported.

## `request_timeout_secs` (type: `integer`):

HTTP request timeout.

## Actor input object example

```json
{
  "packages": [
    {
      "name": "lodash",
      "ecosystem": "npm"
    },
    {
      "name": "requests",
      "ecosystem": "PyPI"
    }
  ],
  "request_timeout_secs": 20
}
```

# 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": [
        {
            "name": "lodash",
            "ecosystem": "npm"
        },
        {
            "name": "requests",
            "ecosystem": "PyPI"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("0xgollum/malicious-package-watch").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": [
        {
            "name": "lodash",
            "ecosystem": "npm",
        },
        {
            "name": "requests",
            "ecosystem": "PyPI",
        },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("0xgollum/malicious-package-watch").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": [
    {
      "name": "lodash",
      "ecosystem": "npm"
    },
    {
      "name": "requests",
      "ecosystem": "PyPI"
    }
  ]
}' |
apify call 0xgollum/malicious-package-watch --silent --output-dataset

```

## MCP server setup

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

```

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/IjnKGssuwAPOBzm1I/builds/xdf803JuZRZHNMAVk/openapi.json