@canonical/styles-primitives-canonical
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Canonical org CSS primitives package; sparse README and no keywords are expected for an internal design system component. | ai | |
| phantom-deps | phantom-dep:@canonical/tokens | AI (phantom-deps): Same-org CSS dependency; phantom-dep heuristic unreliable for CSS-only imports. | ai | |
| phantom-deps | phantom-dep:@canonical/typography | AI (phantom-deps): Same-org CSS dependency; phantom-dep heuristic unreliable for CSS-only imports. | ai | |
| phantom-deps | phantom-dep:normalize.css | AI (phantom-deps): CSS package; normalize.css is likely referenced via @import in CSS files, not JS imports. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.26.0 | 3 / 3 | |
| 0.23.0 | 3 / 3 | |
| 0.22.0 | 3 / 3 | |
| 0.17.1 | 3 / 3 | |
| 0.13.0 | 3 / 3 | |
| 0.10.0 | 3 / 3 | |
| 0.9.0 | 3 / 2 |
v0.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.