# CRA Exploited-Vulnerability Evidence and Art. 14 Deadline Clock (`davidcondrey/wl-cra-exploit-clock`) Actor

Takes a CycloneDX or SPDX JSON SBOM (or a purl list), asks OSV.dev for the advisories that affect each exact component version (OSV evaluates the version ranges per ecosystem), then checks each CVE against the CISA Known Exploited Vulnerabilities catalog and the ENISA EUVD…

- **URL**: https://apify.com/davidcondrey/wl-cra-exploit-clock.md
- **Developed by:** [WritersLogic](https://apify.com/davidcondrey) (community)
- **Categories:** AI, Agents, Developer tools
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2,500.00 / 1,000 cra exploited-vulnerability evidence and art. 14 deadline clock runs

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 Exploited-Vulnerability Evidence and Art. 14 Deadline Clock

Takes a CycloneDX or SPDX JSON SBOM (or a purl list), asks OSV.dev for the advisories that affect each exact component version (OSV evaluates the version ranges per ecosystem), then checks each CVE against the CISA Known Exploited Vulnerabilities catalog and the ENISA EUVD exploited-vulnerability index, and adds FIRST EPSS scores. Returns a per-component verdict, the evidence with source URLs and SHA-256 digests, and the Regulation (EU) 2024/2847 Article 14(2) dates computed in UTC from the awareness time and fix time you supply: early warning within 24 h, notification within 72 h, final report 14 days after a corrective or mitigating measure is available. Also drafts Art. 14(2) content from quoted feed text. Reports evidence and arithmetic, not a legal conclusion. Not legal advice: whether a vulnerability is actively exploited, when you became aware, and what to notify are your determination. A separate standalone awareness record is added only when issue_record is true; every response is in any case a hub-signed credential over its output and input digests. Fan-out is capped (1000 components, 120 advisory records); EUVD is checked per CVE up to 20 CVEs and above that by one read of its whole exploited list; partial results name what is missing. Deterministic, no model call.

Every result is a **signed, verifiable answer**:

- a W3C Verifiable Credential 2.0, signed with `eddsa-jcs-2022` by `did:web:agents.writerslogic.com`;
- a C2PA-style manifest that lists every source the agent read, each with its SHA-256;
- an EIP-191 co-signature over the same digest.

Change one byte and verification fails, so you can pass the result to a client, an auditor or another agent and they can check it without trusting you or us.

### How to use CRA Exploited-Vulnerability Evidence and Art. 14 Deadline Clock

1. Fill in the input form. Required fields are marked; the form opens with a working example.
2. Start the run.
3. Read the result in the **Output** tab, or download the dataset as JSON. The full signed envelope is also saved as the `OUTPUT` record in the key-value store.

### Input

| Field | Required | Description |
|---|---|---|
| `sbom` | no | CycloneDX 1.4-1.6 or SPDX 2.2/2.3 JSON SBOM, as an object or a JSON string, up to 5 MB. Components need a purl with a version (SPDX: a purl externalRef). Exactly one of sbom or purls. |
| `purls` | no | Alternative to sbom: versioned package URLs, e.g. pkg:maven/org.apache.logging.log4j/log4j-core@2.14.1. Ecosystems: npm, pypi, maven, golang, cargo, nuget, gem, composer, hex, pub, swift. |
| `product` | no | Your product with digital elements; used only to fill the draft fields (defaults to the SBOM's own product name). |
| `awareness_time` | no | When the manufacturer became aware, ISO 8601 with UTC offset (e.g. 2026-11-04T09:30:00Z). Defaults to now. Taken as given; this agent cannot verify it. |
| `fix_available_at` | no | When a corrective or mitigating measure became available, ISO 8601 with UTC offset; sets the Art. 14(2)(c) final-report date. |
| `issue_record` | no | Default false. When true, adds a standalone awareness_record (evidence snapshot, SBOM digest, evaluation time; signed with the hub attestation key when configured) for you to retain. It does not switch off the hub's standard signed response credential, which every response carries and which already binds the output and input digests to a timestamp. |

Example input:

```json
{
  "sbom": {
    "bomFormat": "CycloneDX",
    "specVersion": "1.5",
    "version": 1,
    "metadata": {
      "component": {
        "type": "application",
        "name": "acme-gateway",
        "version": "3.2.0"
      }
    },
    "components": [
      {
        "type": "library",
        "bom-ref": "log4j-core",
        "group": "org.apache.logging.log4j",
        "name": "log4j-core",
        "version": "2.14.1",
        "purl": "pkg:maven/org.apache.logging.log4j/log4j-core@2.14.1"
      },
      {
        "type": "library",
        "bom-ref": "lodash",
        "name": "lodash",
        "version": "4.17.15",
        "purl": "pkg:npm/lodash@4.17.15"
      },
      {
        "type": "library",
        "bom-ref": "left-pad",
        "name": "left-pad",
        "version": "1.3.0",
        "purl": "pkg:npm/left-pad@1.3.0"
      }
    ]
  },
  "product": {
    "name": "acme-gateway",
    "version": "3.2.0"
  }
}
```

### Output

```json
{
  "agent": "cra-exploit-clock",
  "priceUsd": 2.50,
  "data": { "...": "the agent's answer" },
  "_provenance": { "credential": {}, "manifest": {}, "ethSignature": "0x..." }
}
```

To check a result for free, POST `{ "data": ..., "_provenance": ... }` to `https://agents.writerslogic.com/api/v1/verify-provenance`, or verify it offline against the public key in the [DID document](https://agents.writerslogic.com/.well-known/did.json).

### Pricing

**$2.50 per successful run**, charged once and only after the agent returns its answer. If the input is rejected or the agent fails, you are not charged for the call.

### Use it from code or an AI assistant

- Apify API and integrations: call this Actor from Make, Zapier, n8n, LangChain or the Apify API like any other Actor.
- MCP: `npx -y @writerslogic/ai-agents-mcp` exposes this agent and the rest of the hub as tools.
- x402: the same agent is available at `POST https://agents.writerslogic.com/api/v1/cra-exploit-clock`, paid per call in USDC on Base.

### More verifiable agents

- [PR / Dependency Breaking-Change & Exploit Gatekeeper](https://apify.com/davidcondrey/wl-diff-gatekeeper)
- [Legal citation and quotation verifier (US case law)](https://apify.com/davidcondrey/wl-legal-cite-verifier)
- [arXiv-to-Production Code & Hyperparameter Compiler](https://apify.com/davidcondrey/wl-arxiv-to-code)
- [Adversarial Unicode & Trojan Source gatekeeper](https://apify.com/davidcondrey/wl-unicode-safety-gate)
- [SMT Contract & Policy Logic Prover](https://apify.com/davidcondrey/wl-smt-contract-prover)
- [AI-BOM License Chain Resolver for Hugging Face Models](https://apify.com/davidcondrey/wl-ai-bom-license-resolver)
- [All agents in one Actor](https://apify.com/davidcondrey/verifiable-ai-agents)

### FAQ

**Who runs this?** [WritersLogic](https://writerslogic.com/agents). The agent runs on the WritersLogic Verifiable AI Agent Hub; this Actor sends your input there and returns the signed result.

**Is my input stored?** The Actor stores your result in your own Apify storage. Ask before sending confidential documents; the hub is a third-party service from your point of view.

# Actor input Schema

## `sbom` (type: `string`):

CycloneDX 1.4-1.6 or SPDX 2.2/2.3 JSON SBOM, as an object or a JSON string, up to 5 MB. Components need a purl with a version (SPDX: a purl externalRef). Exactly one of sbom or purls.

## `purls` (type: `array`):

Alternative to sbom: versioned package URLs, e.g. pkg:maven/org.apache.logging.log4j/log4j-core@2.14.1. Ecosystems: npm, pypi, maven, golang, cargo, nuget, gem, composer, hex, pub, swift.

## `product` (type: `object`):

Your product with digital elements; used only to fill the draft fields (defaults to the SBOM's own product name).

## `awareness_time` (type: `string`):

When the manufacturer became aware, ISO 8601 with UTC offset (e.g. 2026-11-04T09:30:00Z). Defaults to now. Taken as given; this agent cannot verify it.

## `fix_available_at` (type: `string`):

When a corrective or mitigating measure became available, ISO 8601 with UTC offset; sets the Art. 14(2)(c) final-report date.

## `issue_record` (type: `boolean`):

Default false. When true, adds a standalone awareness_record (evidence snapshot, SBOM digest, evaluation time; signed with the hub attestation key when configured) for you to retain. It does not switch off the hub's standard signed response credential, which every response carries and which already binds the output and input digests to a timestamp.

## Actor input object example

```json
{
  "sbom": "[object Object]",
  "product": {
    "name": "acme-gateway",
    "version": "3.2.0"
  }
}
```

# Actor output Schema

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

One dataset item per call: the agent id, the price charged, the agent's result (data) and its signed provenance record (\_provenance).

## `credential` (type: `string`):

The full hub response as a W3C Verifiable Credential with a C2PA-style manifest; verify it at https://agents.writerslogic.com/api/v1/verify-provenance.

# 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 = {
    "sbom": "[object Object]",
    "product": {
        "name": "acme-gateway",
        "version": "3.2.0"
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("davidcondrey/wl-cra-exploit-clock").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 = {
    "sbom": "[object Object]",
    "product": {
        "name": "acme-gateway",
        "version": "3.2.0",
    },
}

# Run the Actor and wait for it to finish
run = client.actor("davidcondrey/wl-cra-exploit-clock").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 '{
  "sbom": "[object Object]",
  "product": {
    "name": "acme-gateway",
    "version": "3.2.0"
  }
}' |
apify call davidcondrey/wl-cra-exploit-clock --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,davidcondrey/wl-cra-exploit-clock"
        }
    }
}
```

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/3XVghT5OYESn4j2wC/builds/wXwqnI8hRwK2u6BWB/openapi.json