VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/cortexproject/promqlsmith: vulnerability history, versions and safety

github.com/cortexproject/promqlsmith 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/cortexproject/promqlsmith vulnerabilities

Vulert verdict on github.com/cortexproject/promqlsmith v0.0.0-20260205231645-0c8ef5fe46a5 i

Updated on 23 Oct 2026

Good news: v0.0.0-20260205231645-0c8ef5fe46a5, the version you would install today, has no known vulnerabilities.

Package health score 61/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v0.0.0-20260205231645-0c8ef5fe46a5 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 26 i
  • OpenSSF scorecard 2/10 i
  • Last release 8 months 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/cortexproject/promqlsmith, 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.0.0-20260205231645-0c8ef5fe46a5 05 Feb 2026 none Apache-2.0 — Details →
v0.0.0-20260205231119-f68541bd7dec 05 Feb 2026 none Apache-2.0 — Details →
v0.0.0-20260205182022-60fd1dcb0bd6 05 Feb 2026 none Apache-2.0 — Details →
v0.0.0-20260112040928-fee8fda7878f 12 Jan 2026 none Apache-2.0 — Details →
v0.0.0-20251018201159-9e00e5e62e4e 18 Oct 2025 none Apache-2.0 — Details →
v0.0.0-20250908165950-c3fd3c65d5c0 08 Sep 2025 none Apache-2.0 — Details →
v0.0.0-20250908105632-17eec607c197 08 Sep 2025 none Apache-2.0 — Details →
v0.0.0-20250429034839-226ab9cf9540 29 Apr 2025 none Apache-2.0 — Details →
v0.0.0-20250407233056-90db95b1a4e4 07 Apr 2025 none Apache-2.0 — Details →
v0.0.0-20250407205744-8bc5b55c0d72 07 Apr 2025 none Apache-2.0 — Details →
v0.0.0-20250407204419-5f8a059de666 07 Apr 2025 none Apache-2.0 — Details →
v0.0.0-20250407204041-c736b838915e 07 Apr 2025 none Apache-2.0 — Details →
v0.0.0-20250406214856-556ca9cd0f67 06 Apr 2025 none Apache-2.0 — Details →
v0.0.0-20250406190632-c16c3d990498 06 Apr 2025 none Apache-2.0 — Details →
v0.0.0-20250224040643-e3c90a69ff25 24 Feb 2025 none Apache-2.0 — Details →
v0.0.0-20250203072244-cbb5738d00ca 03 Feb 2025 none Apache-2.0 — Details →
v0.0.0-20250129215125-22983b251c24 29 Jan 2025 none Apache-2.0 — Details →
v0.0.0-20250129175729-d6c7c7d13939 29 Jan 2025 none Apache-2.0 — Details →
v0.0.0-20250128002239-eaf3e57157fc 28 Jan 2025 none Apache-2.0 — Details →
v0.0.0-20241219110256-498ae9753f09 19 Dec 2024 none Apache-2.0 — Details →
v0.0.0-20241121054008-8b48fe2471ef 21 Nov 2024 none Apache-2.0 — Details →
v0.0.0-20241120173434-efd461891c44 20 Nov 2024 none Apache-2.0 — Details →
v0.0.0-20241113181952-0722cc7c327b 13 Nov 2024 none Apache-2.0 — Details →
v0.0.0-20241106014657-228f5f435934 06 Nov 2024 none Apache-2.0 — Details →
v0.0.0-20241102030034-4051538fd914 02 Nov 2024 none Apache-2.0 — Details →
v0.0.0-20241102011519-39de2f933ef8 02 Nov 2024 none Apache-2.0 — Details →
v0.0.0-20241102003554-29c8eef2073e 02 Nov 2024 none Apache-2.0 — Details →
v0.0.0-20241101182713-3eec5725bc3f 01 Nov 2024 none Apache-2.0 — Details →
v0.0.0-20241101181823-b43dfdbd01d5 01 Nov 2024 none Apache-2.0 — Details →
v0.0.0-20241101165752-80a16983236c 01 Nov 2024 none Apache-2.0 — Details →
v0.0.0-20241101164856-c2b20ddee51e 01 Nov 2024 none Apache-2.0 — Details →
v0.0.0-20241101164428-75c371281652 01 Nov 2024 none Apache-2.0 — Details →
v0.0.0-20241101163142-dec82f2b8773 01 Nov 2024 none Apache-2.0 — Details →
v0.0.0-20240506042652-6cfdd9739a5e 06 May 2024 none Apache-2.0 — Details →
v0.0.0-20240328172224-5e341f0dd08e 28 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240328171741-a5ecbe9fac40 28 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240326071418-c2a9ca1e89f5 26 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240326031350-93acb2043c50 26 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240326030618-19b271be3213 26 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240326030459-a9ee5896e60a 26 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240325050115-fa1791482477 25 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240226050334-c2974f2f8229 26 Feb 2024 none Apache-2.0 — Details →
v0.0.0-20240115062247-9ed0dfba956d 15 Jan 2024 none Apache-2.0 — Details →
v0.0.0-20240103062231-e3aada49136f 03 Jan 2024 none Apache-2.0 — Details →
v0.0.0-20240103061808-a41d40064e92 03 Jan 2024 none Apache-2.0 — Details →
v0.0.0-20240103061017-b27b4ede77f3 03 Jan 2024 none Apache-2.0 — Details →
v0.0.0-20240103055747-0113d96d04b2 03 Jan 2024 none Apache-2.0 — Details →
v0.0.0-20231230030557-5923fd949fbd 30 Dec 2023 none Apache-2.0 — Details →
v0.0.0-20231230024811-b717f2a39a59 30 Dec 2023 none Apache-2.0 — Details →
v0.0.0-20231206201345-a7d143cf5966 06 Dec 2023 none Apache-2.0 — Details →
v0.0.0-20231120073647-0d99c831ff65 20 Nov 2023 none Apache-2.0 — Details →
v0.0.0-20231030070427-e6df839a5eb8 30 Oct 2023 none Apache-2.0 — Details →
v0.0.0-20231023052626-a46ec7542710 23 Oct 2023 none Apache-2.0 — Details →
v0.0.0-20230923180813-bbada50da584 23 Sep 2023 none Apache-2.0 — Details →
v0.0.0-20230923180757-e5f5c89764c7 23 Sep 2023 none Apache-2.0 — Details →
v0.0.0-20230821043140-bf5cdd6c263b 21 Aug 2023 none Apache-2.0 — Details →
v0.0.0-20230731045656-f1242c30f1d7 31 Jul 2023 none Apache-2.0 — Details →
v0.0.0-20230611071142-d9d833b6dc19 11 Jun 2023 none Apache-2.0 — Details →
v0.0.0-20230524045331-d51b0009b84e 24 May 2023 none Apache-2.0 — Details →
v0.0.0-20230508060500-2c71e20d924a 08 May 2023 none Apache-2.0 — Details →
v0.0.0-20230502194647-ed3e43bb7a52 02 May 2023 none Apache-2.0 — Details →
v0.0.0-20230502181235-a8301e43097e 02 May 2023 none Apache-2.0 — Details →
v0.0.0-20230428202307-d5d38dee2020 28 Apr 2023 none Apache-2.0 — Details →
v0.0.0-20230428200707-1a4b3efa4a8d 28 Apr 2023 none Apache-2.0 — Details →
v0.0.0-20230421071515-a6cbb90f0f71 21 Apr 2023 none Apache-2.0 — Details →
v0.0.0-20230417195454-2ec06f458a43 17 Apr 2023 none Apache-2.0 — Details →
v0.0.0-20230416202834-baacdf2e29b1 16 Apr 2023 none Apache-2.0 — Details →
v0.0.0-20230416181840-5762d00a9fcf 16 Apr 2023 none Apache-2.0 — Details →
v0.0.0-20230416093316-773a93c5f63e 16 Apr 2023 none Apache-2.0 — Details →
v0.0.0-20230416073844-bea541c846e3 16 Apr 2023 none Apache-2.0 — Details →
v0.0.0-20230405072254-5d54b4bd487c 05 Apr 2023 none Apache-2.0 — Details →
v0.0.0-20230327061855-47fa3c81f05c 27 Mar 2023 none Apache-2.0 — Details →
v0.0.0-20230327061836-3c222c1110aa 27 Mar 2023 none Apache-2.0 — Details →
v0.0.0-20230313010502-5c380a3b00b0 13 Mar 2023 none Apache-2.0 — Details →
v0.0.0-20230313010308-18faaf2aa393 13 Mar 2023 none Apache-2.0 — Details →
v0.0.0-20230309031733-1c551fa10a5c 09 Mar 2023 none Apache-2.0 — Details →
v0.0.0-20230309031418-9a965091a753 09 Mar 2023 none Apache-2.0 — Details →
v0.0.0-20230309031332-f3aa03b3f808 09 Mar 2023 none Apache-2.0 — Details →
v0.0.0-20230309023236-9868c9b86b5f 09 Mar 2023 none Apache-2.0 — Details →
v0.0.0-20230308221904-4e059e90ddfd 08 Mar 2023 none Apache-2.0 — Details →
v0.0.0-20230308200014-f02b93b755ee 08 Mar 2023 none Apache-2.0 — Details →
v0.0.0-20230308020938-9441296b32b6 08 Mar 2023 none Apache-2.0 — Details →
v0.0.0-20230307171503-1c8ca7c3fc8c 07 Mar 2023 none Apache-2.0 — Details →
v0.0.0-20230307035854-4e107dd6ab63 07 Mar 2023 none Apache-2.0 — Details →

All 84 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/cortexproject/promqlsmith

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/cortexproject/promqlsmith

Is github.com/cortexproject/promqlsmith safe to use?

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

Vulert scores github.com/cortexproject/promqlsmith 61/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/cortexproject/promqlsmith affected?

No. v0.0.0-20260205231645-0c8ef5fe46a5, 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/cortexproject/promqlsmith should I use?

v0.0.0-20260205231645-0c8ef5fe46a5 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/cortexproject/promqlsmith have?

0 vulnerabilities are recorded for github.com/cortexproject/promqlsmith 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/cortexproject/promqlsmith vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/cortexproject/promqlsmith 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/cortexproject/promqlsmith 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/cortexproject/promqlsmith for upcoming vulnerabilities?

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