@vkontakte/videoplayer
Videoplayer 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Likely unused in bundled dist files; publisher has strong track record. | ai | |
| source-diff | net-exec-file-transition:es2018.esm.js | AI (source-diff): Svelte/esbuild bundle: first-party addScript helper + first-party stats telemetry; no dynamic code exec or exfil. | ai | |
| source-diff | obfuscated-file-transition:index.d.ts | AI (source-diff): Bundled TypeScript .d.ts with long lines; readable type declarations, not obfuscation. | ai | |
| source-diff | net-exec-file-transition:es2015.esm.js | AI (source-diff): Svelte/esbuild bundle: first-party addScript helper + first-party stats telemetry; no dynamic code exec or exfil. | ai | |
| source-diff | net-exec-file-transition:es2015.cjs.js | AI (source-diff): Svelte/esbuild bundle: first-party addScript helper + first-party stats telemetry to VK CDN; no eval/fetched-code exec, no exfil. | ai | |
| source-diff | net-exec-file-transition:es2018.cjs.js | AI (source-diff): Svelte/esbuild bundle: first-party addScript helper + first-party stats telemetry; no dynamic code exec or exfil. | ai | |
| provenance | missing-githead | AI (provenance): No behavior change vs prior approved version; publisher has long clean track record. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Ad-tech dep consistent with videoplayer's stated purpose, from same publisher ecosystem. | ai | |
| source-diff | obfuscated-file:esnext.cjs | AI (source-diff): Standard minified build artifact for esnext target; consistent with VK videoplayer's multi-target bundle pattern. | ai | |
| source-diff | obfuscated-file:es2015.cjs | AI (source-diff): Standard minified build artifact for ES2015 target; consistent with VK videoplayer's multi-target bundle pattern. | ai | |
| source-diff | obfuscated-file:es2018.cjs | AI (source-diff): Standard minified build artifact for ES2018 target; consistent with VK videoplayer's multi-target bundle pattern. | ai | |
| source-diff | obfuscated-file:es2024.cjs | AI (source-diff): Standard minified build artifact for ES2024 target; consistent with VK videoplayer's multi-target bundle pattern. | ai | |
| dependencies | unvetted-dep:@adtech/rbadman | AI (dependencies): Internal VK/adtech dependency used consistently across versions of this package; stable false positive. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Fires on Svelte framework internals in bundled output; not actual obfuscation. | ai | |
| license | copyleft-license:GPL-3.0 | AI (license): Package is intentionally GPL-3.0 licensed by VK; stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Long-established VK package with 1043 versions; provenance absence is consistent across all prior releases. | ai | |
| phantom-deps | phantom-dep:@adtech/rbadman | AI (phantom-deps): Ad-tech dep referenced in config files; consistent with VK platform integration across versions. | ai |
Versions (showing 51 of 92)
| Version | Deps | Published |
|---|---|---|
| 1.1.98 | 5 / 0 | |
| 1.1.97 | 5 / 0 | |
| 1.1.96 | 5 / 0 | |
| 1.1.95 | 5 / 0 | |
| 1.1.94 | 5 / 0 | |
| 1.1.93 | 5 / 0 | |
| 1.1.92 | 5 / 0 | |
| 1.1.91 | 5 / 0 | |
| 1.1.90 | 5 / 0 | |
| 1.1.89 | 5 / 0 | |
| 1.1.88 | 5 / 0 | |
| 1.1.87 | 5 / 0 | |
| 1.1.86 | 5 / 0 | |
| 1.1.85 | 5 / 0 | |
| 1.1.84 | 5 / 0 | |
| 1.1.83 | 5 / 0 | |
| 1.1.82 | 5 / 0 | |
| 1.1.81 | 5 / 0 | |
| 1.1.80 | 5 / 0 | |
| 1.1.79 | 5 / 0 | |
| 1.1.78 | 5 / 0 | |
| 1.1.77 | 5 / 0 | |
| 1.1.76 | 5 / 0 | |
| 1.1.60 | 5 / 0 | |
| 1.1.59 | 5 / 0 | |
| 1.1.58 | 5 / 0 | |
| 1.1.57 | 5 / 0 | |
| 1.1.56 | 5 / 0 | |
| 1.1.55 | 5 / 0 | |
| 1.1.54 | 5 / 0 | |
| 1.1.53 | 5 / 0 | |
| 1.1.52 | 5 / 0 | |
| 1.1.51 | 4 / 0 | |
| 1.1.50 | 4 / 0 | |
| 1.1.49 | 4 / 0 | |
| 1.1.48 | 4 / 0 | |
| 1.1.47 | 4 / 0 | |
| 1.1.46 | 4 / 0 | |
| 1.1.45 | 4 / 0 | |
| 1.1.44 | 4 / 0 | |
| 1.1.43 | 4 / 0 | |
| 1.1.42 | 4 / 0 | |
| 1.1.41 | 4 / 0 | |
| 1.1.40 | 4 / 0 | |
| 1.1.39 | 4 / 0 | |
| 1.1.38 | 4 / 0 | |
| 1.1.37 | 4 / 0 | |
| 1.1.36 | 4 / 0 | |
| 1.1.35 | 4 / 0 | |
| 1.1.34 | 4 / 0 | |
| 1.1.33 | 4 / 0 |
v1.1.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.96
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.60
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.59
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.58
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.57
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.56
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.55
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.54
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.53
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.34
6 findingsThis file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
This file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
This file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
This file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.33
6 findingsThis file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
This file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
This file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
This file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.