Vulnerability Database · npm · Package report
@parcel/node-libs-browser: vulnerability history, versions and safety
@parcel/node-libs-browser 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 @parcel/node-libs-browser 2.2.1 i
Updated on 23 Oct 2026
Good news: 2.2.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Widely used
- Community Quiet
What to do: Stay on 2.2.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.2.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 2.2.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 2 packages i
- Stars 44,006 i
- OpenSSF scorecard 2/10 i
- Last release 57 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 @parcel/node-libs-browser, 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.
- 2.2.2-nightly.2609 18 Jan 2022
- 2.2.1 17 Jan 2022
- 2.2.1-nightly.2605 14 Jan 2022
- 2.2.0 12 Jan 2022
- 2.1.2-nightly.2601 11 Jan 2022
- 2.1.2-nightly.2600 08 Jan 2022
- 2.1.1 06 Jan 2022
- 2.1.1-nightly.2593 06 Jan 2022
- 2.1.0 05 Jan 2022
- 2.0.2-nightly.2589 05 Jan 2022
- 2.0.2-nightly.2585 03 Jan 2022
- 2.0.2-nightly.2584 02 Jan 2022
- 2.0.2-nightly.2581 30 Dec 2021
- 2.0.2-nightly.2576 26 Dec 2021
- 2.0.2-nightly.2575 20 Dec 2021
- 2.0.2-nightly.2573 17 Dec 2021
- 2.0.2-nightly.2572 17 Dec 2021
- 2.0.2-nightly.2571 16 Dec 2021
- 2.0.2-nightly.2569 14 Dec 2021
- 2.0.2-nightly.2566 12 Dec 2021
- 2.0.2-nightly.2564 12 Dec 2021
- 2.0.2-nightly.2563 09 Dec 2021
- 2.0.2-nightly.2558 01 Dec 2021
- 2.0.2-nightly.2556 30 Nov 2021
- 2.0.2-nightly.2554 29 Nov 2021
- 2.0.2-nightly.2549 25 Nov 2021
- 2.0.2-nightly.2548 24 Nov 2021
- 2.0.2-nightly.2541 22 Nov 2021
- 2.0.2-nightly.2540 17 Nov 2021
- 2.0.2-nightly.2536 15 Nov 2021
- 2.0.2-nightly.2534 13 Nov 2021
- 2.0.2-nightly.2533 09 Nov 2021
- 2.0.1 08 Nov 2021
- 2.0.1-nightly.2529 06 Nov 2021
- 2.0.1-nightly.2528 05 Nov 2021
- 2.0.1-nightly.2527 03 Nov 2021
- 2.0.1-nightly.2521 02 Nov 2021
- 2.0.1-nightly.2520 01 Nov 2021
- 2.0.1-nightly.2519 30 Oct 2021
- 2.0.1-nightly.2518 28 Oct 2021
- 2.0.1-nightly.2517 27 Oct 2021
- 2.0.1-nightly.2514 25 Oct 2021
- 2.0.1-nightly.2513 22 Oct 2021
- 2.0.1-nightly.2512 19 Oct 2021
- 2.0.1-nightly.2511 17 Oct 2021
- 2.0.1-nightly.2510 16 Oct 2021
- 2.0.1-nightly.2509 15 Oct 2021
- 2.0.1-nightly.2508 14 Oct 2021
- 2.0.0 13 Oct 2021
- 2.0.0-nightly.2506 12 Oct 2021
- 2.0.0-nightly.2503 12 Oct 2021
- 2.0.0-nightly.2501 11 Oct 2021
- 2.0.0-nightly.2500 10 Oct 2021
- 2.0.0-nightly.2497 09 Oct 2021
- 2.0.0-nightly.2491 08 Oct 2021
- 2.0.0-nightly.2488 07 Oct 2021
- 2.0.0-nightly.2483 06 Oct 2021
- 2.0.0-nightly.2479 05 Oct 2021
- 2.0.0-nightly.2476 04 Oct 2021
- 2.0.0-nightly.2474 02 Oct 2021
- 2.0.0-nightly.2471 30 Sep 2021
- 2.0.0-nightly.2469 29 Sep 2021
- 2.0.0-nightly.2468 29 Sep 2021
- 2.0.0-nightly.2467 23 Sep 2021
- 2.0.0-nightly.2466 21 Sep 2021
- 2.0.0-nightly.2465 19 Sep 2021
- 2.0.0-nightly.2464 17 Sep 2021
- 2.0.0-nightly.2462 16 Sep 2021
- 2.0.0-nightly.2461 15 Sep 2021
- 2.0.0-nightly.2460 12 Sep 2021
- 2.0.0-nightly.2448 02 Sep 2021
- 2.0.0-nightly.2445 01 Sep 2021
- 2.0.0-nightly.2443 31 Aug 2021
- 2.0.0-nightly.2441 30 Aug 2021
- 2.0.0-nightly.2437 29 Aug 2021
- 2.0.0-nightly.2436 28 Aug 2021
- 2.0.0-nightly.2435 27 Aug 2021
- 2.0.0-nightly.2434 26 Aug 2021
- 2.0.0-nightly.2433 24 Aug 2021
- 2.0.0-nightly.2430 23 Aug 2021
- 2.0.0-nightly.2428 22 Aug 2021
- 2.0.0-nightly.2426 20 Aug 2021
- 2.0.0-nightly.2425 18 Aug 2021
- 2.0.0-nightly.2424 17 Aug 2021
- 2.0.0-nightly.2423 14 Aug 2021
- 2.0.0-nightly.2422 12 Aug 2021
- 2.0.0-nightly.2420 07 Aug 2021
- 2.0.0-nightly.2418 04 Aug 2021
- 2.0.0-rc.0 03 Aug 2021
- 2.0.0-nightly.2417 03 Aug 2021
- 2.0.0-nightly.2416 31 Jul 2021
- 2.0.0-nightly.2414 29 Jul 2021
- 2.0.0-nightly.2400 19 Jul 2021
- 2.0.0-nightly.2398 18 Jul 2021
- 2.0.0-nightly.2393 13 Jul 2021
- 2.0.0-nightly.2391 12 Jul 2021
- 2.0.0-nightly.2388 11 Jul 2021
- 2.0.0-nightly.2387 10 Jul 2021
- 2.0.0-nightly.2384 09 Jul 2021
- 2.0.0-nightly.2380 08 Jul 2021
- 2.0.0-nightly.2377 07 Jul 2021
- 2.0.0-nightly.2376 06 Jul 2021
- 2.0.0-nightly.2374 03 Jul 2021
- 2.0.0-nightly.2373 02 Jul 2021
- 2.0.0-nightly.2370 29 Jun 2021
- 2.0.0-nightly.2358 26 Jun 2021
- 2.0.0-nightly.2357 25 Jun 2021
- 2.0.0-nightly.2356 24 Jun 2021
- 2.0.0-nightly.2355 23 Jun 2021
- 2.0.0-nightly.2353 21 Jun 2021
- 2.0.0-nightly.2350 20 Jun 2021
- 2.0.0-nightly.2349 18 Jun 2021
- 2.0.0-nightly.2346 16 Jun 2021
- 2.0.0-nightly.2344 14 Jun 2021
- 2.0.0-nightly.2343 13 Jun 2021
- 2.0.0-nightly.2342 12 Jun 2021
- 2.0.0-nightly.2340 11 Jun 2021
- 2.0.0-nightly.2338 09 Jun 2021
- 2.0.0-nightly.2335 07 Jun 2021
- 2.0.0-nightly.2332 06 Jun 2021
The newest 120 of 404 versions Vulert tracks. 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 @parcel/node-libs-browser
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 @parcel/node-libs-browser
Is @parcel/node-libs-browser safe to use?
Vulert has no vulnerabilities on record for @parcel/node-libs-browser 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 @parcel/node-libs-browser's Vulert package health score?
Vulert scores @parcel/node-libs-browser 58/100, which reads as usable, but worth attention. 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 @parcel/node-libs-browser affected?
No. 2.2.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 @parcel/node-libs-browser should I use?
2.2.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 @parcel/node-libs-browser have?
0 vulnerabilities are recorded for @parcel/node-libs-browser 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 @parcel/node-libs-browser vulnerabilities disclosed?
0 vulnerabilities were recorded for @parcel/node-libs-browser 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 @parcel/node-libs-browser 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 @parcel/node-libs-browser for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @parcel/node-libs-browser version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.