@spinajs/rbac-http
HTTP rbac helpers eg, session retrieval, decorators for controllers, args retrieval etc. Use it for modules where you only need user information from session
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has 206 approved packages in the spinajs org; high-frequency release pattern makes dormancy flag a false positive. | ai | |
| dependencies | unvetted-dep:accesscontrol | AI (dependencies): accesscontrol is a well-known RBAC library; stable dependency for this RBAC-focused package. | ai | |
| provenance | no-provenance | AI (provenance): Established spinajs monorepo; no provenance is consistent across all its packages. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Declared in package.json dependencies; likely used indirectly or in config — stable false positive. | ai | |
| phantom-deps | phantom-dep:@spinajs/log | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic fires as false positive for spinajs packages. | ai | |
| phantom-deps | phantom-dep:luxon | AI (phantom-deps): Declared in package.json dependencies; likely used indirectly or in config — stable false positive. | ai | |
| phantom-deps | phantom-dep:@spinajs/orm | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic fires as false positive for spinajs packages. | ai | |
| phantom-deps | phantom-dep:@spinajs/reflection | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic fires as false positive for spinajs packages. | ai |
Versions (showing 100 of 102)
| Version | Deps | Published |
|---|---|---|
| 2.0.474 | 11 / 2 | |
| 2.0.473 | 11 / 2 | |
| 2.0.472 | 11 / 2 | |
| 2.0.471 | 11 / 2 | |
| 2.0.470 | 11 / 2 | |
| 2.0.468 | 11 / 2 | |
| 2.0.467 | 11 / 2 | |
| 2.0.466 | 11 / 2 | |
| 2.0.465 | 11 / 2 | |
| 2.0.464 | 11 / 2 | |
| 2.0.463 | 11 / 2 | |
| 2.0.462 | 11 / 2 | |
| 2.0.461 | 11 / 2 | |
| 2.0.460 | 11 / 2 | |
| 2.0.458 | 11 / 2 | |
| 2.0.457 | 11 / 2 | |
| 2.0.456 | 11 / 2 | |
| 2.0.455 | 11 / 2 | |
| 2.0.454 | 11 / 2 | |
| 2.0.453 | 11 / 2 | |
| 2.0.452 | 11 / 2 | |
| 2.0.451 | 11 / 2 | |
| 2.0.450 | 11 / 2 | |
| 2.0.449 | 11 / 2 | |
| 2.0.448 | 11 / 2 | |
| 2.0.447 | 11 / 2 | |
| 2.0.446 | 11 / 2 | |
| 2.0.445 | 11 / 2 | |
| 2.0.444 | 11 / 2 | |
| 2.0.443 | 11 / 2 | |
| 2.0.441 | 11 / 2 | |
| 2.0.439 | 11 / 2 | |
| 2.0.438 | 11 / 2 | |
| 2.0.436 | 11 / 2 | |
| 2.0.435 | 11 / 2 | |
| 2.0.434 | 11 / 2 | |
| 2.0.433 | 11 / 2 | |
| 2.0.432 | 11 / 2 | |
| 2.0.431 | 11 / 2 | |
| 2.0.430 | 11 / 2 | |
| 2.0.429 | 11 / 2 | |
| 2.0.428 | 11 / 2 | |
| 2.0.427 | 11 / 2 | |
| 2.0.426 | 11 / 2 | |
| 2.0.425 | 11 / 2 | |
| 2.0.423 | 11 / 2 | |
| 2.0.422 | 11 / 2 | |
| 2.0.421 | 11 / 2 | |
| 2.0.420 | 11 / 2 | |
| 2.0.419 | 11 / 2 | |
| 2.0.418 | 11 / 2 | |
| 2.0.417 | 11 / 2 | |
| 2.0.416 | 11 / 2 | |
| 2.0.415 | 11 / 2 | |
| 2.0.414 | 11 / 2 | |
| 2.0.413 | 11 / 2 | |
| 2.0.412 | 11 / 2 | |
| 2.0.411 | 11 / 2 | |
| 2.0.409 | 11 / 2 | |
| 2.0.408 | 11 / 2 | |
| 2.0.407 | 11 / 2 | |
| 2.0.406 | 11 / 2 | |
| 2.0.405 | 11 / 2 | |
| 2.0.404 | 11 / 2 | |
| 2.0.403 | 11 / 2 | |
| 2.0.402 | 11 / 2 | |
| 2.0.401 | 11 / 2 | |
| 2.0.400 | 11 / 2 | |
| 2.0.399 | 11 / 2 | |
| 2.0.398 | 11 / 2 | |
| 2.0.397 | 11 / 2 | |
| 2.0.396 | 11 / 2 | |
| 2.0.395 | 11 / 2 | |
| 2.0.394 | 11 / 2 | |
| 2.0.393 | 11 / 2 | |
| 2.0.392 | 11 / 2 | |
| 2.0.391 | 11 / 2 | |
| 2.0.390 | 11 / 2 | |
| 2.0.389 | 11 / 2 | |
| 2.0.387 | 11 / 2 | |
| 2.0.386 | 11 / 2 | |
| 2.0.385 | 11 / 2 | |
| 2.0.384 | 11 / 2 | |
| 2.0.383 | 11 / 2 | |
| 2.0.382 | 11 / 2 | |
| 2.0.381 | 11 / 2 | |
| 2.0.379 | 11 / 2 | |
| 2.0.378 | 11 / 2 | |
| 2.0.377 | 11 / 2 | |
| 2.0.375 | 11 / 2 | |
| 2.0.374 | 11 / 2 | |
| 2.0.373 | 11 / 2 | |
| 2.0.372 | 11 / 2 | |
| 2.0.371 | 11 / 2 | |
| 2.0.370 | 11 / 2 | |
| 2.0.369 | 11 / 2 | |
| 2.0.368 | 11 / 2 | |
| 2.0.367 | 11 / 2 | |
| 2.0.363 | 11 / 2 | |
| 2.0.362 | 11 / 2 |
v2.0.474
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.473
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.472
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.471
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.470
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.468
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.467
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.466
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.465
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.463
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.462
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.461
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.460
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.458
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.457
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.456
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.455
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.454
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.453
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.452
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.451
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.450
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.449
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.448
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.447
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.446
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.445
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.444
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.443
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.441
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.439
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.438
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.436
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.435
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.434
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.433
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.432
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.431
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.430
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.429
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.428
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.427
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.426
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.425
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.423
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.422
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.421
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.420
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.419
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.418
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.417
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.416
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.415
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.414
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.413
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.412
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.411
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.409
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.408
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.407
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.406
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.405
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.404
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.403
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.402
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.401
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.400
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.399
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.398
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.397
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.396
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.395
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.394
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.393
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.392
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.391
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.390
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.389
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.387
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.386
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.385
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.384
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.383
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.382
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.381
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.379
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.378
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.377
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.375
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.374
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.373
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.372
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.371
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.370
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.369
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.368
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.367
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.363
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.362
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.