@playkit-js/playkit-js-downloads No license 48 versions

@playkit-js/playkit-js-downloads

npm Homepage

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

48

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:rimraf	AI (phantom-deps): rimraf is a declared build-tool dep used in npm scripts; not imported at runtime.	ai	2026/04/29
phantom-deps	phantom-dep:copyfiles	AI (phantom-deps): copyfiles is a declared build-tool dep used in npm scripts; not imported at runtime.	ai	2026/04/29

Versions (showing 48 of 48)

Version	Deps	Published
1.5.1	3 / 34	2026-06-04
1.5.0	3 / 34	2026-05-20
1.4.12	3 / 34	2026-05-07
1.4.11	3 / 34	2026-03-26
1.4.7	3 / 34	2025-11-27
1.4.6	3 / 34	2025-11-06
1.4.5	3 / 34	2025-10-23
1.4.4	3 / 34	2025-05-22
1.4.3	3 / 34	2025-04-24
1.4.2	3 / 34	2025-04-02
1.4.1	3 / 34	2025-03-06
1.4.0	3 / 34	2025-03-06
1.3.16	2 / 34	2025-01-23
1.3.15	2 / 34	2024-12-19
1.3.14	2 / 34	2024-12-01
1.3.13	2 / 34	2024-11-14
1.3.12	2 / 34	2024-11-14
1.3.11	2 / 34	2024-11-01
1.3.10	2 / 34	2024-10-13
1.3.9	2 / 34	2024-09-19
1.3.8	2 / 24	2024-08-25
1.3.7	2 / 24	2024-08-05
1.3.6	2 / 24	2024-08-04
1.3.5	2 / 24	2024-08-03
1.3.4	2 / 24	2024-06-30
1.3.3	2 / 24	2024-06-16
1.3.2	2 / 24	2024-06-02
1.3.1	2 / 25	2024-05-19
1.3.0	2 / 25	2024-05-19
1.2.2	2 / 25	2024-05-02
1.2.1	2 / 25	2024-04-10
1.2.0	2 / 25	2024-04-09
1.1.2	2 / 25	2024-03-14
1.1.1	2 / 25	2024-02-04
1.1.0	2 / 25	2024-01-07
1.0.17	2 / 25	2023-12-21
1.0.16	2 / 25	2023-12-21
1.0.15	3 / 24	2023-12-10
1.0.14	3 / 24	2023-11-28
1.0.13	3 / 24	2023-11-12
1.0.12	3 / 24	2023-11-12
1.0.11	3 / 24	2023-11-12
1.0.10	0 / 24	2023-09-11
1.0.9	0 / 24	2023-09-11
1.0.8	0 / 24	2023-07-26
1.0.7	0 / 23	2023-06-29
1.0.6	0 / 23	2023-06-11
1.0.5	0 / 23	2023-06-07

v1.4.3

1 finding

LOW No provenance attestation provenance

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

v1.4.2

1 finding

LOW No provenance attestation provenance

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

v1.4.1

1 finding

LOW No provenance attestation provenance

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

v1.4.0

1 finding

LOW No provenance attestation provenance

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

v1.3.16

1 finding

LOW No provenance attestation provenance

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

v1.3.15

1 finding

LOW No provenance attestation provenance

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

v1.3.14

1 finding

LOW No provenance attestation provenance

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

v1.3.13

1 finding

LOW No provenance attestation provenance

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

v1.3.12

1 finding

LOW No provenance attestation provenance

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

v1.3.11

1 finding

LOW No provenance attestation provenance

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

v1.3.10

1 finding

LOW No provenance attestation provenance

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

v1.3.9

1 finding

LOW No provenance attestation provenance

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

v1.3.8

1 finding

LOW No provenance attestation provenance

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

v1.3.7

1 finding

LOW No provenance attestation provenance

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

v1.3.6

1 finding

LOW No provenance attestation provenance

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

v1.3.5

1 finding

LOW No provenance attestation provenance

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

v1.3.4

1 finding

LOW No provenance attestation provenance

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

v1.3.3

1 finding

LOW No provenance attestation provenance

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

v1.3.2

1 finding

LOW No provenance attestation provenance

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

v1.3.1

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.2

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

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.2

1 finding

LOW No provenance attestation provenance

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.17

1 finding

LOW No provenance attestation provenance

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

v1.0.16

1 finding

LOW No provenance attestation provenance

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

v1.0.15

1 finding

LOW No provenance attestation provenance

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

v1.0.14

1 finding

LOW No provenance attestation provenance

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

v1.0.13

1 finding

LOW No provenance attestation provenance

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

v1.0.12

1 finding

LOW No provenance attestation provenance

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

v1.0.11

1 finding

LOW No provenance attestation provenance

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

v1.0.10

1 finding

LOW No provenance attestation provenance

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

v1.0.9

1 finding

LOW No provenance attestation provenance

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

v1.0.8

1 finding

LOW No provenance attestation provenance

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

v1.0.7

1 finding

LOW No provenance attestation provenance

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

v1.0.6

1 finding

LOW No provenance attestation provenance

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

v1.0.5

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.