VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

vue-chartjs: vulnerability history, versions and safety

vue-chartjs 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 vue-chartjs vulnerabilities

Vulert verdict on vue-chartjs 5.3.4 i

Updated on 23 Oct 2026

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

Package health score 83/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 5.3.4 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 202 packages i
  • Stars 5,716 i
  • OpenSSF scorecard 3/10 i
  • Last release 3 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 vue-chartjs, 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
5.3.4 07 Jul 2026 none MIT — Details →
5.3.3 03 Nov 2025 none MIT — Details →
5.3.2 31 Oct 2024 none MIT — Details →
5.3.1 09 Apr 2024 none MIT — Details →
5.3.0 14 Dec 2023 none MIT — Details →
5.2.0 09 Jan 2023 none MIT — Details →
5.1.0 19 Dec 2022 none MIT — Details →
5.0.1 06 Dec 2022 none MIT — Details →
5.0.0 05 Dec 2022 none MIT — Details →
4.1.2 27 Sep 2022 none MIT — Details →
4.1.1 27 May 2022 none MIT — Details →
4.1.0 10 May 2022 none MIT — Details →
4.0.7 25 Apr 2022 none MIT — Details →
4.0.6 21 Apr 2022 none MIT — Details →
4.0.5 08 Apr 2022 none MIT — Details →
4.0.4 01 Apr 2022 none MIT — Details →
4.0.3 29 Mar 2022 none MIT — Details →
4.0.2 28 Mar 2022 none MIT — Details →
4.0.1 25 Mar 2022 none MIT — Details →
4.0.0 25 Mar 2022 none MIT — Details →
3.5.1 22 Aug 2020 none MIT — Details →
3.5.0 01 Nov 2019 none MIT — Details →
3.4.2 18 Mar 2019 none MIT — Details →
3.4.1 18 Mar 2019 none MIT — Details →
3.4.0 04 Aug 2018 none MIT — Details →
3.3.2 18 Jun 2018 none MIT — Details →
3.3.1 26 Mar 2018 none MIT — Details →
3.3.0 23 Mar 2018 none MIT — Details →
3.2.1 12 Feb 2018 none MIT — Details →
3.2.0 11 Feb 2018 none MIT — Details →
3.1.1 02 Feb 2018 none MIT — Details →
3.1.0 12 Jan 2018 none MIT — Details →
3.0.2 07 Nov 2017 none MIT — Details →
3.0.1 06 Nov 2017 none MIT — Details →
3.0.1-rc2 06 Nov 2017 none MIT — Details →
3.0.1-rc1 06 Nov 2017 none MIT — Details →
3.0.1-rc0 06 Nov 2017 none MIT — Details →
3.0.0-rc1 29 Oct 2017 none MIT — Details →
3.0.0 14 Oct 2017 none MIT — Details →
3.0.0-rc0 16 Sep 2017 none MIT — Details →
2.8.7 16 Sep 2017 none MIT — Details →
2.8.6 12 Sep 2017 none MIT — Details →
2.8.5 12 Sep 2017 none MIT — Details →
2.8.4 08 Sep 2017 none MIT — Details →
2.8.3 06 Sep 2017 none MIT — Details →
2.8.3-rc-01 06 Sep 2017 none MIT — Details →
2.8.2 12 Aug 2017 none MIT — Details →
2.8.1 05 Aug 2017 none MIT — Details →
2.8.0 04 Aug 2017 none MIT — Details →
1.2.0 25 Jul 2017 none MIT — Details →
2.7.2 22 Jul 2017 none MIT — Details →
2.7.1 05 Jul 2017 none MIT — Details →
2.7.0 04 Jul 2017 none MIT — Details →
2.6.5 10 Jun 2017 none MIT — Details →
2.6.4 04 Jun 2017 none MIT — Details →
2.6.3 14 May 2017 none MIT — Details →
2.6.2 29 Apr 2017 none MIT — Details →
2.6.1 21 Apr 2017 none MIT — Details →
2.6.0 09 Apr 2017 none MIT — Details →
2.6.0-rc1 05 Apr 2017 none MIT — Details →
2.5.7-rc3 05 Apr 2017 none MIT — Details →
2.5.7-rc2 05 Apr 2017 none MIT — Details →
2.5.7-rc1 05 Apr 2017 none MIT — Details →
2.5.6 29 Mar 2017 none MIT — Details →
2.5.5 24 Mar 2017 none MIT — Details →
2.5.4 19 Mar 2017 none MIT — Details →
2.5.3 17 Mar 2017 none MIT — Details →
2.5.2 14 Mar 2017 none MIT — Details →
2.5.1 11 Mar 2017 none MIT — Details →
2.5.0 08 Mar 2017 none MIT — Details →
2.4.1 04 Mar 2017 none MIT — Details →
2.4.0 03 Mar 2017 none MIT — Details →
2.3.9 01 Mar 2017 none MIT — Details →
2.3.9-rc1 01 Mar 2017 none MIT — Details →
2.3.8 01 Mar 2017 none MIT — Details →
1.1.5 23 Feb 2017 none MIT — Details →
2.3.7 22 Feb 2017 none MIT — Details →
2.3.6 22 Feb 2017 none MIT — Details →
1.1.4 22 Feb 2017 none MIT — Details →
2.3.5 14 Feb 2017 none MIT — Details →
2.3.4 11 Feb 2017 none MIT — Details →
2.3.3 19 Jan 2017 none MIT — Details →
2.3.2 23 Dec 2016 none MIT — Details →
2.3.1 20 Dec 2016 none MIT — Details →
2.3.0 17 Dec 2016 none MIT — Details →
2.2.1 07 Dec 2016 none MIT — Details →
2.2.0 24 Oct 2016 none MIT — Details →
2.1.1 02 Oct 2016 none MIT — Details →
2.1.0 23 Sep 2016 none MIT — Details →
1.1.3 08 Sep 2016 none MIT — Details →
1.1.2 07 Sep 2016 none MIT — Details →
2.0.0-alpha 23 Aug 2016 none MIT — Details →
1.1.1 23 Aug 2016 none MIT — Details →
1.1.0 21 Aug 2016 none MIT — Details →
1.0.3 20 Aug 2016 none MIT — Details →
1.0.2 27 Jul 2016 none MIT — Details →
1.0.1 27 Jul 2016 none MIT — Details →

All 97 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 vue-chartjs

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 vue-chartjs

Is vue-chartjs safe to use?

Vulert has no vulnerabilities on record for vue-chartjs 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 vue-chartjs's Vulert package health score?

Vulert scores vue-chartjs 83/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 vue-chartjs affected?

No. 5.3.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 vue-chartjs should I use?

5.3.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 vue-chartjs have?

0 vulnerabilities are recorded for vue-chartjs 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 vue-chartjs vulnerabilities disclosed?

0 vulnerabilities were recorded for vue-chartjs 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 vue-chartjs 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 vue-chartjs for upcoming vulnerabilities?

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