← Home

type-is

Infer the content-type of a request.

40
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

ulisesgasconblakeembreywesleytodddougwilsonjongleberry

Keywords

contenttypechecking

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): wesleytodd is a known jshttp/Express ecosystem maintainer; transition from jongleberry is a documented, legitimate org handoff, not a compromise. ai
maintainer-change maintainer-added AI (maintainer-change): wesleytodd and dougwilson are both recognized jshttp maintainers; this is a legitimate team transition within the same org. ai
publish-pattern new-deps-added AI (publish-pattern): mime-types, media-typer, and content-type are canonical jshttp packages maintained by the same team; their addition in v2.0.0 is a legitimate refactor. ai

Versions (showing 40 of 40)

Version Deps Published
2.1.0 3 / 9
2.0.1 3 / 9
2.0.0 3 / 9
1.6.18 2 / 9
1.6.17 2 / 9
1.6.16 2 / 9
1.6.15 2 / 7
1.6.14 2 / 6
1.6.13 2 / 6
1.6.12 2 / 2
1.6.11 2 / 2
1.6.10 2 / 2
1.6.9 2 / 2
1.6.8 2 / 2
1.6.7 2 / 2
1.6.6 2 / 2
1.6.5 2 / 2
1.6.4 2 / 2
1.6.3 2 / 2
1.6.2 2 / 2
1.6.1 2 / 2
1.6.0 2 / 2
1.5.7 2 / 2
1.5.6 2 / 2
1.5.5 2 / 2
1.5.4 2 / 2
1.5.3 2 / 2
1.5.2 2 / 2
1.5.1 2 / 2
1.5.0 2 / 3
1.4.0 2 / 3
1.3.2 2 / 3
1.3.1 2 / 3
1.3.0 2 / 3
1.2.2 1 / 2
1.2.1 1 / 2
1.2.0 1 / 2
1.1.0 1 / 2
1.0.1 1 / 2
1.0.0 1 / 2

v2.1.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: ulisesgascon → blakeembrey (on 2026-05-13) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-13. This could indicate a legitimate maintainer transition or an account compromise.