koa-convert
convert modern Koa legacy generator-based middleware to promise-based middleware
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): niftylettuce is a well-established Koa ecosystem maintainer (495 approved versions). Legitimate maintainer transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): niftylettuce added as maintainer; known prolific npm contributor with long history in Koa ecosystem. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by maintainer transition; koa-convert is a stable utility that rarely needs updates. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 2 / 7 | |
| 1.2.0 | 2 / 5 | |
| 1.1.0 | 2 / 5 | |
| 1.0.0 | 2 / 4 | |
| 0.0.2 | 1 / 1 | |
| 0.0.1 | 1 / 1 |
v2.0.0
2 findingsThis version was published by a different npm account than previous versions on 2020-09-10. 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.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
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.