koa-json
pretty (non-compressed) json response 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): Legitimate maintainer transition within the Koa ecosystem from jongleberry to coderhaoxin in 2016; both are known Koa contributors. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): aheckmann and coderhaoxin are established npm maintainers added as part of the Koa ecosystem's normal governance. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance; published in 2016 when provenance attestations did not exist. | ai | |
| dependencies | unvetted-dep:koa-is-json | AI (dependencies): koa-is-json is a legitimate koajs ecosystem companion package; this dependency is stable and expected for koa-json across all versions. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Rapid publish is a false positive for this mature, trusted package with a strong publisher track record and no material code changes. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.0.2 | 2 / 4 | |
| 2.0.1 | 2 / 4 | |
| 2.0.0 | 2 / 4 | |
| 1.1.3 | 2 / 4 | |
| 1.1.2 | 2 / 4 | |
| 1.1.1 | 2 / 4 | |
| 1.1.0 | 3 / 4 | |
| 1.0.1 | 1 / 4 | |
| 1.0.0 | 1 / 4 |
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findingsThis version was published by a different npm account than previous versions on 2016-03-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.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
2 findings[Accepted risk] Package 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 2014-07-24. This could indicate a legitimate maintainer transition or an account compromise.
v1.1.0
2 findings[Accepted risk] Package 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 2014-05-28. This could indicate a legitimate maintainer transition or an account compromise.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.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.