Vulnerability Database · Go · Package report
github.com/hugelgupf/p9: vulnerability history, versions and safety
github.com/hugelgupf/p9 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/hugelgupf/p9 v0.4.1 i
Updated on 23 Oct 2026
Good news: v0.4.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Niche
- Community Quiet
What to do: Stay on v0.4.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.4.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.4.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 120 i
- OpenSSF scorecard 3/10 i
- Last release 5 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/hugelgupf/p9, 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.4.2-0.20260625151848-3fd948847ea4 25 Jun 2026
- v0.4.2-0.20260625024654-a0d13a00794d 25 Jun 2026
- v0.4.1 15 May 2026
- v0.3.1-0.20260209234446-ba5af0b37df0 09 Feb 2026
- v0.4.0 09 Feb 2026
- v0.0.0-20250420164440-abc96d20b308 20 Apr 2025
- v0.3.1-0.20250420164440-abc96d20b308 20 Apr 2025
- v0.0.0-20240118043522-6f4f11e5296e 18 Jan 2024
- v0.3.1-0.20240118043522-6f4f11e5296e 18 Jan 2024
- v0.3.1-0.20240113225541-2311f485053c 13 Jan 2024
- v0.3.1-0.20231218015705-e7440fbfbaed 18 Dec 2023
- v0.3.1-0.20230822151754-54f5c5530921 22 Aug 2023
- v0.3.0 22 Aug 2023
- v0.2.1-0.20230821144744-218df7a62bb9 21 Aug 2023
- v0.2.1-0.20230821130946-0c790987eb44 21 Aug 2023
- v0.2.1-0.20230814004337-e6037077d6dc 14 Aug 2023
- v0.2.1-0.20230813061204-660eb2337e3c 13 Aug 2023
- v0.2.1-0.20230809172052-8313e2fcf87d 09 Aug 2023
- v0.2.1-0.20230803231326-7b9704081cf5 03 Aug 2023
- v0.2.1-0.20230102222142-5cb68b4d03bb 02 Jan 2023
- v0.2.1-0.20221222075609-78606c499424 22 Dec 2022
- v0.2.1-0.20221218082413-2951c9b03c58 18 Dec 2022
- v0.2.1-0.20221218082413-34688015b55a 18 Dec 2022
- v0.2.1-0.20220127205516-ede3efe35943 27 Jan 2022
- v0.2.1-0.20220127042022-01d3b35d2381 27 Jan 2022
- v0.1.1-0.20210528120703-cc05b77b314b 28 May 2021
- v0.2.0 28 May 2021
- v0.0.0-20200813040537-7cc848b3cdfd 13 Aug 2020
- v0.1.0 13 Aug 2020
- v0.0.0-20200728071702-98ef6e0b2889 28 Jul 2020
- v0.0.0-20200723185606-616ec381eec3 23 Jul 2020
- v0.0.0-20200719194532-7cee1f927616 19 Jul 2020
- v0.0.0-20200719194532-8d527d2b0d17 19 Jul 2020
- v0.0.0-20200707092319-ecc83b974f0f 07 Jul 2020
- v0.0.0-20200521075819-5bab8bc5f59f 21 May 2020
- v0.0.0-20200124185850-99779e29a270 24 Jan 2020
- v0.0.0-20200121012303-215c1b152a8b 21 Jan 2020
- v0.0.0-20200121012303-8cbb99146038 21 Jan 2020
- v0.0.0-20200121012303-e521180b4735 21 Jan 2020
- v0.0.0-20200119212354-04be54a0c1f6 19 Jan 2020
- v0.0.0-20200119194214-157d75718261 19 Jan 2020
- v0.0.0-20200119193954-71d87f9a9ea8 19 Jan 2020
- v0.0.0-20191116210530-ede262f409e3 16 Nov 2019
- v0.0.0-20190923080529-a5e7bac5e555 23 Sep 2019
- v0.0.0-20190902012917-f08d8f7f979b 02 Sep 2019
- v0.0.0-20190806022330-7ba0920fba11 06 Aug 2019
- v0.0.0-20190730163255-e22b6295de2a 30 Jul 2019
- v0.0.0-20190730070042-01e3b5ba6bd4 30 Jul 2019
- v0.0.0-20190730034503-1942fd50d252 30 Jul 2019
All 49 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/hugelgupf/p9
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/hugelgupf/p9
Is github.com/hugelgupf/p9 safe to use?
Vulert has no vulnerabilities on record for github.com/hugelgupf/p9 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/hugelgupf/p9's Vulert package health score?
Vulert scores github.com/hugelgupf/p9 70/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/hugelgupf/p9 affected?
No. v0.4.1, 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/hugelgupf/p9 should I use?
v0.4.1 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/hugelgupf/p9 have?
0 vulnerabilities are recorded for github.com/hugelgupf/p9 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/hugelgupf/p9 vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/hugelgupf/p9 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/hugelgupf/p9 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/hugelgupf/p9 for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/hugelgupf/p9 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.