VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/google/licenseclassifier/v2: vulnerability history, versions and safety

github.com/google/licenseclassifier/v2 is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/google/licenseclassifier/v2 vulnerabilities

Vulert verdict on github.com/google/licenseclassifier/v2 v2.0.0 i

Updated on 23 Oct 2026

Good news: v2.0.0, the version you would install today, has no known vulnerabilities.

Package health score 52/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Niche
  • Community Quiet

What to do: Stay on v2.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v2.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v2.0.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 351 i
  • OpenSSF scorecard 3/10 i
  • Last release 49 months ago i
  • Licence AFL-1.1 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/licenseclassifier/v2, 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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v2.0.1-0.20260218193730-3cfbab2d0e0d 18 Feb 2026 none AFL-1.1 — Details →
v2.0.1-0.20250213175939-b5d1a3369749 13 Feb 2025 none AFL-1.1 — Details →
v2.0.1-0.20250212230413-0181809d0f4b 12 Feb 2025 none AFL-1.1 — Details →
v2.0.1-0.20250108172508-0c3884c4cd43 08 Jan 2025 none AFL-1.1 — Details →
v2.0.0-20221004142553-c1ed8fcf4bab 04 Oct 2022 none AFL-1.1 — Details →
v2.0.1-0.20221004142553-c1ed8fcf4bab 04 Oct 2022 none AFL-1.1 — Details →
v2.0.0 16 Sep 2022 none AFL-1.1 — Details →
v2.0.0-pre6.0.20220912220135-29185c80d3fd 12 Sep 2022 none AFL-1.1 — Details →
v2.0.0-pre6.0.20220907210658-23923d047d0e 07 Sep 2022 none AFL-1.1 — Details →
v2.0.0-20220907210610-7c5bb21c30de 07 Sep 2022 none AFL-1.1 — Details →
v2.0.0-pre4.0.20220712234305-c913e304a153 12 Jul 2022 none AFL-1.1 — Details →
v2.0.0-pre6 12 Jul 2022 none AFL-1.1 — Details →
v2.0.0-20220326190949-7c62d6fe8d3a 26 Mar 2022 none AFL-1.1 — Details →
v2.0.0-pre4.0.20220326190949-7c62d6fe8d3a 26 Mar 2022 none AFL-1.1 — Details →
v2.0.0-pre4.0.20220321203144-ead99f4528b8 21 Mar 2022 none AFL-1.1 — Details →
v2.0.0-pre5 21 Mar 2022 none AFL-1.1 — Details →
v2.0.0-pre3.0.20220321201908-5a81a7518700 21 Mar 2022 none AFL-1.1 — Details →
v2.0.0-pre4 21 Mar 2022 none AFL-1.1 — Details →
v2.0.0-pre.2.0.20220321201737-24b312723b9b 21 Mar 2022 none AFL-1.1 — Details →
v2.0.0-pre3 21 Mar 2022 none AFL-1.1 — Details →
v2.0.0-alpha.3.0.20220321195219-5d426f379162 21 Mar 2022 none AFL-1.1 — Details →
v2.0.0-pre.2 21 Mar 2022 none AFL-1.1 — Details →
v2.0.0-alpha.2.0.20220321191234-a6f4b9f7a6aa 21 Mar 2022 none AFL-1.1 — Details →
v2.0.0-alpha.3 21 Mar 2022 none AFL-1.1 — Details →
v2.0.0-pre.1 21 Mar 2022 none AFL-1.1 — Details →
v2.0.0-alpha.1.0.20220316224345-0f3a421c4dc7 16 Mar 2022 none AFL-1.1 — Details →
v2.0.0-alpha.2 16 Mar 2022 none AFL-1.1 — Details →
v2.0.0-alpha.1.0.20210722185704-3043a050f148 22 Jul 2021 none Apache-2.0 — Details →
v2.0.0-alpha.1.0.20210722185704-9369ededc590 22 Jul 2021 none Apache-2.0 — Details →
v2.0.0-alpha.1.0.20210325184830-bb04aff29e72 25 Mar 2021 none Apache-2.0 — Details →
v2.0.0-alpha.1.0.20210324205846-148b633b0534 24 Mar 2021 none Apache-2.0 — Details →
v2.0.0-alpha.1.0.20210108172934-df6aa8a2788b 08 Jan 2021 none Apache-2.0 — Details →
v2.0.0-20201113175434-78a70215ca36 13 Nov 2020 none Apache-2.0 — Details →
v2.0.0-alpha.1 13 Nov 2020 none Apache-2.0 — Details →

All 34 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/licenseclassifier/v2

No vulnerability write-ups match this view

Search all 0 in the database →

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

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/google/licenseclassifier/v2

Is github.com/google/licenseclassifier/v2 safe to use?

Vulert has no vulnerabilities on record for github.com/google/licenseclassifier/v2 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/licenseclassifier/v2's Vulert package health score?

Vulert scores github.com/google/licenseclassifier/v2 52/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/licenseclassifier/v2 affected?

No. v2.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/licenseclassifier/v2 should I use?

v2.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/licenseclassifier/v2 have?

0 vulnerabilities are recorded for github.com/google/licenseclassifier/v2 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/licenseclassifier/v2 vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/google/licenseclassifier/v2 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/licenseclassifier/v2 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/licenseclassifier/v2 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/google/licenseclassifier/v2 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.