# Dependency Vulnerability Check (OSV) for npm, PyPI, Go, Maven (`implementable_antler/dependency-vuln-check`) Actor

Paste package@version pins or a requirements.txt / package.json; get known vulnerabilities, malicious-package flags, severity and fixed versions per package from the OSV.dev database. Built for agents and CI.

- **URL**: https://apify.com/implementable_antler/dependency-vuln-check.md
- **Developed by:** [Blake Runckel](https://apify.com/implementable_antler) (community)
- **Categories:** Developer tools, AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 package checkeds

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?

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

## Dependency Vulnerability Check (OSV): npm, PyPI, Go, Maven, Cargo and more

Give it a list of pinned packages, or paste a `requirements.txt` or `package.json`. For each package@version it returns the known vulnerabilities from the [OSV.dev](https://osv.dev) database: OSV/GHSA/CVE IDs, severity, versions that fix each issue, and a flag for **known-malicious packages** (OpenSSF `MAL-` records). One row per package, JSON-ready for agents, CI jobs and LLM tool calls.

### Input

| Field | Description |
|---|---|
| `packages` | One per line: `ecosystem:name@version`. Examples: `npm:lodash@4.17.20`, `pypi:requests==2.19.0`, `go:github.com/gin-gonic/gin@v1.6.0`, `maven:org.apache.logging.log4j:log4j-core@2.14.1`, `crates.io:time@0.1.0`. |
| `defaultEcosystem` | Used for lines without a prefix. |
| `requirementsTxt` | Optional. Only pinned `name==version` lines are checked. |
| `packageJson` | Optional. `dependencies` and `devDependencies`. A range such as `^4.17.20` is checked **as the stated version 4.17.20**, not the version your lockfile resolved. |

Ecosystems: npm, PyPI, Go, crates.io, Maven, RubyGems, NuGet, Packagist, Pub, Hex, CRAN.

### Output (per package)

`ecosystem, name, version, vulnerable, vulnCount, maliciousPackage, highestSeverity, fixedVersions, highestFixedVersion, vulnsWithoutFixAbove, vulns[{id, aliases, summary, severity, fixedIn, published, modified, url, malicious}], checkedAt, source`

Lines that can't be parsed are not output or charged. They are listed in the run log and in the `UNPARSED` record of the run's key-value store.

### Limits, read before relying on this

- It checks **exactly the versions you give**. It does not resolve lockfiles or transitive dependencies. Use a lockfile (pinned versions) for the best results.
- `fixedIn` lists fixed versions above your version, taken from OSV ranges. A package can be on several release branches, so `highestFixedVersion` is the newest fix across them. It is not always the smallest safe upgrade.
- `severity` is the label that the source database gives (for example, GHSA's). Many records have none, and then it is `null`. No severity is inferred.
- No result means no record in OSV. It does not mean the package is safe.
- Linux distribution feeds (Ubuntu, Chainguard/Wolfi) are excluded because of their licences (ShareAlike / NonCommercial-NoDerivatives).

### Pricing

Pay per event: **$0.003 per package checked** (one dataset row), plus Apify's standard tiny Actor-start event. Unparsed lines are free.

### Source and terms

Data comes from the public OSV.dev API (https://api.osv.dev, run by Google; its docs say it has no rate limits). OSV has no single licence. Each record keeps its source's licence, mostly CC-BY 4.0 (GitHub Advisory Database, PyPI, Go, OSS-Fuzz) and otherwise CC0, MIT or Apache-2.0 (https://google.github.io/osv.dev/data/). Each result links to its record on osv.dev for attribution. Summaries are cut to 200 characters, and the full advisory text is not copied. This Actor is not affiliated with or endorsed by Google, OSV or GitHub.

Built by Ledger. Issues and requests go to the Issues tab.

# Actor input Schema

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

One per line: ecosystem:name@version (e.g. npm:lodash@4.17.20, pypi:requests==2.19.0, go:github.com/gin-gonic/gin@v1.6.0, maven:org.apache.logging.log4j:log4j-core@2.14.1). Without a prefix the default ecosystem is used.

## `defaultEcosystem` (type: `string`):

Used when a line has no ecosystem: prefix.

## `requirementsTxt` (type: `string`):

Paste a requirements.txt. Only pinned lines (name==version) are checked.

## `packageJson` (type: `string`):

Paste a package.json. Only exact or ^/~ versions are checked (as the stated version).

## `maxPackages` (type: `integer`):

Safety cap per run.

## Actor input object example

```json
{
  "packages": [
    "npm:lodash@4.17.20",
    "pypi:requests==2.19.0",
    "maven:org.apache.logging.log4j:log4j-core@2.14.1"
  ],
  "defaultEcosystem": "npm",
  "maxPackages": 500
}
```

# 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": [
        "npm:lodash@4.17.20",
        "pypi:requests==2.19.0",
        "maven:org.apache.logging.log4j:log4j-core@2.14.1"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("implementable_antler/dependency-vuln-check").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@4.17.20",
        "pypi:requests==2.19.0",
        "maven:org.apache.logging.log4j:log4j-core@2.14.1",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("implementable_antler/dependency-vuln-check").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@4.17.20",
    "pypi:requests==2.19.0",
    "maven:org.apache.logging.log4j:log4j-core@2.14.1"
  ]
}' |
apify call implementable_antler/dependency-vuln-check --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,implementable_antler/dependency-vuln-check"
        }
    }
}
```

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/ACCpjiAFx4nj4WRIM/builds/bex1ctlmxBBj81RfI/openapi.json