Deliverables and certificates
What a sealed deliverable is, what its certificate proves, and how to obtain it.
The deliverable
A deliverable freezes, for one version of the product, the state of each requirement: specified, covered, proven. It is sealed — its SHA-256 fingerprint is computed over its content in canonical JSON — and signed with Ed25519 by the key of your space.
GET /livrable/telecharger?no=<number>: the sealed JSON, the form that is passed on (the content, its fingerprint and its signature travel together);GET /livrable/certificat?no=<number>: the readable certificate;&format=pdffor the signed and timestamped PDF. It is sealed once, at issuance, then kept: every download returns exactly the same file.GET /livrable/dossier?no=<number>: the sealed bundle, a detached XAdES signature (as in the EU Official Journal) covering the sealed PDF and JSON by their fingerprints; signed with the service seal and timestamped, made once and then kept. Whoever receives the three files checks them without an account, on /verifier.
The verdict
The verdict follows Annex I of the CRA (Part I, 2 a): a product is placed on the market without known exploitable vulnerabilities. It therefore crosses the requirements with the vulnerabilities of the version's SBOM, using the VEX status you gave them ("SBOM/Vulnerabilities" tab).
| Situation | Effect on the verdict |
|---|---|
| a requirement is not proven (not covered, not run, or failed) | NON-COMPLIANT |
| a vulnerability is declared "affected" (exploitable in the product) | NON-COMPLIANT |
| an actively exploited vulnerability (CISA KEV or EUVD catalogue) is still "under investigation" | VERDICT BLOCKED, no grace period: assess it |
| another vulnerability is still "under investigation" | reservation "to be assessed" |
| "not affected" with its justification, or "fixed" | no effect |
| component that cannot be analysed, incomplete analysis (source down), no SBOM | reservation, stated |
| a requirement proven by a manual test (review, inspection, test bench) | reservation, stated: a declared and named result, not run by the CI |
| otherwise | COMPLIANT, its reservations written |
A requirement you declare not applicable ("Requirements" tab, "edit") requires its justification (CRA, Annex VII, point 3): it leaves the calculation, and the certificate lists it with its justification, author and date. Any change to the plan requires a reason and stays in the history; nothing is erased. Likewise, each different upload of a version's SBOM is a numbered revision (difference, author, reason): the deliverable seals the number and fingerprint of the revision it uses. See Correct without erasing.
Each outcome carries its reasons and reservations; the certificate prints them. A NON-COMPLIANT or BLOCKED verdict does not prevent you from issuing: the deliverable states what is. The justification of a "not affected" is yours; QATrax seals and dates it, it does not check it.
What the verdict asserts: the requirements of your plan are proven by runs received, and no vulnerability known at the date of the seal is declared exploitable or left unanswered while it is being exploited. What it does not assert: the absence of vulnerabilities, or compliance with the regulation, which remains the manufacturer's responsibility.
What the certificate proves
That this content, at this date, was established by this space and has not changed since. It serves the technical documentation required by the CRA (art. 13), which the manufacturer keeps for at least ten years.
The certificate is written in French and English: each heading, the verdict and its reasons appear in both languages, English after French. Certificates issued before 11/10/2026 give the reasons for the verdict in French only.