Vulnerability Database · Go · Package report
github.com/go-faster/city: vulnerability history, versions and safety
github.com/go-faster/city 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/go-faster/city v1.0.1 i
Updated on 23 Oct 2026
Good news: v1.0.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Little adoption
- Community Inactive
What to do: Stay on v1.0.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.0.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.0.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 41 i
- OpenSSF scorecard 3/10 i
- Last release 56 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/go-faster/city, 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.
- v1.0.2-0.20220807193947-558942b0ebab 07 Aug 2022
- v1.0.1 25 Jan 2022
- v1.0.1-0.20220125005458-a8bba0b791a6 25 Jan 2022
- v1.0.1-0.20220112171110-670b326b4fc2 12 Jan 2022
- v1.0.1-0.20220108203945-0eb7b7bd73c0 08 Jan 2022
- v0.6.1-0.20211224214507-10659168148e 24 Dec 2021
- v1.0.0 24 Dec 2021
- v0.6.1-0.20211224123646-94362829dc81 24 Dec 2021
- v0.6.0 24 Dec 2021
- v0.5.1-0.20211129113606-2732b10f2668 29 Nov 2021
- v0.5.1-0.20211126184902-8314dfb6d1c4 26 Nov 2021
- v0.5.1-0.20211122073956-08c4034a6505 22 Nov 2021
- v0.5.0 21 Nov 2021
- v0.4.0 21 Nov 2021
- v0.3.3-0.20211121121923-c17c6a42f3e1 21 Nov 2021
- v0.3.2 20 Nov 2021
- v0.3.1 20 Nov 2021
- v0.3.1-0.20211118175052-98448971375f 18 Nov 2021
- v0.3.0 17 Nov 2021
- v0.2.1-0.20211117122331-a7ccc4778f0b 17 Nov 2021
- v0.2.0 17 Nov 2021
- v0.1.1-0.20211117091003-ca7fbcf0cf31 17 Nov 2021
- v0.1.1-0.20211117073953-367b2f2465df 17 Nov 2021
- v0.1.0 17 Nov 2021
- v0.0.3-0.20211117012326-a531774f5b1f 17 Nov 2021
- v0.0.2 17 Nov 2021
All 26 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/go-faster/city
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/go-faster/city
Is github.com/go-faster/city safe to use?
Vulert has no vulnerabilities on record for github.com/go-faster/city 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/go-faster/city's Vulert package health score?
Vulert scores github.com/go-faster/city 45/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/go-faster/city affected?
No. v1.0.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/go-faster/city should I use?
v1.0.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/go-faster/city have?
0 vulnerabilities are recorded for github.com/go-faster/city 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/go-faster/city vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/go-faster/city 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/go-faster/city 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/go-faster/city for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/go-faster/city version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.