koa-route
Koa route 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): jongleberry is the original Koa ecosystem creator and koajs org owner; this publisher change is a legitimate return to original maintainership, not a takeover. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 4.0.1 | 3 / 4 | |
| 4.0.0 | 3 / 4 | |
| 3.2.0 | 3 / 5 | |
| 3.1.0 | 3 / 5 | |
| 3.0.0 | 3 / 5 | |
| 2.4.2 | 3 / 5 | |
| 2.4.1 | 3 / 5 | |
| 2.4.0 | 3 / 5 | |
| 2.3.0 | 3 / 5 | |
| 2.2.0 | 3 / 5 | |
| 2.1.0 | 3 / 4 | |
| 2.0.0 | 3 / 4 | |
| 1.1.4 | 3 / 4 | |
| 1.1.2 | 3 / 4 | |
| 1.1.1 | 3 / 4 | |
| 1.1.0 | 3 / 4 | |
| 1.0.2 | 3 / 1 | |
| 1.0.1 | 3 / 1 | |
| 1.0.0 | 3 / 1 |
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findingsThis version was published by a different npm account than previous versions on 2024-02-25. 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.
v3.2.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 2016-08-24. This could indicate a legitimate maintainer transition or an account compromise.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.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 2015-11-17. This could indicate a legitimate maintainer transition or an account compromise.