Vulnerability Database · Go · Package report
github.com/google/licensecheck: vulnerability history, versions and safety
github.com/google/licensecheck 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/licensecheck v0.3.1 i
Updated on 23 Oct 2026
Good news: v0.3.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Widely used
- Community Quiet
What to do: Stay on v0.3.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.3.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.3.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 517 i
- OpenSSF scorecard 4/10 i
- Last release 73 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/licensecheck, 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.3.2-0.20220312115527-0279a51dbb8a 12 Mar 2022
- v0.3.2-0.20220131190415-db1987b6bdd3 31 Jan 2022
- v0.3.2-0.20220131165800-719b7d8affd0 31 Jan 2022
- v0.3.2-0.20210127144437-5aa300fd3333 27 Jan 2021
- v0.3.2-0.20210108091156-6523801c6c92 08 Jan 2021
- v0.3.2-0.20200908002009-2649e2fc42cc 08 Sep 2020
- v0.3.1 03 Sep 2020
- v0.3.0 02 Sep 2020
- v0.2.1 01 Sep 2020
- v0.2.0 01 Sep 2020
- v0.0.0-20200805042302-c54f297c3b57 05 Aug 2020
- v0.1.0 05 Aug 2020
- v0.0.0-20200805031514-4c8fcd50051a 05 Aug 2020
- v0.0.0-20200805015412-3cf959ba4f74 05 Aug 2020
- v0.0.0-20200804110753-1aa59f5c9d70 04 Aug 2020
- v0.0.0-20200804052021-83a39dcc2bde 04 Aug 2020
- v0.0.0-20200731082947-25409fb345da 31 Jul 2020
- v0.0.0-20200731034052-fd7755a53808 31 Jul 2020
- v0.0.0-20200710184526-158d942212ef 10 Jul 2020
- v0.0.0-20200406170604-d5d259d76f74 06 Apr 2020
- v0.0.0-20200324034158-633564932ad4 24 Mar 2020
- v0.0.0-20200226161255-fb7b516dfddc 26 Feb 2020
- v0.0.0-20200226151905-83092ede5666 26 Feb 2020
- v0.0.0-20200226150354-de0f59960f20 26 Feb 2020
- v0.0.0-20200214050835-9580b5fd1d6c 14 Feb 2020
- v0.0.0-20200214043149-1f5d45128a23 14 Feb 2020
- v0.0.0-20200213173046-5cc4f616f8db 13 Feb 2020
- v0.0.0-20200213163314-7388e7b0608d 13 Feb 2020
- v0.0.0-20200213160824-d48f3bd76aca 13 Feb 2020
- v0.0.0-20200213155256-5b2f5295c170 13 Feb 2020
- v0.0.0-20200213150712-a18cfb0627bf 13 Feb 2020
- v0.0.0-20200212152353-63e806fe99e4 12 Feb 2020
- v0.0.0-20200205041826-9240d01bd357 05 Feb 2020
- v0.0.0-20200110003425-e43db20c1115 10 Jan 2020
- v0.0.0-20200108042349-bcd885b47dfc 08 Jan 2020
- v0.0.0-20200108041021-aca499d57c3f 08 Jan 2020
- v0.0.0-20200108034447-d686698f934a 08 Jan 2020
- v0.0.0-20191108030757-acad3136ad4c 08 Nov 2019
- v0.0.0-20191017214201-4292f3df2c72 17 Oct 2019
- v0.0.0-20191003024511-41a7f7871e86 03 Oct 2019
- v0.0.0-20190611011822-e07107a3842f 11 Jun 2019
- v0.0.0-20190416041930-a13d4b3c90fd 16 Apr 2019
All 42 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/licensecheck
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/licensecheck
Is github.com/google/licensecheck safe to use?
Vulert has no vulnerabilities on record for github.com/google/licensecheck 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/licensecheck's Vulert package health score?
Vulert scores github.com/google/licensecheck 60/100, which reads as usable, but worth attention. 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/licensecheck affected?
No. v0.3.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/google/licensecheck should I use?
v0.3.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/google/licensecheck have?
0 vulnerabilities are recorded for github.com/google/licensecheck 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/licensecheck vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/google/licensecheck 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/licensecheck 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/licensecheck for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/google/licensecheck version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.