koa-send
Transfer static files
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): Documented maintainer transition from jongleberry to coderhaoxin within the koajs org; coderhaoxin has a long, clean track record and the repo URL remains koajs/send. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance; absence of attestation is expected for this era of publishing and not a risk signal for this package. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 5.0.1 | 3 / 12 | |
| 5.0.0 | 4 / 12 | |
| 4.1.3 | 4 / 12 | |
| 4.1.2 | 4 / 12 | |
| 4.1.1 | 4 / 12 | |
| 4.1.0 | 4 / 12 | |
| 4.0.0 | 4 / 5 | |
| 3.3.0 | 4 / 5 | |
| 3.2.0 | 4 / 5 | |
| 3.1.1 | 4 / 5 | |
| 3.1.0 | 4 / 5 | |
| 3.0.1 | 3 / 5 | |
| 3.0.0 | 3 / 5 | |
| 2.0.3 | 3 / 5 | |
| 2.0.2 | 3 / 5 | |
| 2.0.1 | 3 / 5 | |
| 2.0.0 | 3 / 5 | |
| 1.3.2 | 2 / 5 | |
| 1.3.1 | 2 / 5 | |
| 1.3.0 | 2 / 5 | |
| 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.2 | 2 / 4 | |
| 1.1.1 | 2 / 4 | |
| 1.0.0 | 1 / 4 |
v5.0.1
2 findingsThis version was published by a different npm account than previous versions on 2020-07-08. 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.
v5.0.0
2 findingsThis version was published by a different npm account than previous versions on 2018-06-19. 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.1.3
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 2018-02-14. This could indicate a legitimate maintainer transition or an account compromise.
v4.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.