@koa/router
Router 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 | missing-githead | AI (provenance): Established package with long history; missing gitHead reflects a publish environment change, not malicious activity. No other risk signals present. | ai | |
| provenance | no-provenance | AI (provenance): Lack of Sigstore provenance is a process gap, not a security indicator for this well-established, trusted package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 15.6.0 | 4 / 27 | |
| 15.5.0 | 4 / 27 | |
| 15.4.0 | 4 / 27 | |
| 15.3.2 | 4 / 27 | |
| 15.3.1 | 4 / 27 | |
| 15.3.0 | 4 / 25 | |
| 15.2.0 | 4 / 25 | |
| 15.1.2 | 4 / 25 | |
| 15.1.1 | 4 / 25 | |
| 15.1.0 | 4 / 25 | |
| 15.0.0 | 4 / 24 | |
| 13.1.0 | 3 / 16 | |
| 13.0.1 | 3 / 16 | |
| 13.0.0 | 3 / 16 |
v15.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: 3imed-jaberi.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: 3imed-jaberi.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: 3imed-jaberi.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: 3imed-jaberi.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: 3imed-jaberi.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: 3imed-jaberi.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.