The Cyber Resilience Act (Regulation (EU) 2024/2847) is the EU law that sets baseline cybersecurity requirements for products with digital elements sold into the EU market. This page covers two specific parts of it in detail — Annex VII (the content of the technical documentation, referenced by Article 31) and Annex V (the EU declaration of conformity, referenced by Article 28) — not the whole regulation. Every requirement below is quoted or closely paraphrased from the consolidated regulation text and cited to its exact point.
Article 31 requires manufacturers to draw up technical documentation before a product is placed on the market and to keep it updated throughout the support period. Annex VII sets the minimum content: eight numbered points, the first two of which are broken down further into lettered sub-points.
Four sub-points, each required "as applicable":
An assessment of the cybersecurity risks against which the product is designed, developed, produced, delivered and maintained under Article 13, including how the essential cybersecurity requirements in Part I of Annex I apply. Annex VII, point 3
The relevant information taken into account to determine the product's support period under Article 13(8). Annex VII, point 4
A list of the harmonised standards applied (in full or in part) whose references are published in the Official Journal, or common specifications (Article 27) or European cybersecurity certification schemes applied instead. Where such standards, specifications or schemes were not applied, a description of the alternative solutions used to meet the essential cybersecurity requirements, including any other relevant technical specifications. If a standard was only partly applied, the documentation must specify which parts. Annex VII, point 5
Reports of the tests carried out to verify conformity of the product and of its vulnerability handling processes with the applicable essential cybersecurity requirements. Annex VII, point 6
A copy of the Annex V declaration itself, included in the technical documentation package. Annex VII, point 7
Where applicable, the SBOM, to be provided further to a reasoned request from a market surveillance authority where necessary for that authority to check compliance with the essential cybersecurity requirements. Annex VII, point 8
Article 28 requires manufacturers to draw up an EU declaration of conformity stating that the applicable essential cybersecurity requirements in Annex I have been demonstrated, using the model structure set out in Annex V. Unlike Annex VII, Annex V is not organised into lettered sub-points under each item — it is a flat list of eight points, all at the same level.
See a real Annex V DoC draft generated by ceproof.
First, what it needs to read at all: a repository containing an npm manifest (package.json, plus package-lock.json / pnpm-lock.yaml / yarn.lock if present) or a Python one (pyproject.toml, requirements.txt, poetry.lock, uv.lock). Given neither, ceproof report refuses to run rather than producing a document off no evidence. A C or C++ firmware project is still not scanned: ceproof does not read C or C++ sources and does not parse Yocto, Buildroot, Conan or CMake trees. For those projects the components come in as an SBOM you already have, and that import is FDA-profile only — ceproof scan --profile fda --sbom firmware.cdx.json reads CycloneDX JSON (spec 1.4, 1.5 or 1.6), repeatable per file, and the CRA profile refuses --sbom with a usage error instead of ignoring it. Pasting a component list by hand is accepted on neither profile.
Given one of those manifests, ceproof works through the 21 items across Annex VII and Annex V (13 from Annex VII, 8 from Annex V) and sorts each one into one of four categories, based on whether it can be resolved from evidence a scan can actually find:
ceproof init into a ceproof.config.json file. Manufacturer identity, product description, risk-assessment narrative, and the reasoning behind a chosen support period fall here — a scan genuinely cannot infer these from source code.Concretely, a scan of your repository can surface: whether a SECURITY.md or security.txt file is present, whether a vulnerability disclosure policy exists, your git release identity (a real tag versus just a commit hash), your declared project license, the full npm or Python dependency tree with resolved licenses, and SBOM readiness — how many packages you depend on and whether all of their licenses are known.
It cannot derive: the product's intended purpose in prose, hardware photographs, a system architecture narrative, the actual cybersecurity risk assessment, the reasoning behind a chosen support period, which harmonised standards were applied, test reports, or the declaration-of-conformity signatory block. Those require a human who understands the product.
On a typical repository with a tagged release and a resolved dependency lockfile, this means 2 of the 13 Annex VII items resolve fully from scan evidence alone (DERIVED), and a 3rd gets partial evidence and is flagged PARTIAL for review. The rest — the majority of both annexes — are correctly flagged as needing your input, not silently guessed at.
The same scan runs in CI. The published GitHub Action is one uses: line that puts this checklist in your job summary and keeps it as a build artifact: run the CRA gap checklist in GitHub Actions →
Article 71 sets the Regulation's entry into force and application dates. The general application date is 11 December 2027 — this is when the Annex VII technical documentation obligation (Article 31) and the Annex V declaration of conformity obligation (Article 28) take effect for products placed on the market. Two provisions started earlier, and both already apply:
| Provision | Status | What it covers |
|---|---|---|
| Article 14 | Has applied since 11 September 2026 | Manufacturer reporting of actively exploited vulnerabilities and severe incidents to ENISA and the coordinating CSIRT |
| Chapter IV (Articles 35–51) | Has applied since 11 June 2026 | Notification of conformity assessment bodies (notified bodies) |
| General application date | Applies from 11 December 2027 | All remaining obligations, including Annex VII technical documentation (Article 31) and Annex V declaration of conformity (Article 28) |
Article 71(2): "This Regulation shall apply from 11 December 2027. However, Article 14 shall apply from 11 September 2026 and Chapter IV (Articles 35 to 51) shall apply from 11 June 2026."
ceproof does not file or monitor these notifications; it drafts technical documentation. Article 14 is a live reporting duty owed to a CSIRT and to ENISA through the Article 16 single reporting platform, on clocks measured in hours. It is described here as context for the CRA's timeline, not because this tool addresses it. All four dates, with the quoted article text.
ceproof lays out all 21 items in the regulation's order, cites each one, derives what your repository can evidence, and lists what is still open. Free to scan and to see the gap checklist. $99, one-time to export the Annex VII pack and the Annex V DoC draft.
Needs a repository with an npm or Python manifest. C or C++ firmware is not supported today.