@canonical/react-ds-app-landscape
Landscape-specific components for the Pragma design system
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/CD publishing is an improvement; consistent with canonical org's supply chain practices. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of human publisher in favor of GitHub Actions automation is expected for CI/CD-published packages in the canonical org. | ai | |
| 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 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.32.0 | 5 / 23 | |
| 0.31.0 | 5 / 23 | |
| 0.30.0 | 5 / 23 | |
| 0.29.1 | 5 / 22 | |
| 0.29.0 | 5 / 22 | |
| 0.28.0 | 5 / 22 | |
| 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.20.0 | 5 / 22 | |
| 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.32.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.31.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.29.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.29.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-03. 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.
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
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mariadias143) than the most recent previously approved version (ad.vl) on 2026-04-01, but mariadias143 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.20.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mariadias143) than the most recent previously approved version (ad.vl) on 2026-03-26, but mariadias143 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.