Vulnerability Database · Go · Package report
github.com/alicebob/gopher-json: vulnerability history, versions and safety
github.com/alicebob/gopher-json 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/alicebob/gopher-json v0.0.0-20230218143504-906a9b012302 i
Updated on 23 Oct 2026
Good news: v0.0.0-20230218143504-906a9b012302, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.0.0-20230218143504-906a9b012302 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20230218143504-906a9b012302 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20230218143504-906a9b012302 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 4 i
- OpenSSF scorecard 1/10 i
- Last release 44 months ago i
- Licence Unlicense 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/alicebob/gopher-json, 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-20230218143504-906a9b012302 18 Feb 2023
- v0.0.0-20201124131017-552bb3c4c3bf 24 Nov 2020
- v0.0.0-20200520072559-a9ecdc9d1d3a 20 May 2020
- v0.0.0-20200518222753-e825cc070c2e 18 May 2020
- v0.0.0-20190114024228-0e11930d1c57 14 Jan 2019
- v0.0.0-20190114024228-97fed8db8427 14 Jan 2019
- v0.0.0-20181116191917-d3d498bb4913 16 Nov 2018
- v0.0.0-20181114224359-db6ad9ee368f 14 Nov 2018
- v0.0.0-20181112132036-24b0cabf6699 12 Nov 2018
- v0.0.0-20180720235322-d0a7d8b4c69a 20 Jul 2018
- v0.0.0-20180125190556-5a6b3ba71ee6 25 Jan 2018
- v0.0.0-20180123231145-1f632b9a4f86 23 Jan 2018
- v0.0.0-20160118202121-e45b65570c08 18 Jan 2016
- v0.0.0-20151227161246-3ed52f21e19e 27 Dec 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/alicebob/gopher-json
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/alicebob/gopher-json
Is github.com/alicebob/gopher-json safe to use?
Vulert has no vulnerabilities on record for github.com/alicebob/gopher-json 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/alicebob/gopher-json's Vulert package health score?
Vulert scores github.com/alicebob/gopher-json 48/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/alicebob/gopher-json affected?
No. v0.0.0-20230218143504-906a9b012302, 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/alicebob/gopher-json should I use?
v0.0.0-20230218143504-906a9b012302 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/alicebob/gopher-json have?
0 vulnerabilities are recorded for github.com/alicebob/gopher-json 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/alicebob/gopher-json vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/alicebob/gopher-json 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/alicebob/gopher-json 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/alicebob/gopher-json for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/alicebob/gopher-json version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.