@huaweicloud/huaweicloud-sdk-iotdm
Huaweicloud SDK for iotdm
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@huaweicloud/huaweicloud-sdk-core | AI (dependencies): First-party Huawei Cloud SDK core dependency; stable pattern across all versions of this package family. | ai | |
| provenance | no-provenance | AI (provenance): Established Huawei Cloud SDK monorepo; provenance attestation not used across the entire package family. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 3.1.199 | 1 / 2 | |
| 3.1.198 | 1 / 2 | |
| 3.1.197 | 1 / 2 | |
| 3.1.196 | 1 / 2 | |
| 3.1.195 | 1 / 2 | |
| 3.1.194 | 1 / 2 | |
| 3.1.193 | 1 / 2 | |
| 3.1.192 | 1 / 2 | |
| 3.1.191 | 1 / 2 | |
| 3.1.186 | 1 / 2 | |
| 3.1.185 | 1 / 2 | |
| 3.1.183 | 1 / 2 | |
| 3.1.178 | 1 / 2 | |
| 3.1.174 | 1 / 2 | |
| 3.1.153 | 1 / 2 |
v3.1.199
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.198
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.197
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.196
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.195
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.194
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.193
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.192
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.191
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.186
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.185
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.183
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.178
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.174
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.153
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.