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:

{
  "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

{
  "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.

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
• Legal citation and quotation verifier (US case law)
• arXiv-to-Production Code & Hyperparameter Compiler
• Adversarial Unicode & Trojan Source gatekeeper
• SMT Contract & Policy Logic Prover
• AI-BOM License Chain Resolver for Hugging Face Models
• All agents in one Actor

FAQ

Who runs this? WritersLogic. 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.