# CRA SBOM Audit (`eloquent_mountain/cra-sbom-audit`) Actor

Lockfile or SBOM in, CRA evidence pack out: OSV flaws, fixes, licence risk and Annex I mapping.

- **URL**: https://apify.com/eloquent_mountain/cra-sbom-audit.md
- **Developed by:** [Paco](https://apify.com/eloquent_mountain) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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

## CRA SBOM Audit

Lockfile or SBOM in, CRA evidence pack out: OSV flaws, fixes, licence risk and Annex I mapping.

### Who it's for

CTOs, engineering leads and compliance owners at software and connected-device makers who sell into the EU and need to show their dependency tree is under control before the Cyber Resilience Act applies in full on 11 December 2027 (Article 14 reporting already applies since 11 September 2026).

### What you get

Paste a package-lock.json, yarn.lock, pnpm-lock.yaml, uv.lock, poetry.lock, pinned requirements.txt, or a CycloneDX or SPDX JSON SBOM. You get an evidence pack, not a certificate:

- Every unique component checked against the OSV vulnerability database, results paged to the end, with the query time and the newest advisory date as a snapshot.
- One finding per distinct flaw (CVE and GHSA aliases merged), CVSS v3 score computed from the published vector, and the smallest fixed version above yours or "no fix published".
- VEX-style triage: affected, or proposed not affected for dev-only packages (you confirm).
- Licences read from your file or the npm and PyPI registries and classified for copyleft or restricted terms. Ambiguous or missing ones are flagged unresolved, never guessed.
- A remediation plan (fix now, schedule, no fix, licence review) and a mapping to CRA Annex I and Article 14 where each requirement is evidence provided, action needed or not assessed.
- Coverage counts: received, duplicates merged, answered, skipped, anything not fully read.

### Example

A lockfile with lodash 4.17.11 returns the critical prototype pollution advisory with CVSS 9.1 and the fix in 4.17.12, listed under fix now.

### Limits

Process duties (disclosure policy, update distribution, Article 14 reporting) cannot be shown by an inventory and are marked not assessed. Exploitation status is not checked. Not legal advice. Up to 2,000 unique components; yarn berry, Pipfile.lock and XML SBOMs are refused for free.

### How to use

- **Run it** in Apify Console or through the API: choose what to do, fill in the fields for that tool and start. The result is one item in the run's dataset.
- **From an AI assistant** through Apify's MCP server (mcp.apify.com), which finds and runs this Actor with the same fields. What each choice does:
  - `cra_requirements`: List the Cyber Resilience Act requirements this evidence pack maps to (Annex I Part I and II, Article 14) with their application dates, which of them an inventory can evidence and which are process duties it cannot show, plus the accepted input formats and licence classes.
  - `audit_inventory`: Audit a dependency lockfile or SBOM: every unique component is checked against the OSV vulnerability database (batch query, paged to the end), flaws are deduplicated by alias, scored from the published CVSS v3 vector, matched to the smallest fixed version, and triaged (affected, or proposed not affected for dev-only).

### Pricing

- CRA evidence pack for one lockfile or SBOM: $1.76
- Component assessed (first 1,000): $0.006
- Component assessed (1,001 to 2,000): $0.003

Failed calls are never charged.

# Actor input Schema

## `tool` (type: `string`):

cra_requirements: List the Cyber Resilience Act requirements this evidence pack maps to (Annex I Part I and II, Article 14) with their application dates, which of them an inventory can evidence and which are process duties it cannot show, plus the accepted input formats and licence classes. audit_inventory: Audit a dependency lockfile or SBOM: every unique component is checked against the OSV vulnerability database (batch query, paged to the end), flaws are deduplicated by alias, scored from the published CVSS v3 vector, matched to the smallest fixed version, and triaged (affected, or proposed not affected for dev-only).

## `content` (type: `string`):

Full text of package-lock.json, yarn.lock (v1), pnpm-lock.yaml, uv.lock, poetry.lock, requirements.txt (pinned), or a CycloneDX or SPDX JSON SBOM. Used by: audit_inventory.

## `filename` (type: `string`):

Optional original file name, used to tell formats apart. Used by: audit_inventory.

## `product` (type: `string`):

Optional product name for the report header. Used by: audit_inventory.

## `include_dev` (type: `boolean`):

Assess dev-only dependencies too; they are triaged as proposed not affected. Used by: audit_inventory.

## Actor input object example

```json
{
  "tool": "audit_inventory",
  "content": "{\"bomFormat\": \"CycloneDX\", \"specVersion\": \"1.5\", \"version\": 1, \"components\": [{\"type\": \"library\", \"name\": \"left-pad\", \"version\": \"1.3.0\", \"purl\": \"pkg:npm/left-pad@1.3.0\", \"licenses\": [{\"license\": {\"id\": \"WTFPL\"}}]}]}",
  "filename": "bom.json",
  "include_dev": true
}
```

# Actor output Schema

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

The tool result as a dataset item, shown in the overview view.

# 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 = {
    "content": "{\"bomFormat\": \"CycloneDX\", \"specVersion\": \"1.5\", \"version\": 1, \"components\": [{\"type\": \"library\", \"name\": \"left-pad\", \"version\": \"1.3.0\", \"purl\": \"pkg:npm/left-pad@1.3.0\", \"licenses\": [{\"license\": {\"id\": \"WTFPL\"}}]}]}",
    "filename": "bom.json"
};

// Run the Actor and wait for it to finish
const run = await client.actor("eloquent_mountain/cra-sbom-audit").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 = {
    "content": "{\"bomFormat\": \"CycloneDX\", \"specVersion\": \"1.5\", \"version\": 1, \"components\": [{\"type\": \"library\", \"name\": \"left-pad\", \"version\": \"1.3.0\", \"purl\": \"pkg:npm/left-pad@1.3.0\", \"licenses\": [{\"license\": {\"id\": \"WTFPL\"}}]}]}",
    "filename": "bom.json",
}

# Run the Actor and wait for it to finish
run = client.actor("eloquent_mountain/cra-sbom-audit").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 '{
  "content": "{\\"bomFormat\\": \\"CycloneDX\\", \\"specVersion\\": \\"1.5\\", \\"version\\": 1, \\"components\\": [{\\"type\\": \\"library\\", \\"name\\": \\"left-pad\\", \\"version\\": \\"1.3.0\\", \\"purl\\": \\"pkg:npm/left-pad@1.3.0\\", \\"licenses\\": [{\\"license\\": {\\"id\\": \\"WTFPL\\"}}]}]}",
  "filename": "bom.json"
}' |
apify call eloquent_mountain/cra-sbom-audit --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,eloquent_mountain/cra-sbom-audit"
        }
    }
}
```

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/okXvwIgqM11h5MH3k/builds/sOrjEYPrTXshP1g0C/openapi.json