@axa-fr/design-system-slash-react
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; expected for AxaFrance org automation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer roster change consistent with org-level CI/CD takeover of publishing; no malicious indicators. | ai | |
| dependencies | unvetted-dep:@fontsource/source-sans-pro | AI (dependencies): @fontsource/source-sans-pro is a well-known, widely-used font package from the Fontsource project; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo component; tiny payload and missing description are expected for this package type. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Intentionally minimal metadata for an internal design system component package. | ai | |
| dependencies | unvetted-dep:@axa-fr/canopee-react | AI (dependencies): Same-org internal dependency within the AXA France design system monorepo; stable pattern across versions. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.6.0 | 1 / 0 | |
| 4.5.0 | 1 / 0 | |
| 4.4.1 | 1 / 0 | |
| 4.4.0 | 1 / 0 | |
| 4.3.0 | 1 / 0 | |
| 4.2.0 | 1 / 0 | |
| 4.1.0 | 1 / 0 | |
| 4.0.0 | 1 / 0 | |
| 3.0.0 | 8 / 18 | |
| 0.1.0 | 1 / 0 |
v4.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.1
2 findingsThis 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.0
2 findingsThis 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.0
2 findingsThis 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.0
2 findingsThis 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.