EOL.WikiEOL.Wiki
← ← Back to all products

pnpm

Active
Tools & MonitoringLatest Version: 11.22.0Latest Release: Aug 15, 2026

pnpm is a fast, disk space efficient JavaScript package manager using a content-addressable file system.

Support summary

pnpm currently has supported cycles. Track the next EOL date and validate upgrades before your change window.

What do EOL and support statuses mean?

Next EOL

Apr 30, 2027

pnpm 10 · 252 days left

Supported cycles

2

0 lts

Versions

8

Latest Version

11.22.0

Active Support

2

EOL

6

Lifecycle Timeline

Today
11
11
10
10
9
9
8
8
7
7
6
6
5
5
4
4
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
11Apr 28, 2026YesNo11.22.0No
Active
10Jan 7, 2025YesApr 30, 202710.34.5No
Active
9Apr 16, 2024NoApr 30, 20269.15.9No
EOL
8Mar 27, 2023NoApr 30, 20258.15.9No
EOL
7Apr 30, 2022NoApr 16, 20247.33.7No
EOL
6Apr 5, 2021NoMar 20, 20236.35.1No
EOL
5May 27, 2020NoApr 29, 20225.18.11No
EOL
4Oct 7, 2019NoApr 24, 20214.14.4No
EOL

Data sources

Frequently Asked Questions

Which versions of pnpm have reached end of life?
The following pnpm versions have reached end of life and no longer receive security updates: 9, 8, 7, 6, 5, 4. It is recommended to upgrade to a supported version.
Is it safe to continue using pnpm 9?
pnpm 9 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of pnpm?
The latest version of pnpm is 11.22.0, released in the 11 release cycle.
How many versions of pnpm are currently supported?
pnpm currently has 2 actively supported version(s): 11, 10.
When does pnpm 11 reach end of life?
pnpm 11 does not have a specific end-of-life date announced yet.
What should I do when pnpm reaches end of life?
When a pnpm version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.