ibm-cloud-sdk-core
Core functionality to support SDKs generated with IBM's OpenAPI SDK Generator.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from individual IBM dev (dpopp07) to IBM team account (ibm-devx-sdk) with 157 approved packages. Legitimate org transition. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types packages are loaded by TypeScript convention, not direct import. Standard for TS projects. | ai | |
| phantom-deps | phantom-dep:@types/isstream | AI (phantom-deps): @types packages are loaded by TypeScript convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@types/file-type | AI (phantom-deps): @types packages are loaded by TypeScript convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@types/tough-cookie | AI (phantom-deps): @types packages are loaded by TypeScript convention, not direct import. | ai |
Versions (showing 51 of 152)
| Version | Deps | Published |
|---|---|---|
| 5.4.15 | 15 / 0 | |
| 5.4.14 | 16 / 0 | |
| 5.4.13 | 16 / 0 | |
| 5.4.12 | 16 / 0 | |
| 5.4.11 | 16 / 0 | |
| 5.4.10 | 16 / 0 | |
| 5.4.9 | 16 / 0 | |
| 5.4.8 | 15 / 0 | |
| 5.4.7 | 15 / 0 | |
| 5.4.6 | 15 / 0 | |
| 5.4.5 | 15 / 0 | |
| 5.4.4 | 15 / 0 | |
| 5.4.3 | 15 / 0 | |
| 5.4.2 | 15 / 0 | |
| 5.4.1 | 15 / 0 | |
| 5.4.0 | 15 / 0 | |
| 5.3.2 | 15 / 0 | |
| 5.3.1 | 15 / 0 | |
| 5.3.0 | 15 / 0 | |
| 5.2.0 | 15 / 0 | |
| 5.1.4 | 15 / 0 | |
| 5.1.3 | 15 / 0 | |
| 5.1.2 | 15 / 0 | |
| 5.1.1 | 15 / 0 | |
| 5.1.0 | 15 / 0 | |
| 5.0.2 | 15 / 0 | |
| 5.0.1 | 15 / 0 | |
| 5.0.0 | 15 / 0 | |
| 4.3.3 | 16 / 0 | |
| 4.3.2 | 15 / 0 | |
| 4.3.1 | 18 / 0 | |
| 4.3.0 | 18 / 0 | |
| 4.2.5 | 19 / 0 | |
| 4.2.4 | 19 / 0 | |
| 4.2.3 | 19 / 0 | |
| 4.2.2 | 19 / 0 | |
| 4.2.1 | 19 / 0 | |
| 4.2.0 | 19 / 0 | |
| 4.1.5 | 19 / 0 | |
| 4.1.4 | 18 / 0 | |
| 4.1.3 | 18 / 0 | |
| 4.1.2 | 18 / 0 | |
| 4.1.1 | 18 / 0 | |
| 4.1.0 | 18 / 0 | |
| 4.0.9 | 18 / 0 | |
| 4.0.8 | 21 / 0 | |
| 4.0.7 | 21 / 0 | |
| 4.0.6 | 21 / 0 | |
| 4.0.5 | 21 / 0 | |
| 4.0.4 | 21 / 0 | |
| 4.0.3 | 21 / 0 |
v5.4.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
2 findingsThis version was published by a different npm account than previous versions on 2024-09-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
2 findingsThis version was published by a different npm account than previous versions on 2023-05-18. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
2 findingsThis version was published by a different npm account than previous versions on 2023-03-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
2 findingsThis version was published by a different npm account than previous versions on 2023-02-27. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.