← Home

@playkit-js/playkit-js-ivq

npm

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

12
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

orenmeadi-mach-kalturashai.kalturaeransakalkalturasemarcheplaykitjs.bot

Keywords

ivqquizkalturaplayerplaykit-jsplaykit-js-ivqhtml5 player

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@playkit-js/common AI (phantom-deps): Same-org dep; phantom-dep heuristic fires as false positive for this package's build pattern. ai
phantom-deps phantom-dep:@playkit-js/playkit-js-ui AI (phantom-deps): Same-org dep; phantom-dep heuristic fires as false positive for this package's build pattern. ai
phantom-deps phantom-dep:@playkit-js/webpack-common AI (phantom-deps): Same-org dep; phantom-dep heuristic fires as false positive for this package's build pattern. ai

Versions (showing 12 of 12)

Version Deps Published
3.7.26 3 / 19
3.7.25 3 / 19
3.7.24 3 / 19
3.7.23 3 / 19
3.7.22 3 / 19
3.7.20 3 / 19
3.7.19 3 / 19
3.7.18 3 / 19
3.7.17 3 / 19
3.7.16 3 / 19
3.7.15 3 / 19
3.7.14 3 / 19

v3.7.22

1 finding
LOW No provenance attestation provenance

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

v3.7.20

1 finding
LOW No provenance attestation provenance

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

v3.7.19

1 finding
LOW No provenance attestation provenance

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

v3.7.18

1 finding
LOW No provenance attestation provenance

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

v3.7.17

1 finding
LOW No provenance attestation provenance

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

v3.7.16

1 finding
LOW No provenance attestation provenance

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

v3.7.15

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.

v3.7.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.