CycloneDX JSON
Versions 1.4 to 1.6 are also checked against the official schema. Up to 64 MB.
For manufacturers selling connected products in the EU
Upload the software bill of materials (SBOM) of your product. Venlark checks every component against public vulnerability databases and gives you a clear report for the EU Cyber Resilience Act. Your product files never leave your computer.
11 Sept 2026 In force
Reporting applies. Actively exploited vulnerabilities must be reported to the authorities.
11 Dec 2027
Every requirement applies, including documented software components for each product.
days until
full application
§ 01The problem
Customers, auditors and market surveillance authorities will ask how you know what is in a product. The answer has to hold up for every version you have shipped.
Hand-made lists go stale
A spreadsheet of components drifts away from the build the moment a supplier updates a library.
Scanners quietly guess
One tool misses what another finds, and versions it cannot read are often filled in rather than flagged.
Nobody can show their work
When a customer asks why a vulnerability does or does not apply, there is no trail to point at.
§ 02What you upload
CycloneDX JSON
Versions 1.4 to 1.6 are also checked against the official schema. Up to 64 MB.
SPDX JSON
Versions 2.2 and 2.3 are also checked against the official schema. Up to 64 MB.
No SBOM yet?
We are building desktop apps for Mac and Windows that make the SBOM for you, on your own computer.
Coming soon
Firmware images, app packages, archives and source code are refused before they are stored. CycloneDX XML and SPDX tag-value are not supported yet.
§ 03How it works
Most build tools can write one, for example Syft, Trivy or cdxgen. Our desktop apps for Mac and Windows will make it for you; they are coming soon.
CycloneDX JSON or SPDX JSON. Anything else is refused before it is stored, so your firmware, apps and source code never reach us.
Grype, Trivy and OSV-Scanner check every component against public vulnerability databases. The database date is recorded with every result.
A one-page summary with a red, amber or green status, the full list of findings, and machine-readable files. It is produced automatically and says so.
When new vulnerabilities are published, your SBOMs are checked again and you get an alert, without uploading anything new.
§ 04Evidence
Finding · sample
openssl 1.1.1k
libvendor unknown
The SBOM gives no version. Reported as unknown, with the reason, instead of a guessed version that would produce false matches.
One status for the whole product
One status language
Read any result at a glance, in colour or in black and white.
Every status has a mark, a word and a colour. The same scale is used in the app, the report and the export.
Severity
Confidence
Review
§ 05The report
Business owners get a plain-language report: what needs action, what to ask suppliers, and what is fine. Engineers get the machine-readable findings for the same SBOM.
§ 06Pricing
Example prices, not final. Plans and prices will be confirmed before launch.
See where a product stands.
€0one SBOM
Everything you need for one release.
€49per product version
Stay informed after you ship.
€19per product, per month
The desktop apps for Mac and Windows, which make the SBOM for you, are coming soon. Reports are produced automatically and are not legal advice.
§ 07Privacy and security
SBOM only
Anything that is not a CycloneDX or SPDX file is refused before it is stored.
Isolated checks
The workers that read your SBOM cannot reach the internet.
Pinned tools
Exact versions and SHA-256 checksums, checked at build and every time a worker starts.
Full audit log
Every sign-in and change is recorded, so you can show who did what and when.
Vulnerability matching by open tools, pinned to exact versions
§ 08Questions
No. You upload only the software bill of materials (SBOM), a list of the software components in your product. Every other file is refused before it is stored, so firmware, apps and source code never reach us.