← Home

@axa-fr/canopee-react

npm Repository Homepage

Package React - Design System Canopée

8
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

guillaume.chervet.axasamuel-gomezarnaudforaisonjohnathan.meuniermartinweb

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from personal account to GitHub Actions CI/CD publisher; SLSA attestation confirms legitimate org-controlled pipeline. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer consolidation consistent with org-level CI/CD migration; no malicious indicators present. ai
source-diff large-new-source-files AI (source-diff): New files are TypeScript declarations for a design system feature expansion; no obfuscation or suspicious code patterns. ai
dependencies unvetted-dep:@tanem/svg-injector AI (dependencies): Legitimate SVG injection utility; stable dependency for this design system package. ai
dependencies unvetted-dep:@fontsource/source-sans-pro AI (dependencies): Standard font package from the @fontsource org; no security concern. ai

Versions (showing 8 of 8)

Version Deps Published
1.6.0 8 / 18
1.5.0 8 / 18
1.4.1 8 / 18
1.4.0 8 / 18
1.3.0 8 / 18
1.2.0 8 / 18
1.1.0 8 / 18
1.0.0 8 / 18

v1.6.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.4.1

2 findings
HIGH Publisher changed: samuel-gomez → GitHub Actions (on 2026-03-12) provenance

This version was published by a different npm account than previous versions on 2026-03-12. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.4.0

2 findings
HIGH Publisher changed: samuel-gomez → GitHub Actions (on 2026-03-10) provenance

This version was published by a different npm account than previous versions on 2026-03-10. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.3.0

2 findings
HIGH Publisher changed: samuel-gomez → GitHub Actions (on 2026-01-29) provenance

This version was published by a different npm account than previous versions on 2026-01-29. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.2.0

2 findings
HIGH Publisher changed: samuel-gomez → GitHub Actions (on 2025-12-15) provenance

This version was published by a different npm account than previous versions on 2025-12-15. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.