Vulnerability Database · Go · Package report
github.com/tj/go-update: vulnerability history, versions and safety
github.com/tj/go-update 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/tj/go-update v2.2.4+incompatible i
Updated on 23 Oct 2026
Good news: v2.2.4+incompatible, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Niche
- Community Inactive
What to do: Stay on v2.2.4+incompatible or newer. This can change: a vulnerability disclosed tomorrow can affect v2.2.4+incompatible too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v2.2.4+incompatible — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 241 i
- OpenSSF scorecard 1/10 i
- Last release 97 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/tj/go-update, 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.1-0.20200519121640-62b4b798fd68 19 May 2020
- v2.2.4-0.20200519121640-62b4b798fd68+incompatible 19 May 2020
- v2.2.5-0.20200519121640-62b4b798fd68+incompatible 19 May 2020
- v2.2.5-0.20200424114311-ca5542b6e7e5+incompatible 24 Apr 2020
- v2.2.5-0.20200423155647-72dee9041e75+incompatible 23 Apr 2020
- v2.2.5-0.20200219103523-c6b6a2a75ba3+incompatible 19 Feb 2020
- v2.2.4+incompatible 18 Sep 2018
- v2.2.3+incompatible 18 Sep 2018
- v2.2.2+incompatible 17 Sep 2018
- v2.2.0+incompatible 23 Jan 2018
- v0.0.0-20180105191633-a963589e45a4 05 Jan 2018
- v2.1.0+incompatible 05 Jan 2018
- v2.2.1+incompatible 05 Jan 2018
- v2.0.2+incompatible 13 Nov 2017
- v2.0.1+incompatible 04 Nov 2017
- v2.0.0+incompatible 30 Oct 2017
- v1.0.0 07 Jul 2017
All 17 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/tj/go-update
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/tj/go-update
Is github.com/tj/go-update safe to use?
Vulert has no vulnerabilities on record for github.com/tj/go-update 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/tj/go-update's Vulert package health score?
Vulert scores github.com/tj/go-update 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/tj/go-update affected?
No. v2.2.4+incompatible, 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/tj/go-update should I use?
v2.2.4+incompatible 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/tj/go-update have?
0 vulnerabilities are recorded for github.com/tj/go-update 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/tj/go-update vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/tj/go-update 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/tj/go-update 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/tj/go-update for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/tj/go-update version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.