VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@parcel/logger: vulnerability history, versions and safety

@parcel/logger 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/logger vulnerabilities

Vulert verdict on @parcel/logger 2.16.4 i

Updated on 23 Oct 2026

Good news: 2.16.4, the version you would install today, has no known vulnerabilities.

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

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

  • Current release 2.16.4 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 1,038 packages i
  • Stars 44,006 i
  • OpenSSF scorecard 2/10 i
  • Last release 8 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/logger, 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-canary.1875 03 Feb 2026 none MIT — Details →
2.16.4 02 Feb 2026 none MIT — Details →
2.0.0-canary.1873 07 Dec 2025 none MIT — Details →
2.16.3 06 Dec 2025 none MIT — Details →
2.16.2 06 Dec 2025 none MIT — Details →
2.0.0-canary.1866 06 Nov 2025 none MIT — Details →
2.16.1 05 Nov 2025 none MIT — Details →
2.0.0-canary.1864 24 Oct 2025 none MIT — Details →
2.0.0-canary.1863 19 Sep 2025 none MIT — Details →
2.16.0 18 Sep 2025 none MIT — Details →
2.0.0-canary.1861 31 Aug 2025 none MIT — Details →
2.0.0-canary.1860 21 Jun 2025 none MIT — Details →
2.15.4 20 Jun 2025 none MIT — Details →
2.15.3 20 Jun 2025 none MIT — Details →
2.0.0-canary.1853 08 Jun 2025 none MIT — Details →
2.0.0-canary.1850 29 May 2025 none MIT — Details →
2.0.0-canary.1849 25 May 2025 none MIT — Details →
2.15.2 25 May 2025 none MIT — Details →
2.0.0-canary.1842 21 May 2025 none MIT — Details →
2.0.0-canary.1837 19 May 2025 none MIT — Details →
2.0.0-canary.1835 17 May 2025 none MIT — Details →
2.15.1 16 May 2025 none MIT — Details →
2.0.0-canary.1833 16 May 2025 none MIT — Details →
2.0.0-canary.1832 13 May 2025 none MIT — Details →
2.15.0 12 May 2025 none MIT — Details →
2.0.0-canary.1826 11 May 2025 none MIT — Details →
2.0.0-canary.1820 11 May 2025 none MIT — Details →
2.0.0-canary.1819 30 Apr 2025 none MIT — Details →
2.0.0-canary.1818 28 Apr 2025 none MIT — Details →
2.0.0-canary.1814 31 Mar 2025 none MIT — Details →
2.14.4 29 Mar 2025 none MIT — Details →
2.14.3 29 Mar 2025 none MIT — Details →
2.0.0-canary.1805 25 Mar 2025 none MIT — Details →
2.14.2 23 Mar 2025 none MIT — Details →
2.0.0-canary.1799 21 Mar 2025 none MIT — Details →
2.14.1 19 Mar 2025 none MIT — Details →
2.0.0-canary.1794 19 Mar 2025 none MIT — Details →
2.14.0 18 Mar 2025 none MIT — Details →
2.0.0-canary.1791 18 Mar 2025 none MIT — Details →
2.0.0-canary.1789 09 Mar 2025 none MIT — Details →
2.0.0-canary.1787 06 Mar 2025 none MIT — Details →
2.0.0-canary.1781 24 Feb 2025 none MIT — Details →
2.0.0-canary.1780 21 Feb 2025 none MIT — Details →
2.0.0-canary.1779 05 Feb 2025 none MIT — Details →
2.0.0-canary.1778 03 Feb 2025 none MIT — Details →
2.0.0-canary.1777 03 Feb 2025 none MIT — Details →
2.0.0-canary.1776 21 Jan 2025 none MIT — Details →
2.0.0-canary.1775 21 Jan 2025 none MIT — Details →
2.0.0-canary.1772 12 Jan 2025 none MIT — Details →
2.0.0-canary.1770 08 Jan 2025 none MIT — Details →
2.0.0-canary.1769 06 Jan 2025 none MIT — Details →
2.0.0-canary.1768 03 Jan 2025 none MIT — Details →
2.0.0-canary.1766 31 Dec 2024 none MIT — Details →
2.0.0-canary.1765 26 Dec 2024 none MIT — Details →
2.0.0-canary.1764 24 Dec 2024 none MIT — Details →
2.0.0-canary.1763 23 Dec 2024 none MIT — Details →
2.0.0-canary.1761 17 Dec 2024 none MIT — Details →
2.13.3 16 Dec 2024 none MIT — Details →
2.0.0-dev.1795 16 Dec 2024 none MIT — Details →
2.0.0-dev.1789 10 Dec 2024 none MIT — Details →
2.0.0-dev.1781 09 Dec 2024 none MIT — Details →
2.0.0-canary.1759 28 Nov 2024 none MIT — Details →
2.13.2 25 Nov 2024 none MIT — Details →
2.13.1 25 Nov 2024 none MIT — Details →
2.0.0-canary.1749 13 Nov 2024 none MIT — Details →
2.13.0 12 Nov 2024 none MIT — Details →
2.0.0-canary.1742 11 Nov 2024 none MIT — Details →
2.0.0-canary.1741 11 Nov 2024 none MIT — Details →
2.0.0-canary.1736 10 Nov 2024 none MIT — Details →
2.0.0-canary.1735 05 Nov 2024 none MIT — Details →
2.0.0-canary.1733 15 Oct 2024 none MIT — Details →
2.0.0-canary.1732 11 Oct 2024 none MIT — Details →
2.0.0-canary.1731 01 Oct 2024 none MIT — Details →
2.0.0-canary.1730 30 Sep 2024 none MIT — Details →
2.0.0-canary.1728 29 Sep 2024 none MIT — Details →
2.0.0-canary.1727 28 Sep 2024 none MIT — Details →
2.0.0-canary.1722 28 Aug 2024 none MIT — Details →
2.0.0-canary.1721 28 Aug 2024 none MIT — Details →
2.0.0-canary.1720 22 Aug 2024 none MIT — Details →
2.0.0-canary.1719 15 Aug 2024 none MIT — Details →
2.0.0-canary.1718 13 Aug 2024 none MIT — Details →
2.0.0-canary.1717 12 Aug 2024 none MIT — Details →
2.0.0-canary.1716 12 Aug 2024 none MIT — Details →
2.0.0-canary.1715 09 Aug 2024 none MIT — Details →
2.0.0-canary.1714 08 Aug 2024 none MIT — Details →
2.0.0-canary.1713 08 Aug 2024 none MIT — Details →
2.0.0-canary.1712 06 Aug 2024 none MIT — Details →
2.0.0-canary.1711 06 Aug 2024 none MIT — Details →
2.0.0-dev.1712 06 Aug 2024 none MIT — Details →
2.0.0-canary.1710 05 Aug 2024 none MIT — Details →
2.0.0-canary.1709 05 Aug 2024 none MIT — Details →
2.0.0-canary.1707 02 Aug 2024 none MIT — Details →
2.0.0-canary.1706 02 Aug 2024 none MIT — Details →
2.0.0-canary.1705 02 Aug 2024 none MIT — Details →
2.0.0-canary.1704 01 Aug 2024 none MIT — Details →
2.0.0-canary.1702 31 Jul 2024 none MIT — Details →
2.0.0-canary.1700 31 Jul 2024 none MIT — Details →
2.0.0-canary.1699 30 Jul 2024 none MIT — Details →
2.0.0-canary.1697 30 Jul 2024 none MIT — Details →
2.0.0-canary.1696 29 Jul 2024 none MIT — Details →
2.0.0-canary.1695 29 Jul 2024 none — — Details →
2.0.0-canary.1694 26 Jul 2024 none — — Details →
2.0.0-canary.1693 26 Jul 2024 none — — Details →
2.0.0-canary.1691 24 Jul 2024 none — — Details →
2.0.0-canary.1690 24 Jul 2024 none — — Details →
2.0.0-canary.1688 23 Jul 2024 none — — Details →
2.0.0-canary.1687 19 Jul 2024 none — — Details →
2.0.0-canary.1685 17 Jul 2024 none — — Details →
2.0.0-canary.1684 17 Jul 2024 none — — Details →
2.0.0-canary.1683 17 Jul 2024 none — — Details →
2.0.0-canary.1681 15 Jul 2024 none — — Details →
2.0.0-dev.1680 15 Jul 2024 none — — Details →
2.0.0-canary.1670 11 Jul 2024 none — — Details →
2.0.0-canary.1669 11 Jul 2024 none — — Details →
2.0.0-canary.1667 26 Jun 2024 none — — Details →
2.0.0-canary.1666 26 Jun 2024 none — — Details →
2.0.0-canary.1665 25 Jun 2024 none — — Details →
2.0.0-canary.1663 25 Jun 2024 none — — Details →
2.0.0-canary.1662 25 Jun 2024 none — — Details →
2.0.0-canary.1661 24 Jun 2024 none — — Details →

The newest 120 of 957 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/logger

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/logger

Is @parcel/logger safe to use?

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

Vulert scores @parcel/logger 81/100, which reads as in good shape. 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/logger affected?

No. 2.16.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.

Which version of @parcel/logger should I use?

2.16.4 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/logger have?

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

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

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