← Home

fast-content-type-parse

Parse HTTP Content-Type header according to RFC 7231

1
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

zektheommgurgundayivan-tymoshenkosimonebclimba03003jsumnersfdawgsmetcoder95matteo.collinauzlopak

Keywords

content-typerfc7231

Versions (showing 1 of 1)

Version Deps Published
3.0.0 0 / 8