@playkit-js/playkit-js-youtube
[](https://github.com/kaltura/playkit-js-youtube/actions/workflows/run_canary_full_flow.yaml) [ relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Kaltura package; lack of provenance is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.3.2 | 1 / 54 | |
| 2.3.1 | 1 / 54 | |
| 2.3.0 | 1 / 54 | |
| 2.2.6 | 1 / 54 | |
| 2.2.5 | 1 / 54 | |
| 2.2.4 | 1 / 54 | |
| 2.2.3 | 1 / 54 |
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.