Transparenz v2.4.0
CRA · T- days to deadline View on GitHub →
Open source · local-first CRA Art. 14 · 11 Sept 2026

Don't let the Cyber Resilience Act be the reason you can't ship into the EU.

Get reporting-ready before 11 September 2026 with an open-source toolchain you self-host — and a team that helps you stand it up. Your vulnerability data never leaves your infrastructure.

Statutory deadline
11 Sep2026
Reporting clock
24hr · CRA Art. 14
Vuln. feeds
EUVD+ NVD · OSV · KEV
Deployment
Local-first
01 — The Obligation

If you ship into the EU, you're now legally required to keep doing this.

The Cyber Resilience Act makes every product placed on the EU market a multi-year safety obligation for the vendor — not at release, but for the entire support period. NIS2 layers the operator-side regime on top for essential services. Non-compliance under the CRA carries administrative fines of up to €15M (or 2.5% of global turnover) and revocation of EU market access.

Statutory deadline
11 Sept 2026
CRA reporting obligations enter force · T- days, h
Who it hits
Any vendor selling into the EU
US, UK, anywhere — extraterritorial reach, no exemption for SaaS or OSS-derived products
If you don't
€15M or 2.5%
CRA Art. 64 administrative fines · a second tier of €5M / 1% applies to incorrect or incomplete information · plus loss of EU market access
01

Maintain a conformant SBOM

A machine-readable bill of materials for every product, kept current across releases, available to authorities on request.

CRA · Annex I §2(1)
02

Monitor continuously, post-release

Not at build — continuously, against live feeds, for the entire support period of the product (5 years minimum).

CRA · Annex I §2(2)–(3)
03

Notify regulators within 24 hours

Actively exploited vulnerabilities require an early-warning notification to the designated CSIRT and ENISA inside one day.

CRA · Art. 14(1)
04

Publish coordinated advisories

Disclose to users without undue delay with mitigation guidance, and retain the record for at least ten years.

CRA · Art. 13(8) · NIS2 · Art. 23
02 — Why not a scanner

Build-time scanners stop where the law begins.

SCA tools like Snyk or Dependency-Track are good citizens of the pipeline. Post-market safety and regulator reporting are a different category — a different system, a different data stack, a different operational model.

Build-time scannersSCA / SBOM gen
  • Scans dependencies in CI at merge or release.
  • Stops at ship. No post-release monitoring.
  • No regulator-facing reporting workflow.
  • US-centric feeds; minimal EUVD / ENISA coverage.
  • Finds problems. Doesn't file anything.
TransparenzPost-market safety engine
  • Re-runs every shipped SBOM against new CVEs, continuously, for the product's full support life.
  • Maps each finding to the article, control and deadline it triggers.
  • Drafts CSAF / VEX advisories in ENISA-ready format on schedule.
  • EU-native vulnerability stack — EUVD primary, reconciled with NVD, OSV and CISA KEV.
  • An audit-grade record of every obligation, designed to meet every deadline.
03 — Engine

A single safety pipeline. Always-on.

The Transparenz engine ingests your SBOMs, reconciles EUVD, NVD, OSV and CISA KEV in real time, maps every finding to the controls it triggers, and emits regulator-ready advisories. Built as one system, not glued tools.

/transparenz.engine
runs in your own infrastructure ● built as one system, not glued tools
01 · INGEST

EU-native SBOM

The transparenz CLI generates BSI TR-03183-2 SBOMs out of CI — SHA-512 hashes, supplier & license enrichment, validated by bsi-check.

BSI TR-03183-2 CycloneDX 1.6 SPDX 2.3
02 · CORE

Vulnerability Reactor

VulnzMatcher scans every stored SBOM against EUVD, NVD, OSV and CISA KEV — re-running the moment a feed sync lands a new CVE.

EUVD NVD OSV KEV
03 · MAP

Compliance Mapper

Every finding maps to the CRA article it triggers and starts the 24h / 72h SLA clock automatically — anchored to the CVE's publish date, not scan time.

CRA Art. 14 NIS2 SLA 24h/72h
04 · EMIT

Advisory Pipeline

Generates CSAF 2.0 advisories and runs the VEX lifecycle and coordinated disclosure. ENISA submissions are formatted and staged, ready for the platform.

CSAF 2.0 VEX ENISA-ready
stack Go + PostgreSQL
SLA clock 24h / 72h
licence AGPL-3.0
deploy self-hosted
04 — Safety Surface

Six guarantees, instrumented by design.

Safety isn't a posture, it's a measurable surface. Every Transparenz subsystem is engineered with SLOs, telemetry and an audit trail — the same instruments your reliability team already runs.

Continuous post-market scanning

Every shipped SBOM is re-evaluated against new vulnerabilities the moment they land in any feed — not on a nightly batch.

Target TTD< 90 sec

24-hour disclosure pipeline

Active exploits trigger an auto-drafted early-warning notification, formatted to CSIRT and ENISA spec, ready for sign-off.

Engineered forCRA Art. 14(1)

74-framework compliance mapping

One finding lights up every regime it triggers — CRA, NIS2, DORA, ISO 27001, SOC 2, FedRAMP and 68 more — with the exact control referenced.

Frameworks74 mapped

Cryptographic provenance

Every SBOM, scan run and advisory is signed and chained — Sigstore-rooted, regulator-replayable, tamper-evident.

Standardin-toto + Sigstore

Multi-feed reconciliation

EUVD, NVD, OSV and CISA KEV reconciled into one canonical record — no duplicate alerts, no missed CVEs, no source ambiguity.

FeedsEUVD-first

Audit-grade record

Every obligation, every deadline, every notice — signed, timestamped, append-only. Architected so any historical state can be reconstructed for an auditor on request.

Retention10 yr by design
Built in the EU · for the EU

The only safety engine engineered natively for the European stack.

Vulnerability data, hosting, submission pipelines and engineering — all inside the Union. While generic scanners route through US feeds and US clouds, Transparenz speaks the EU vocabulary by default. Structurally hard for US incumbents to replicate.

Local-first deployment
Runs in your own infrastructure. Your code and findings never leave your environment — no transatlantic transfer to worry about.
Vulnerability primary
EUVD-first reconciliation — the European database is the source of truth, not an afterthought.
ENISA-ready format
Submissions formatted to ENISA single reporting platform spec — ready for the API the moment it’s formalised.
BSI TR-03183-2 SBOMs
EU-centric SBOM output to the German BSI technical guideline — not US-default formats.
REG · 2024/2847 Cyber Resilience Act (CRA) mapped
DIR · 2022/2555 NIS2 directive mapped
REG · 2022/2554 DORA financial sector mapped
REG · 2024/1689 EU AI Act provider safety mapped
REG · 2016/679 GDPR data residency mapped
REG · 2024/1183 eIDAS 2.0 trust framework mapped
DIR · 2022/2557 CER critical entities mapped
Statutory clock — 11 Sept 2026
CRA reporting obligations enter force · T- days
05 — Integrate

Plugs into your CI in one step.

Push your SBOM out of CI; everything downstream is automatic. APIs and webhooks for the systems your team already runs.

# .github/workflows/transparenz.yml
on: [push, release]

jobs:
  monitor:
    runs-on: ubuntu-latest
    steps:
      - uses: transparenz/action@v2
        with:
          token:    ${{ secrets.TRANSPARENZ }}
          product:  "acme-gateway"
          sbom:     "dist/sbom.cdx.json"
          host:     ${{ secrets.TPZ_HOST }}   # your self-hosted server
          # server takes it from here — scan,
          # map and ENISA-ready advisories.
# install the SBOM CLI
$ go install github.com/vincents-ai/transparenz@latest

# generate a BSI TR-03183-2 compliant SBOM
$ transparenz generate . \
    --format cyclonedx --bsi-compliant \
    --manufacturer "Acme Corp"

# validate, then submit to your server
$ transparenz bsi-check sbom.json
  ✓ SHA-512 hashes · supplier + license coverage
  ✓ CycloneDX 1.6 · BSI TR-03183-2 compliant
$ transparenz generate . --bsi-compliant --submit
// upload an SBOM to your self-hosted server (JWT)
await fetch(`${TPZ_HOST}/api/sboms/upload`, {
  method: "POST",
  headers: { "Authorization": `Bearer ${TOKEN}` },
  body: sbom
});

// stream SLA + vulnerability alerts in real time
new EventSource(`${TPZ_HOST}/api/alerts/stream`);

// verify the compliance audit chain
await fetch(`${TPZ_HOST}/api/audit/verify`);

Two open-source repos

The transparenz SBOM CLI and the transparenz-server compliance server — both AGPL-3.0, both self-hosted.

Native SBOM standards

CycloneDX 1.6 and SPDX 2.3, generated with the native Syft library — no proprietary lock-in, no translation layer.

Real-time SSE alerts

Stream new-vulnerability and SLA-deadline alerts over Server-Sent Events — wire them into Slack, PagerDuty or Jira.

JWT auth, RBAC, audit chain

Role-based access (admin / compliance officer), multi-tenant isolation, and a verifiable append-only audit chain.

06 — Partners

A safety platform you can wholesale.

Both engines are open core — AGPL-3.0 community editions, with commercial licensing for closed-source or SaaS use. MSPs resell it as managed service, funds offer it as portfolio coverage, platforms integrate it as the EU-compliance surface their customers already need.

→ Managed Service Providers

White-label the engine

Run a CRA / NIS2 managed service under your own brand. We power the monitoring and reporting; you own the customer and the margin.

ModelOEM · per-seat
→ Venture Funds

Portfolio coverage

One vendor deal, every portco protected. EU market access stays open across the whole book — no founder time spent rebuilding compliance.

ModelFund-rate license
→ Strategic Platforms

Integrate or acquire

The EU-compliance surface your platform doesn't currently serve — EUVD-native data, 74-framework engine, ENISA pipeline. Years to build, ready today.

ModelNative integration

Clone it. Run it locally. Ship safely.

Both engines are open source and local-first — self-host in minutes inside your own pipeline, with nothing leaving your environment. Get compliance out of static spreadsheets and into the build. Need it managed or rolled out across a portfolio? That's what partners are for.

Want a hand getting reporting-ready?

Join the early-access list for self-hosted CRA onboarding and support. We'll reach out as we open spots — no spam, no sales blast.

AGPL-3.0 · local-first · no data leaves your infrastructure