@huaweicloud/huaweicloud-sdk-aos
Huaweicloud SDK for aos
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Huawei Cloud SDK org; no provenance is consistent across all their packages. | ai |
Versions (showing 100 of 114)
| 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.147 | 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 | |
| 3.1.124 | 1 / 2 | |
| 3.1.123 | 1 / 2 | |
| 3.1.122 | 1 / 2 | |
| 3.1.121 | 1 / 2 | |
| 3.1.120 | 1 / 2 | |
| 3.1.119 | 1 / 2 | |
| 3.1.118 | 1 / 2 | |
| 3.1.117 | 1 / 2 | |
| 3.1.116 | 1 / 2 | |
| 3.1.115 | 1 / 2 | |
| 3.1.114 | 1 / 2 | |
| 3.1.113 | 1 / 2 | |
| 3.1.112 | 1 / 2 | |
| 3.1.111 | 1 / 2 | |
| 3.1.110 | 1 / 2 | |
| 3.1.109 | 1 / 2 | |
| 3.1.108 | 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.191
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.190
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.189
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.188
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.185
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.184
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.183
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.182
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.180
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.178
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.176
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.174
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.172
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.171
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.169
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.168
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.165
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.164
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.163
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.162
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.161
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.160
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.158
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.157
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.156
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.155
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.153
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.151
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.149
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.148
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.147
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.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.
v3.1.136
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.135
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.134
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.133
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.132
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.131
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.130
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.129
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.128
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.127
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.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.
v3.1.124
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.123
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.122
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.121
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.120
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.119
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.118
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.117
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.116
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.115
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.114
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.113
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.112
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.111
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.110
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.109
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.108
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.