@aeriajs/cli
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @aeriajs/cli package; Levenshtein match to 'joi' is coincidental, not a typosquat. | ai |
Versions (showing 100 of 277)
| Version | Deps | Published |
|---|---|---|
| 0.0.292 | 3 / 6 | |
| 0.0.291 | 3 / 6 | |
| 0.0.290 | 3 / 6 | |
| 0.0.289 | 3 / 6 | |
| 0.0.288 | 3 / 6 | |
| 0.0.287 | 3 / 6 | |
| 0.0.286 | 3 / 6 | |
| 0.0.285 | 3 / 6 | |
| 0.0.284 | 3 / 6 | |
| 0.0.283 | 3 / 6 | |
| 0.0.282 | 3 / 6 | |
| 0.0.281 | 3 / 6 | |
| 0.0.280 | 3 / 6 | |
| 0.0.279 | 3 / 6 | |
| 0.0.278 | 3 / 6 | |
| 0.0.277 | 3 / 6 | |
| 0.0.276 | 3 / 6 | |
| 0.0.275 | 3 / 6 | |
| 0.0.274 | 3 / 6 | |
| 0.0.273 | 3 / 6 | |
| 0.0.272 | 3 / 6 | |
| 0.0.271 | 3 / 6 | |
| 0.0.270 | 3 / 6 | |
| 0.0.269 | 3 / 6 | |
| 0.0.268 | 3 / 6 | |
| 0.0.267 | 3 / 6 | |
| 0.0.266 | 3 / 6 | |
| 0.0.265 | 3 / 6 | |
| 0.0.264 | 3 / 6 | |
| 0.0.263 | 3 / 6 | |
| 0.0.262 | 3 / 6 | |
| 0.0.261 | 3 / 6 | |
| 0.0.260 | 3 / 6 | |
| 0.0.259 | 3 / 6 | |
| 0.0.258 | 3 / 6 | |
| 0.0.257 | 3 / 6 | |
| 0.0.256 | 3 / 6 | |
| 0.0.255 | 3 / 6 | |
| 0.0.254 | 3 / 6 | |
| 0.0.253 | 3 / 6 | |
| 0.0.252 | 3 / 6 | |
| 0.0.251 | 3 / 6 | |
| 0.0.250 | 3 / 6 | |
| 0.0.249 | 3 / 6 | |
| 0.0.248 | 3 / 6 | |
| 0.0.247 | 3 / 6 | |
| 0.0.246 | 3 / 6 | |
| 0.0.245 | 3 / 6 | |
| 0.0.244 | 3 / 6 | |
| 0.0.243 | 3 / 6 | |
| 0.0.242 | 3 / 6 | |
| 0.0.241 | 3 / 6 | |
| 0.0.240 | 3 / 6 | |
| 0.0.239 | 3 / 6 | |
| 0.0.238 | 3 / 6 | |
| 0.0.237 | 3 / 6 | |
| 0.0.236 | 3 / 6 | |
| 0.0.235 | 3 / 6 | |
| 0.0.234 | 3 / 6 | |
| 0.0.233 | 3 / 6 | |
| 0.0.232 | 3 / 6 | |
| 0.0.231 | 3 / 6 | |
| 0.0.230 | 3 / 6 | |
| 0.0.229 | 3 / 6 | |
| 0.0.228 | 3 / 6 | |
| 0.0.227 | 3 / 6 | |
| 0.0.226 | 3 / 6 | |
| 0.0.225 | 3 / 6 | |
| 0.0.224 | 3 / 6 | |
| 0.0.223 | 3 / 6 | |
| 0.0.222 | 3 / 6 | |
| 0.0.221 | 3 / 6 | |
| 0.0.220 | 3 / 6 | |
| 0.0.219 | 3 / 6 | |
| 0.0.218 | 3 / 6 | |
| 0.0.217 | 3 / 6 | |
| 0.0.216 | 3 / 6 | |
| 0.0.215 | 3 / 6 | |
| 0.0.214 | 3 / 6 | |
| 0.0.213 | 3 / 6 | |
| 0.0.212 | 3 / 6 | |
| 0.0.211 | 3 / 6 | |
| 0.0.210 | 3 / 6 | |
| 0.0.209 | 3 / 6 | |
| 0.0.208 | 3 / 6 | |
| 0.0.207 | 3 / 6 | |
| 0.0.206 | 3 / 6 | |
| 0.0.205 | 3 / 6 | |
| 0.0.204 | 3 / 6 | |
| 0.0.203 | 3 / 6 | |
| 0.0.202 | 3 / 6 | |
| 0.0.201 | 3 / 6 | |
| 0.0.200 | 3 / 6 | |
| 0.0.198 | 3 / 6 | |
| 0.0.197 | 3 / 6 | |
| 0.0.196 | 3 / 6 | |
| 0.0.195 | 3 / 6 | |
| 0.0.194 | 3 / 6 | |
| 0.0.193 | 3 / 6 | |
| 0.0.192 | 3 / 6 |
v0.0.214
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.213
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.212
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.211
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.210
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.209
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.208
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.207
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.206
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.205
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.204
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.203
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.202
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.201
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.200
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.198
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.197
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.196
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.195
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.194
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.193
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.192
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.