koa-conditional-get
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): Transition from dead_horse to niftylettuce is a legitimate koajs org maintainer handoff; repo remains at koajs/conditional-get and niftylettuce is a well-established npm publisher. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): niftylettuce is a known, reputable npm publisher with strong track record; addition is consistent with legitimate koajs org maintainer transition. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by a dev-tooling update on a stable, mature middleware is expected behavior; no malicious indicators present. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 0 / 13 | |
| 2.0.0 | 0 / 6 | |
| 1.0.4 | 0 / 6 | |
| 1.0.3 | 0 / 6 | |
| 1.0.2 | 0 / 5 | |
| 1.0.1 | 0 / 5 | |
| 1.0.0 | 0 / 5 |
v3.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.
v2.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 2016-03-20. This could indicate a legitimate maintainer transition or an account compromise.