VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

nuxt-component-meta: vulnerability history, versions and safety

nuxt-component-meta 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 nuxt-component-meta vulnerabilities

Vulert verdict on nuxt-component-meta 0.19.0 i

Updated on 23 Oct 2026

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

Package health score 85/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

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

  • Current release 0.19.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 1 packages 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 nuxt-component-meta, 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
0.19.0 15 Oct 2026 none MIT — Details →
0.18.0 13 Jul 2026 none MIT — Details →
0.17.2 09 Feb 2026 none MIT — Details →
0.17.1 15 Jan 2026 none MIT — Details →
0.17.0 15 Jan 2026 none MIT — Details →
0.16.0 23 Dec 2025 none MIT — Details →
0.15.0 27 Nov 2025 none MIT — Details →
0.14.2 13 Nov 2025 none MIT — Details →
0.14.1 17 Oct 2025 none MIT — Details →
0.14.0 10 Sep 2025 none MIT — Details →
0.13.1 05 Aug 2025 none MIT — Details →
0.13.0 23 Jul 2025 none MIT — Details →
0.12.2 23 Jul 2025 none MIT — Details →
0.12.1 02 Jul 2025 none MIT — Details →
0.12.0 27 Jun 2025 none MIT — Details →
0.11.0 23 Apr 2025 none MIT — Details →
0.10.1 25 Mar 2025 none MIT — Details →
0.10.0 14 Jan 2025 none MIT — Details →
0.9.1-20241029-123556-a6efba4 29 Oct 2024 none MIT — Details →
0.9.0 29 Oct 2024 none MIT — Details →
0.8.3-1726151818.e892375 12 Sep 2024 none MIT — Details →
0.8.2 12 Sep 2024 none MIT — Details →
0.8.2-1726151556.98e9719 12 Sep 2024 none MIT — Details →
0.8.2-1726056992.3c67692 11 Sep 2024 none MIT — Details →
0.8.1 11 Sep 2024 none MIT — Details →
0.8.1-1726053684.40aea05 11 Sep 2024 none MIT — Details →
0.8.1-1725971445.db7943a 10 Sep 2024 none MIT — Details →
0.8.1-1725964378.09a96cd 10 Sep 2024 none MIT — Details →
0.8.1-1725882515.1390217 09 Sep 2024 none MIT — Details →
0.8.0 09 Sep 2024 none MIT — Details →
0.7.1-1725881601.4e27090 09 Sep 2024 none MIT — Details →
0.7.1-1720190199.72b989c 05 Jul 2024 none MIT — Details →
0.7.1-1719592296.6a83bc2 28 Jun 2024 none MIT — Details →
0.7.0 28 Jun 2024 none MIT — Details →
0.6.7-1719591232.3728d72 28 Jun 2024 none MIT — Details →
0.6.7-1719573287.10ad753 28 Jun 2024 none MIT — Details →
0.6.6 28 Jun 2024 none MIT — Details →
0.6.6-1718891962.c0dd84e 20 Jun 2024 none MIT — Details →
0.6.5 20 Jun 2024 none MIT — Details →
0.6.5-1718891509.44bbdf6 20 Jun 2024 none MIT — Details →
0.6.5-1714736465.f544d51 03 May 2024 none MIT — Details →
0.6.4 03 May 2024 none MIT — Details →
0.6.4-1714733914.5b8f450 03 May 2024 none MIT — Details →
0.6.4-1705570419.f5e4201 18 Jan 2024 none MIT — Details →
0.6.3 18 Jan 2024 none MIT — Details →
0.6.3-1705512489.84c11e8 17 Jan 2024 none MIT — Details →
0.6.2 17 Jan 2024 none MIT — Details →
0.6.2-1705510883.8435f4c 17 Jan 2024 none MIT — Details →
0.6.2-1705507037.22b307b 17 Jan 2024 none MIT — Details →
0.6.2-1705506407.22b307b 17 Jan 2024 none MIT — Details →
0.6.2-1705505083.bacda79 17 Jan 2024 none MIT — Details →
0.6.2-1705504819.032ff4a 17 Jan 2024 none MIT — Details →
0.6.2-1704910015.1a173aa 10 Jan 2024 none MIT — Details →
0.6.2-1704809475.d440d97 09 Jan 2024 none MIT — Details →
0.6.2-1704809206.d4171c2 09 Jan 2024 none MIT — Details →
0.6.1 09 Jan 2024 none MIT — Details →
0.6.0 05 Dec 2023 none MIT — Details →
0.5.4 15 Sep 2023 none MIT — Details →
0.5.3 26 May 2023 none MIT — Details →
0.5.2 20 May 2023 none MIT — Details →
0.5.1 21 Mar 2023 none MIT — Details →
0.5.0 21 Mar 2023 none MIT — Details →
0.4.3 06 Jan 2023 none MIT — Details →
0.4.2 29 Dec 2022 none MIT — Details →
0.4.1 21 Dec 2022 none MIT — Details →
0.4.0 21 Dec 2022 none MIT — Details →
0.3.8 06 Dec 2022 none MIT — Details →
0.3.7 06 Dec 2022 none MIT — Details →
0.3.6 06 Dec 2022 none MIT — Details →
0.3.5 27 Nov 2022 none MIT — Details →
0.3.4 16 Nov 2022 none MIT — Details →
0.3.3 01 Nov 2022 none MIT — Details →
0.2.3 20 Sep 2022 none MIT — Details →
0.3.2 18 Sep 2022 none MIT — Details →
0.3.1 18 Sep 2022 none MIT — Details →
0.3.0 17 Sep 2022 none MIT — Details →
0.2.2 31 Aug 2022 none MIT — Details →
0.2.1 29 Aug 2022 none MIT — Details →
0.2.0 29 Aug 2022 none MIT — Details →
0.1.9 21 Jul 2022 none MIT — Details →
0.1.8 20 Jul 2022 none MIT — Details →
0.1.7 19 Jul 2022 none MIT — Details →
0.1.6 19 Jul 2022 none MIT — Details →
0.1.5 11 May 2022 none MIT — Details →
0.1.4 06 May 2022 none MIT — Details →
0.1.3 04 May 2022 none MIT — Details →
0.1.2 19 Apr 2022 none MIT — Details →
0.1.0 15 Apr 2022 none MIT — Details →
0.0.7 22 Nov 2021 none MIT — Details →
0.0.6 22 Nov 2021 none MIT — Details →
0.0.5 16 Nov 2021 none MIT — Details →
0.0.4 09 Nov 2021 none MIT — Details →
0.0.3 13 Oct 2021 none MIT — Details →
0.0.2 13 Oct 2021 none MIT — Details →
0.0.1 13 Oct 2021 none MIT — Details →

All 95 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 nuxt-component-meta

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 nuxt-component-meta

Is nuxt-component-meta safe to use?

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

Vulert scores nuxt-component-meta 85/100, which reads as healthy. 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 nuxt-component-meta affected?

No. 0.19.0, 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 nuxt-component-meta have?

0 vulnerabilities are recorded for nuxt-component-meta 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 nuxt-component-meta vulnerabilities disclosed?

0 vulnerabilities were recorded for nuxt-component-meta 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 nuxt-component-meta 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 nuxt-component-meta for upcoming vulnerabilities?

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