ibm-cos-sdk
5
Versions
—
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
cos-sdk
Keywords
apis3iam
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:credential-dir-access | AI (semgrep): IBM COS SDK legitimately reads ~/.aws/credentials for AWS-compatible credential loading; stable pattern across all versions. | ai | |
| phantom-deps | phantom-dep:xmlbuilder | AI (phantom-deps): xmlbuilder is declared as a runtime dependency and used transitively via xml2js/AWS SDK internals; phantom-dep heuristic fires but it is a legitimate dependency. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.15.1 | 7 / 15 | |
| 1.15.0 | 7 / 15 | |
| 1.14.2 | 7 / 15 | |
| 1.14.1 | 7 / 15 | |
| 1.14.0 | 7 / 15 |
v1.14.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.14.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.