Vulnerability Database · Go · Package report
github.com/prysmaticlabs/fastssz: vulnerability history, versions and safety
github.com/prysmaticlabs/fastssz 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/prysmaticlabs/fastssz v0.0.0-20260421202104-7a6eb71e6e45 i
Updated on 23 Oct 2026
Good news: v0.0.0-20260421202104-7a6eb71e6e45, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.0.0-20260421202104-7a6eb71e6e45 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20260421202104-7a6eb71e6e45 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20260421202104-7a6eb71e6e45 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 2 i
- OpenSSF scorecard 2/10 i
- Last release 6 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/prysmaticlabs/fastssz, 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-20260421202104-7a6eb71e6e45 21 Apr 2026
- v0.0.0-20260419225829-25957f7654fe 19 Apr 2026
- v0.0.0-20260401175048-c57e478b88da 01 Apr 2026
- v0.0.0-20260313210737-46c2c806e3e1 13 Mar 2026
- v0.0.0-20251103153600-259302269bfc 03 Nov 2025
- v0.0.0-20250818163020-6fd8d25f1211 18 Aug 2025
- v0.0.0-20241008181541-518c4ce73516 08 Oct 2024
- v0.0.0-20240620202422-a981b8ef89d3 20 Jun 2024
- v0.0.0-20230216165902-cac1483628fe 16 Feb 2023
- v0.0.0-20230215205823-6741487670ed 15 Feb 2023
- v0.0.0-20221107182844-78142813af44 07 Nov 2022
- v0.0.0-20221026003717-9fc1ea020cbd 26 Oct 2022
- v0.0.0-20220719165930-057abd9e71df 19 Jul 2022
- v0.0.0-20220719165412-782c5704e367 19 Jul 2022
- v0.0.0-20220719164546-570ef0a8fcc2 19 Jul 2022
- v0.0.0-20220719151335-b6260ba12a78 19 Jul 2022
- v0.0.0-20220628131814-351fdcbb9964 28 Jun 2022
- v0.0.0-20220628121656-93dfe28febab 28 Jun 2022
- v0.0.0-20220627140622-afcf89957aa0 27 Jun 2022
- v0.0.0-20220624091035-af5440c5d1dc 24 Jun 2022
- v0.0.0-20220623154914-0eefbc420cfd 23 Jun 2022
All 21 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/prysmaticlabs/fastssz
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/prysmaticlabs/fastssz
Is github.com/prysmaticlabs/fastssz safe to use?
Vulert has no vulnerabilities on record for github.com/prysmaticlabs/fastssz 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/prysmaticlabs/fastssz's Vulert package health score?
Vulert scores github.com/prysmaticlabs/fastssz 61/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/prysmaticlabs/fastssz affected?
No. v0.0.0-20260421202104-7a6eb71e6e45, 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/prysmaticlabs/fastssz should I use?
v0.0.0-20260421202104-7a6eb71e6e45 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/prysmaticlabs/fastssz have?
0 vulnerabilities are recorded for github.com/prysmaticlabs/fastssz 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/prysmaticlabs/fastssz vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/prysmaticlabs/fastssz 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/prysmaticlabs/fastssz 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/prysmaticlabs/fastssz for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/prysmaticlabs/fastssz version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.