@spinajs/configuration-http
API for configuration module. Allows to set / get configuration values from db
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@spinajs/di | AI (phantom-deps): Same-org dependency used transitively; stable false positive for this package. | ai |
Versions (showing 51 of 105)
| Version | Deps | Published |
|---|---|---|
| 2.0.474 | 1 / 0 | |
| 2.0.473 | 1 / 0 | |
| 2.0.472 | 1 / 0 | |
| 2.0.471 | 1 / 0 | |
| 2.0.470 | 1 / 0 | |
| 2.0.469 | 1 / 0 | |
| 2.0.468 | 1 / 0 | |
| 2.0.467 | 1 / 0 | |
| 2.0.466 | 1 / 0 | |
| 2.0.465 | 1 / 0 | |
| 2.0.464 | 1 / 0 | |
| 2.0.463 | 1 / 0 | |
| 2.0.462 | 1 / 0 | |
| 2.0.461 | 1 / 0 | |
| 2.0.460 | 1 / 0 | |
| 2.0.458 | 1 / 0 | |
| 2.0.457 | 1 / 0 | |
| 2.0.456 | 1 / 0 | |
| 2.0.455 | 1 / 0 | |
| 2.0.454 | 1 / 0 | |
| 2.0.453 | 1 / 0 | |
| 2.0.452 | 1 / 0 | |
| 2.0.451 | 1 / 0 | |
| 2.0.450 | 1 / 0 | |
| 2.0.449 | 1 / 0 | |
| 2.0.448 | 1 / 0 | |
| 2.0.447 | 1 / 0 | |
| 2.0.446 | 1 / 0 | |
| 2.0.445 | 1 / 0 | |
| 2.0.444 | 1 / 0 | |
| 2.0.443 | 1 / 0 | |
| 2.0.442 | 1 / 0 | |
| 2.0.441 | 1 / 0 | |
| 2.0.439 | 1 / 0 | |
| 2.0.438 | 1 / 0 | |
| 2.0.436 | 1 / 0 | |
| 2.0.435 | 1 / 0 | |
| 2.0.434 | 1 / 0 | |
| 2.0.433 | 1 / 0 | |
| 2.0.432 | 1 / 0 | |
| 2.0.431 | 1 / 0 | |
| 2.0.430 | 1 / 0 | |
| 2.0.429 | 1 / 0 | |
| 2.0.428 | 1 / 0 | |
| 2.0.427 | 1 / 0 | |
| 2.0.426 | 1 / 0 | |
| 2.0.425 | 1 / 0 | |
| 2.0.424 | 1 / 0 | |
| 2.0.423 | 1 / 0 | |
| 2.0.422 | 1 / 0 | |
| 2.0.421 | 1 / 0 |
v2.0.474
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.473
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.472
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.471
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.470
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.469
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.468
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.467
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.466
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.465
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.463
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.462
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.461
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.460
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.458
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.457
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.456
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.455
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.454
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.453
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.452
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.451
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.450
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.445
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.444
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.443
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.442
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.441
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.439
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.438
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.436
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.435
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.434
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.433
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.431
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.430
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.429
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.428
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.427
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.425
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.424
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.423
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.422
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.421
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.