Vulnerability Database · npm · Package report

@npmcli/arborist: vulnerability history, versions and safety

@npmcli/arborist is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 0 release, first recorded in Aug 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on @npmcli/arborist 10.0.4 i

Updated on 23 Oct 2026

Good news: 10.0.4, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 85/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 10.0.4 or newer. This can change: a vulnerability disclosed tomorrow can affect 10.0.4 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 10.0.4 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 31 Aug 2021 i
  • Highest CVSS 8.2 i
  • With no published fix 0 i
  • Depended on by 139 packages i
  • Stars 10,196 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence ISC 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 @npmcli/arborist, 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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
10.0.4 15 Oct 2026 none ISC — Details →
9.9.3 15 Oct 2026 none ISC — Details →
9.9.2 22 Sep 2026 none ISC — Details →
10.0.3 22 Sep 2026 none ISC — Details →
10.0.2 29 Jul 2026 none ISC — Details →
9.9.1 29 Jul 2026 none ISC — Details →
10.0.1 10 Jul 2026 none ISC — Details →
10.0.0 08 Jul 2026 none ISC — Details →
9.9.0 29 Jun 2026 none ISC — Details →
10.0.0-pre.2 29 Jun 2026 none ISC — Details →
10.0.0-pre.1 19 Jun 2026 none ISC — Details →
9.8.0 11 Jun 2026 none ISC — Details →
9.7.0 27 May 2026 none ISC — Details →
10.0.0-pre.0.0 20 May 2026 none ISC — Details →
9.6.0 20 May 2026 none ISC — Details →
9.5.0 06 May 2026 none ISC — Details →
9.4.3 22 Apr 2026 none ISC — Details →
8.0.5 27 Mar 2026 none ISC — Details →
8.0.4 18 Mar 2026 none ISC — Details →
9.4.2 18 Mar 2026 none ISC — Details →
9.4.1 11 Mar 2026 none ISC — Details →
8.0.3 11 Mar 2026 none ISC — Details →
8.0.2 04 Mar 2026 none ISC — Details →
9.4.0 25 Feb 2026 none ISC — Details →
9.3.1 19 Feb 2026 none ISC — Details →
9.3.0 11 Feb 2026 none ISC — Details →
9.2.0 04 Feb 2026 none ISC — Details →
9.1.10 21 Jan 2026 none ISC — Details →
9.1.9 09 Dec 2025 none ISC — Details →
9.1.8 25 Nov 2025 none ISC — Details →
9.1.7 19 Nov 2025 none ISC — Details →
9.1.6 08 Oct 2025 none ISC — Details →
9.1.5 24 Sep 2025 none ISC — Details →
9.1.4 03 Sep 2025 none ISC — Details →
9.1.3 24 Jul 2025 none ISC — Details →
8.0.1 25 Jun 2025 none ISC — Details →
9.1.2 12 Jun 2025 none ISC — Details →
9.1.1 21 May 2025 none ISC — Details →
9.1.0 15 May 2025 none ISC — Details →
9.0.2 08 Apr 2025 none ISC — Details →
9.0.1 05 Mar 2025 none ISC — Details →
9.0.0 16 Dec 2024 none ISC — Details →
9.0.0-pre.1 06 Dec 2024 none ISC — Details →
9.0.0-pre.0 26 Nov 2024 none ISC — Details →
8.0.0 03 Oct 2024 none ISC — Details →
7.5.4 10 Jul 2024 none ISC — Details →
7.5.3 29 May 2024 none ISC — Details →
7.5.2 15 May 2024 none ISC — Details →
7.5.1 30 Apr 2024 none ISC — Details →
7.5.0 25 Apr 2024 none ISC — Details →
7.4.2 10 Apr 2024 none ISC — Details →
7.4.1 03 Apr 2024 none ISC — Details →
7.4.0 28 Feb 2024 none ISC — Details →
6.5.1 28 Feb 2024 none ISC — Details →
7.3.1 24 Jan 2024 none ISC — Details →
7.3.0 10 Jan 2024 none ISC — Details →
7.2.2 06 Dec 2023 none ISC — Details →
7.2.1 31 Oct 2023 none ISC — Details →
6.5.0 06 Oct 2023 none ISC — Details →
7.2.0 03 Oct 2023 none ISC — Details →
6.4.0 18 Sep 2023 none ISC — Details →
7.1.0 08 Sep 2023 none ISC — Details →
7.0.0 31 Aug 2023 none ISC — Details →
7.0.0-pre.0 31 Aug 2023 none ISC — Details →
6.3.0 05 Jul 2023 none ISC — Details →
6.2.10 21 Jun 2023 none ISC — Details →
6.2.9 03 May 2023 none ISC — Details →
6.2.8 19 Apr 2023 none ISC — Details →
6.2.7 05 Apr 2023 none ISC — Details →
6.2.6 30 Mar 2023 none ISC — Details →
6.2.5 08 Mar 2023 none ISC — Details →
6.2.4 02 Mar 2023 none ISC — Details →
6.2.3 22 Feb 2023 none ISC — Details →
6.2.2 07 Feb 2023 none ISC — Details →
6.2.1 02 Feb 2023 none ISC — Details →
6.2.0 25 Jan 2023 none ISC — Details →
6.1.6 12 Jan 2023 none ISC — Details →
6.1.5 07 Dec 2022 none ISC — Details →
6.1.4 30 Nov 2022 none ISC — Details →
6.1.3 16 Nov 2022 none ISC — Details →
6.1.2 09 Nov 2022 none ISC — Details →
5.6.3 03 Nov 2022 none ISC — Details →
6.1.1 02 Nov 2022 none ISC — Details →
6.1.0 26 Oct 2022 none ISC — Details →
6.0.0 19 Oct 2022 none ISC — Details →
6.0.0-pre.5 19 Oct 2022 none ISC — Details →
6.0.0-pre.4 05 Oct 2022 none ISC — Details →
6.0.0-pre.3 30 Sep 2022 none ISC — Details →
6.0.0-pre.2 23 Sep 2022 none ISC — Details →
6.0.0-pre.1 14 Sep 2022 none ISC — Details →
5.6.2 13 Sep 2022 none ISC — Details →
6.0.0-pre.0 12 Sep 2022 none ISC — Details →
5.6.1 31 Aug 2022 none ISC — Details →
5.6.0 17 Aug 2022 none ISC — Details →
5.5.0 10 Aug 2022 none ISC — Details →
5.4.0 03 Aug 2022 none ISC — Details →
5.3.1 27 Jul 2022 none ISC — Details →
5.3.0 12 Jul 2022 none ISC — Details →
5.2.3 23 Jun 2022 none ISC — Details →
5.2.2 22 Jun 2022 none ISC — Details →
5.2.1 01 Jun 2022 none — — Details →
5.2.0 11 May 2022 none — — Details →
5.1.1 26 Apr 2022 none — — Details →
5.1.0 20 Apr 2022 none — — Details →
5.0.6 13 Apr 2022 none — — Details →
5.0.5 07 Apr 2022 none — — Details →
5.0.4 31 Mar 2022 none — — Details →
5.0.3 17 Mar 2022 none — — Details →
5.0.2 10 Mar 2022 none — — Details →
5.0.1 08 Mar 2022 none — — Details →
5.0.0 24 Feb 2022 none — — Details →
4.3.1 07 Feb 2022 none — — Details →
4.3.0 27 Jan 2022 none — — Details →
4.2.1 20 Jan 2022 none — — Details →
4.2.0 06 Jan 2022 none — — Details →
4.1.2 05 Jan 2022 none — — Details →
4.1.1 08 Dec 2021 none — — Details →
4.1.0 02 Dec 2021 none — — Details →
4.0.5 18 Nov 2021 none — — Details →
4.0.4 03 Nov 2021 none — — Details →

The newest 120 of 237 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for @npmcli/arborist

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →

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

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About @npmcli/arborist

Is @npmcli/arborist safe to use?

Vulert records 2 vulnerabilities for @npmcli/arborist in npm: 0 critical, 2 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is @npmcli/arborist's Vulert package health score?

Vulert scores @npmcli/arborist 85/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 @npmcli/arborist affected?

No. 10.0.4, 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.

How many vulnerabilities does @npmcli/arborist have?

2 vulnerabilities are recorded for @npmcli/arborist in the npm ecosystem: 0 critical, 2 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 @npmcli/arborist vulnerabilities disclosed?

0 vulnerabilities were recorded for @npmcli/arborist in the last 12 months, and the oldest entry in this database dates to 31 Aug 2021. 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 @npmcli/arborist 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 @npmcli/arborist for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @npmcli/arborist version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.