Is body-parser healthy, maintained, and safe?
Mostly yes — body-parser is maintained, with a couple of watch-items rather than red flags.
The verdict
OSPulse scores body-parser at 69/100 (low risk), computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. Mostly yes — body-parser is maintained, with a couple of watch-items rather than red flags.
Its most recent release shipped on 9 July 2026 — 20 days ago — so development is clearly active. Across 84 releases the cadence has been steady, which is a good sign of an ongoing maintenance rhythm. 4 maintainers are listed on npm, so the project isn't hostage to any single contributor.
OSV lists 3 known advisories for body-parser, including 1 high. Review whether your version is in the affected range and whether a fixed release is available before depending on it. Each advisory is listed with its OSV/GHSA identifier below.
A couple of watch-items aside, body-parser is a reasonable dependency to rely on; keep an eye on the flagged signals. This is a one-time snapshot of a single package — real projects depend on dozens or hundreds of packages, and any one of them can drift or be compromised between releases. Run your own package.json through the free health check, or have OSPulse monitor your whole dependency tree continuously.
Evidence trail — deterministic, auditable
Known vulnerabilities (3)
body-parser vulnerable to denial of service when url encoding is enabled
body-parser vulnerable to denial of service when invalid limit value silently disables size enforcement
body-parser is vulnerable to denial of service when url encoding is used
Key facts
- Latest version
- v2.3.0
- Last release
- 9 July 2026 (20 days ago)
- Total releases
- 84
- First release
- 6 January 2014
- Package age
- 12.6 years
- Maintainers
- 4
- Known advisories
- 3
- Confidence
- High
Frequently asked
Is body-parser still maintained?
Yes — body-parser released as recently as 9 July 2026 (20 days ago), so it is actively maintained.
Does body-parser have known security vulnerabilities?
Yes — OSV lists 3 advisories for body-parser. See the advisory list on this page for the OSV/GHSA identifiers.
Is body-parser safe to use?
Mostly yes — body-parser is maintained, with a couple of watch-items rather than red flags. OSPulse rates it 69/100 (low risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
body-parser is one package. What about the other hundreds in your tree?
Paste your own package.json into the free health check for an instant snapshot — or let OSPulse monitor your whole dependency tree continuously, before your CVE scanner wakes up.
Data from the npm registry & OSV.dev · snapshot generated 2026-07-28 · scores are deterministic and recomputed on each refresh.