Vulnerability Database · Go · Package report
github.com/terramate-io/hcl/v2: vulnerability history, versions and safety
github.com/terramate-io/hcl/v2 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/terramate-io/hcl/v2 v2.0.0-rc6 i
Updated on 23 Oct 2026
Good news: v2.0.0-rc6, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Slowing
- Popularity Little adoption
- Community Inactive
What to do: Stay on v2.0.0-rc6 or newer. This can change: a vulnerability disclosed tomorrow can affect v2.0.0-rc6 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v2.0.0-rc6 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Last release 25 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/terramate-io/hcl/v2, 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.
- v2.0.0-rc6.0.20250407124131-d8d9af4013e3 07 Apr 2025
- v2.0.0-rc5.0.20240904155846-e1d9cdb8dbc9 04 Sep 2024
- v2.0.0-rc6 04 Sep 2024
- v2.0.0-rc5.0.20240903134035-45940aef5ce3 03 Sep 2024
- v2.0.0-rc5.0.20240903131557-446775544e05 03 Sep 2024
- v2.0.0-rc4.0.20240902115808-0f47cf5974b9 02 Sep 2024
- v2.0.0-rc5 02 Sep 2024
- v2.0.0-rc4 30 Aug 2024
- v2.0.0-rc2.0.20240830090346-c4b87c22ef27 30 Aug 2024
- v2.0.0-rc3 30 Aug 2024
- v2.0.0-rc1.0.20240829182013-a2b4473778cc 29 Aug 2024
- v2.0.0-rc2 29 Aug 2024
- v2.0.0-rc1.0.20240829163431-5a7bd0176d9c 29 Aug 2024
- v2.0.0-rc1.0.20240829161934-a97cb5745ac9 29 Aug 2024
- v2.0.0-20240829151916-b0ec608bb65d 29 Aug 2024
- v2.0.0-rc1 29 Aug 2024
All 16 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/terramate-io/hcl/v2
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/terramate-io/hcl/v2
Is github.com/terramate-io/hcl/v2 safe to use?
Vulert has no vulnerabilities on record for github.com/terramate-io/hcl/v2 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/terramate-io/hcl/v2's Vulert package health score?
Vulert scores github.com/terramate-io/hcl/v2 59/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/terramate-io/hcl/v2 affected?
No. v2.0.0-rc6, 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/terramate-io/hcl/v2 should I use?
v2.0.0-rc6 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/terramate-io/hcl/v2 have?
0 vulnerabilities are recorded for github.com/terramate-io/hcl/v2 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/terramate-io/hcl/v2 vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/terramate-io/hcl/v2 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/terramate-io/hcl/v2 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/terramate-io/hcl/v2 for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/terramate-io/hcl/v2 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.