koa-compress
Compress middleware for koa
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate maintainer transition from jongleberry to elazutkin (listed contributor, 11yr npm account, 140 approved pkgs). | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Eugene Lazutkin is a listed contributor in package.json; legitimate koajs maintainer addition. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established 12yr-old package with 471k weekly downloads; low-value signals are false positives. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 5.2.1 | 5 / 9 | |
| 5.2.0 | 5 / 9 | |
| 5.1.1 | 4 / 9 | |
| 5.1.0 | 5 / 9 | |
| 5.0.1 | 5 / 9 | |
| 5.0.0 | 5 / 9 | |
| 4.0.1 | 5 / 9 | |
| 4.0.0 | 5 / 9 | |
| 3.1.0 | 4 / 9 | |
| 3.0.0 | 4 / 12 | |
| 2.0.0 | 4 / 5 | |
| 1.0.9 | 4 / 5 | |
| 1.0.8 | 4 / 5 | |
| 1.0.7 | 4 / 4 | |
| 1.0.6 | 4 / 4 | |
| 1.0.5 | 3 / 4 | |
| 1.0.4 | 2 / 4 | |
| 1.0.3 | 2 / 4 | |
| 1.0.2 | 2 / 4 | |
| 1.0.1 | 2 / 4 | |
| 1.0.0 | 2 / 4 | |
| 0.0.1 | 2 / 4 |
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-08-18. This could indicate a legitimate maintainer transition or an account compromise.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-07-06. This could indicate a legitimate maintainer transition or an account compromise.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.