@types/content-type
2
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
types
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Stub types packages are updated infrequently by design; dormancy is expected for this package type. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Adding content-type as a dep is the explicit purpose of this stub — redirecting to the package's own types. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Stub types packages intentionally have tiny payloads, no code, and minimal metadata; this is the expected structure. | ai | |
| phantom-deps | phantom-dep:content-type | AI (phantom-deps): Stub package declares content-type as a dep by design; it is not imported because it only re-exports types. | ai |
v2.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
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.