# From Sigstore to CRA readiness: Sylva's journey with OpenSSF

DevFeed: [From Sigstore to CRA readiness: Sylva's journey with OpenSSF](<https://devfeed.tech/articles/from-sigstore-to-cra-readiness-sylva-s-journey-with-openssf-122125.md>)

Original publisher: [Read original article](<https://openssf.org/blog/2026/11/06/from-sigstore-to-cra-readiness-sylvas-journey-with-openssf/>)

Author: OpenSSF

Published: 2026-11-06T14:44:01Z

Content type: article

Language: en

Sources: [Open Source Security Foundation](<https://devfeed.tech/sources/open-source-security-foundation.md>)

Topics: [cyber resilience act](<https://devfeed.tech/topics/cyber-resilience-act.md>), [sigstore](<https://devfeed.tech/topics/sigstore.md>), [openssf](<https://devfeed.tech/topics/openssf.md>), [slsa levels](<https://devfeed.tech/topics/slsa-levels.md>), [Security](<https://devfeed.tech/topics/security.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [software supply-chain attack](<https://devfeed.tech/topics/software-supply-chain-attack.md>)

Tags: [best-practices](<https://devfeed.tech/tags/best-practices.md>), [best-practices-badge](<https://devfeed.tech/tags/best-practices-badge.md>), [blog](<https://devfeed.tech/tags/blog.md>), [cra](<https://devfeed.tech/tags/cra.md>), [cra-readiness](<https://devfeed.tech/tags/cra-readiness.md>), [cyber-resilience-act](<https://devfeed.tech/tags/cyber-resilience-act.md>), [eu-cyber-resilience-act](<https://devfeed.tech/tags/eu-cyber-resilience-act.md>), [guest-blog](<https://devfeed.tech/tags/guest-blog.md>), [openssf](<https://devfeed.tech/tags/openssf.md>), [openssf-scorecard](<https://devfeed.tech/tags/openssf-scorecard.md>), [operators](<https://devfeed.tech/tags/operators.md>), [osps-baseline](<https://devfeed.tech/tags/osps-baseline.md>), [security-insights](<https://devfeed.tech/tags/security-insights.md>), [sigstore](<https://devfeed.tech/tags/sigstore.md>), [slsa](<https://devfeed.tech/tags/slsa.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>), [sylva](<https://devfeed.tech/tags/sylva.md>), [trust](<https://devfeed.tech/tags/trust.md>)

## AI overview

Sylva uses OpenSSF tools to give downstream operators ways to verify deployed artifacts and assess project security, while treating CRA readiness as voluntary transparency rather than certification or legal compliance. Its CI builds SBOMs, scans images with Trivy and Dependency-Track, and signs and attests its own artifacts with Sigstore; it aims for SLSA Level 3. Attestation remains in progress, and nested Helm charts and unsigned upstream dependencies are difficult to verify. GitLab also limits some SLSA capabilities and Scorecard checks: about 94% of recent sylva-core changes were reviewed, while Scorecard reported about 65%. Scorecard provided a trackable baseline and prompted publication of SECURITY.md; the Best Practices assessment rose from 93% of passing criteria to 96% of silver-level criteria. For CRA preparation, Sylva uses the OpenSSF guide alongside OSPS Baseline, Security Insights and Best Practices criteria, documents vulnerability coordination with its CRA steward, and plans human- and machine-readable readiness information. The project says manufacturers retain CRA due diligence responsibility.

## Source excerpt

Sylva's security work relies heavily on the OpenSSF ecosystem. From supply chain tooling with Sigstore and SLSA to adopting OpenSSF Scorecard and Best Practices badges, learn how Sylva is approaching EU Cyber Resilience Act (CRA) readiness and building verifiable trust for downstream operators.