Vulnerability Database · Go · Package report
github.com/hashicorp/logutils: vulnerability history, versions and safety
github.com/hashicorp/logutils 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/hashicorp/logutils v1.0.0 i
Updated on 23 Oct 2026
Good news: v1.0.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Niche
- Community Quiet
What to do: Stay on v1.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.0.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 371 i
- OpenSSF scorecard 2/10 i
- Last release 97 months ago i
- Licence MPL-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/hashicorp/logutils, 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.0.0-20260123160512-ac8b318eab76 23 Jan 2026
- v1.0.1-0.20260123160512-ac8b318eab76 23 Jan 2026
- v1.0.1-0.20250730155314-0227883d12c3 30 Jul 2025
- v1.0.1-0.20250703095147-aabc2800b07e 03 Jul 2025
- v1.0.1-0.20241126175231-c9a4e4c3d38b 26 Nov 2024
- v1.0.1-0.20230201170046-7c1afd479c96 01 Feb 2023
- v1.0.1-0.20230125174900-127077f645bf 25 Jan 2023
- v1.0.1-0.20221012203117-a37fa1a1bdad 12 Oct 2022
- v1.0.1-0.20191203235416-a1157f7e3c0e 03 Dec 2019
- v0.0.0-20180828161249-a335183dfd07 28 Aug 2018
- v1.0.0 28 Aug 2018
- v0.0.0-20180828155211-28eff7f8aa25 28 Aug 2018
- v0.0.0-20150609070431-0dc08b1671f3 09 Jun 2015
- v0.0.0-20150324060341-367a65d59043 24 Mar 2015
- v0.0.0-20150324060109-393600872c6f 24 Mar 2015
- v0.0.0-20141023011011-23b0af5510a2 23 Oct 2014
- v0.0.0-20131204182759-8e0820fe7ac5 04 Dec 2013
- v0.0.0-20131204180428-455f2d01f846 04 Dec 2013
- v0.0.0-20131010081503-bb1a37c4f09c 10 Oct 2013
- v0.0.0-20131010080117-07cf02b01b39 10 Oct 2013
- v0.0.0-20131009082335-176b71a8dc95 09 Oct 2013
All 21 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/hashicorp/logutils
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/hashicorp/logutils
Is github.com/hashicorp/logutils safe to use?
Vulert has no vulnerabilities on record for github.com/hashicorp/logutils 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/hashicorp/logutils's Vulert package health score?
Vulert scores github.com/hashicorp/logutils 50/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/hashicorp/logutils affected?
No. v1.0.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/hashicorp/logutils should I use?
v1.0.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/hashicorp/logutils have?
0 vulnerabilities are recorded for github.com/hashicorp/logutils 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/hashicorp/logutils vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/hashicorp/logutils 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/hashicorp/logutils 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/hashicorp/logutils for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/hashicorp/logutils version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.