@inversifyjs/http-validation
InversifyJs http validation common package
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@inversifyjs/framework-core | AI (dependencies): Same inversify monorepo/publisher; stable internal dependency across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established inversify monorepo package; lack of provenance is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 5.4.4 | 3 / 11 | |
| 5.4.3 | 3 / 11 | |
| 5.4.1 | 3 / 12 | |
| 5.4.0 | 3 / 12 | |
| 5.2.0 | 3 / 12 | |
| 5.0.0 | 3 / 12 | |
| 4.9.0 | 3 / 13 | |
| 4.8.1 | 3 / 13 | |
| 4.5.0 | 3 / 13 | |
| 4.3.0 | 3 / 13 | |
| 4.2.0 | 3 / 13 |
v5.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.