Vulnerability Database · Go · Package report
github.com/peterbourgon/ff/v4: vulnerability history, versions and safety
github.com/peterbourgon/ff/v4 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/peterbourgon/ff/v4 v4.0.0-beta.1 i
Updated on 23 Oct 2026
Good news: v4.0.0-beta.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Maintaining
- Popularity Widely used
- Community Quiet
What to do: Stay on v4.0.0-beta.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v4.0.0-beta.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v4.0.0-beta.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 1,441 i
- OpenSSF scorecard 2/10 i
- Last release 14 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/peterbourgon/ff/v4, 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.
- v4.0.0-beta.1.0.20261019011201-31df54c6f57c 19 Oct 2026
- v4.0.0-beta.1 02 Aug 2025
- v4.0.0-alpha.4.0.20250721190127-2b13f7e8c0cf 21 Jul 2025
- v4.0.0-alpha.4.0.20250720204205-f8588a1c826f 20 Jul 2025
- v4.0.0-alpha.4.0.20250720172430-23ed87b7ac38 20 Jul 2025
- v4.0.0-alpha.4.0.20250717164919-34997509d358 17 Jul 2025
- v4.0.0-alpha.4.0.20240224220309-4e42878b21c9 24 Feb 2024
- v4.0.0-alpha.4.0.20240216105926-21ddd055d8e4 16 Feb 2024
- v4.0.0-alpha.4.0.20240208225525-a70a3781e58d 08 Feb 2024
- v4.0.0-alpha.4.0.20240126011528-29a1b5cd7c9d 26 Jan 2024
- v4.0.0-alpha.4.0.20230929172201-43f89de44877 29 Sep 2023
- v4.0.0-alpha.4.0.20230927000101-48b4143c5c52 27 Sep 2023
- v4.0.0-alpha.3.0.20230920234754-f9e427600ad6 20 Sep 2023
- v4.0.0-alpha.4 20 Sep 2023
- v4.0.0-alpha.2.0.20230915115031-8abca347b2d6 15 Sep 2023
- v4.0.0-alpha.3 15 Sep 2023
- v4.0.0-alpha.1.0.20230909010249-0debd9dd24f1 09 Sep 2023
- v4.0.0-alpha.2 09 Sep 2023
- v4.0.0-20230831171633-743f646567c5 31 Aug 2023
- v4.0.0-alpha.1 31 Aug 2023
- v4.0.0-20230814233617-24a92813d477 14 Aug 2023
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/peterbourgon/ff/v4
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/peterbourgon/ff/v4
Is github.com/peterbourgon/ff/v4 safe to use?
Vulert has no vulnerabilities on record for github.com/peterbourgon/ff/v4 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/peterbourgon/ff/v4's Vulert package health score?
Vulert scores github.com/peterbourgon/ff/v4 68/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/peterbourgon/ff/v4 affected?
No. v4.0.0-beta.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/peterbourgon/ff/v4 should I use?
v4.0.0-beta.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/peterbourgon/ff/v4 have?
0 vulnerabilities are recorded for github.com/peterbourgon/ff/v4 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/peterbourgon/ff/v4 vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/peterbourgon/ff/v4 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/peterbourgon/ff/v4 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/peterbourgon/ff/v4 for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/peterbourgon/ff/v4 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.