← Home

cos-nodejs-sdk-v5

5
Versions
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

galenyipyinshawnraocarsonxutianfengwonderswangannexwu

Keywords

tencenttencent cloudqcloudcoscos-sdk

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): Demo-only utility script, not shipped SDK code. ai
dependencies unvetted-dep:cos-request AI (dependencies): First-party fork of `request` maintained under Tencent's cos-nodejs-sdk-v5 org. ai
dependencies unvetted-dep:cos-fast-xml-parser AI (dependencies): First-party fork of fast-xml-parser used to replace deprecated dep. ai
semgrep semgrep:base64-decode AI (semgrep): Decodes auth header string for parsing; no code execution involved. Stable false positive for this SDK. ai
dependencies unvetted-dep:request AI (dependencies): request is a well-known deprecated HTTP library; no security risk specific to this package's usage. ai

Versions (showing 5 of 5)

Version Deps Published
3.0.0 3 / 6
2.15.4 4 / 6
2.15.3 4 / 6
2.15.1 4 / 6
2.14.3 4 / 7

v3.0.0

1 finding
LOW No provenance attestation provenance

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

v2.14.3

2 findings
HIGH child-process-import: demo/util.js:24 semgrep

child_process imported — can execute arbitrary system commands Source: https://github.com/tencentyun/cos-nodejs-sdk-v5/blob/68ba295a236a2cfc56419a43c96a881c5c7dcab0/demo/util.js#L24 22 | break; 23 | } > 24 | var exec = require('child_process').exec; 25 | exec(cmd, function (err, stdout, stderr) { 26 | cb(err);

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.