@vkontakte/videoplayer-core
Videoplayer core library 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, 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.cjs.js | AI (source-diff): New bundler target output; polyfill/HLS patterns, not injected malware. | ai | |
| source-diff | net-exec-file:es2024.esm.js | AI (source-diff): Same as cjs counterpart; standard bundled build target. | ai | |
| provenance | missing-githead | AI (provenance): Publish metadata gap from trusted long-standing publisher, no behavioral change. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same VK org transition, consistent with publisher change. | ai | |
| provenance | publisher-changed | AI (provenance): Trusted publisher with strong track record; internal VK org transition. | ai | |
| source-diff | obfuscated-file:types/providers/utils/parsers/__tests/data.d.ts | AI (source-diff): Long lines are inline XML test fixture data (MPD manifest), not obfuscated code. Stable false positive for this package. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() appears in bundled debug logging code from VK's own video player; not an evasion pattern. | ai |
Versions (showing 67 of 167)
| Version | Deps | Published |
|---|---|---|
| 2.0.67 | 4 / 0 | |
| 2.0.66 | 4 / 0 | |
| 2.0.65 | 4 / 0 | |
| 2.0.64 | 4 / 0 | |
| 2.0.63 | 4 / 0 | |
| 2.0.62 | 4 / 0 | |
| 2.0.61 | 4 / 0 | |
| 2.0.60 | 4 / 0 | |
| 2.0.59 | 4 / 0 | |
| 2.0.58 | 4 / 0 | |
| 2.0.57 | 4 / 0 | |
| 2.0.56 | 4 / 0 | |
| 2.0.55 | 4 / 0 | |
| 2.0.54 | 4 / 0 | |
| 2.0.53 | 4 / 0 | |
| 2.0.52 | 4 / 0 | |
| 2.0.51 | 4 / 0 | |
| 2.0.50 | 4 / 0 | |
| 2.0.49 | 4 / 0 | |
| 2.0.48 | 4 / 0 | |
| 2.0.47 | 4 / 0 | |
| 2.0.46 | 4 / 0 | |
| 2.0.45 | 4 / 0 | |
| 2.0.44 | 4 / 0 | |
| 2.0.43 | 4 / 0 | |
| 2.0.42 | 4 / 0 | |
| 2.0.41 | 4 / 0 | |
| 2.0.40 | 4 / 0 | |
| 2.0.39 | 4 / 0 | |
| 2.0.38 | 4 / 0 | |
| 2.0.37 | 4 / 0 | |
| 2.0.36 | 4 / 0 | |
| 2.0.35 | 4 / 0 | |
| 2.0.34 | 4 / 0 | |
| 2.0.33 | 4 / 0 | |
| 2.0.32 | 4 / 0 | |
| 2.0.31 | 4 / 0 | |
| 2.0.30 | 4 / 0 | |
| 2.0.29 | 4 / 0 | |
| 2.0.28 | 4 / 0 | |
| 2.0.27 | 4 / 0 | |
| 2.0.26 | 4 / 0 | |
| 2.0.25 | 4 / 0 | |
| 2.0.24 | 4 / 0 | |
| 2.0.23 | 4 / 0 | |
| 2.0.22 | 4 / 0 | |
| 2.0.21 | 4 / 0 | |
| 2.0.20 | 4 / 0 | |
| 2.0.19 | 4 / 0 | |
| 2.0.18 | 4 / 0 | |
| 2.0.17 | 4 / 0 | |
| 2.0.16 | 3 / 0 | |
| 2.0.15 | 3 / 0 | |
| 2.0.14 | 3 / 0 | |
| 2.0.13 | 3 / 0 | |
| 2.0.12 | 3 / 0 | |
| 2.0.11 | 3 / 0 | |
| 2.0.10 | 3 / 0 | |
| 2.0.9 | 3 / 0 | |
| 2.0.8 | 3 / 0 | |
| 2.0.7 | 3 / 0 | |
| 2.0.6 | 3 / 0 | |
| 2.0.5 | 3 / 0 | |
| 2.0.4 | 3 / 0 | |
| 2.0.3 | 3 / 0 | |
| 2.0.2 | 3 / 0 | |
| 2.0.1 | 3 / 0 |
v2.0.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.