@vkontakte/videoplayer-shared
Shared code for vk.com videoplayer
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are canonical OpenTelemetry packages matching existing telemetry dependencies; no malicious signal. | ai | |
| dependencies | unvetted-dep:@tracer/opentelemetry | AI (dependencies): Internal VK Artifactory URL; consistent across versions of this org's packages. | ai | |
| npm-metadata | url-dep:@tracer/opentelemetry | AI (npm-metadata): Points to vkpartner.ru Artifactory — VK's own registry; stable pattern for this org. | ai | |
| license | copyleft-license:GPL-3.0 | AI (license): GPL-3.0 is declared in package.json; expected for vk.com shared library. | ai | |
| dependencies | unvetted-dep:@apptracer/opentelemetry | AI (dependencies): VK's own OpenTelemetry wrapper; consistent with this package's stated purpose across all versions. | ai | |
| dependencies | unvetted-dep:@apptracer/sdk | AI (dependencies): VK's own telemetry SDK; consistent with this package's stated purpose across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Long-established VK package; absence of Sigstore provenance is consistent across all 1001 versions. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 1.0.91 | 6 / 0 | |
| 1.0.90 | 6 / 0 | |
| 1.0.89 | 4 / 0 | |
| 1.0.88 | 4 / 0 | |
| 1.0.87 | 4 / 0 | |
| 1.0.86 | 4 / 0 | |
| 1.0.85 | 4 / 0 | |
| 1.0.84 | 4 / 0 | |
| 1.0.83 | 4 / 0 | |
| 1.0.82 | 4 / 0 | |
| 1.0.81 | 3 / 0 | |
| 1.0.80 | 3 / 0 | |
| 1.0.79 | 3 / 0 | |
| 1.0.78 | 3 / 0 | |
| 1.0.77 | 3 / 0 | |
| 1.0.76 | 3 / 0 | |
| 1.0.75 | 3 / 0 | |
| 1.0.74 | 3 / 0 | |
| 1.0.73 | 3 / 0 | |
| 1.0.72 | 3 / 0 | |
| 1.0.71 | 3 / 0 | |
| 1.0.70 | 3 / 0 | |
| 1.0.69 | 3 / 0 | |
| 1.0.68 | 3 / 0 | |
| 1.0.67 | 3 / 0 | |
| 1.0.66 | 3 / 0 | |
| 1.0.65 | 3 / 0 | |
| 1.0.64 | 3 / 0 | |
| 1.0.63 | 3 / 0 | |
| 1.0.61 | 3 / 0 | |
| 1.0.60 | 3 / 0 |
v1.0.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.88
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.0.87
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.0.86
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.0.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.84
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.0.83
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.0.82
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.0.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.79
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.0.78
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.0.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.76
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.0.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.74
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.0.73
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.0.72
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.0.71
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.0.70
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.0.69
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.0.68
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.0.67
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.0.66
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.0.65
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.0.64
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.0.63
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.0.61
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.0.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.