VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/grafana/jfr-parser: vulnerability history, versions and safety

github.com/grafana/jfr-parser is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go 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 github.com/grafana/jfr-parser vulnerabilities

Vulert verdict on github.com/grafana/jfr-parser v0.19.0 i

Updated on 23 Oct 2026

Good news: v0.19.0, 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 Moderate

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

  • Current release v0.19.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 49 i
  • OpenSSF scorecard 7/10 i
  • Last release 1 month ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the Go module proxy, 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 github.com/grafana/jfr-parser, 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
v0.19.0 09 Sep 2026 none Apache-2.0 — Details →
v0.18.0 15 Jul 2026 none Apache-2.0 — Details →
v0.17.2-0.20260606002545-06dc1978b00f 06 Jun 2026 none Apache-2.0 — Details →
v0.17.1 01 Jun 2026 none Apache-2.0 — Details →
v0.17.0 12 May 2026 none Apache-2.0 — Details →
v0.16.0 31 Mar 2026 none Apache-2.0 — Details →
v0.15.0 05 Mar 2026 none Apache-2.0 — Details →
v0.14.1-0.20260301191208-97bb5dab4194 01 Mar 2026 none Apache-2.0 — Details →
v0.14.0 20 Feb 2026 none Apache-2.0 — Details →
v0.13.0 08 Feb 2026 none Apache-2.0 — Details →
v0.12.1-0.20251021032336-7d0e6b262614 21 Oct 2025 none Apache-2.0 — Details →
v0.12.0 03 Oct 2025 none Apache-2.0 — Details →
v0.0.0-20250819085511-b2de37b047ee 19 Aug 2025 none Apache-2.0 — Details →
v0.11.1-0.20250819085511-b2de37b047ee 19 Aug 2025 none Apache-2.0 — Details →
v0.11.1-0.20250810075107-4d620535ba07 10 Aug 2025 none Apache-2.0 — Details →
v0.11.0 29 Jul 2025 none Apache-2.0 — Details →
v0.10.1-0.20250728051010-0526d18d1def 28 Jul 2025 none Apache-2.0 — Details →
v0.10.1-0.20250728044356-169b50489e6f 28 Jul 2025 none Apache-2.0 — Details →
v0.10.1-0.20250728035107-f1ab7c8c25f5 28 Jul 2025 none Apache-2.0 — Details →
v0.10.1-0.20250430094214-82e372d2c34b 30 Apr 2025 none Apache-2.0 — Details →
v0.10.1-0.20250411002907-c08c42b153e1 11 Apr 2025 none Apache-2.0 — Details →
v0.10.0 11 Apr 2025 none Apache-2.0 — Details →
v0.9.4-0.20250410080713-8cde6cbfa5bb 10 Apr 2025 none Apache-2.0 — Details →
v0.9.4-0.20250304020700-557a6bd35a2d 04 Mar 2025 none Apache-2.0 — Details →
v0.9.3 04 Mar 2025 none Apache-2.0 — Details →
v0.9.3-0.20250120092754-1ec78d48f07e 20 Jan 2025 none Apache-2.0 — Details →
v0.9.2 16 Oct 2024 none Apache-2.0 — Details →
v0.9.2-0.20241016061537-a8d22a1cd731 16 Oct 2024 none Apache-2.0 — Details →
v0.9.2-0.20240909142717-1987b3f3c91a 09 Sep 2024 none Apache-2.0 — Details →
v0.9.2-0.20240909083122-4fda3b3ed66b 09 Sep 2024 none Apache-2.0 — Details →
v0.9.1-0.20240906142354-c7aebd80db92 06 Sep 2024 none Apache-2.0 — Details →
v0.9.1 04 Sep 2024 none Apache-2.0 — Details →
v0.9.1-0.20240904075200-365b30328459 04 Sep 2024 none Apache-2.0 — Details →
v0.9.0 04 Sep 2024 none Apache-2.0 — Details →
v0.0.0-20240821021831-cfd6e79a1afc 21 Aug 2024 none Apache-2.0 — Details →
v0.8.1 21 Aug 2024 none Apache-2.0 — Details →
v0.8.1-0.20240821021831-cfd6e79a1afc 21 Aug 2024 none Apache-2.0 — Details →
v0.0.0-20240815065100-4296f63fd6d7 15 Aug 2024 none Apache-2.0 — Details →
v0.8.1-0.20240815065100-4296f63fd6d7 15 Aug 2024 none Apache-2.0 — Details →
v0.0.0-20240428042017-f984a370a654 28 Apr 2024 none Apache-2.0 — Details →
v0.8.1-0.20240428042017-f984a370a654 28 Apr 2024 none Apache-2.0 — Details →
v0.0.0-20240228024232-8abcb81c304c 28 Feb 2024 none Apache-2.0 — Details →
v0.8.1-0.20240228024232-8abcb81c304c 28 Feb 2024 none Apache-2.0 — Details →
v0.0.0-20240126072739-986e71dc0361 26 Jan 2024 none Apache-2.0 — Details →
v0.8.1-0.20240126072739-986e71dc0361 26 Jan 2024 none Apache-2.0 — Details →
v0.8.1-0.20240126042837-a37602764d79 26 Jan 2024 none Apache-2.0 — Details →
v0.8.1-0.20240126035610-2d7477aec93f 26 Jan 2024 none Apache-2.0 — Details →
v0.7.2-0.20240119055449-c8e77257aa11 19 Jan 2024 none Apache-2.0 — Details →
v0.8.0 19 Jan 2024 none Apache-2.0 — Details →
v0.0.0-20240108135448-c7f61c1f689e 08 Jan 2024 none Apache-2.0 — Details →
v0.7.2-0.20240108135448-c7f61c1f689e 08 Jan 2024 none Apache-2.0 — Details →
v0.0.0-20240108100259-6b558fedfb6f 08 Jan 2024 none Apache-2.0 — Details →
v0.7.2-0.20240108100259-6b558fedfb6f 08 Jan 2024 none Apache-2.0 — Details →
v0.7.2-0.20240108092556-b3bccd4e73a9 08 Jan 2024 none Apache-2.0 — Details →
v0.7.2-0.20240108082221-63c3c2cab13a 08 Jan 2024 none Apache-2.0 — Details →
v0.7.2-0.20240108081411-f7685e4606e1 08 Jan 2024 none Apache-2.0 — Details →
v0.7.2-0.20240108080901-93b5eb245c78 08 Jan 2024 none Apache-2.0 — Details →
v0.7.2-0.20240108080141-3fe0ff40bf9e 08 Jan 2024 none Apache-2.0 — Details →
v0.7.2-0.20240108075341-b57b226cf62c 08 Jan 2024 none Apache-2.0 — Details →
v0.7.2-0.20240108073656-53b3866825e5 08 Jan 2024 none Apache-2.0 — Details →
v0.7.2-0.20240108072338-ead9fd85238b 08 Jan 2024 none Apache-2.0 — Details →
v0.0.0-20230831140626-08fa3a941bf8 31 Aug 2023 none Apache-2.0 — Details →
v0.7.2-0.20230831140626-08fa3a941bf8 31 Aug 2023 none Apache-2.0 — Details →
v0.7.2-0.20230831015425-6e62bc9cf4d2 31 Aug 2023 none Apache-2.0 — Details →
v0.7.2-0.20230830113601-c9e553050c48 30 Aug 2023 none Apache-2.0 — Details →
v0.7.2-0.20230830112321-3f0ee07d15a7 30 Aug 2023 none Apache-2.0 — Details →
v0.7.2-0.20230830111733-00e6058e9d68 30 Aug 2023 none Apache-2.0 — Details →

All 67 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 github.com/grafana/jfr-parser

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 github.com/grafana/jfr-parser

Is github.com/grafana/jfr-parser safe to use?

Vulert has no vulnerabilities on record for github.com/grafana/jfr-parser in Go 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 github.com/grafana/jfr-parser's Vulert package health score?

Vulert scores github.com/grafana/jfr-parser 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 github.com/grafana/jfr-parser affected?

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

Which version of github.com/grafana/jfr-parser should I use?

v0.19.0 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 github.com/grafana/jfr-parser have?

0 vulnerabilities are recorded for github.com/grafana/jfr-parser in the Go 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 github.com/grafana/jfr-parser vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/grafana/jfr-parser 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 github.com/grafana/jfr-parser 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 github.com/grafana/jfr-parser for upcoming vulnerabilities?

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