← Home

@byteplus/vcloud-sdk-nodejs

npm Repository

Vcloud Byteplus OpenAPI SDK of NodeJs

8
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 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

bytednpmxiujie.1vcloud_fexiongxiong.001zhangshize.fshushushuluofan.0406yanzhen.0756ash.yutiehongjichenyunfei.cshuangkaisheng.0x0wangguangbin.2022xuguoqingzhuhongshuyu

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff source-size-tripled AI (source-diff): Size growth from large generated .d.ts type files for new live service, not a payload. ai
phantom-deps phantom-dep:dayjs AI (phantom-deps): Runtime dependency legitimately imported; stable false positive. ai
phantom-deps phantom-dep:ts-jest AI (phantom-deps): Test framework referenced in jest config; stable false positive. ai
phantom-deps phantom-dep:babel-jest AI (phantom-deps): Test framework referenced in jest config; stable false positive. ai
phantom-deps phantom-dep:@types/node AI (phantom-deps): Standard TypeScript convention dependency; stable false positive. ai

Versions (showing 8 of 8)

Version Deps Published
1.0.7 12 / 25
1.0.6 12 / 25
1.0.5 11 / 25
1.0.4 11 / 25
1.0.3 9 / 23
1.0.2 9 / 23
1.0.1 9 / 23
1.0.0 9 / 23

v1.0.3

2 findings
HIGH Publisher changed: tiehongji → wangyuehan.starry (on 2025-04-17) provenance

This version was published by a different npm account than previous versions on 2025-04-17. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.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.0.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.