← Home

@volcengine/vegame

npm
30
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

zhang6464bytednpmvcloud_fezhouykmsq17xiongxiong.001shushushuluofan.0406yanzhen.0756ash.yuchenyunfei.csyuhuajian.1yunyi_6512ethan.bytetiebytewangmengyuanxuguoqingvolc-iaas-test01volc-iaasxiujie.1zhuhongshuyu

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): No behavior change vs prior approved version; likely publish env variance for trusted maintainer. ai
dependencies unvetted-dep:@byted/ve-core AI (dependencies): First-party ByteDance/Volcengine dependency, not an unrelated supply-chain risk. ai
phantom-deps phantom-dep:core-js AI (phantom-deps): Known implicit polyfill dependency. ai
phantom-deps phantom-dep:@byted/ve-core AI (phantom-deps): Referenced via config, first-party sibling package. ai
source-diff encoded-string-file:dist/index.umd.min.js AI (source-diff): Long encoded strings are standard minification artifacts in this SDK's UMD bundle; no malicious payload pattern visible. ai
bogus-package bogus-package AI (bogus-package): Established Volcengine SDK; sparse metadata is intentional for a scoped corporate package. ai

Versions (showing 30 of 30)

Version Deps Published
1.78.0 0 / 0
1.77.0 0 / 0
1.75.2 0 / 0
1.75.1 0 / 0
1.74.1 0 / 0
1.74.0 0 / 0
1.72.1 0 / 0
1.72.0 0 / 0
1.71.0 0 / 0
1.69.0 0 / 0
1.68.0 0 / 0
1.67.1 0 / 0
1.67.0 0 / 0
1.66.0 0 / 0
1.65.0 0 / 0
1.62.0 0 / 0
1.61.0 0 / 0
1.56.1 0 / 0
1.56.0 2 / 0
1.55.0 0 / 0
1.53.2 0 / 0
1.53.1 0 / 0
1.53.0 0 / 0
1.51.2 0 / 0
1.48.1 0 / 0
1.48.0 0 / 0
1.45.0 0 / 0
1.44.0 0 / 0
1.43.1 0 / 0
1.43.0 0 / 0

v1.62.0

1 finding
LOW No provenance attestation provenance

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

v1.61.0

1 finding
LOW No provenance attestation provenance

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

v1.56.1

1 finding
LOW No provenance attestation provenance

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

v1.56.0

1 finding
LOW No provenance attestation provenance

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

v1.55.0

1 finding
LOW No provenance attestation provenance

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

v1.53.2

1 finding
LOW No provenance attestation provenance

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

v1.53.1

1 finding
LOW No provenance attestation provenance

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

v1.53.0

1 finding
LOW No provenance attestation provenance

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

v1.51.2

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vcloud_fe.

LOW No provenance attestation provenance

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

v1.48.1

1 finding
LOW No provenance attestation provenance

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

v1.48.0

1 finding
LOW No provenance attestation provenance

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

v1.45.0

1 finding
LOW No provenance attestation provenance

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

v1.44.0

1 finding
LOW No provenance attestation provenance

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

v1.43.1

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

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.