Cyber Resilience Act · NIS2 · ISO 27001

The Notary of your Supply Chain

Every build is signed, timestamped in a public log and kept in storage that cannot be altered. With every commit, you produce the evidence your auditors and the CRA will ask for.

Hosted in FranceOpen source agent, Apache 2.0Cybersecurity Made in Europe label
Art. 1 · Collection

Your CI produces a build.

The Wisec agent gathers the commit, the dependencies, the SBOM and your scanners' results. It runs in your pipeline, on GitLab, GitHub, Azure DevOps or Jenkins. Wisec never clones your repository and has no access to your source control.

Art. 2 · Signature

It is sealed.

The agent signs the whole with your Ed25519 key. The signature covers the build as it is recorded: change a single field afterwards, and the proof no longer holds.

SHA-256 hash of the build04adbdf50a1e639205dfa8cbf5148f5670802668a7bc0bf39f169142a4d55376
Art. 3 · Anchoring

It joins the chain.

Each build carries the hash of the previous one, so none can be removed without it showing. It is anchored on IPFS and copied to WORM storage for three years. Its SLSA attestation is timestamped in Rekor, Sigstore's public log, and the signed VEX follows the vulnerability analysis.

Art. 4 · Proof

Check it yourself.

This build is real. It comes from project_go, one of our test projects, on 4 November 2026 at 21:54 UTC. Verifiable without a Wisec account, with standard tools.

Branch
main · commit 0fb9eb903d1d
Hash
04adbdf5…a4d55376
Previous
0c3c47c0…4d371794
Rekor
entry 3,691,977,370
IPFS
QmXU1sx9…bMDj2sFNVc
They support us

Backed by the French tech and cybersecurity ecosystem.

  • Les Pépites Tech
  • Extragone
  • French Tech Saint-Étienne Lyon
  • ACN, Alliance pour la Confiance Numérique
The context

The CRA turns software security into a duty of proof.

The Cyber Resilience Act applies to every product with digital elements sold in the Union. Manufacturers will have to show how they handle their vulnerabilities, product by product and over time.

  1. Entry into force

    The regulation is published and the countdown starts.

  2. Mandatory reporting

    Actively exploited vulnerabilities and severe incidents must be notified.

  3. Full application

    All requirements apply to products placed on the market.

“Which components does this product contain?”

A signed CycloneDX SBOM for every build, anchored with the rest of the proof.

“Are you affected by this CVE?”

A search across your build history, by component or by vulnerability, and a signed VEX for each decision.

“How do you handle your vulnerabilities?”

A posture measured against your own deadlines, frozen every month in a signed record.

Wisec produces the evidence and maps it to the requirements. It does not issue a certificate of compliance.

Sovereignty
48,86° N
2,35° E
fr-par region · Paris

Hosted in France. The analysis sends no dependency name out.

  • HostingScaleway, in Paris.Database, WORM storage and IPFS node are operated in France.
  • AnalysisThe vulnerability database runs on our side.We download OSV's public archives and the CVE lookup happens in our cluster.
  • Public logRekor only receives a hash.The content of your builds is not in it.
  • AgentOpen source, Apache 2.0 licensed.Your team can read it before installing it.
  • LabelCybersecurity Made in Europe.Wisec is a member of the Alliance pour la Confiance Numérique.Cybersecurity Made in Europe label
Get started

Your next audit will ask for evidence. Start producing it with your next build.

contact@wisec.io