@epicgames-ps/lib-pixelstreamingfrontend-ue5.6
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 with SLSA attestation; legitimate for this Epic Games org package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy aligns with UE version-specific release cadence; SLSA attestation confirms legitimate CI publish. | ai | |
| provenance | no-provenance | AI (provenance): Epic Games org package; lack of Sigstore attestation is common and not indicative of risk here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.3.0 | 2 / 13 | |
| 0.2.5 | 2 / 13 | |
| 0.2.4 | 2 / 13 | |
| 0.2.3 | 2 / 13 | |
| 0.2.2 | 2 / 13 | |
| 0.2.1 | 2 / 13 | |
| 0.2.0 | 2 / 12 | |
| 0.1.2 | 2 / 12 | |
| 0.1.0 | 2 / 12 |
v0.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-01. 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.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.