VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

dash-core-components: vulnerability history, versions and safety

dash-core-components is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 88 releases, first recorded in Feb 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
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 dash-core-components vulnerabilities

Vulert verdict on dash-core-components 4.5.1 i

Updated on 23 Oct 2026

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

Package health score 80/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 4.5.1 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 02 Feb 2024 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Stars 24,463 i
  • OpenSSF scorecard 4/10 i
  • Last release this month 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 dash-core-components, 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
4.5.1 15 Oct 2026 none MIT — Details →
4.5.0 21 Sep 2026 none MIT — Details →
4.4.1 21 Jul 2026 none MIT — Details →
4.4.0 03 Jul 2026 none MIT — Details →
4.3.0 19 Jun 2026 none MIT — Details →
4.2.0 01 Jun 2026 none MIT — Details →
4.1.0 23 Mar 2026 none MIT — Details →
4.0.0 03 Feb 2026 none MIT — Details →
3.4.0 20 Jan 2026 none MIT — Details →
4.0.0-rc6 12 Jan 2026 none MIT — Details →
4.0.0-rc5 17 Dec 2025 none MIT — Details →
4.0.0-rc4 05 Dec 2025 none MIT — Details →
4.0.0-rc3 27 Nov 2025 none MIT — Details →
3.3.0 12 Nov 2025 none MIT — Details →
4.0.0-rc2 10 Oct 2025 none MIT — Details →
4.0.0-rc1 22 Sep 2025 none MIT — Details →
4.0.0-rc0 11 Sep 2025 none MIT — Details →
3.2.0 31 Jul 2025 none MIT — Details →
3.1.0 26 Jun 2025 none MIT — Details →
3.0.6 24 Apr 2025 none MIT — Details →
3.0.5 14 Apr 2025 none MIT — Details →
3.0.4 01 Apr 2025 none MIT — Details →
3.0.3 17 Mar 2025 none MIT — Details →
3.0.2 04 Mar 2025 none MIT — Details →
3.0.1 18 Feb 2025 none MIT — Details →
3.0.0 28 Jan 2025 none MIT — Details →
2.14.3 04 Nov 2024 none MIT — Details →
2.14.2 04 Sep 2024 none MIT — Details →
2.14.1 12 Jun 2024 none MIT — Details →
2.14.0 03 May 2024 none MIT — Details →
2.13.1 01 Mar 2024 none MIT — Details →
2.13.0 31 Jan 2024 none MIT — Details →
2.12.1 11 Oct 2023 M1 MIT Yes Details →
2.12.0 28 Aug 2023 M1 MIT Yes Details →
2.11.1 14 Aug 2023 M1 MIT Yes Details →
2.11.0 23 Jun 2023 M1 MIT Yes Details →
2.10.0 25 May 2023 M1 MIT Yes Details →
2.9.2 13 Apr 2023 M1 MIT Yes Details →
2.9.1 29 Mar 2023 M1 MIT Yes Details →
2.9.0 16 Mar 2023 M1 MIT Yes Details →
2.8.0 24 Jan 2023 M1 MIT Yes Details →
2.7.1 12 Dec 2022 M1 MIT Yes Details →
2.7.0 03 Nov 2022 M1 MIT Yes Details →
2.6.2 23 Sep 2022 M1 MIT Yes Details →
2.6.1 02 Aug 2022 M1 MIT Yes Details →
2.6.0 15 Jul 2022 M1 MIT Yes Details →
2.5.0 07 Jun 2022 M1 MIT Yes Details →
2.4.0 11 May 2022 M1 MIT Yes Details →
2.3.0 14 Mar 2022 M1 MIT Yes Details →
2.2.0 18 Feb 2022 M1 MIT Yes Details →
2.1.0 28 Jan 2022 M1 MIT Yes Details →
2.0.0 07 Sep 2021 M1 MIT Yes Details →
1.17.1 13 Jul 2021 M1 MIT Yes Details →
1.16.0 08 Apr 2021 M1 MIT Yes Details →
1.15.0 19 Jan 2021 M1 MIT Yes Details →
1.14.1 09 Dec 2020 M1 MIT Yes Details →
1.14.0 07 Dec 2020 M1 MIT Yes Details →
1.13.0 29 Oct 2020 M1 MIT Yes Details →
1.12.1 16 Sep 2020 M1 MIT Yes Details →
1.12.0 03 Sep 2020 M1 MIT Yes Details →
1.11.0 25 Aug 2020 M1 MIT Yes Details →
1.10.2 27 Jul 2020 M1 MIT Yes Details →
1.10.1 18 Jun 2020 M1 MIT Yes Details →
1.10.0 05 May 2020 M1 MIT Yes Details →
1.9.1 10 Apr 2020 M1 MIT Yes Details →
1.9.0 01 Apr 2020 M1 MIT Yes Details →
1.8.1 27 Feb 2020 M1 MIT Yes Details →
1.8.0 04 Feb 2020 M1 MIT Yes Details →
1.7.1 15 Jan 2020 M1 MIT Yes Details →
1.7.0 14 Jan 2020 M1 MIT Yes Details →
1.6.0 27 Nov 2019 M1 MIT Yes Details →
1.5.1 14 Nov 2019 M1 MIT Yes Details →
1.5.0 04 Nov 2019 M1 MIT Yes Details →
1.4.0 29 Oct 2019 M1 MIT Yes Details →
1.3.1 17 Oct 2019 M1 MIT Yes Details →
1.3.0 08 Oct 2019 M1 MIT Yes Details →
1.2.1 19 Sep 2019 M1 MIT Yes Details →
1.2.0 17 Sep 2019 M1 MIT Yes Details →
1.1.2 27 Aug 2019 M1 MIT Yes Details →
1.1.1 06 Aug 2019 M1 MIT Yes Details →
1.1.0 05 Aug 2019 M1 MIT Yes Details →
1.0.0 20 Jun 2019 M1 MIT Yes Details →
0.48.0 15 May 2019 M1 MIT Yes Details →
0.47.0 25 Apr 2019 M1 MIT Yes Details →
0.46.0 10 Apr 2019 M1 MIT Yes Details →
0.45.0 25 Mar 2019 M1 MIT Yes Details →
0.45.0-rc1 20 Mar 2019 M1 MIT Yes Details →
0.44.0 05 Mar 2019 M1 MIT Yes Details →
0.44.0-rc3 14 Feb 2019 M1 MIT Yes Details →
0.44.0-rc2 13 Feb 2019 M1 MIT Yes Details →
0.43.1 11 Feb 2019 M1 MIT Yes Details →
0.43.0 25 Jan 2019 M1 MIT Yes Details →
0.42.1 08 Jan 2019 M1 MIT Yes Details →
0.42.0 27 Dec 2018 M1 MIT Yes Details →
1.0.0-alpha4 18 Dec 2018 M1 MIT Yes Details →
1.0.0-alpha3 18 Dec 2018 M1 MIT Yes Details →
1.0.0-alpha2 18 Dec 2018 M1 MIT Yes Details →
1.0.0-alpha1 18 Dec 2018 M1 MIT Yes Details →
0.42.0-rc1 18 Dec 2018 M1 MIT Yes Details →
0.41.0 11 Dec 2018 M1 MIT Yes Details →
0.40.5 11 Dec 2018 M1 — Yes Details →
0.40.4 11 Dec 2018 M1 — Yes Details →
0.40.3 07 Dec 2018 M1 — Yes Details →
0.40.2 04 Dec 2018 M1 — Yes Details →
0.40.1 04 Dec 2018 M1 — Yes Details →
0.41.0-rc4 03 Dec 2018 M1 — Yes Details →
0.41.0-rc3 03 Dec 2018 M1 — Yes Details →
0.41.0-rc2 03 Dec 2018 M1 — Yes Details →
0.39.0-rc103 30 Nov 2018 M1 — Yes Details →
0.41.0-rc1 30 Nov 2018 M1 — Yes Details →
0.40.0 29 Nov 2018 M1 — Yes Details →
0.39.0 28 Nov 2018 M1 — Yes Details →
0.39.0-rc101 24 Nov 2018 M1 — Yes Details →
0.38.1 21 Nov 2018 M1 — Yes Details →
0.39.0-rc4 19 Nov 2018 M1 — Yes Details →
0.39.0-rc3 08 Nov 2018 M1 — Yes Details →
0.39.0-rc2 08 Nov 2018 M1 — Yes Details →
0.39.0-rc1 08 Nov 2018 M1 — Yes Details →
0.38.0 08 Nov 2018 M1 — Yes Details →
0.37.2 07 Nov 2018 M1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for dash-core-components

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Vulnerability in Dash Apps: Cross-site Scripting (XSS) 6.5 medium 2.13.0 02 Feb 2024

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 dash-core-components

Is dash-core-components safe to use?

Vulert records 1 vulnerabilities for dash-core-components in npm: 0 critical, 0 high, 1 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 dash-core-components's Vulert package health score?

Vulert scores dash-core-components 80/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 dash-core-components affected?

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

How many vulnerabilities does dash-core-components have?

1 vulnerability is recorded for dash-core-components in the npm ecosystem: 0 critical, 0 high, 1 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 dash-core-components vulnerabilities disclosed?

0 vulnerabilities were recorded for dash-core-components in the last 12 months, and the oldest entry in this database dates to 02 Feb 2024. 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 dash-core-components 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 dash-core-components for upcoming vulnerabilities?

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