@vkontakte/videoplayer-interactive GPL-3.0 32 versions

@vkontakte/videoplayer-interactive

npm Homepage

Movika interactive SDK

32

Versions

GPL-3.0

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

odnoklassniki-opsvkvideocalls-sdk-web

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	dormant-publish	AI (publish-pattern): Publisher vkvideo has strong track record (444 approved); no content changes from prior version indicate legitimate resumption.	ai	2026/05/04
dependencies	unvetted-dep:@vkontakte/videoplayer-core	AI (dependencies): First-party VK dependency; stable pattern across all versions of this package.	ai	2026/04/29
dependencies	unvetted-dep:@vkontakte/videoplayer-shared	AI (dependencies): First-party VK dependency; stable pattern across all versions of this package.	ai	2026/04/29
dependencies	unvetted-dep:@vkontakte/videoplayer-statistics	AI (dependencies): First-party VK dependency; stable pattern across all versions of this package.	ai	2026/04/29
dependencies	unvetted-dep:@interactiveplatform/movika-manifest	AI (dependencies): Known Movika interactive platform dependency; expected for this SDK.	ai	2026/04/29
dependencies	unvetted-dep:@interactiveplatform/movika-graph-editor	AI (dependencies): Known Movika interactive platform dependency; expected for this SDK.	ai	2026/04/29

Versions (showing 32 of 32)

Version	Deps	Published
1.0.68	5 / 0	2026-06-02
1.0.67	5 / 0	2026-05-21
1.0.66	5 / 0	2026-04-27
1.0.65	5 / 0	2026-04-13
1.0.64	5 / 0	2026-04-07
1.0.63	5 / 0	2026-03-26
1.0.62	5 / 0	2026-03-24
1.0.61	5 / 0	2026-03-11
1.0.60	5 / 0	2026-03-10
1.0.59	5 / 0	2026-02-24
1.0.58	5 / 0	2026-02-12
1.0.57	5 / 0	2026-02-10
1.0.56	5 / 0	2026-01-28
1.0.55	5 / 0	2025-12-16
1.0.54	5 / 0	2025-12-04
1.0.53	5 / 0	2025-11-24
1.0.52	5 / 0	2025-11-14
1.0.51	5 / 0	2025-11-06
1.0.50	5 / 0	2025-10-24
1.0.49	5 / 0	2025-10-20
1.0.48	5 / 0	2025-10-07
1.0.47	5 / 0	2025-09-23
1.0.46	5 / 0	2025-09-10
1.0.45	5 / 0	2025-08-22
1.0.44	5 / 0	2025-08-20
1.0.43	5 / 0	2025-08-05
1.0.42	5 / 0	2025-07-23
1.0.41	5 / 0	2025-07-09
1.0.40	5 / 0	2025-07-02
1.0.39	5 / 0	2025-06-10
1.0.38	5 / 0	2025-06-05
1.0.37	5 / 0	2025-05-21

v1.0.68

1 finding

LOW No provenance attestation provenance

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

v1.0.67

1 finding

LOW No provenance attestation provenance

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

v1.0.65

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

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

1 finding

LOW No provenance attestation provenance

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

v1.0.62

1 finding

LOW No provenance attestation provenance

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

v1.0.61

1 finding

LOW No provenance attestation provenance

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

v1.0.60

1 finding

LOW No provenance attestation provenance

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

v1.0.59

1 finding

LOW No provenance attestation provenance

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

v1.0.58

1 finding

LOW No provenance attestation provenance

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

v1.0.57

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

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

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

1 finding

LOW No provenance attestation provenance

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

v1.0.53

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

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

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

1 finding

LOW No provenance attestation provenance

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

v1.0.49

1 finding

LOW No provenance attestation provenance

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

v1.0.48

1 finding

LOW No provenance attestation provenance

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

v1.0.47

1 finding

LOW No provenance attestation provenance

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

v1.0.46

1 finding

LOW No provenance attestation provenance

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

v1.0.45

1 finding

LOW No provenance attestation provenance

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

v1.0.44

1 finding

LOW No provenance attestation provenance

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

v1.0.43

1 finding

LOW No provenance attestation provenance

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

v1.0.42

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

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

1 finding

LOW No provenance attestation provenance

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

v1.0.39

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

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

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.