Vulnerability Database · npm · Package report
@pnpm/resolver-base: vulnerability history, versions and safety
@pnpm/resolver-base is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the npm ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on @pnpm/resolver-base 1005.4.1 i
Updated on 23 Oct 2026
Good news: 1005.4.1, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Sustainable
- Popularity Key ecosystem project
- Community Active
What to do: Stay on 1005.4.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 1005.4.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 1005.4.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 239 packages i
- Stars 36,888 i
- OpenSSF scorecard 7/10 i
- Last release 9 months ago i
- Licence MIT i
Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Versions
Which versions are affected
Every version Vulert tracks for @pnpm/resolver-base, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.
- 1005.4.3 10 Jun 2026
- 1005.4.2 06 May 2026
- 1005.4.1 19 Jan 2026
- 1005.4.0 30 Dec 2025
- 1005.3.3 15 Dec 2025
- 1005.3.2 08 Dec 2025
- 1005.3.1 20 Nov 2025
- 1005.3.0 12 Nov 2025
- 1005.2.0 09 Nov 2025
- 1005.1.0 21 Oct 2025
- 1005.0.1 12 Sep 2025
- 1005.0.0 31 Jul 2025
- 1004.1.0 23 Jul 2025
- 1004.0.0 08 Jun 2025
- 1003.0.1 13 May 2025
- 1003.0.0 21 Apr 2025
- 1002.0.0 14 Apr 2025
- 1001.0.0 07 Apr 2025
- 1000.2.1 26 Mar 2025
- 1000.2.0 19 Mar 2025
- 1000.1.4 06 Mar 2025
- 1000.1.3 25 Feb 2025
- 1000.1.2 26 Jan 2025
- 1000.1.1 05 Jan 2025
- 1000.1.0 16 Dec 2024
- 1000.0.0 29 Nov 2024
- 900.0.0 28 Nov 2024
- 13.0.4 09 Sep 2024
- 13.0.3 26 Aug 2024
- 13.0.2 05 Aug 2024
- 13.0.1 21 Jul 2024
- 13.0.0 04 Jul 2024
- 12.0.2 17 Jun 2024
- 12.0.1 21 May 2024
- 12.0.0 09 Apr 2024
- 11.1.0 27 Jan 2024
- 11.0.2 26 Dec 2023
- 11.0.1 14 Dec 2023
- 11.0.0 01 Nov 2023
- 10.0.4 24 Oct 2023
- 10.0.3 08 Oct 2023
- 10.0.2 17 Jul 2023
- 10.0.1 28 May 2023
- 10.0.0 24 Mar 2023
- 9.2.0 08 Feb 2023
- 9.1.5 21 Dec 2022
- 9.1.4 09 Nov 2022
- 9.1.3 19 Oct 2022
- 9.1.2 03 Oct 2022
- 9.1.1 18 Sep 2022
- 9.1.0 10 Aug 2022
- 9.0.6 31 Jul 2022
- 8.1.7 05 Jul 2022
- 9.0.5 24 Jun 2022
- 9.0.4 22 Jun 2022
- 9.0.3 18 Jun 2022
- 9.0.2 10 Jun 2022
- 9.0.1 30 Apr 2022
- 9.0.0 19 Mar 2022
- 8.1.6 22 Feb 2022
- 8.1.5 12 Jan 2022
- 8.1.4 29 Dec 2021
- 8.1.3 15 Dec 2021
- 8.1.2 14 Dec 2021
- 8.1.1 10 Nov 2021
- 8.1.0 01 Nov 2021
- 8.0.4 30 Jul 2021
- 8.0.3 23 Jun 2021
- 8.0.2 01 Jun 2021
- 8.0.1 24 Apr 2021
- 8.0.0 05 Apr 2021
- 7.1.1 23 Jan 2021
- 7.1.0 17 Nov 2020
- 7.0.5 22 Oct 2020
- 7.0.4 19 Oct 2020
- 7.0.3 22 Jun 2020
- 7.0.2 15 Jun 2020
- 7.0.1 23 May 2020
- 7.0.1-alpha.0 11 May 2020
- 7.0.0 07 Jan 2020
- 6.0.0 14 Dec 2019
- 5.1.0 08 Dec 2019
- 5.0.0 09 Nov 2019
- 4.0.0 06 Oct 2019
- 3.1.2 24 Apr 2019
- 3.1.1 21 Apr 2019
- 3.1.0 13 Apr 2019
- 3.0.0 08 Mar 2019
- 2.1.0 10 Jan 2019
- 2.0.0 21 Oct 2018
- 1.2.0 18 Aug 2018
- 1.1.0 09 May 2018
- 1.0.0 09 Feb 2018
- 0.0.0 09 Feb 2018
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| 1005.4.3 | 10 Jun 2026 | none | MIT | — | Details → |
| 1005.4.2 | 06 May 2026 | none | MIT | — | Details → |
| 1005.4.1 | 19 Jan 2026 | none | MIT | — | Details → |
| 1005.4.0 | 30 Dec 2025 | none | MIT | — | Details → |
| 1005.3.3 | 15 Dec 2025 | none | MIT | — | Details → |
| 1005.3.2 | 08 Dec 2025 | none | MIT | — | Details → |
| 1005.3.1 | 20 Nov 2025 | none | MIT | — | Details → |
| 1005.3.0 | 12 Nov 2025 | none | MIT | — | Details → |
| 1005.2.0 | 09 Nov 2025 | none | MIT | — | Details → |
| 1005.1.0 | 21 Oct 2025 | none | MIT | — | Details → |
| 1005.0.1 | 12 Sep 2025 | none | MIT | — | Details → |
| 1005.0.0 | 31 Jul 2025 | none | MIT | — | Details → |
| 1004.1.0 | 23 Jul 2025 | none | MIT | — | Details → |
| 1004.0.0 | 08 Jun 2025 | none | MIT | — | Details → |
| 1003.0.1 | 13 May 2025 | none | MIT | — | Details → |
| 1003.0.0 | 21 Apr 2025 | none | MIT | — | Details → |
| 1002.0.0 | 14 Apr 2025 | none | MIT | — | Details → |
| 1001.0.0 | 07 Apr 2025 | none | MIT | — | Details → |
| 1000.2.1 | 26 Mar 2025 | none | MIT | — | Details → |
| 1000.2.0 | 19 Mar 2025 | none | MIT | — | Details → |
| 1000.1.4 | 06 Mar 2025 | none | MIT | — | Details → |
| 1000.1.3 | 25 Feb 2025 | none | MIT | — | Details → |
| 1000.1.2 | 26 Jan 2025 | none | MIT | — | Details → |
| 1000.1.1 | 05 Jan 2025 | none | MIT | — | Details → |
| 1000.1.0 | 16 Dec 2024 | none | MIT | — | Details → |
| 1000.0.0 | 29 Nov 2024 | none | MIT | — | Details → |
| 900.0.0 | 28 Nov 2024 | none | MIT | — | Details → |
| 13.0.4 | 09 Sep 2024 | none | MIT | — | Details → |
| 13.0.3 | 26 Aug 2024 | none | MIT | — | Details → |
| 13.0.2 | 05 Aug 2024 | none | MIT | — | Details → |
| 13.0.1 | 21 Jul 2024 | none | MIT | — | Details → |
| 13.0.0 | 04 Jul 2024 | none | MIT | — | Details → |
| 12.0.2 | 17 Jun 2024 | none | MIT | — | Details → |
| 12.0.1 | 21 May 2024 | none | MIT | — | Details → |
| 12.0.0 | 09 Apr 2024 | none | MIT | — | Details → |
| 11.1.0 | 27 Jan 2024 | none | MIT | — | Details → |
| 11.0.2 | 26 Dec 2023 | none | MIT | — | Details → |
| 11.0.1 | 14 Dec 2023 | none | MIT | — | Details → |
| 11.0.0 | 01 Nov 2023 | none | MIT | — | Details → |
| 10.0.4 | 24 Oct 2023 | none | MIT | — | Details → |
| 10.0.3 | 08 Oct 2023 | none | MIT | — | Details → |
| 10.0.2 | 17 Jul 2023 | none | MIT | — | Details → |
| 10.0.1 | 28 May 2023 | none | MIT | — | Details → |
| 10.0.0 | 24 Mar 2023 | none | MIT | — | Details → |
| 9.2.0 | 08 Feb 2023 | none | MIT | — | Details → |
| 9.1.5 | 21 Dec 2022 | none | MIT | — | Details → |
| 9.1.4 | 09 Nov 2022 | none | MIT | — | Details → |
| 9.1.3 | 19 Oct 2022 | none | MIT | — | Details → |
| 9.1.2 | 03 Oct 2022 | none | MIT | — | Details → |
| 9.1.1 | 18 Sep 2022 | none | MIT | — | Details → |
| 9.1.0 | 10 Aug 2022 | none | MIT | — | Details → |
| 9.0.6 | 31 Jul 2022 | none | MIT | — | Details → |
| 8.1.7 | 05 Jul 2022 | none | MIT | — | Details → |
| 9.0.5 | 24 Jun 2022 | none | MIT | — | Details → |
| 9.0.4 | 22 Jun 2022 | none | MIT | — | Details → |
| 9.0.3 | 18 Jun 2022 | none | MIT | — | Details → |
| 9.0.2 | 10 Jun 2022 | none | MIT | — | Details → |
| 9.0.1 | 30 Apr 2022 | none | MIT | — | Details → |
| 9.0.0 | 19 Mar 2022 | none | MIT | — | Details → |
| 8.1.6 | 22 Feb 2022 | none | MIT | — | Details → |
| 8.1.5 | 12 Jan 2022 | none | MIT | — | Details → |
| 8.1.4 | 29 Dec 2021 | none | MIT | — | Details → |
| 8.1.3 | 15 Dec 2021 | none | MIT | — | Details → |
| 8.1.2 | 14 Dec 2021 | none | MIT | — | Details → |
| 8.1.1 | 10 Nov 2021 | none | MIT | — | Details → |
| 8.1.0 | 01 Nov 2021 | none | MIT | — | Details → |
| 8.0.4 | 30 Jul 2021 | none | MIT | — | Details → |
| 8.0.3 | 23 Jun 2021 | none | MIT | — | Details → |
| 8.0.2 | 01 Jun 2021 | none | MIT | — | Details → |
| 8.0.1 | 24 Apr 2021 | none | MIT | — | Details → |
| 8.0.0 | 05 Apr 2021 | none | MIT | — | Details → |
| 7.1.1 | 23 Jan 2021 | none | MIT | — | Details → |
| 7.1.0 | 17 Nov 2020 | none | MIT | — | Details → |
| 7.0.5 | 22 Oct 2020 | none | MIT | — | Details → |
| 7.0.4 | 19 Oct 2020 | none | MIT | — | Details → |
| 7.0.3 | 22 Jun 2020 | none | MIT | — | Details → |
| 7.0.2 | 15 Jun 2020 | none | MIT | — | Details → |
| 7.0.1 | 23 May 2020 | none | MIT | — | Details → |
| 7.0.1-alpha.0 | 11 May 2020 | none | MIT | — | Details → |
| 7.0.0 | 07 Jan 2020 | none | MIT | — | Details → |
| 6.0.0 | 14 Dec 2019 | none | MIT | — | Details → |
| 5.1.0 | 08 Dec 2019 | none | MIT | — | Details → |
| 5.0.0 | 09 Nov 2019 | none | MIT | — | Details → |
| 4.0.0 | 06 Oct 2019 | none | MIT | — | Details → |
| 3.1.2 | 24 Apr 2019 | none | MIT | — | Details → |
| 3.1.1 | 21 Apr 2019 | none | MIT | — | Details → |
| 3.1.0 | 13 Apr 2019 | none | MIT | — | Details → |
| 3.0.0 | 08 Mar 2019 | none | MIT | — | Details → |
| 2.1.0 | 10 Jan 2019 | none | MIT | — | Details → |
| 2.0.0 | 21 Oct 2018 | none | MIT | — | Details → |
| 1.2.0 | 18 Aug 2018 | none | MIT | — | Details → |
| 1.1.0 | 09 May 2018 | none | MIT | — | Details → |
| 1.0.0 | 09 Feb 2018 | none | MIT | — | Details → |
| 0.0.0 | 09 Feb 2018 | none | MIT | — | Details → |
All 94 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.
02 Disclosure history
How often vulnerabilities are recorded
No dated vulnerabilities are recorded for this package yet.
03 Vulnerabilities
Recorded vulnerabilities for @pnpm/resolver-base
No vulnerabilities match this view.
Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback
Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315
Questions
About @pnpm/resolver-base
Is @pnpm/resolver-base safe to use?
Vulert has no vulnerabilities on record for @pnpm/resolver-base in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.
What is @pnpm/resolver-base's Vulert package health score?
Vulert scores @pnpm/resolver-base 88/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).
Is the latest version of @pnpm/resolver-base affected?
No. 1005.4.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.
Which version of @pnpm/resolver-base should I use?
1005.4.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.
How many vulnerabilities does @pnpm/resolver-base have?
0 vulnerabilities are recorded for @pnpm/resolver-base in the npm ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.
How often are new @pnpm/resolver-base vulnerabilities disclosed?
0 vulnerabilities were recorded for @pnpm/resolver-base in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.
Which versions of @pnpm/resolver-base are affected?
Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.
How do I monitor @pnpm/resolver-base for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @pnpm/resolver-base version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.