← Home

@inversifyjs/http-core

7
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

notaphplover

Keywords

dependency injectiondependency inversiondiinversion of control containeriocjavascriptnodetypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@inversifyjs/logger AI (dependencies): Same-org monorepo sibling dependency; stable false positive for this package family. ai
dependencies unvetted-dep:@inversifyjs/framework-core AI (dependencies): Same-org monorepo sibling dependency; stable false positive for this package family. ai
provenance no-provenance AI (provenance): Inversify monorepo consistently publishes without provenance; stable false positive for this package family. ai

Versions (showing 7 of 7)

Version Deps Published
5.4.4 4 / 11
5.3.0 4 / 12
5.2.0 4 / 12
5.1.1 4 / 12
4.10.0 4 / 13
4.9.0 4 / 13
4.2.0 4 / 13

v5.3.0

1 finding
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.1.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.10.0

1 finding
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.