@canonical/react-ds-app-portal
Portal-specific components for the Pragma design system
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@canonical/styles | AI (phantom-deps): Same-org sibling dep used transitively; not directly imported in source is expected for this package. | ai | |
| phantom-deps | phantom-dep:@canonical/react-ds-global | AI (phantom-deps): Same-org sibling dep used transitively; not directly imported in source is expected for this package. | ai | |
| phantom-deps | phantom-dep:@canonical/storybook-config | AI (phantom-deps): Storybook config dep; not directly imported in component source is expected. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Peer/runtime dep declared for consumers; not directly imported in library source is normal. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.27.0 | 5 / 22 | |
| 0.26.0 | 5 / 23 | |
| 0.25.0 | 5 / 23 | |
| 0.24.0 | 5 / 23 | |
| 0.23.0 | 5 / 23 | |
| 0.22.0 | 5 / 23 | |
| 0.21.0 | 5 / 23 | |
| 0.17.1 | 5 / 22 | |
| 0.17.0 | 5 / 22 | |
| 0.16.0 | 5 / 22 | |
| 0.15.1 | 5 / 22 | |
| 0.15.0 | 5 / 22 |
v0.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.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.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.