pnpm 10 · Version Status
pnpm 10 End of Life Date
pnpm 10 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚡
pnpm 10 reaches end of life on April 30, 2027. Plan your migration now — 174 days remaining.
📅 Get reminded before pnpm 10 reaches EOL on April 30, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Apr 30, 2027
174 days remaining
Latest Release
10.34.9
Standard release
Release Date
Jan 7, 2025
pnpm 10 series
Where these dates come from
End of lifeApr 30, 2027endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseJan 7, 2025endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
pnpm 10 was released on January 7, 2025 and support is scheduled to end on April 30, 2027 — a planned supported lifespan of 2 years and 4 months, longer than the 2 years median for pnpm releases. Its most recent patch is 10.34.9, published October 25, 2026.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended pnpm 10 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 4 |
4.14.4 |
Apr 24, 2021 |
EOL |
| 5 |
5.18.11 |
Apr 29, 2022 |
EOL |
| 6 |
6.35.1 |
Mar 20, 2023 |
EOL |
| 7 |
7.33.7 |
Apr 16, 2024 |
EOL |
| 8 |
8.15.9 |
Apr 30, 2025 |
EOL |
| 9 |
9.15.9 |
Apr 30, 2026 |
EOL |
| → 10 |
10.34.9 |
Apr 30, 2027 |
Warning |
| 11 |
11.28.11 |
Apr 30, 2027 |
Warning |
What does pnpm 10 end of life mean?
When pnpm 10 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running pnpm 10 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to pnpm 12 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does pnpm 10 reach end of life?
pnpm 10 reaches end of life on April 30, 2027. That is 174 days remaining.
Is pnpm 10 still supported?
pnpm 10 is still supported but approaching end of life on April 30, 2027. Begin planning your migration now.
What should I upgrade to from pnpm 10?
The recommended upgrade from pnpm 10 is
pnpm 12 — the latest actively supported version. Check the
pnpm full timeline for all supported versions.
What are the security risks of running pnpm 10 past EOL?
When pnpm 10 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL pnpm should migrate immediately or implement compensating controls.