Vulnerability Database · Go · Package report
github.com/prometheus/sigv4: vulnerability history, versions and safety
github.com/prometheus/sigv4 is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on github.com/prometheus/sigv4 v0.5.0 i
Updated on 23 Oct 2026
Good news: v0.5.0, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Sustainable
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.5.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.5.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.5.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 8 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/prometheus/sigv4, 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.
- v0.5.1-0.20261010064017-cc95fc177bf5 10 Oct 2026
- v0.5.0 31 Aug 2026
- v0.4.2-0.20260719095153-c9421d0fd5fe 19 Jul 2026
- v0.4.2-0.20260624113153-4a2ffe4bb8e3 24 Jun 2026
- v0.4.1 02 Feb 2026
- v0.4.0 06 Jan 2026
- v0.3.0 03 Nov 2025
- v0.2.2-0.20250802084208-fd9fd9a3b8ce 02 Aug 2025
- v0.2.1 12 Jul 2025
- v0.2.1-0.20250712074842-d1e42b58d9cc 12 Jul 2025
- v0.2.1-0.20250710210034-18deb24018c2 10 Jul 2025
- v0.2.0 26 May 2025
- v0.1.3-0.20250521220506-8619290c6404 21 May 2025
- v0.1.3-0.20250505073009-b79095b55204 05 May 2025
- v0.1.3-0.20250423182721-3a2c9c752c68 23 Apr 2025
- v0.1.3-0.20250323085508-4cc0fcc9d120 23 Mar 2025
- v0.1.3-0.20250322174910-3a6e3b2abe96 22 Mar 2025
- v0.1.3-0.20250308140205-2afd4b357402 08 Mar 2025
- v0.1.3-0.20250209081715-fe55cf24565c 09 Feb 2025
- v0.1.2 01 Feb 2025
- v0.1.2-0.20250103125903-84677e62ea45 03 Jan 2025
- v0.1.1 01 Jan 2025
- v0.1.1-0.20241112182407-6254fee40f16 12 Nov 2024
- v0.1.1-0.20241106175423-3d350b20aa21 06 Nov 2024
- v0.0.0-20241106104255-cb2777f39a7b 06 Nov 2024
- v0.1.0 06 Nov 2024
- v0.0.0-20241106103000-350117d76a74 06 Nov 2024
- v0.0.0-20241106090304-492a24d9953f 06 Nov 2024
- v0.0.0-20241031141919-1cd0af0151ff 31 Oct 2024
All 29 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/prometheus/sigv4
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
Questions
About github.com/prometheus/sigv4
Is github.com/prometheus/sigv4 safe to use?
Vulert has no vulnerabilities on record for github.com/prometheus/sigv4 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/prometheus/sigv4's Vulert package health score?
Vulert scores github.com/prometheus/sigv4 74/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/prometheus/sigv4 affected?
No. v0.5.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/prometheus/sigv4 should I use?
v0.5.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/prometheus/sigv4 have?
0 vulnerabilities are recorded for github.com/prometheus/sigv4 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/prometheus/sigv4 vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/prometheus/sigv4 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/prometheus/sigv4 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/prometheus/sigv4 for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/prometheus/sigv4 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.