@cleardu/aws
Nest - modern, fast, powerful node.js web framework (@aws)
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:qs | AI (typosquat): Scoped package @cleardu/aws; Levenshtein match to 'qs' is a false positive with no semantic similarity. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @cleardu/aws; Levenshtein match to 'ajv' is a false positive with no semantic similarity. | ai |
Versions (showing 100 of 515)
| Version | Deps | Published |
|---|---|---|
| 1.0.465 | 4 / 2 | |
| 1.0.462 | 4 / 2 | |
| 1.0.461 | 4 / 2 | |
| 1.0.460 | 4 / 2 | |
| 1.0.459 | 4 / 2 | |
| 1.0.458 | 4 / 2 | |
| 1.0.457 | 4 / 2 | |
| 1.0.456 | 4 / 2 | |
| 1.0.455 | 4 / 2 | |
| 1.0.454 | 4 / 2 | |
| 1.0.453 | 4 / 2 | |
| 1.0.452 | 4 / 2 | |
| 1.0.451 | 4 / 2 | |
| 1.0.450 | 4 / 2 | |
| 1.0.449 | 4 / 2 | |
| 1.0.448 | 4 / 2 | |
| 1.0.447 | 4 / 2 | |
| 1.0.446 | 4 / 2 | |
| 1.0.445 | 4 / 2 | |
| 1.0.444 | 4 / 2 | |
| 1.0.443 | 4 / 2 | |
| 1.0.442 | 4 / 2 | |
| 1.0.441 | 4 / 2 | |
| 1.0.440 | 4 / 2 | |
| 1.0.439 | 4 / 2 | |
| 1.0.438 | 4 / 2 | |
| 1.0.437 | 4 / 2 | |
| 1.0.436 | 4 / 2 | |
| 1.0.435 | 4 / 2 | |
| 1.0.434 | 4 / 2 | |
| 1.0.433 | 4 / 2 | |
| 1.0.432 | 4 / 2 | |
| 1.0.431 | 4 / 2 | |
| 1.0.430 | 4 / 2 | |
| 1.0.429 | 4 / 2 | |
| 1.0.428 | 4 / 2 | |
| 1.0.427 | 4 / 2 | |
| 1.0.426 | 4 / 2 | |
| 1.0.425 | 4 / 2 | |
| 1.0.424 | 4 / 2 | |
| 1.0.423 | 4 / 2 | |
| 1.0.422 | 4 / 2 | |
| 1.0.421 | 4 / 2 | |
| 1.0.420 | 4 / 2 | |
| 1.0.419 | 4 / 2 | |
| 1.0.418 | 4 / 2 | |
| 1.0.417 | 4 / 2 | |
| 1.0.416 | 4 / 2 | |
| 1.0.415 | 4 / 2 | |
| 1.0.414 | 4 / 2 | |
| 1.0.413 | 4 / 2 | |
| 1.0.412 | 4 / 2 | |
| 1.0.411 | 4 / 2 | |
| 1.0.410 | 4 / 2 | |
| 1.0.409 | 4 / 2 | |
| 1.0.408 | 4 / 2 | |
| 1.0.407 | 4 / 2 | |
| 1.0.406 | 4 / 2 | |
| 1.0.405 | 4 / 2 | |
| 1.0.404 | 4 / 2 | |
| 1.0.403 | 4 / 2 | |
| 1.0.402 | 4 / 2 | |
| 1.0.401 | 4 / 2 | |
| 1.0.400 | 4 / 2 | |
| 1.0.399 | 4 / 2 | |
| 1.0.398 | 4 / 2 | |
| 1.0.397 | 4 / 2 | |
| 1.0.396 | 4 / 2 | |
| 1.0.395 | 4 / 2 | |
| 1.0.394 | 4 / 2 | |
| 1.0.393 | 4 / 2 | |
| 1.0.392 | 4 / 2 | |
| 1.0.391 | 4 / 2 | |
| 1.0.389 | 4 / 2 | |
| 1.0.388 | 4 / 2 | |
| 1.0.387 | 4 / 2 | |
| 1.0.386 | 4 / 2 | |
| 1.0.385 | 4 / 2 | |
| 1.0.384 | 4 / 2 | |
| 1.0.382 | 4 / 2 | |
| 1.0.381 | 4 / 2 | |
| 1.0.380 | 4 / 2 | |
| 1.0.379 | 4 / 2 | |
| 1.0.378 | 4 / 2 | |
| 1.0.377 | 4 / 2 | |
| 1.0.376 | 4 / 2 | |
| 1.0.375 | 4 / 2 | |
| 1.0.374 | 4 / 2 | |
| 1.0.373 | 4 / 2 | |
| 1.0.372 | 4 / 2 | |
| 1.0.371 | 4 / 2 | |
| 1.0.369 | 4 / 2 | |
| 1.0.368 | 4 / 2 | |
| 1.0.367 | 4 / 2 | |
| 1.0.366 | 4 / 2 | |
| 1.0.365 | 4 / 2 | |
| 1.0.364 | 4 / 2 | |
| 1.0.363 | 4 / 2 | |
| 1.0.362 | 4 / 2 | |
| 1.0.361 | 4 / 2 |
v1.0.459
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.457
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.456
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.455
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.454
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.453
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.452
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.451
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.448
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.447
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.446
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.444
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.442
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.440
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.439
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.438
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.437
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.436
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.435
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.434
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.433
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.430
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.429
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.428
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.426
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.425
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.424
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.422
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.421
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.419
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.418
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.417
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.415
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.414
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.412
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.411
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.410
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.407
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.406
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.405
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.404
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.403
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.402
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.401
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.400
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.399
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.398
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.397
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.396
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.395
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.394
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.393
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.392
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.389
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.388
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.387
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.386
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.385
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.382
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.381
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.380
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.378
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.377
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.376
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.375
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.374
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.373
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.371
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.368
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.367
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.366
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.364
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.363
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.362
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.361
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.