← Home

@types/http-proxy-middleware

Stub TypeScript definitions entry for http-proxy-middleware, which provides its own types definitions

12
Versions
MIT
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

types

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@types/node AI (phantom-deps): @types packages conventionally declare but don't directly import type dependencies; this is the standard pattern for TypeScript definitions. ai
phantom-deps phantom-dep:@types/connect AI (phantom-deps): @types packages conventionally declare but don't directly import type dependencies; this is the standard pattern for TypeScript definitions. ai
phantom-deps phantom-dep:@types/http-proxy AI (phantom-deps): @types packages conventionally declare but don't directly import type dependencies; this is the standard pattern for TypeScript definitions. ai
publish-pattern dormant-publish AI (publish-pattern): @types stubs go dormant until the upstream ships its own types; this publish pattern is expected for DefinitelyTyped stub packages. ai
phantom-deps phantom-dep:http-proxy-middleware AI (phantom-deps): Stub packages declare the upstream as a dep for transitive resolution without importing it; phantom-dep is a structural false positive here. ai
publish-pattern new-deps-added AI (publish-pattern): Adding http-proxy-middleware as a dependency is the intended behavior of a stub package redirecting to the upstream's bundled types. ai
bogus-package bogus-package AI (bogus-package): Stub @types packages legitimately have no code, minimal README, and tiny payloads — these signals are structural false positives for this package type. ai

Versions (showing 12 of 12)

Version Deps Published
1.0.0 1 / 0
0.19.3 3 / 0
0.19.2 3 / 0
0.19.1 3 / 0
0.19.0 3 / 0
0.17.6 3 / 0
0.17.5 4 / 0
0.17.4 3 / 0
0.17.3 3 / 0
0.17.2 3 / 0
0.17.1 3 / 0
0.17.0 3 / 0

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.19.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.19.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.19.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.19.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.0

1 finding
LOW No provenance attestation provenance

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