# Manifest to OSV Vulnerability Triage (`vedder1980/osv-manifest-triage`) Actor

Triages up to 500 dependency versions against the public OSV vulnerability database.

- **URL**: https://apify.com/vedder1980/osv-manifest-triage.md
- **Developed by:** [Daniel Ferreira de Almeida](https://apify.com/vedder1980) (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/actors/running/actors-in-store.md#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

## Manifest to OSV Vulnerability Triage

Turn a bounded list of package versions or dependency manifests into structured vulnerability findings from the [Open Source Vulnerabilities (OSV) database](https://osv.dev/).

### What it does

- Queries only the public OSV batch API; it does not clone repositories or inspect source code.
- Accepts explicit packages, npm `package-lock.json` v1+, exact Python `requirements.txt` pins, and explicit Maven `pom.xml` dependency versions.
- Emits one dataset item per OSV finding plus one final `summary` item.
- Deduplicates package/version/ecosystem combinations before querying OSV.

### Input

Use one or more input methods. The combined normalized dependency limit is **500**, and total text across manifest fields is **2 MiB**.

#### Explicit package records

```json
{
  "packages": [
    { "name": "lodash", "version": "4.17.20", "ecosystem": "npm" },
    { "name": "requests", "version": "2.31.0", "ecosystem": "PyPI" }
  ]
}
```

#### npm lockfile

```json
{
  "npmPackageLock": "{\n  \"lockfileVersion\": 3,\n  \"packages\": { ... }\n}"
}
```

#### Python requirements

```json
{ "requirementsTxt": "requests==2.31.0\nurllib3==1.26.5\n" }
```

Only exact `package==version` pins are queried. Ranges, editable installs, URLs and unpinned requirements are returned as parse warnings and are never sent to OSV.

#### Maven POM

```json
{
  "pomXml": "<project><dependencies><dependency><groupId>org.apache.logging.log4j</groupId><artifactId>log4j-core</artifactId><version>2.14.1</version></dependency></dependencies></project>"
}
```

Maven dependencies need explicit `groupId`, `artifactId`, and `version`. Property substitution such as `${version}`, inherited versions, and `dependencyManagement` resolution are not performed; property-based versions are reported as parse warnings and are never queried.

### Output

Finding records contain the package coordinate, OSV ID, aliases, summary, references, and affected ranges. Example finding:

```json
{
  "package": "lodash",
  "version": "4.17.20",
  "ecosystem": "npm",
  "osvId": "GHSA-example",
  "aliases": ["CVE-2026-0001"],
  "summary": "Example OSV finding",
  "references": [{ "type": "WEB", "url": "https://osv.dev/" }],
  "affected": []
}
```

The final dataset record is a summary:

```json
{
  "type": "summary",
  "recordCount": 5,
  "unresolvedPackageCount": 0,
  "parseWarningCount": 0
}
```

`recordCount` is the number of finding records emitted. `unresolvedPackageCount` is the number of OSV-query warnings, and `parseWarningCount` is the number of skipped or unsupported input entries. No findings means OSV returned no known matching vulnerabilities for the submitted versions at the time of the query; it does **not** mean the software is secure.

### Limits, privacy, and responsible use

- Maximum 500 normalized dependencies per run; total manifest text is capped at 2 MiB.
- Do **not** submit credentials, tokens, source code, private archives, personal data, or private repository details.
- The Actor sends only package name, version, and ecosystem to the public OSV API.
- Results are triage data, not a security certification, remediation plan, or legal advice. Verify findings and affected ranges before acting.

### Pricing and support

The Actor is currently free to run. It has no Pay-per-Event billing configured.

For reproducible bug reports, include a minimal non-sensitive input and the run ID. Do not include secrets in reports.

### Local development

```bash
npm ci
CRAWLEE_STORAGE_DIR=storage npm start
```

Place input at `storage/key_value_stores/default/INPUT.json`.

# Actor input Schema

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

Explicit package/version records for supported OSV ecosystems.

## `npmPackageLock` (type: `string`):

Optional npm package-lock.json content (lockfile v1 or later). Parsed alongside explicit packages; entries are deduplicated. Total manifest text across all fields is limited to 2 MiB.

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

Optional Python requirements.txt content. Only exact package==version pins are queried; other lines are reported as warnings. Total manifest text across all fields is limited to 2 MiB.

## `pomXml` (type: `string`):

Optional Maven pom.xml content. Dependencies with explicit groupId, artifactId and version are queried; property/version-management resolution is not performed, and property-based versions are reported as warnings. Total manifest text across all fields is limited to 2 MiB.

## Actor input object example

```json
{
  "packages": [
    {
      "name": "lodash",
      "version": "4.17.20",
      "ecosystem": "npm"
    }
  ]
}
```

# Actor output Schema

## `findings` (type: `string`):

Default dataset items: one record per OSV vulnerability plus a final summary record.

# 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",
            "version": "4.17.20",
            "ecosystem": "npm"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("vedder1980/osv-manifest-triage").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",
            "version": "4.17.20",
            "ecosystem": "npm",
        }] }

# Run the Actor and wait for it to finish
run = client.actor("vedder1980/osv-manifest-triage").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",
      "version": "4.17.20",
      "ecosystem": "npm"
    }
  ]
}' |
apify call vedder1980/osv-manifest-triage --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,vedder1980/osv-manifest-triage"
        }
    }
}

```

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/2wyWwxuC3Pp1qWfNv/builds/0oOi1QuTBkVF4xh9P/openapi.json