Vulnerability Database · Go · Package report

github.com/go-gl/gl: vulnerability history, versions and safety

github.com/go-gl/gl 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.

Vulert verdict on github.com/go-gl/gl v0.0.0-20260331235117-4566fea9a276 i

Updated on 23 Oct 2026

Good news: v0.0.0-20260331235117-4566fea9a276, the version you would install today, has no known vulnerabilities.

Package health score 75/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release v0.0.0-20260331235117-4566fea9a276 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,210 i
  • OpenSSF scorecard 3/10 i
  • Last release 6 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/go-gl/gl, 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
v0.0.0-20260331235117-4566fea9a276 31 Mar 2026 none MIT — Details →
v0.0.0-20260331235117-b1a7743ebc77 31 Mar 2026 none MIT — Details →
v0.0.0-20231021071112-07e5d0ea2e71 21 Oct 2023 none MIT — Details →
v0.0.0-20211210172815-726fda9656d6 10 Dec 2021 none MIT — Details →
v0.0.0-20211208232342-48a7a0013f73 08 Dec 2021 none MIT — Details →
v0.0.0-20211025173605-bda47ffaa784 25 Oct 2021 none MIT — Details →
v0.0.0-20210905235341-f7a045908259 05 Sep 2021 none MIT — Details →
v0.0.0-20210813123233-e4099ee2221f 13 Aug 2021 none MIT — Details →
v0.0.0-20210812231146-e33571d17ed6 12 Aug 2021 none MIT — Details →
v0.0.0-20210501111010-69f74958bac0 01 May 2021 none MIT — Details →
v0.0.0-20210426225639-a3bfa832c8aa 26 Apr 2021 none MIT — Details →
v0.0.0-20210315015930-ae072cafe09d 15 Mar 2021 none MIT — Details →
v0.0.0-20210308051507-640c6464cf3e 08 Mar 2021 none MIT — Details →
v0.0.0-20190320180904-bf2b1f2f34d7 20 Mar 2019 none MIT — Details →
v0.0.0-20181026044259-55b76b7df9d2 26 Oct 2018 none MIT — Details →
v0.0.0-20181020191150-629e6eb0370b 20 Oct 2018 none MIT — Details →
v0.0.0-20180407155706-68e253793080 07 Apr 2018 none MIT — Details →
v0.0.0-20180319200113-f8cee0ff968a 19 Mar 2018 none MIT — Details →
v0.0.0-20180304232605-eafa86a81d97 04 Mar 2018 none MIT — Details →
v0.0.0-20170915061432-ac0d3d2af0fe 15 Sep 2017 none MIT — Details →
v0.0.0-20170620202532-39ef8e959f40 20 Jun 2017 none MIT — Details →
v0.0.0-20170607153539-ddd40c0c6ba7 07 Jun 2017 none MIT — Details →
v0.0.0-20170607044029-305537d185e4 07 Jun 2017 none MIT — Details →
v0.0.0-20170511235925-887577e03012 11 May 2017 none MIT — Details →
v0.0.0-20170511233948-9010c3afbc57 11 May 2017 none MIT — Details →
v0.0.0-20160814231129-b303bcb3e83b 14 Aug 2016 none MIT — Details →
v0.0.0-20160306111150-cd1cf4a9b229 06 Mar 2016 none MIT — Details →
v0.0.0-20151213080133-d27345b13436 13 Dec 2015 none MIT — Details →
v0.0.0-20150804085940-f6ff8aa6163d 04 Aug 2015 none MIT — Details →
v0.0.0-20150709154440-41aed3351edc 09 Jul 2015 none MIT — Details →
v0.0.0-20150316231753-7c718d1758f0 16 Mar 2015 none MIT — Details →
v0.0.0-20150316231645-d217cd554f2f 16 Mar 2015 none MIT — Details →
v0.0.0-20141115200744-a1db9f3987d4 15 Nov 2014 none MIT — Details →
v0.0.0-20140925220011-10aed5061e70 25 Sep 2014 none MIT — Details →
v0.0.0-20140520030651-0c2e34e3d8c6 20 May 2014 none MIT — Details →
v0.0.0-20140414235409-df014f1b4c07 14 Apr 2014 none MIT — Details →
v0.0.0-20140410202513-0d8b6d97be83 10 Apr 2014 none MIT — Details →

All 37 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/go-gl/gl

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/go-gl/gl

Is github.com/go-gl/gl safe to use?

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

Vulert scores github.com/go-gl/gl 75/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/go-gl/gl affected?

No. v0.0.0-20260331235117-4566fea9a276, 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/go-gl/gl should I use?

v0.0.0-20260331235117-4566fea9a276 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/go-gl/gl have?

0 vulnerabilities are recorded for github.com/go-gl/gl 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/go-gl/gl vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/go-gl/gl 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/go-gl/gl 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/go-gl/gl for upcoming vulnerabilities?

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