Vulnerability Database · Go · Package report
github.com/google/go-github/v71: vulnerability history, versions and safety
github.com/google/go-github/v71 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/google/go-github/v71 v71.0.0 i
Updated on 23 Oct 2026
Good news: v71.0.0, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Maintaining
- Popularity Key ecosystem project
- Community Moderate
What to do: Stay on v71.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v71.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v71.0.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 11,325 i
- OpenSSF scorecard 6/10 i
- Last release 18 months ago i
- Licence BSD-3-Clause 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/google/go-github/v71, 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.
- v71.0.1-0.20250508115815-6a2c098e7853 08 May 2025
- v71.0.1-0.20250505194155-9a4137d1ff1d 05 May 2025
- v71.0.1-0.20250430122735-c9e1ad0d3b65 30 Apr 2025
- v71.0.1-0.20250428160911-bdd7396e2d69 28 Apr 2025
- v71.0.1-0.20250423165150-04274a98708f 23 Apr 2025
- v71.0.1-0.20250418200928-5b75aa86dba5 18 Apr 2025
- v71.0.1-0.20250417000929-f99490e58a13 17 Apr 2025
- v71.0.1-0.20250415170657-687f9336e850 15 Apr 2025
- v71.0.1-0.20250413102143-462cda4535c1 13 Apr 2025
- v71.0.1-0.20250408131814-b98b707876c8 08 Apr 2025
- v71.0.0 07 Apr 2025
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| v71.0.1-0.20250508115815-6a2c098e7853 | 08 May 2025 | none | BSD-3-Clause | — | Details → |
| v71.0.1-0.20250505194155-9a4137d1ff1d | 05 May 2025 | none | BSD-3-Clause | — | Details → |
| v71.0.1-0.20250430122735-c9e1ad0d3b65 | 30 Apr 2025 | none | BSD-3-Clause | — | Details → |
| v71.0.1-0.20250428160911-bdd7396e2d69 | 28 Apr 2025 | none | BSD-3-Clause | — | Details → |
| v71.0.1-0.20250423165150-04274a98708f | 23 Apr 2025 | none | BSD-3-Clause | — | Details → |
| v71.0.1-0.20250418200928-5b75aa86dba5 | 18 Apr 2025 | none | BSD-3-Clause | — | Details → |
| v71.0.1-0.20250417000929-f99490e58a13 | 17 Apr 2025 | none | BSD-3-Clause | — | Details → |
| v71.0.1-0.20250415170657-687f9336e850 | 15 Apr 2025 | none | BSD-3-Clause | — | Details → |
| v71.0.1-0.20250413102143-462cda4535c1 | 13 Apr 2025 | none | BSD-3-Clause | — | Details → |
| v71.0.1-0.20250408131814-b98b707876c8 | 08 Apr 2025 | none | BSD-3-Clause | — | Details → |
| v71.0.0 | 07 Apr 2025 | none | BSD-3-Clause | — | Details → |
All 11 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/google/go-github/v71
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/google/go-github/v71
Is github.com/google/go-github/v71 safe to use?
Vulert has no vulnerabilities on record for github.com/google/go-github/v71 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/google/go-github/v71's Vulert package health score?
Vulert scores github.com/google/go-github/v71 84/100, which reads as in good shape. 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/google/go-github/v71 affected?
No. v71.0.0, 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/google/go-github/v71 should I use?
v71.0.0 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/google/go-github/v71 have?
0 vulnerabilities are recorded for github.com/google/go-github/v71 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/google/go-github/v71 vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/google/go-github/v71 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/google/go-github/v71 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/google/go-github/v71 for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/google/go-github/v71 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.