@playcanvas/pcui
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Mature, well-known PlayCanvas package; absence of Sigstore attestation is not a risk signal here. | ai | |
| dependencies | unvetted-dep:@playcanvas/observer | AI (dependencies): First-party PlayCanvas org dependency; stable companion package to pcui across all versions. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 6.1.4 | 1 / 41 | |
| 6.0.0 | 1 / 41 | |
| 5.8.0 | 1 / 41 | |
| 5.7.0 | 1 / 41 | |
| 5.4.1 | 1 / 41 |
v6.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.