@canonical/react-ds-app-landscape
Landscape-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 monorepo sibling; declared as peer/runtime dep, not directly imported in this component package. | ai | |
| phantom-deps | phantom-dep:@canonical/react-ds-global | AI (phantom-deps): Same-org monorepo sibling; expected transitive dependency pattern. | ai | |
| phantom-deps | phantom-dep:@canonical/storybook-config | AI (phantom-deps): Same-org storybook config dep; used via config files, not direct imports. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is a standard peer dep referenced in config/test files; stable false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.27.0 | 5 / 22 | |
| 0.26.0 | 5 / 23 | |
| 0.25.0 | 5 / 23 | |
| 0.24.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
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.