@types/compression
TypeScript definitions for compression
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| email-domain | unclaimed-email:https://github.com/santialbo/ | AI (email-domain): The 'email' field is a GitHub profile URL, not an email address. The analyzer is misinterpreting a URL as an email domain — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): @types/express is a standard type dependency for compression middleware types in DefinitelyTyped; not a real phantom dependency. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.8.1 | 2 / 0 | |
| 1.8.0 | 2 / 0 | |
| 1.7.5 | 1 / 0 | |
| 1.7.4 | 1 / 0 | |
| 1.7.3 | 1 / 0 | |
| 1.7.2 | 1 / 0 | |
| 1.7.1 | 1 / 0 | |
| 1.7.0 | 1 / 0 | |
| 1.0.1 | 1 / 0 | |
| 1.0.0 | 1 / 0 | |
| 0.0.36 | 1 / 0 | |
| 0.0.35 | 1 / 0 | |
| 0.0.34 | 1 / 0 | |
| 0.0.33 | 1 / 0 | |
| 0.0.32 | 1 / 0 | |
| 0.0.31 | 1 / 0 | |
| 0.0.29 | 1 / 0 |
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
2 findingsMaintainer email 'https://github.com/santialbo/' uses domain 'https://github.com/santialbo/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.