@player-ui/react
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Established @player-ui monorepo; missing gitHead reflects CI environment change, not a supply-chain risk. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across the entire @player-ui release suite; low risk given package age and track record. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo scoped package; missing description is consistent across the @player-ui namespace. | ai | |
| dependencies | unvetted-dep:tapable-ts | AI (dependencies): tapable-ts is a well-known typed wrapper for webpack's tapable; no malicious indicators. | ai | |
| dependencies | unvetted-dep:@player-ui/player | AI (dependencies): Same monorepo/publisher; version-locked to matching release. Not an independent risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo package; missing metadata is a hygiene issue, not a spam/malware indicator for this established library. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a well-known implicit runtime dep for TypeScript-compiled packages; stable false positive. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.15.3 | 9 / 1 | |
| 0.15.2 | 9 / 1 | |
| 0.15.1 | 9 / 1 | |
| 0.15.0 | 9 / 1 | |
| 0.14.1 | 9 / 1 | |
| 0.14.0 | 9 / 1 | |
| 0.13.0 | 9 / 1 | |
| 0.12.0 | 8 / 1 | |
| 0.11.2 | 8 / 1 | |
| 0.11.1 | 8 / 1 | |
| 0.11.0 | 8 / 1 |
v0.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: player-oss.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: player-oss.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: player-oss.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.