body-parser
2.4.0 · 22 Oct 2026MIT201.6M / weekRepositoryHomepagenpmAtom feed
Where each line stands
Plan an upgrade- 2.x2.4.0Safe from 2.4.0Latest line
- 1.x1.20.9Safe from 1.20.9To 2.4.0
What to use instead
A better maintained package
From the e18e module-replacements list, maintained by the community.
The list compares the options for body-parser: read the comparison.
Before you switch
- 1
Check what else depends on it
Paste your package.json in the dependency check to see every deprecated or outdated package in one pass, not only this one.
- 2
Read the replacement's peers and releases
A native API or a few lines of code need no release notes, but check the Node version your project runs on.
- 3
Know when it ships
Follow the new package on inlinr: its releases and advisories land in your feed, and the time spent on the migration branch shows on its page.
Latest releases
All 85 releases- 2.x · latest line
2.4.0
22 Oct 2026- security
Security fix for CVE-2026-111181 (GHSA-27r3-jxmh-p828)
Avoid mutating read options when reading body
json: Avoid first-char regex for direct JSON bodies
Important: Security
- security
Security fix for CVE-2026-111181 (GHSA-27r3-jxmh-p828)
What's Changed
Avoid mutating read options when reading body
json: Avoid first-char regex for direct JSON bodies
Zstandard support
Inline content stream setup
2.3.0
15 Jun 2026- security
Security fix for CVE-2026-12590 (GHSA-v422-hmwv-36x6)
urlencoded: Move empty-body guard to avoid extra function closure
Improve ESM compatibility
Important: Security
- security
Security fix for CVE-2026-12590 (GHSA-v422-hmwv-36x6)
What's Changed
urlencoded: Move empty-body guard to avoid extra function closure
Improve ESM compatibility
Improve limit option validation
Eliminate conditional check in json strict mode hot path
Upgrade "content-type"
Update outdated reference to MDN docs
2.2.2
7 Jan 2026Maintenance only: docs, tests, build or refactoring. Nothing changes in how you use it.
Dependency tracking · free for 3 projects
Know when your own dependencies move
body-parser had 3 security advisories in the last 12 months. inlinr emails you the day one touches a project of yours, with the version that fixes it.
Advisories reach you
An email when a critical or high advisory affects a project, before the next install.
Upgrades checked first
Peer ranges, Node, ESM-only and types changes read before you bump.
Only what matters
Majors and breaking notes stay; patches and sibling bumps fold into one line.
Registry facts last checked 4 Nov 2026. Releases and advisories last read 4 Nov 2026.