← Home

@playkit-js/playkit-js-ima

npm Repository Homepage

[![Build Status](https://github.com/kaltura/playkit-js-ima/actions/workflows/run_canary_full_flow.yaml/badge.svg)](https://github.com/kaltura/playkit-js-ima/actions/workflows/run_canary_full_flow.yaml) [![code style: prettier](https://img.shields.io/badge

4
Versions
AGPL-3.0
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

advastvmapimaadsmonetizationkalturaplayerplaykit-jsplaykit-js-imahtml5 player

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata url-dep:javascript-state-machine AI (npm-metadata): Kaltura-maintained fork pinned to a specific tag; stable pattern across this package's versions. ai
phantom-deps phantom-dep:raw-loader AI (phantom-deps): raw-loader is a webpack loader used in build config, not directly imported in source — stable false positive. ai
phantom-deps phantom-dep:javascript-state-machine AI (phantom-deps): Used via webpack bundle, not direct import — stable false positive for this package. ai

Versions (showing 4 of 4)

Version Deps Published
1.7.1 2 / 52
1.7.0 2 / 52
1.6.14 2 / 51
1.6.13 2 / 51

v1.7.0

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.

v1.6.14

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.

v1.6.13

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.