This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 0.12.0 instead.
Reason given by maintainers: Renamed to jochwacht-sbom — install jochwacht-sbom instead.
embtrace-check
Free CRA Readiness Check collector — one command in your project folder, and within 24 hours you receive a report showing where your product stands with the EU Cyber Resilience Act: traffic-light readiness status, your full component inventory, and known vulnerabilities with severity.
This collector is open source for one reason: so you can verify exactly what leaves your machine.
What it transmits — and what it never does
Transmitted (JSON, ~a few kB):
- names, versions and package ecosystems of your dependencies (from lockfiles and build files: Conan, vcpkg, CMake, Cargo, npm/yarn/pnpm, Python incl. uv, Go, Maven/Gradle, Meson, Alire, and more),
- Zephyr workspaces: the
west.ymlmodule manifest — every module with its pinned revision, - Yocto and Buildroot BUILD OUTPUT: run the check in your build
directory — it reads
deploy/images/**/*.manifest(what is actually in your image) resp.legal-info/manifest.csv. The recipe source tree only says what could be built, so the build output is what counts, - names and versions of FPGA IP cores
(AMD/Xilinx Vivado
.hwh/.xci, Microchip Libero Tcl/.cxf, Intel/Altera Quartus*_hw.tcl), - the project folder name (hash it with
--anonymize), - scan statistics (number of build files, tool version),
- only if you wrote them yourself in
embtrace-deps.yaml: the supplier, license, purl and CPE entries of your declaration — a declaration is written for SBOM purposes, so it travels by default and makes your report complete (58 instead of 17 attributed licenses on a typical Zephyr project). Withhold it with--no-declared-metadata. Discovered components never carry these fields.
Never transmitted: source code, file paths, file contents, configuration,
credentials. The supplier of a detected FPGA IP core is known locally but
deliberately not transmitted — a supplier you declare yourself in
embtrace-deps.yaml is your statement and does travel.
See for yourself before sending anything:
embtrace-check . --dry-run # prints the exact payload, uploads nothing
Build outputs (dist/, build/, node_modules/, …) and hidden
directories are never scanned. Project-specific excludes go into a
committed .embtraceignore at the project root — one glob pattern per
line, # comments.
Quality rules (v0.6.0): component identity is (name, version,
ecosystem) — nested second versions of one package are kept as own rows
(the older nested version is often the vulnerable one); build tools and
system libraries (Doxygen, -lanl, find_package(Git), …) are
dropped via a curated 950-name skip list — your own embtrace-deps.yaml
declarations are never skipped; * and guessed versions are never
reported — a missing version is shown as honestly missing. If no
supported build system is found, nothing is uploaded and the tool tells
you exactly what it looks for and where.
Usage
- Get your free one-time code at https://embtrace.dev/check (the report goes to the e-mail address you register there).
- Run the collector in your project folder:
pipx install embtrace-check # or: pip install embtrace-check,
# or download the standalone binary
embtrace-check . --code CHK-XXXX-YYYY
- Your report arrives within 24 hours. The code is valid for one check.
More options: embtrace-check --help — including --output payload.json
for air-gapped environments (send the file by mail) and --with-tools to
additionally use native package-manager CLIs for higher-fidelity results.
Exit codes
| Code | Meaning |
|---|---|
| 0 | success |
| 1 | error (network, invalid code, …) |
| 2 | no components found — declare dependencies manually in embtrace-deps.yaml |
Privacy
Data is processed exclusively on Innomatica's own servers in Germany and is never shared or sold. Full notes: https://embtrace.dev/check-privacy.
About
embtrace-check is the free entry point to
embtrace — the CRA/NIS2 compliance toolchain for
embedded software teams by Innomatica GmbH.
The server side (enrichment, vulnerability monitoring, reports) is a
commercial product; this repository contains the complete client.
Maintained by Innomatica; the roadmap follows the product. Issues and PRs are welcome — please report security topics per SECURITY.md.
License
MIT © 2026 Innomatica GmbH
Metadata
Release files for embtrace-check 0.8.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| embtrace_check-0.8.2.tar.gz | 91.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| embtrace_check-0.8.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 190.8 kB
Release files / embtrace_check-0.8.2.tar.gz
| Download URL | embtrace_check-0.8.2.tar.gz |
|---|---|
| Size | 91.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8fb09d7811fd68af4d3276d8259ea1d8cf9732eb1c1a056027d5b68a840c3fe1
|
|
BLAKE2b-256 checksum How to use checksums |
9dfd02aba96d279be8de7a731370f97320720a8c6475f2487f31b78aafe61f64
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency logRelease files / embtrace_check-0.8.2-py3-none-any.whl
| Download URL | embtrace_check-0.8.2-py3-none-any.whl |
|---|---|
| Size | 98.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d9898ba88131f898e6d4aa16f022b56da99d80eb4d65f878b9bc06ee722b66e9
|
|
BLAKE2b-256 checksum How to use checksums |
7e3ccfd3427718e8a07a36db88344fb7f1bf78ef6595b3934679e9d2be452c29
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency log