VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/ipfs/go-metrics-prometheus: vulnerability history, versions and safety

github.com/ipfs/go-metrics-prometheus 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/ipfs/go-metrics-prometheus vulnerabilities

Vulert verdict on github.com/ipfs/go-metrics-prometheus v0.1.0 i

Updated on 23 Oct 2026

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

Package health score 58/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v0.1.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 9 i
  • OpenSSF scorecard 3/10 i
  • Last release 20 months ago i
  • Licence MIT 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/ipfs/go-metrics-prometheus, 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.1.1-0.20260222154742-f156d946f5be 22 Feb 2026 none MIT — Details →
v0.1.1-0.20250821073250-36a184fce70b 21 Aug 2025 none MIT — Details →
v0.1.1-0.20250328130830-0f3199b28c73 28 Mar 2025 none MIT — Details →
v0.1.0 19 Feb 2025 none MIT — Details →
v0.0.4-0.20250216200242-8a2514d49594 16 Feb 2025 none MIT — Details →
v0.0.3 11 Oct 2024 none MIT — Details →
v0.0.3-0.20241011195806-903b4df4aca0 11 Oct 2024 none MIT — Details →
v0.0.3-0.20240826102723-8304a9d09139 26 Aug 2024 none MIT — Details →
v0.0.3-0.20240322071826-89cf81dd7d92 22 Mar 2024 none MIT — Details →
v0.0.3-0.20240314112657-99025fa2dcae 14 Mar 2024 none MIT — Details →
v0.0.3-0.20240131173431-6b42aaa644ae 31 Jan 2024 none MIT — Details →
v0.0.3-0.20230814133703-4ac96c9acc93 14 Aug 2023 none MIT — Details →
v0.0.3-0.20230814062135-6b8a6ee55f5f 14 Aug 2023 none MIT — Details →
v0.0.3-0.20230628085125-1b7e9b5425bf 28 Jun 2023 none MIT — Details →
v0.0.3-0.20230614111258-b924938e6e8e 14 Jun 2023 none MIT — Details →
v0.0.3-0.20230208150305-d3cc37bd486a 08 Feb 2023 none MIT — Details →
v0.0.3-0.20210818121700-107f5b49c70d 18 Aug 2021 none MIT — Details →
v0.0.3-0.20210601174311-142a4d7c8714 01 Jun 2021 none MIT — Details →
v0.0.3-0.20210423210507-5821ebc561cf 23 Apr 2021 none MIT — Details →
v0.0.3-0.20200504100440-8ab43ee91e01 04 May 2020 none MIT — Details →
v0.0.2 20 Mar 2019 none MIT — Details →
v0.0.2-0.20190302165955-aa46d2b7b1e3 02 Mar 2019 none MIT — Details →
v0.0.1 02 Mar 2019 none MIT — Details →
v0.0.0-20190218150412-12f9c60d4ed5 18 Feb 2019 none MIT — Details →
v0.0.0-20181102235149-2384ea0bb991 02 Nov 2018 none MIT — Details →
v0.0.0-20181030222517-63f2f089f305 30 Oct 2018 none MIT — Details →
v0.0.0-20180924121125-ab7df2ea1dfa 24 Sep 2018 none MIT — Details →
v0.0.0-20180809015044-b90bf8f27b88 09 Aug 2018 none MIT — Details →
v0.0.0-20180723184715-ee70188439f0 23 Jul 2018 none MIT — Details →
v0.0.0-20180626002303-2cc5d2c6c94c 26 Jun 2018 none MIT — Details →
v0.0.0-20180609053108-7dbd5a9c7178 09 Jun 2018 none MIT — Details →
v0.0.0-20180609032540-ada5d9827d67 09 Jun 2018 none MIT — Details →
v0.0.0-20180504042319-893fcbb8519f 04 May 2018 none MIT — Details →
v0.0.0-20180201025416-43ce3046b14f 01 Feb 2018 none MIT — Details →
v0.0.0-20170203034342-c3c0ab135967 03 Feb 2017 none MIT — Details →
v0.0.0-20160912172530-c91071975f47 12 Sep 2016 none MIT — Details →
v0.0.0-20160912171537-9b94afb1e1a6 12 Sep 2016 none MIT — Details →
v0.0.0-20160907161135-874213d5663f 07 Sep 2016 none MIT — Details →
v0.0.0-20160905154504-b6e31ba477bc 05 Sep 2016 none MIT — Details →
v0.0.0-20160902185002-8dfc00a7c03f 02 Sep 2016 none MIT — Details →

All 40 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/ipfs/go-metrics-prometheus

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/ipfs/go-metrics-prometheus

Is github.com/ipfs/go-metrics-prometheus safe to use?

Vulert has no vulnerabilities on record for github.com/ipfs/go-metrics-prometheus 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/ipfs/go-metrics-prometheus's Vulert package health score?

Vulert scores github.com/ipfs/go-metrics-prometheus 58/100, which reads as usable, but worth attention. 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/ipfs/go-metrics-prometheus affected?

No. v0.1.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/ipfs/go-metrics-prometheus should I use?

v0.1.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/ipfs/go-metrics-prometheus have?

0 vulnerabilities are recorded for github.com/ipfs/go-metrics-prometheus 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/ipfs/go-metrics-prometheus vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/ipfs/go-metrics-prometheus 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/ipfs/go-metrics-prometheus 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/ipfs/go-metrics-prometheus for upcoming vulnerabilities?

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