koa-mount
Mounting 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
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 a long-standing, highly trusted npm publisher historically associated with the koajs org; this transition appears legitimate. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer 'aaron' added as part of what appears to be a legitimate koajs org maintainer transition; no code-level risk present. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of aheckmann consistent with legitimate maintainer rotation in the koajs org; no suspicious code changes accompany this. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 2 / 10 | |
| 4.1.0 | 2 / 10 | |
| 4.0.0 | 2 / 10 | |
| 3.0.0 | 2 / 5 | |
| 2.0.0 | 2 / 8 | |
| 1.3.1 | 2 / 5 | |
| 1.3.0 | 2 / 4 | |
| 1.2.5 | 2 / 4 | |
| 1.2.4 | 2 / 4 | |
| 1.2.3 | 2 / 4 | |
| 1.2.2 | 2 / 4 | |
| 1.2.1 | 2 / 4 | |
| 1.2.0 | 2 / 4 | |
| 1.1.0 | 2 / 4 | |
| 1.0.0 | 1 / 1 |
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
2 findingsThis version was published by a different npm account than previous versions on 2025-04-27. 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.
v4.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 2018-09-26. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.