@huaweicloud/huaweicloud-sdk-smnglobal
Huaweicloud SDK for smnglobal
Supply chain provenance
Status for the latest visible version.
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
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): Core SDK dependency from the same Huawei Cloud publisher; expected and stable across all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Large corporate SDK publisher; provenance absence is common and not a risk signal here. | ai |
Versions (showing 70 of 70)
| Version | Deps | Published |
|---|---|---|
| 3.1.207 | 1 / 2 | |
| 3.1.206 | 1 / 2 | |
| 3.1.205 | 1 / 2 | |
| 3.1.204 | 1 / 2 | |
| 3.1.203 | 1 / 2 | |
| 3.1.202 | 1 / 2 | |
| 3.1.201 | 1 / 2 | |
| 3.1.200 | 1 / 2 | |
| 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.190 | 1 / 2 | |
| 3.1.189 | 1 / 2 | |
| 3.1.188 | 1 / 2 | |
| 3.1.187 | 1 / 2 | |
| 3.1.186 | 1 / 2 | |
| 3.1.185 | 1 / 2 | |
| 3.1.184 | 1 / 2 | |
| 3.1.183 | 1 / 2 | |
| 3.1.182 | 1 / 2 | |
| 3.1.181 | 1 / 2 | |
| 3.1.180 | 1 / 2 | |
| 3.1.179 | 1 / 2 | |
| 3.1.178 | 1 / 2 | |
| 3.1.177 | 1 / 2 | |
| 3.1.176 | 1 / 2 | |
| 3.1.175 | 1 / 2 | |
| 3.1.174 | 1 / 2 | |
| 3.1.173 | 1 / 2 | |
| 3.1.172 | 1 / 2 | |
| 3.1.171 | 1 / 2 | |
| 3.1.170 | 1 / 2 | |
| 3.1.169 | 1 / 2 | |
| 3.1.168 | 1 / 2 | |
| 3.1.167 | 1 / 2 | |
| 3.1.166 | 1 / 2 | |
| 3.1.165 | 1 / 2 | |
| 3.1.164 | 1 / 2 | |
| 3.1.163 | 1 / 2 | |
| 3.1.162 | 1 / 2 | |
| 3.1.161 | 1 / 2 | |
| 3.1.160 | 1 / 2 | |
| 3.1.159 | 1 / 2 | |
| 3.1.158 | 1 / 2 | |
| 3.1.157 | 1 / 2 | |
| 3.1.156 | 1 / 2 | |
| 3.1.155 | 1 / 2 | |
| 3.1.154 | 1 / 2 | |
| 3.1.153 | 1 / 2 | |
| 3.1.152 | 1 / 2 | |
| 3.1.151 | 1 / 2 | |
| 3.1.150 | 1 / 2 | |
| 3.1.149 | 1 / 2 | |
| 3.1.148 | 1 / 2 | |
| 3.1.146 | 1 / 2 | |
| 3.1.145 | 1 / 2 | |
| 3.1.144 | 1 / 2 | |
| 3.1.143 | 1 / 2 | |
| 3.1.142 | 1 / 2 | |
| 3.1.141 | 1 / 2 | |
| 3.1.140 | 1 / 2 | |
| 3.1.139 | 1 / 2 | |
| 3.1.138 | 1 / 2 | |
| 3.1.137 | 1 / 2 |
v3.1.207
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.206
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.205
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.204
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.203
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.202
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.146
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.145
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.144
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.143
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.142
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.141
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.140
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.139
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.138
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.137
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.