@huaweicloud/huaweicloud-sdk-all
Huawei Cloud SDK for Node.js includes all cloud services
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@huaweicloud/huaweicloud-sdk-versatile | AI (phantom-deps): Meta-package with no code; phantom-dep is structural false positive. | ai | |
| phantom-deps | phantom-dep:@huaweicloud/huaweicloud-sdk-cph | AI (phantom-deps): Same structural false positive as all other phantom-dep findings for this meta-package. | ai | |
| phantom-deps | phantom-dep:@huaweicloud/huaweicloud-sdk-ucs | AI (phantom-deps): Same structural false positive as all other phantom-dep findings for this meta-package. | ai | |
| phantom-deps | phantom-dep:@huaweicloud/huaweicloud-sdk-deh | AI (phantom-deps): Same structural false positive as all other phantom-dep findings for this meta-package. | ai | |
| phantom-deps | phantom-dep:@huaweicloud/huaweicloud-sdk-esw | AI (phantom-deps): Same structural false positive as all other phantom-dep findings for this meta-package. | ai | |
| phantom-deps | phantom-dep:@huaweicloud/huaweicloud-sdk-rfs | AI (phantom-deps): Same structural false positive as all other phantom-dep findings for this meta-package. | ai | |
| phantom-deps | phantom-dep:@huaweicloud/huaweicloud-sdk-dcc | AI (phantom-deps): Same structural false positive as all other phantom-dep findings for this meta-package. | ai | |
| phantom-deps | phantom-dep:@huaweicloud/huaweicloud-sdk-codeartside | AI (phantom-deps): Meta-package pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@huaweicloud/huaweicloud-sdk-as | AI (phantom-deps): Meta-package with only package.json; all deps are intentionally declared but not directly imported. | ai | |
| phantom-deps | phantom-dep:@huaweicloud/huaweicloud-sdk-cc | AI (phantom-deps): Meta-package pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@huaweicloud/huaweicloud-sdk-dc | AI (phantom-deps): Meta-package pattern; stable false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Umbrella SDK aggregator; sparse README and no keywords are expected for this package type. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 3.1.196 | 129 / 0 | |
| 3.1.193 | 128 / 0 | |
| 3.1.181 | 126 / 0 | |
| 3.1.180 | 125 / 0 | |
| 3.1.179 | 125 / 0 | |
| 3.1.174 | 119 / 0 | |
| 3.1.155 | 108 / 0 | |
| 3.1.154 | 106 / 0 | |
| 3.1.153 | 106 / 0 | |
| 3.1.151 | 105 / 0 | |
| 3.1.148 | 104 / 0 |
v3.1.196
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.181
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.180
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.179
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.174
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.155
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.154
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.153
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.151
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.148
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.