@spinajs/http
framework HTTP module base on express.js
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:glob | AI (phantom-deps): glob is a declared runtime dependency in package.json; phantom-dep heuristic is a false positive here. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; lack of provenance is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 11 of 111)
| Version | Deps | Published |
|---|---|---|
| 2.0.373 | 24 / 11 | |
| 2.0.372 | 24 / 11 | |
| 2.0.371 | 24 / 11 | |
| 2.0.370 | 24 / 11 | |
| 2.0.369 | 24 / 11 | |
| 2.0.368 | 24 / 11 | |
| 2.0.367 | 24 / 11 | |
| 2.0.363 | 24 / 11 | |
| 2.0.362 | 24 / 11 | |
| 2.0.361 | 24 / 11 | |
| 2.0.360 | 24 / 11 |
v2.0.373
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.372
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.371
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.370
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.369
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.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.
v2.0.361
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.360
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.