@player-ui/player
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; missing description/repo/keywords is normal for scoped workspace packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package pattern; no description is expected. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper; phantom-dep false positive for compiled TS packages. | ai | |
| phantom-deps | phantom-dep:@types/dlv | AI (phantom-deps): Type-only package; not directly imported at runtime by design. | ai | |
| phantom-deps | phantom-dep:error-polyfill | AI (phantom-deps): Referenced in config/polyfill context, not direct import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@player-ui/make-flow | AI (phantom-deps): Same-org scoped package; phantom-dep heuristic unreliable for monorepo siblings. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.15.3 | 13 / 0 | |
| 0.15.2 | 13 / 0 | |
| 0.14.0 | 13 / 0 | |
| 0.13.0 | 13 / 0 | |
| 0.12.0 | 13 / 0 | |
| 0.11.2 | 13 / 0 | |
| 0.11.1 | 13 / 0 | |
| 0.11.0 | 13 / 0 |
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.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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.