← Home

@volcengine/dataleap20260301

npm

swagger client for @volcengine/dataleap20260301

4
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

zhang6464fanziqingjjjkkkaaabytednpmvcloud_fezhouykzyqhiboya1127kongfanzizhangjing.2037msq17huangkaisheng.0x0zhebuchongwangrui.trgaowujianvikinglbxugaroyxuemanchi.bytedancezhujie.0kaijie_bytezhenxiongqqdxygtank_xiediyijieniguitangjinwei123songhnpamaforcexuxiaofeng.workyangaofeng.lykvtiebytexiongxiong.001shushushuluofan.0406yanzhen.0756ash.yuchenyunfei.csyuhuajian.1yunyi_6512ethan.bytewangmengyuanxuguoqingvolc-iaas-test01volc-iaasxiujie.1zhuhongshuyu

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): No code/behavior change; likely CI publish env variance for a scaffolded SDK client. ai
maintainer-change maintainer-added AI (maintainer-change): Bulk maintainer list typical of large-org (volcengine) package management, no malicious behavior present. ai
provenance no-provenance AI (provenance): Volcengine SDK family; provenance absence is consistent across the org's packages and not a risk indicator here. ai

Versions (showing 4 of 4)

Version Deps Published
1.0.4 1 / 2
1.0.3 1 / 2
1.0.2 1 / 2
1.0.1 1 / 2

v1.0.4

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: diyijienigui.

INFO No provenance attestation provenance

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