Article 31 of Regulation (EU) 2024/2847 provides that the technical documentation “shall at least contain the elements set out in Annex VII”. Article 28 provides that the EU declaration of conformity “shall have the model structure set out in Annex V”. Annex VII has 13 items once its lettered sub-points are counted; Annex V has 8. Twenty-one in total, and the table below is generated from the same reference data the ceproof CLI ships, so it cannot drift from the tool.
| Item | What the regulation asks for | Who can answer it |
|---|---|---|
| Annex VII 1(a) annex7.1.a |
General description of the product with digital elements, including its intended purpose. | Your answer |
| Annex VII 1(b) annex7.1.b |
General description must state versions of software affecting compliance with essential cybersecurity requirements. | Derived from your repository |
| Annex VII 1(c) annex7.1.c |
For hardware products, photographs or illustrations showing external features, marking and internal layout. | Your answer |
| Annex VII 1(d) annex7.1.d |
User information and instructions as set out in Annex II. | Your answer |
| Annex VII 2(a) annex7.2.a |
Necessary information on the design and development of the product, including drawings/schemes and a description of the system architecture. | Your answer |
| Annex VII 2(b) annex7.2.b |
Necessary information and specifications of the vulnerability handling processes: software bill of materials, coordinated vulnerability disclosure policy, contact address for reporting vulnerabilities, and secure update distribution. | Partially derived |
| Annex VII 2(c) annex7.2.c |
Necessary information and specifications of the production and monitoring processes of the product and the validation of those processes. | Your answer |
| Annex VII 3 annex7.3 |
An assessment of the cybersecurity risks against which the product is designed, developed, produced, delivered and maintained pursuant to Article 13, including how the essential cybersecurity requirements in Annex I Part I are applicable. | Your answer |
| Annex VII 4 annex7.4 |
Relevant information taken into account to determine the support period pursuant to Article 13(8). | Your answer |
| Annex VII 5 annex7.5 |
A list of the harmonised standards, common specifications, or European cybersecurity certification schemes applied (in full or in part), or descriptions of the solutions adopted where none were applied. | Your answer |
| Annex VII 6 annex7.6 |
Reports of the tests carried out to verify conformity of the product and of the vulnerability handling processes with the essential cybersecurity requirements in Annex I Parts I and II. | Your answer |
| Annex VII 7 annex7.7 |
A copy of the EU declaration of conformity. | Your answer |
| Annex VII 8 annex7.8 |
Where applicable, the software bill of materials, further to a reasoned request from a market surveillance authority. | Derived from your repository |
| Item | What the regulation asks for | Who can answer it |
|---|---|---|
| Annex V 1 annex5.1 |
Name and type and any additional information enabling the unique identification of the product with digital elements. | Your answer |
| Annex V 2 annex5.2 |
Name and address of the manufacturer or its authorised representative. | Your answer |
| Annex V 3 annex5.3 |
A statement that the EU declaration of conformity is issued under the sole responsibility of the provider. | Standard wording |
| Annex V 4 annex5.4 |
Object of the declaration (identification of the product allowing traceability, which may include a photograph, where appropriate). | Your answer |
| Annex V 5 annex5.5 |
A statement that the object of the declaration is in conformity with the relevant Union harmonisation legislation. | Your answer |
| Annex V 6 annex5.6 |
References to any relevant harmonised standards used, or any other common specification or cybersecurity certification, in relation to which conformity is declared. | Your answer |
| Annex V 7 annex5.7 |
Where applicable, the name and number of the notified body, a description of the conformity assessment procedure performed, and identification of the certificate issued. | Your answer |
| Annex V 8 annex5.8 |
Additional information: signed for and on behalf of (place and date of issue; name, function, signature). | Your answer |
Two items are derivable from a repository scan: the software versions affecting compliance (Annex VII 1(b)), taken from a real version-control tag rather than a bare commit hash, and the software bill of materials (Annex VII 8), built from the resolved dependency tree. One is partial: the vulnerability-handling specification (Annex VII 2(b)), where a scan can find a security policy and a disclosure contact but cannot describe your process. One is standard wording that never varies by product: the sole-responsibility statement (Annex V 3).
The other seventeen need a person who understands the product. Intended purpose, design rationale, risk assessment, support-period reasoning, standards applied, test reports, the signatory block. A tool that filled those in would be writing plausible sentences into a legal document, which is worse than leaving them open.
Every citation in the table above carries the full consolidated-text reference in the tool's own output: Regulation (EU) 2024/2847 (Cyber Resilience Act), consolidated text 02024R2847-20241120 (base act + Corrigenda 1-3, none of which touch Annex V, Annex VII, or Articles 13/31/33).
What goes in each Annex VII section → · The same 21 items, filled in →
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.