VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@parcel/source-map: vulnerability history, versions and safety

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

Vulert verdict on @parcel/source-map 2.1.1 i

Updated on 23 Oct 2026

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

Package health score 53/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Widely used
  • Community Inactive

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

  • Current release 2.1.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 2,468 packages i
  • Stars 111 i
  • OpenSSF scorecard 2/10 i
  • Last release 49 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/source-map, 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.1.1 17 Sep 2022 none MIT — Details →
2.1.0 04 Jul 2022 none MIT — Details →
2.0.5 20 May 2022 none MIT — Details →
2.0.4 20 May 2022 none MIT — Details →
2.0.3 19 May 2022 none MIT — Details →
2.0.2 27 Jan 2022 none MIT — Details →
2.0.1 18 Jan 2022 none MIT — Details →
2.0.0 08 Oct 2021 none MIT — Details →
2.0.0-rc.7 19 Aug 2021 none MIT — Details →
2.0.0-rc.6 31 Jul 2021 none MIT — Details →
2.0.0-rc.5 06 Jul 2021 none MIT — Details →
2.0.0-rc.4 25 May 2021 none MIT — Details →
2.0.0-rc.3 25 May 2021 none MIT — Details →
2.0.0-rc.2 22 May 2021 none MIT — Details →
2.0.0-rc.1.0 13 May 2021 none MIT — Details →
2.0.0-alpha.4.23 12 May 2021 none MIT — Details →
2.0.0-alpha.4.22 03 Mar 2021 none MIT — Details →
2.0.0-alpha.4.21 08 Feb 2021 none MIT — Details →
2.0.0-alpha.4.20 14 Dec 2020 none MIT — Details →
2.0.0-alpha.4.19 13 Dec 2020 none MIT — Details →
2.0.0-alpha.4.18 30 Nov 2020 none MIT — Details →
2.0.0-alpha.4.17 20 Oct 2020 none MIT — Details →
2.0.0-alpha.4.16 13 Oct 2020 none MIT — Details →
2.0.0-alpha.4.15 07 Sep 2020 none MIT — Details →
2.0.0-alpha.4.14 06 Sep 2020 none MIT — Details →
2.0.0-alpha.4.13 16 Jun 2020 none MIT — Details →
2.0.0-alpha.4.12 11 Jun 2020 none MIT — Details →
2.0.0-alpha.4.11 01 Jun 2020 none MIT — Details →
2.0.0-alpha.4.10 01 May 2020 none MIT — Details →
2.0.0-alpha.4.9 10 Apr 2020 none MIT — Details →
2.0.0-alpha.4.8 05 Apr 2020 none MIT — Details →
2.0.0-alpha.4.7 04 Apr 2020 none MIT — Details →
2.0.0-alpha.4.6 31 Mar 2020 none MIT — Details →
2.0.0-alpha.4.5 31 Mar 2020 none MIT — Details →
2.0.0-alpha.4.4 28 Mar 2020 none MIT — Details →
2.0.0-nightly.167 24 Mar 2020 none MIT — Details →
2.0.0-alpha.4.3 23 Mar 2020 none MIT — Details →
2.0.0-alpha.4.2 23 Mar 2020 none MIT — Details →
2.0.0-alpha.4.1 23 Mar 2020 none MIT — Details →
2.0.0-nightly.166 23 Mar 2020 none MIT — Details →
2.0.0-alpha.4 22 Mar 2020 none MIT — Details →
2.0.0-nightly.165 22 Mar 2020 none MIT — Details →
2.0.0-nightly.159 21 Mar 2020 none MIT — Details →
2.0.0-nightly.156 20 Mar 2020 none MIT — Details →
2.0.0-nightly.155 18 Mar 2020 none MIT — Details →
2.0.0-nightly.151 16 Mar 2020 none MIT — Details →
2.0.0-nightly.150 15 Mar 2020 none MIT — Details →
2.0.0-nightly.149 14 Mar 2020 none MIT — Details →
2.0.0-nightly.148 12 Mar 2020 none MIT — Details →
2.0.0-nightly.146 10 Mar 2020 none MIT — Details →
2.0.0-nightly.144 09 Mar 2020 none MIT — Details →
2.0.0-nightly.143 08 Mar 2020 none MIT — Details →
2.0.0-nightly.142 07 Mar 2020 none MIT — Details →
2.0.0-nightly.140 06 Mar 2020 none MIT — Details →
2.0.0-nightly.137 05 Mar 2020 none MIT — Details →
2.0.0-nightly.135 04 Mar 2020 none MIT — Details →
2.0.0-nightly.133 02 Mar 2020 none MIT — Details →
2.0.0-nightly.132 28 Feb 2020 none MIT — Details →
2.0.0-nightly.130 27 Feb 2020 none MIT — Details →
2.0.0-nightly.127 26 Feb 2020 none MIT — Details →
2.0.0-nightly.122 25 Feb 2020 none MIT — Details →
2.0.0-nightly.121 22 Feb 2020 none MIT — Details →
2.0.0-nightly.120 20 Feb 2020 none MIT — Details →
2.0.0-nightly.119 20 Feb 2020 none MIT — Details →
2.0.0-nightly.118 19 Feb 2020 none MIT — Details →
2.0.0-nightly.117 18 Feb 2020 none MIT — Details →
2.0.0-nightly.116 17 Feb 2020 none MIT — Details →
2.0.0-nightly.115 16 Feb 2020 none MIT — Details →
2.0.0-nightly.112 15 Feb 2020 none MIT — Details →
2.0.0-nightly.107 14 Feb 2020 none MIT — Details →
2.0.0-nightly.102 13 Feb 2020 none MIT — Details →
2.0.0-nightly.101 12 Feb 2020 none MIT — Details →
2.0.0-nightly.97 12 Feb 2020 none MIT — Details →
2.0.0-nightly.92 11 Feb 2020 none MIT — Details →
2.0.0-nightly.88 09 Feb 2020 none MIT — Details →
2.0.0-nightly.87 08 Feb 2020 none MIT — Details →
2.0.0-nightly.85 06 Feb 2020 none MIT — Details →
2.0.0-nightly.79 03 Feb 2020 none MIT — Details →
2.0.0-nightly.72 02 Feb 2020 none MIT — Details →
2.0.0-nightly.69 01 Feb 2020 none MIT — Details →
2.0.0-nightly.68 31 Jan 2020 none MIT — Details →
2.0.0-nightly.67 30 Jan 2020 none MIT — Details →
2.0.0-nightly.66 29 Jan 2020 none MIT — Details →
2.0.0-nightly.65 28 Jan 2020 none MIT — Details →
2.0.0-alpha.3.1 20 Nov 2019 none MIT — Details →
2.0.0-alpha.3 20 Nov 2019 none MIT — Details →
2.0.0-alpha.2.1 15 Oct 2019 none MIT — Details →
2.0.0-alpha.2 15 Oct 2019 none MIT — Details →
2.0.0-alpha.1.1 13 Aug 2019 none MIT — Details →
2.0.0-alpha.1 13 Aug 2019 none MIT — Details →

All 90 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 @parcel/source-map

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/source-map

Is @parcel/source-map safe to use?

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

Vulert scores @parcel/source-map 53/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/source-map affected?

No. 2.1.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/source-map should I use?

2.1.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/source-map have?

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

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

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