co-body
request body parsing for co
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): fengmk2 is a highly trusted npm publisher (641 approved/0 rejected) and a known core contributor to the cojs/Koa ecosystem alongside dead_horse. This is a legitimate maintainer transition. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @hapi/bourne is a well-known, trusted Hapi.js package for safe JSON parsing (prototype pollution protection). Its addition is a security improvement, not a supply-chain risk. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 6.2.0 | 5 / 7 | |
| 6.1.0 | 4 / 8 | |
| 6.0.0 | 4 / 8 | |
| 5.2.0 | 4 / 6 | |
| 5.1.1 | 4 / 6 | |
| 5.1.0 | 4 / 6 | |
| 5.0.3 | 4 / 6 | |
| 5.0.2 | 4 / 6 | |
| 5.0.1 | 4 / 6 | |
| 5.0.0 | 4 / 6 | |
| 4.2.0 | 4 / 6 | |
| 4.1.0 | 3 / 6 | |
| 4.0.0 | 3 / 5 | |
| 3.1.0 | 3 / 5 | |
| 3.0.0 | 2 / 5 | |
| 2.0.0 | 2 / 5 | |
| 1.2.0 | 2 / 5 | |
| 1.1.0 | 2 / 5 | |
| 1.0.0 | 2 / 4 | |
| 0.0.2 | 2 / 4 | |
| 0.0.1 | 2 / 4 |
v6.2.0
2 findingsThis version was published by a different npm account than previous versions on 2024-06-05. 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.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.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 2017-03-01. This could indicate a legitimate maintainer transition or an account compromise.