@canonical/react-components

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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/jest | AI (phantom-deps): Framework-scoped types loaded by convention in TypeScript/Jest projects. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Framework-scoped types loaded by convention in TypeScript/Node projects. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): Framework-scoped types loaded by convention in React projects. | ai | |
| phantom-deps | phantom-dep:@types/react-dom | AI (phantom-deps): Framework-scoped types loaded by convention in React projects. | ai | |
| phantom-deps | phantom-dep:@types/react-table | AI (phantom-deps): Framework-scoped types loaded by convention in TypeScript projects. | ai | |
| phantom-deps | phantom-dep:jest-environment-jsdom | AI (phantom-deps): Referenced in jest config; standard test environment setup. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 4.5.3 | 10 / 71 | |
| 4.5.2 | 10 / 71 | |
| 4.5.1 | 10 / 71 | |
| 4.5.0 | 10 / 71 | |
| 4.4.1 | 10 / 71 | |
| 4.4.0 | 10 / 71 | |
| 4.3.1 | 10 / 71 | |
| 4.3.0 | 10 / 71 | |
| 4.2.0 | 10 / 71 | |
| 4.1.0 | 10 / 71 | |
| 4.0.1 | 10 / 71 | |
| 4.0.0 | 10 / 71 | |
| 3.12.4 | 10 / 71 | |
| 3.12.3 | 10 / 71 | |
| 3.12.2 | 10 / 71 | |
| 3.12.1 | 10 / 71 | |
| 3.12.0 | 10 / 71 | |
| 3.11.1 | 10 / 71 | |
| 3.11.0 | 10 / 71 | |
| 3.10.0 | 10 / 71 | |
| 3.9.1 | 10 / 71 | |
| 3.9.0 | 10 / 71 | |
| 3.8.3 | 10 / 71 | |
| 3.8.2 | 10 / 71 | |
| 3.8.1 | 10 / 71 | |
| 3.8.0 | 10 / 71 | |
| 3.7.1 | 10 / 71 | |
| 3.7.0 | 10 / 71 |
v4.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.1
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
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.12.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.12.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.12.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.11.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.