@huaweicloud/huaweicloud-sdk-mastudio
Huaweicloud SDK for mastudio
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): Standard sibling dependency within the Huawei Cloud SDK ecosystem; expected and stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established Huawei Cloud SDK org; provenance absence is common and not a risk signal here. | ai |
Versions (showing 51 of 51)
| 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.187 | 1 / 2 | |
| 3.1.186 | 1 / 2 | |
| 3.1.185 | 1 / 2 | |
| 3.1.184 | 1 / 2 | |
| 3.1.182 | 1 / 2 | |
| 3.1.181 | 1 / 2 | |
| 3.1.179 | 1 / 2 | |
| 3.1.178 | 1 / 2 | |
| 3.1.177 | 1 / 2 | |
| 3.1.176 | 1 / 2 | |
| 3.1.174 | 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 | |
| 3.1.136 | 1 / 2 | |
| 3.1.135 | 1 / 2 | |
| 3.1.134 | 1 / 2 | |
| 3.1.133 | 1 / 2 | |
| 3.1.132 | 1 / 2 | |
| 3.1.131 | 1 / 2 | |
| 3.1.130 | 1 / 2 | |
| 3.1.129 | 1 / 2 | |
| 3.1.128 | 1 / 2 | |
| 3.1.127 | 1 / 2 | |
| 3.1.126 | 1 / 2 | |
| 3.1.125 | 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. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.145
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.144
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.143
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.142
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.141
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.140
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.139
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.138
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.137
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.136
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.135
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.134
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.133
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.132
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.131
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.130
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.129
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.128
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.127
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.126
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.125
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.