@vkontakte/calls-sdk
Library for video calls based on the vk.com platform
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| license | copyleft-license:GPL-3.0 | AI (license): Package is intentionally GPL-3.0 licensed by VK; stable across all versions. | ai | |
| dependencies | unvetted-dep:messagepack | AI (dependencies): Stable dependency of this VK SDK across many versions; no malicious indicators. | ai | |
| dependencies | unvetted-dep:@vkontakte/libvpx | AI (dependencies): First-party VK package (libvpx binding); consistent with WebRTC SDK use. | ai | |
| dependencies | unvetted-dep:simple-ebml-builder | AI (dependencies): Small EBML utility; expected for WebRTC/media recording SDK. | ai | |
| dependencies | unvetted-dep:@vkontakte/calls-audio-effects | AI (dependencies): First-party VK package; stable dependency of this SDK. | ai | |
| dependencies | unvetted-dep:@vkontakte/calls-video-effects | AI (dependencies): First-party VK package; stable dependency of this SDK. | ai | |
| dependencies | unvetted-dep:@vkontakte/calls-vmoji | AI (dependencies): First-party VK package; stable dependency of this SDK. | ai | |
| provenance | no-provenance | AI (provenance): Established VK platform SDK; no provenance is consistent with its long publish history predating Sigstore adoption. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.8.10 | 9 / 0 | |
| 2.8.9 | 9 / 0 | |
| 2.8.8 | 9 / 0 | |
| 2.8.7 | 9 / 0 | |
| 2.8.6 | 9 / 0 |
v2.8.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.