Vulnerability Database · Go · Package report
github.com/pseudomuto/protokit: vulnerability history, versions and safety
github.com/pseudomuto/protokit 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/pseudomuto/protokit v0.3.0 i
Updated on 23 Oct 2026
Good news: v0.3.0, 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.3.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.3.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.3.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 82 i
- OpenSSF scorecard 3/10 i
- Last release 3 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/pseudomuto/protokit, 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.3.0 20 Jul 2026
- v0.0.0-20251021172619-c9e5558d53d8 21 Oct 2025
- v0.2.2-0.20251021172619-c9e5558d53d8 21 Oct 2025
- v0.0.0-20220215120536-dc6fd1c8003a 15 Feb 2022
- v0.2.2-0.20220215120536-dc6fd1c8003a 15 Feb 2022
- v0.2.1 15 Feb 2022
- v0.2.1-0.20220215030724-eaa1fc1efed6 15 Feb 2022
- v0.2.0 15 Apr 2019
- v0.0.0-20181108154750-3705a628937f 08 Nov 2018
- v0.1.1-0.20181108154750-3705a628937f 08 Nov 2018
- v0.1.1-0.20181107180538-93d6ac86c251 07 Nov 2018
- v0.0.0-20180905140404-a93184a99124 05 Sep 2018
- v0.1.1-0.20180905140404-a93184a99124 05 Sep 2018
- v0.1.1-0.20180905132546-13945a9a133d 05 Sep 2018
- v0.1.1-0.20180817082005-a37fb75874a7 17 Aug 2018
- v0.1.0 23 Feb 2018
- v0.1.0-pre3 22 Feb 2018
- v0.1.0-pre2 22 Feb 2018
- v0.1.0-pre 22 Feb 2018
- v0.0.0-20180220140348-cb3ae78699c4 20 Feb 2018
- v0.0.0-20180219191440-1d257b5ecd3e 19 Feb 2018
- v0.0.0-20180218201725-62027c5a170c 18 Feb 2018
All 22 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/pseudomuto/protokit
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/pseudomuto/protokit
Is github.com/pseudomuto/protokit safe to use?
Vulert has no vulnerabilities on record for github.com/pseudomuto/protokit 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/pseudomuto/protokit's Vulert package health score?
Vulert scores github.com/pseudomuto/protokit 73/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/pseudomuto/protokit affected?
No. v0.3.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/pseudomuto/protokit should I use?
v0.3.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/pseudomuto/protokit have?
0 vulnerabilities are recorded for github.com/pseudomuto/protokit 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/pseudomuto/protokit vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/pseudomuto/protokit 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/pseudomuto/protokit 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/pseudomuto/protokit for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/pseudomuto/protokit version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.