@vkontakte/videoplayer-interactive
Movika interactive SDK
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:es2024.esm.js | AI (source-diff): Bundled build-target output consistent with existing es2018/es2015/esnext variants, not injected code. | ai | |
| source-diff | net-exec-file:es2024.cjs.js | AI (source-diff): Bundled build-target output consistent with existing es2018/es2015/esnext variants, not injected code. | ai | |
| provenance | missing-githead | AI (provenance): Trusted publisher, no malicious behavior; minor CI metadata gap. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a related first-party interactiveplatform package, not unvetted. | ai | |
| 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 | |
| dependencies | unvetted-dep:@vkontakte/videoplayer-core | AI (dependencies): First-party VK dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@interactiveplatform/movika-graph-editor | AI (dependencies): Known Movika interactive platform dependency; expected for this SDK. | ai | |
| dependencies | unvetted-dep:@interactiveplatform/movika-manifest | AI (dependencies): Known Movika interactive platform dependency; expected for this SDK. | ai | |
| dependencies | unvetted-dep:@vkontakte/videoplayer-statistics | AI (dependencies): First-party VK dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@vkontakte/videoplayer-shared | AI (dependencies): First-party VK dependency; stable pattern across all versions of this package. | ai |
Versions (showing 51 of 73)
| Version | Deps | Published |
|---|---|---|
| 1.0.73 | 5 / 0 | |
| 1.0.72 | 5 / 0 | |
| 1.0.71 | 5 / 0 | |
| 1.0.70 | 5 / 0 | |
| 1.0.69 | 5 / 0 | |
| 1.0.68 | 5 / 0 | |
| 1.0.67 | 5 / 0 | |
| 1.0.66 | 5 / 0 | |
| 1.0.65 | 5 / 0 | |
| 1.0.64 | 5 / 0 | |
| 1.0.63 | 5 / 0 | |
| 1.0.62 | 5 / 0 | |
| 1.0.61 | 5 / 0 | |
| 1.0.60 | 5 / 0 | |
| 1.0.59 | 5 / 0 | |
| 1.0.58 | 5 / 0 | |
| 1.0.57 | 5 / 0 | |
| 1.0.56 | 5 / 0 | |
| 1.0.55 | 5 / 0 | |
| 1.0.54 | 5 / 0 | |
| 1.0.53 | 5 / 0 | |
| 1.0.52 | 5 / 0 | |
| 1.0.51 | 5 / 0 | |
| 1.0.50 | 5 / 0 | |
| 1.0.49 | 5 / 0 | |
| 1.0.48 | 5 / 0 | |
| 1.0.47 | 5 / 0 | |
| 1.0.46 | 5 / 0 | |
| 1.0.45 | 5 / 0 | |
| 1.0.44 | 5 / 0 | |
| 1.0.43 | 5 / 0 | |
| 1.0.42 | 5 / 0 | |
| 1.0.41 | 5 / 0 | |
| 1.0.40 | 5 / 0 | |
| 1.0.39 | 5 / 0 | |
| 1.0.38 | 5 / 0 | |
| 1.0.37 | 5 / 0 | |
| 1.0.36 | 5 / 0 | |
| 1.0.35 | 5 / 0 | |
| 1.0.34 | 5 / 0 | |
| 1.0.33 | 5 / 0 | |
| 1.0.32 | 5 / 0 | |
| 1.0.31 | 5 / 0 | |
| 1.0.30 | 5 / 0 | |
| 1.0.29 | 5 / 0 | |
| 1.0.28 | 5 / 0 | |
| 1.0.27 | 5 / 0 | |
| 1.0.26 | 5 / 0 | |
| 1.0.25 | 5 / 0 | |
| 1.0.24 | 5 / 0 | |
| 1.0.23 | 5 / 0 |
v1.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.36
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: odnoklassniki-ops.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.35
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: odnoklassniki-ops.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.34
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: odnoklassniki-ops.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: odnoklassniki-ops.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: odnoklassniki-ops.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: odnoklassniki-ops.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: odnoklassniki-ops.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: odnoklassniki-ops.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: odnoklassniki-ops.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.