VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@grafana/plugin-ui: vulnerability history, versions and safety

@grafana/plugin-ui 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 @grafana/plugin-ui vulnerabilities

Vulert verdict on @grafana/plugin-ui 0.17.8 i

Updated on 23 Oct 2026

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

Package health score 75/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

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

  • Current release 0.17.8 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 4 packages i
  • Stars 18 i
  • Last release this month i
  • Licence Apache-2.0 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 @grafana/plugin-ui, 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.17.8 13 Oct 2026 none Apache-2.0 — Details →
0.17.6 24 Sep 2026 none Apache-2.0 — Details →
0.17.5 10 Sep 2026 none Apache-2.0 — Details →
0.17.4 17 Aug 2026 none Apache-2.0 — Details →
0.17.3 22 Jul 2026 none Apache-2.0 — Details →
0.17.2 21 Jul 2026 none Apache-2.0 — Details →
0.17.1 16 Jul 2026 none Apache-2.0 — Details →
0.17.0 15 Jul 2026 none Apache-2.0 — Details →
0.16.1 09 Jul 2026 none Apache-2.0 — Details →
0.16.0-dsconfig.a155abe 08 Jul 2026 none Apache-2.0 — Details →
0.16.0-dsconfig.d7f2506 08 Jul 2026 none Apache-2.0 — Details →
0.16.0 18 Jun 2026 none Apache-2.0 — Details →
0.15.1 16 Jun 2026 none Apache-2.0 — Details →
0.15.0 10 Jun 2026 none Apache-2.0 — Details →
0.14.0 05 Jun 2026 none Apache-2.0 — Details →
0.14.1-dsconfig.032cfc4 28 May 2026 none Apache-2.0 — Details →
0.14.1-dsconfig.f952c80 28 May 2026 none Apache-2.0 — Details →
0.14.1-dsconfig.7535e54 21 May 2026 none Apache-2.0 — Details →
0.14.1-dsconfig.a233348 21 May 2026 none Apache-2.0 — Details →
0.14.1-dsconfig.9143abf 21 May 2026 none Apache-2.0 — Details →
0.14.1-dsconfig.ced809d 20 May 2026 none Apache-2.0 — Details →
0.14.1-dsconfig.4bdebf6 14 May 2026 none — — Details →
0.14.1-dsconfig.0d5c985 14 May 2026 none — — Details →
0.14.1-dsconfig.f7c437a 13 May 2026 none — — Details →
0.14.1-dsconfig.b962e11 13 May 2026 none — — Details →
0.14.1-dsconfig.bccd84e 13 May 2026 none — — Details →
0.14.0-dev.1 13 Mar 2026 none — — Details →
0.13.1 10 Feb 2026 none — — Details →
0.13.0 05 Feb 2026 none — — Details →
0.12.1 05 Jan 2026 none — — Details →
0.12.0 21 Nov 2025 none — — Details →
0.11.1 17 Oct 2025 none — — Details →
0.11.0 16 Oct 2025 none — — Details →
0.10.10 28 Aug 2025 none — — Details →
0.10.9 07 Aug 2025 none — — Details →
0.10.8 05 Aug 2025 none — — Details →
0.10.7 18 Jun 2025 none — — Details →
0.10.6 16 May 2025 none — — Details →
0.10.5 07 Apr 2025 none — — Details →
0.10.4 19 Feb 2025 none — — Details →
0.10.3 04 Feb 2025 none — — Details →
0.10.2 04 Feb 2025 none — — Details →
0.10.1 30 Jan 2025 none — — Details →
0.10.0 30 Jan 2025 none — — Details →
0.9.6 20 Jan 2025 none — — Details →
0.9.5 16 Jan 2025 none — — Details →
0.9.4 18 Dec 2024 none — — Details →
0.9.3 13 Dec 2024 none — — Details →
0.9.2 28 Nov 2024 none — — Details →
0.9.1 25 Nov 2024 none — — Details →
0.9.0 25 Nov 2024 none — — Details →
0.8.0 27 Aug 2024 none — — Details →
0.7.2 09 May 2024 none — — Details →
0.7.1 08 May 2024 none — — Details →
0.7.0 30 Apr 2024 none — — Details →
0.6.3 15 Apr 2024 none — — Details →
0.6.2 02 Feb 2024 none — — Details →
0.6.1 10 Jan 2024 none — — Details →
0.6.0 25 Oct 2023 none — — Details →
0.5.0 24 Oct 2023 none — — Details →
0.4.0 26 Jul 2023 none — — Details →
0.3.8 11 Jul 2023 none — — Details →
0.3.7 11 Jul 2023 none — — Details →
0.3.6 11 Jul 2023 none — — Details →
0.3.5 07 Jul 2023 none — — Details →
0.3.4 16 Jun 2023 none — — Details →
0.3.3 16 Jun 2023 none — — Details →
0.3.1 02 Jun 2023 none — — Details →
0.3.0 01 Jun 2023 none — — Details →
0.2.1 12 May 2023 none — — Details →
0.2.0 12 May 2023 none — — Details →
0.1.17 10 May 2023 none — — Details →
0.1.16 12 Apr 2023 none — — Details →
0.1.15 28 Mar 2023 none — — Details →
0.1.14 27 Mar 2023 none — — Details →
0.1.13 27 Mar 2023 none — — Details →
0.1.12 27 Mar 2023 none — — Details →
0.1.11 17 Oct 2022 none — — Details →
0.1.10 17 Oct 2022 none — — Details →

All 79 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 @grafana/plugin-ui

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 @grafana/plugin-ui

Is @grafana/plugin-ui safe to use?

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

Vulert scores @grafana/plugin-ui 75/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 @grafana/plugin-ui affected?

No. 0.17.8, 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 @grafana/plugin-ui have?

0 vulnerabilities are recorded for @grafana/plugin-ui 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 @grafana/plugin-ui vulnerabilities disclosed?

0 vulnerabilities were recorded for @grafana/plugin-ui 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 @grafana/plugin-ui 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 @grafana/plugin-ui for upcoming vulnerabilities?

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