VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@parcel/scope-hoisting: vulnerability history, versions and safety

@parcel/scope-hoisting is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

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.

See all @parcel/scope-hoisting vulnerabilities

Vulert verdict on @parcel/scope-hoisting 2.0.0-alpha.3 i

Updated on 23 Oct 2026

Good news: 2.0.0-alpha.3, the version you would install today, has no known vulnerabilities.

Package health score 58/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Widely used
  • Community Quiet

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

  • Current release 2.0.0-alpha.3 — 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 83 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/scope-hoisting, 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
2.0.0-nightly.656 10 May 2021 none MIT — Details →
2.0.0-nightly.655 07 May 2021 none MIT — Details →
2.0.0-nightly.653 06 May 2021 none MIT — Details →
2.0.0-nightly.652 05 May 2021 none MIT — Details →
2.0.0-nightly.651 30 Apr 2021 none MIT — Details →
2.0.0-nightly.649 29 Apr 2021 none MIT — Details →
2.0.0-nightly.648 28 Apr 2021 none MIT — Details →
2.0.0-nightly.646 27 Apr 2021 none MIT — Details →
2.0.0-nightly.645 20 Apr 2021 none MIT — Details →
2.0.0-nightly.644 17 Apr 2021 none MIT — Details →
2.0.0-nightly.643 15 Apr 2021 none MIT — Details →
2.0.0-nightly.642 14 Apr 2021 none MIT — Details →
2.0.0-nightly.641 13 Apr 2021 none MIT — Details →
2.0.0-nightly.639 12 Apr 2021 none MIT — Details →
2.0.0-nightly.638 09 Apr 2021 none MIT — Details →
2.0.0-nightly.637 07 Apr 2021 none MIT — Details →
2.0.0-nightly.636 04 Apr 2021 none MIT — Details →
2.0.0-nightly.635 03 Apr 2021 none MIT — Details →
2.0.0-nightly.634 30 Mar 2021 none MIT — Details →
2.0.0-nightly.633 24 Mar 2021 none MIT — Details →
2.0.0-nightly.632 22 Mar 2021 none MIT — Details →
2.0.0-nightly.631 21 Mar 2021 none MIT — Details →
2.0.0-nightly.630 18 Mar 2021 none MIT — Details →
2.0.0-nightly.629 16 Mar 2021 none MIT — Details →
2.0.0-beta.2 16 Mar 2021 none MIT — Details →
2.0.0-nightly.628 14 Mar 2021 none MIT — Details →
2.0.0-nightly.627 13 Mar 2021 none MIT — Details →
2.0.0-nightly.625 11 Mar 2021 none MIT — Details →
2.0.0-nightly.622 10 Mar 2021 none MIT — Details →
2.0.0-nightly.621 08 Mar 2021 none MIT — Details →
2.0.0-nightly.620 06 Mar 2021 none MIT — Details →
2.0.0-nightly.617 05 Mar 2021 none MIT — Details →
2.0.0-nightly.616 04 Mar 2021 none MIT — Details →
2.0.0-nightly.612 27 Feb 2021 none MIT — Details →
2.0.0-nightly.611 26 Feb 2021 none MIT — Details →
2.0.0-nightly.610 25 Feb 2021 none MIT — Details →
2.0.0-nightly.609 24 Feb 2021 none MIT — Details →
2.0.0-nightly.608 23 Feb 2021 none MIT — Details →
2.0.0-nightly.607 22 Feb 2021 none MIT — Details →
2.0.0-nightly.605 20 Feb 2021 none MIT — Details →
2.0.0-nightly.602 19 Feb 2021 none MIT — Details →
2.0.0-nightly.600 18 Feb 2021 none MIT — Details →
2.0.0-nightly.599 17 Feb 2021 none MIT — Details →
2.0.0-nightly.598 15 Feb 2021 none MIT — Details →
2.0.0-nightly.594 14 Feb 2021 none MIT — Details →
2.0.0-nightly.592 13 Feb 2021 none MIT — Details →
2.0.0-nightly.587 12 Feb 2021 none MIT — Details →
2.0.0-nightly.581 10 Feb 2021 none MIT — Details →
2.0.0-nightly.579 09 Feb 2021 none MIT — Details →
2.0.0-nightly.576 06 Feb 2021 none MIT — Details →
2.0.0-nightly.575 05 Feb 2021 none MIT — Details →
2.0.0-nightly.572 04 Feb 2021 none MIT — Details →
2.0.0-nightly.568 03 Feb 2021 none MIT — Details →
2.0.0-nightly.564 02 Feb 2021 none MIT — Details →
2.0.0-nightly.562 01 Feb 2021 none MIT — Details →
2.0.0-nightly.560 30 Jan 2021 none MIT — Details →
2.0.0-nightly.556 27 Jan 2021 none MIT — Details →
2.0.0-nightly.555 26 Jan 2021 none MIT — Details →
2.0.0-nightly.553 23 Jan 2021 none MIT — Details →
2.0.0-nightly.550 22 Jan 2021 none MIT — Details →
2.0.0-nightly.542 19 Jan 2021 none MIT — Details →
2.0.0-nightly.541 18 Jan 2021 none MIT — Details →
2.0.0-nightly.539 17 Jan 2021 none MIT — Details →
2.0.0-nightly.537 15 Jan 2021 none MIT — Details →
2.0.0-nightly.534 14 Jan 2021 none MIT — Details →
2.0.0-nightly.529 13 Jan 2021 none MIT — Details →
2.0.0-nightly.526 11 Jan 2021 none MIT — Details →
2.0.0-nightly.524 10 Jan 2021 none MIT — Details →
2.0.0-nightly.522 09 Jan 2021 none MIT — Details →
2.0.0-nightly.516 07 Jan 2021 none MIT — Details →
2.0.0-nightly.515 06 Jan 2021 none MIT — Details →
2.0.0-nightly.513 05 Jan 2021 none MIT — Details →
2.0.0-nightly.508 03 Jan 2021 none MIT — Details →
2.0.0-nightly.506 03 Jan 2021 none MIT — Details →
2.0.0-nightly.502 01 Jan 2021 none MIT — Details →
2.0.0-nightly.498 31 Dec 2020 none MIT — Details →
2.0.0-nightly.497 30 Dec 2020 none MIT — Details →
2.0.0-nightly.494 29 Dec 2020 none MIT — Details →
2.0.0-nightly.493 26 Dec 2020 none MIT — Details →
2.0.0-nightly.492 25 Dec 2020 none MIT — Details →
2.0.0-nightly.491 24 Dec 2020 none MIT — Details →
2.0.0-nightly.488 20 Dec 2020 none MIT — Details →
2.0.0-nightly.487 19 Dec 2020 none MIT — Details →
2.0.0-nightly.483 16 Dec 2020 none MIT — Details →
2.0.0-nightly.481 15 Dec 2020 none MIT — Details →
2.0.0-nightly.479 14 Dec 2020 none MIT — Details →
2.0.0-nightly.478 11 Dec 2020 none MIT — Details →
2.0.0-nightly.477 10 Dec 2020 none MIT — Details →
2.0.0-nightly.476 09 Dec 2020 none MIT — Details →
2.0.0-nightly.474 08 Dec 2020 none MIT — Details →
2.0.0-nightly.471 07 Dec 2020 none MIT — Details →
2.0.0-nightly.469 06 Dec 2020 none MIT — Details →
2.0.0-nightly.468 04 Dec 2020 none MIT — Details →
2.0.0-nightly.467 03 Dec 2020 none MIT — Details →
2.0.0-nightly.466 02 Dec 2020 none MIT — Details →
2.0.0-nightly.465 01 Dec 2020 none MIT — Details →
2.0.0-nightly.464 24 Nov 2020 none MIT — Details →
2.0.0-nightly.462 23 Nov 2020 none MIT — Details →
2.0.0-nightly.459 22 Nov 2020 none MIT — Details →
2.0.0-nightly.456 21 Nov 2020 none MIT — Details →
2.0.0-nightly.455 20 Nov 2020 none — — Details →
2.0.0-nightly.454 19 Nov 2020 none — — Details →
2.0.0-nightly.449 15 Nov 2020 none — — Details →
2.0.0-nightly.448 14 Nov 2020 none — — Details →
2.0.0-nightly.447 13 Nov 2020 none — — Details →
2.0.0-nightly.446 12 Nov 2020 none — — Details →
2.0.0-nightly.445 10 Nov 2020 none — — Details →
2.0.0-nightly.444 09 Nov 2020 none — — Details →
2.0.0-nightly.442 07 Nov 2020 none — — Details →
2.0.0-nightly.441 06 Nov 2020 none — — Details →
2.0.0-nightly.440 31 Oct 2020 none — — Details →
2.0.0-nightly.437 29 Oct 2020 none — — Details →
2.0.0-nightly.435 27 Oct 2020 none — — Details →
2.0.0-nightly.434 26 Oct 2020 none — — Details →
2.0.0-nightly.432 25 Oct 2020 none — — Details →
2.0.0-nightly.431 22 Oct 2020 none — — Details →
2.0.0-nightly.430 21 Oct 2020 none — — Details →
2.0.0-nightly.429 21 Oct 2020 none — — Details →
2.0.0-nightly.428 20 Oct 2020 none — — Details →
2.0.0-nightly.427 14 Oct 2020 none — — Details →

The newest 120 of 293 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/scope-hoisting

No vulnerability write-ups match this view

Search all 0 in the database →

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

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 @parcel/scope-hoisting

Is @parcel/scope-hoisting safe to use?

Vulert has no vulnerabilities on record for @parcel/scope-hoisting 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/scope-hoisting's Vulert package health score?

Vulert scores @parcel/scope-hoisting 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/scope-hoisting affected?

No. 2.0.0-alpha.3, 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/scope-hoisting should I use?

2.0.0-alpha.3 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/scope-hoisting have?

0 vulnerabilities are recorded for @parcel/scope-hoisting 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/scope-hoisting vulnerabilities disclosed?

0 vulnerabilities were recorded for @parcel/scope-hoisting 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/scope-hoisting 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/scope-hoisting for upcoming vulnerabilities?

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