← Home

@playkit-js/kaltura-player-js

npm Repository Homepage
8
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

orenmeadi-mach-kalturashai.kalturaeransakalkalturasemarcheplaykitjs.bot

Keywords

kalturaplayerhtml5 player

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 8 of 8)

Version Deps Published
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

v3.17.85

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.17.84

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.17.83

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.17.82

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.17.81

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.17.80

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.17.78

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.