@playkit-js/kaltura-player-js
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:hls.js | AI (phantom-deps): hls.js is a bundled media engine dependency; not directly imported in source but used via build config — stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:shaka-player | AI (phantom-deps): shaka-player is a bundled media engine dependency; same pattern as hls.js — stable for this package. | ai | |
| phantom-deps | phantom-dep:@playkit-js/webpack-common | AI (phantom-deps): Same-org build tooling referenced in webpack config; not a runtime import — stable false positive for this package. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 3.17.91 | 8 / 37 | |
| 3.17.90 | 8 / 37 | |
| 3.17.89 | 8 / 37 | |
| 3.17.88 | 8 / 37 | |
| 3.17.87 | 8 / 37 | |
| 3.17.86 | 8 / 37 | |
| 3.17.85 | 8 / 37 | |
| 3.17.84 | 8 / 37 | |
| 3.17.83 | 8 / 37 | |
| 3.17.82 | 8 / 37 | |
| 3.17.81 | 8 / 37 | |
| 3.17.80 | 8 / 37 | |
| 3.17.79 | 8 / 37 | |
| 3.17.78 | 8 / 37 | |
| 3.17.77 | 8 / 37 | |
| 3.17.76 | 8 / 37 | |
| 3.17.75 | 8 / 37 | |
| 3.17.74 | 8 / 37 | |
| 3.17.73 | 8 / 37 | |
| 3.17.72 | 8 / 37 | |
| 3.17.71 | 8 / 37 | |
| 3.17.70 | 8 / 37 | |
| 3.17.69 | 8 / 37 | |
| 3.17.68 | 8 / 37 | |
| 3.17.67 | 8 / 37 | |
| 3.17.66 | 8 / 37 | |
| 3.17.65 | 8 / 37 | |
| 3.17.64 | 8 / 37 | |
| 3.17.63 | 8 / 37 | |
| 3.17.62 | 8 / 37 | |
| 3.17.61 | 8 / 37 |
v3.17.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.