Vulnerability Database · Go · Package report
github.com/k0kubun/pp/v3: vulnerability history, versions and safety
github.com/k0kubun/pp/v3 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/k0kubun/pp/v3 v3.5.4 i
Updated on 23 Oct 2026
Good news: v3.5.4, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Key ecosystem project
- Community Quiet
What to do: Stay on v3.5.4 or newer. This can change: a vulnerability disclosed tomorrow can affect v3.5.4 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v3.5.4 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 2,055 i
- OpenSSF scorecard 3/10 i
- Last release this month 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/k0kubun/pp/v3, 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.
- v3.5.4 21 Oct 2026
- v3.5.3 09 Oct 2026
- v3.5.3-0.20261001233325-d971595a3b70 01 Oct 2026
- v3.5.3-0.20260801233317-46f9a64dbe95 01 Aug 2026
- v3.5.2 15 Jul 2026
- v3.5.2-0.20260603163603-a37f78250a5e 03 Jun 2026
- v3.5.2-0.20260201233309-0167f5fe2fbb 01 Feb 2026
- v3.5.1 23 Jan 2026
- v3.5.1-0.20251101230152-78dff184f1f4 01 Nov 2025
- v3.5.1-0.20251001230217-c5324ec057e8 01 Oct 2025
- v3.5.1-0.20250902163355-1021801426b2 02 Sep 2025
- v3.5.1-0.20250801231050-2526ca9b370e 01 Aug 2025
- v3.5.0 09 Jul 2025
- v3.4.2-0.20250526133719-43f40e91b4a1 26 May 2025
- v3.4.2-0.20250501233518-38fbbc214f7a 01 May 2025
- v3.4.2-0.20250301235729-ef2a449bbef2 01 Mar 2025
- v3.4.2-0.20250201235327-5f1259035722 01 Feb 2025
- v3.4.2-0.20250101235253-26a23a95520c 01 Jan 2025
- v3.4.2-0.20241201234354-825e0b46bf5f 01 Dec 2024
- v3.4.1 27 Nov 2024
- v3.4.1-0.20241127121336-6f00411bf43b 27 Nov 2024
- v3.3.1-0.20241127074924-9feac886a0dc 27 Nov 2024
- v3.4.0 27 Nov 2024
- v3.3.1-0.20241101232653-c9d35c3b4c9f 01 Nov 2024
- v3.3.1-0.20241025161614-de3c8d81b621 25 Oct 2024
- v3.3.0 25 Oct 2024
- v3.2.1-0.20241009044356-aa23dcd87c35 09 Oct 2024
- v3.2.1-0.20230401235711-9c753284ae79 01 Apr 2023
- v3.2.1-0.20230302050442-6f55b4dc4b26 02 Mar 2023
- v3.2.1-0.20221016073918-0b9e4d983495 16 Oct 2022
- v3.0.0-20221016070930-f2ac4d319e7f 16 Oct 2022
- v3.2.0 16 Oct 2022
- v3.1.1-0.20220902013640-1f07572ee586 02 Sep 2022
- v3.1.1-0.20220216035903-af1e26e8087e 16 Feb 2022
- v3.1.1-0.20220106074234-784c001031c3 06 Jan 2022
- v3.1.0 06 Jan 2022
- v3.0.10 06 Jan 2022
- v3.0.10-0.20220106061847-118249c7c627 06 Jan 2022
- v3.0.9 06 Jan 2022
- v3.0.9-0.20220106060551-7f4419250924 06 Jan 2022
- v3.0.8 30 Nov 2021
- v3.0.8-0.20211130055516-28dbe910808d 30 Nov 2021
- v3.0.8-0.20211130050359-3f962d3c9c44 30 Nov 2021
- v3.0.8-0.20211123061828-5f032f3104b5 23 Nov 2021
- v3.0.8-0.20211123043350-6179818469d3 23 Nov 2021
- v3.0.8-0.20210415165650-b87d88f85b84 15 Apr 2021
- v3.0.8-0.20210304073353-eb8477a7f1c8 04 Mar 2021
- v3.0.8-0.20210114031835-157d45224c59 14 Jan 2021
- v3.0.8-0.20201229034827-b84083f678e8 29 Dec 2020
- v3.0.7 18 Nov 2020
- v3.0.6 14 Nov 2020
- v3.0.5 14 Nov 2020
- v3.0.4 12 Nov 2020
- v3.0.3 11 Aug 2020
All 54 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/k0kubun/pp/v3
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/k0kubun/pp/v3
Is github.com/k0kubun/pp/v3 safe to use?
Vulert has no vulnerabilities on record for github.com/k0kubun/pp/v3 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/k0kubun/pp/v3's Vulert package health score?
Vulert scores github.com/k0kubun/pp/v3 83/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/k0kubun/pp/v3 affected?
No. v3.5.4, 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.
How many vulnerabilities does github.com/k0kubun/pp/v3 have?
0 vulnerabilities are recorded for github.com/k0kubun/pp/v3 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/k0kubun/pp/v3 vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/k0kubun/pp/v3 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/k0kubun/pp/v3 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/k0kubun/pp/v3 for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/k0kubun/pp/v3 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.