@vxrn/utils
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo utility package; missing metadata is expected for @vxrn scoped packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across @vxrn monorepo packages; not indicative of malice. | ai |
Versions (showing 100 of 428)
| Version | Deps | Published |
|---|---|---|
| 1.1.496 | 2 / 1 | |
| 1.1.495 | 2 / 1 | |
| 1.1.494 | 2 / 1 | |
| 1.1.493 | 2 / 1 | |
| 1.1.492 | 2 / 1 | |
| 1.1.491 | 2 / 1 | |
| 1.1.490 | 2 / 1 | |
| 1.1.489 | 2 / 1 | |
| 1.1.488 | 2 / 1 | |
| 1.1.487 | 2 / 1 | |
| 1.1.486 | 2 / 1 | |
| 1.1.485 | 2 / 1 | |
| 1.1.484 | 2 / 1 | |
| 1.1.483 | 2 / 1 | |
| 1.1.481 | 2 / 1 | |
| 1.1.480 | 2 / 1 | |
| 1.1.479 | 2 / 1 | |
| 1.1.478 | 2 / 1 | |
| 1.1.477 | 2 / 1 | |
| 1.1.476 | 2 / 1 | |
| 1.1.475 | 2 / 1 | |
| 1.1.474 | 2 / 1 | |
| 1.1.473 | 2 / 1 | |
| 1.1.472 | 2 / 1 | |
| 1.1.471 | 2 / 1 | |
| 1.1.470 | 2 / 1 | |
| 1.1.469 | 2 / 1 | |
| 1.1.468 | 2 / 1 | |
| 1.1.467 | 2 / 1 | |
| 1.1.466 | 2 / 1 | |
| 1.1.465 | 2 / 1 | |
| 1.1.464 | 2 / 1 | |
| 1.1.463 | 2 / 1 | |
| 1.1.462 | 2 / 1 | |
| 1.1.461 | 2 / 1 | |
| 1.1.460 | 2 / 1 | |
| 1.1.459 | 2 / 1 | |
| 1.1.458 | 2 / 1 | |
| 1.1.457 | 2 / 1 | |
| 1.1.456 | 2 / 1 | |
| 1.1.455 | 2 / 1 | |
| 1.1.454 | 2 / 1 | |
| 1.1.453 | 2 / 1 | |
| 1.1.452 | 2 / 1 | |
| 1.1.451 | 2 / 1 | |
| 1.1.450 | 2 / 1 | |
| 1.1.449 | 2 / 1 | |
| 1.1.448 | 2 / 1 | |
| 1.1.447 | 2 / 1 | |
| 1.1.446 | 2 / 1 | |
| 1.1.445 | 2 / 1 | |
| 1.1.444 | 2 / 1 | |
| 1.1.443 | 2 / 1 | |
| 1.1.442 | 2 / 1 | |
| 1.1.441 | 2 / 1 | |
| 1.1.440 | 2 / 1 | |
| 1.1.439 | 2 / 1 | |
| 1.1.438 | 2 / 1 | |
| 1.1.437 | 2 / 1 | |
| 1.1.436 | 2 / 1 | |
| 1.1.435 | 2 / 1 | |
| 1.1.434 | 2 / 1 | |
| 1.1.433 | 2 / 1 | |
| 1.1.432 | 2 / 1 | |
| 1.1.431 | 2 / 1 | |
| 1.1.430 | 2 / 1 | |
| 1.1.429 | 2 / 1 | |
| 1.1.428 | 2 / 1 | |
| 1.1.427 | 2 / 1 | |
| 1.1.426 | 2 / 1 | |
| 1.1.425 | 2 / 1 | |
| 1.1.424 | 2 / 1 | |
| 1.1.423 | 2 / 1 | |
| 1.1.422 | 2 / 1 | |
| 1.1.421 | 2 / 1 | |
| 1.1.420 | 2 / 1 | |
| 1.1.419 | 2 / 1 | |
| 1.1.418 | 2 / 1 | |
| 1.1.417 | 2 / 1 | |
| 1.1.416 | 2 / 1 | |
| 1.1.415 | 2 / 1 | |
| 1.1.414 | 2 / 1 | |
| 1.1.413 | 2 / 1 | |
| 1.1.412 | 2 / 1 | |
| 1.1.411 | 2 / 1 | |
| 1.1.410 | 2 / 1 | |
| 1.1.409 | 2 / 1 | |
| 1.1.408 | 2 / 1 | |
| 1.1.407 | 2 / 1 | |
| 1.1.406 | 2 / 1 | |
| 1.1.405 | 2 / 1 | |
| 1.1.404 | 2 / 1 | |
| 1.1.403 | 2 / 1 | |
| 1.1.402 | 2 / 1 | |
| 1.1.401 | 2 / 1 | |
| 1.1.400 | 2 / 1 | |
| 1.1.399 | 2 / 1 | |
| 1.1.398 | 2 / 1 | |
| 1.1.397 | 2 / 1 | |
| 1.1.396 | 0 / 1 |
v1.1.480
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.479
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.478
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.477
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.476
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.475
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.474
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.473
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.472
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.471
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.470
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.469
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.468
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.467
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.466
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.465
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.464
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.463
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.462
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.461
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.460
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.459
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.458
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.457
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.456
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.455
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.454
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.453
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.452
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.451
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.450
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.449
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.448
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.447
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.446
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.445
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.444
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.443
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.442
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.441
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.440
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.439
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.438
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.437
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.436
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.435
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.434
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.433
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.432
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.431
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.430
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.429
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.428
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.427
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.426
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.425
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.424
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.423
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.422
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.421
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.420
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.419
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.418
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.417
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.416
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.415
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.414
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.413
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.412
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.411
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.410
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.409
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.408
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.407
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.406
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.405
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.404
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.403
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.402
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.401
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.400
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.399
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.398
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.397
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.396
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.