Vulnerability Database · Go · Package report
github.com/peterhellberg/link: vulnerability history, versions and safety
github.com/peterhellberg/link 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/peterhellberg/link v1.2.0 i
Updated on 23 Oct 2026
Good news: v1.2.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Little adoption
- Community Inactive
What to do: Stay on v1.2.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.2.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.2.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 47 i
- OpenSSF scorecard 3/10 i
- Last release 47 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/peterhellberg/link, 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-20230908120112-34a13d14bf2e 08 Sep 2023
- v1.2.1-0.20230908120112-34a13d14bf2e 08 Sep 2023
- v0.0.0-20221029111645-980077b804b0 29 Oct 2022
- v1.2.0 29 Oct 2022
- v1.1.1 29 Oct 2022
- v1.1.1-0.20221023195223-8ba0eda8e658 23 Oct 2022
- v0.0.0-20220203132150-491171805b8b 03 Feb 2022
- v1.1.1-0.20220203132150-491171805b8b 03 Feb 2022
- v1.1.1-0.20220203131918-396cf0e58c4b 03 Feb 2022
- v0.0.0-20191113174948-7d8125c3085c 13 Nov 2019
- v1.1.0 13 Nov 2019
- v0.0.0-20190124114551-9b91929be50d 24 Jan 2019
- v1.0.1-0.20190124114551-9b91929be50d 24 Jan 2019
- v1.0.1-0.20190124114524-7ce3e68837d1 24 Jan 2019
- v0.0.0-20180124233705-6d32b8d78d1e 24 Jan 2018
- v1.0.1-0.20180124233705-6d32b8d78d1e 24 Jan 2018
- v1.0.1-0.20180124233220-056405bd5ac0 24 Jan 2018
- v1.0.1-0.20171231092049-8768c6d4dc56 31 Dec 2017
- v0.0.0-20170220155451-3eea38ca14b7 20 Feb 2017
- v1.0.1-0.20170220155451-3eea38ca14b7 20 Feb 2017
- v1.0.1-0.20170130154736-24c1495e8c97 30 Jan 2017
- v0.0.0-20160404082645-d1cebc7ea14a 04 Apr 2016
- v1.0.0 04 Apr 2016
- v0.0.0-20151119141522-1053d3b2893e 19 Nov 2015
- v0.0.0-20151117150035-1082c67c1c8c 17 Nov 2015
- v0.0.0-20151108095102-d78293549066 08 Nov 2015
- v0.0.0-20151025161648-571fa63bf346 25 Oct 2015
- v0.0.0-20151024005015-8f0d2d4e989e 24 Oct 2015
- v0.0.0-20151023125628-d16fd7b85a7b 23 Oct 2015
- v0.0.0-20151019154706-d977990c7c55 19 Oct 2015
All 30 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/peterhellberg/link
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/peterhellberg/link
Is github.com/peterhellberg/link safe to use?
Vulert has no vulnerabilities on record for github.com/peterhellberg/link 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/peterhellberg/link's Vulert package health score?
Vulert scores github.com/peterhellberg/link 52/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/peterhellberg/link affected?
No. v1.2.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/peterhellberg/link should I use?
v1.2.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/peterhellberg/link have?
0 vulnerabilities are recorded for github.com/peterhellberg/link 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/peterhellberg/link vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/peterhellberg/link 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/peterhellberg/link 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/peterhellberg/link for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/peterhellberg/link version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.