Vulnerability Database · Go · Package report
github.com/sebest/xff: vulnerability history, versions and safety
github.com/sebest/xff 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/sebest/xff v0.0.0-20210106013422-671bd2870b3a i
Updated on 23 Oct 2026
Good news: v0.0.0-20210106013422-671bd2870b3a, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Niche
- Community Inactive
What to do: Stay on v0.0.0-20210106013422-671bd2870b3a or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20210106013422-671bd2870b3a too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20210106013422-671bd2870b3a — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 99 i
- OpenSSF scorecard 1/10 i
- Last release 69 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/sebest/xff, 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-20210106013422-671bd2870b3a 06 Jan 2021
- v0.0.0-20201109074112-736b8033bb58 09 Nov 2020
- v0.0.0-20201027103347-8cf901441da1 27 Oct 2020
- v0.0.0-20160910043805-6c115e0ffa35 10 Sep 2016
- v0.0.0-20160910041837-b19cda4a98d7 10 Sep 2016
- v0.0.0-20160507092249-382894583616 07 May 2016
- v0.0.0-20160507090329-382b8d9c7215 07 May 2016
- v0.0.0-20151025122837-325cb7697e6d 25 Oct 2015
- v0.0.0-20150728015220-d90d345f39f4 28 Jul 2015
- v0.0.0-20150611211316-7a36e3a787b5 11 Jun 2015
- v0.0.0-20150306202926-52c18ae0a40f 06 Mar 2015
- v0.0.0-20150220200658-4d68cd3bbbc3 20 Feb 2015
- v0.0.0-20150220200640-e07361998bef 20 Feb 2015
- v0.0.0-20150220020033-548095678c49 20 Feb 2015
All 14 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/sebest/xff
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/sebest/xff
Is github.com/sebest/xff safe to use?
Vulert has no vulnerabilities on record for github.com/sebest/xff 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/sebest/xff's Vulert package health score?
Vulert scores github.com/sebest/xff 49/100, which reads as risky. 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/sebest/xff affected?
No. v0.0.0-20210106013422-671bd2870b3a, 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/sebest/xff should I use?
v0.0.0-20210106013422-671bd2870b3a 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/sebest/xff have?
0 vulnerabilities are recorded for github.com/sebest/xff 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/sebest/xff vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/sebest/xff 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/sebest/xff 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/sebest/xff for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/sebest/xff version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.