Vulnerability Database · Go · Package report

github.com/awalterschulze/gographviz: vulnerability history, versions and safety

github.com/awalterschulze/gographviz 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/awalterschulze/gographviz v2.0.3+incompatible i

Updated on 23 Oct 2026

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

Package health score 57/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Widely used
  • Community Quiet

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

  • Current release v2.0.3+incompatible — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 565 i
  • OpenSSF scorecard 3/10 i
  • Last release 71 months ago i
  • Licence Apache-2.0 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/awalterschulze/gographviz, 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-20230228183502-1aeb6b15b39e 28 Feb 2023 none Apache-2.0 — Details →
v2.0.4-0.20220601184953-129542da04dc+incompatible 01 Jun 2022 none Apache-2.0 — Details →
v0.0.0-20210715170308-148e69759983 15 Jul 2021 none Apache-2.0 — Details →
v2.0.4-0.20210715170308-148e69759983+incompatible 15 Jul 2021 none Apache-2.0 — Details →
v2.0.4-0.20210510122956-b4d5ee20b7d2+incompatible 10 May 2021 none Apache-2.0 — Details →
v0.0.0-20201102112227-61ac52a9250b 02 Nov 2020 none Apache-2.0 — Details →
v2.0.3+incompatible 02 Nov 2020 none Apache-2.0 — Details →
v0.0.0-20201004175929-a1621d071286 04 Oct 2020 none Apache-2.0 — Details →
v0.0.0-20201004073644-909238c0580e 04 Oct 2020 none Apache-2.0 — Details →
v0.0.0-20200917185114-d1b7d4b0c188 17 Sep 2020 none Apache-2.0 — Details →
v0.0.0-20200901124122-0eecad45bd71 01 Sep 2020 none Apache-2.0 — Details →
v2.0.2-0.20200810082452-794ba2878b95+incompatible 10 Aug 2020 none Apache-2.0 — Details →
v2.0.2-0.20200810082452-87b7ba42c7bb+incompatible 10 Aug 2020 none Apache-2.0 — Details →
v2.0.2-0.20200627090231-f8ebb8d3fadd+incompatible 27 Jun 2020 none Apache-2.0 — Details →
v0.0.0-20190522210029-fa59802746ab 22 May 2019 none Apache-2.0 — Details →
v2.0.1+incompatible 22 May 2019 none Apache-2.0 — Details →
v0.0.0-20190521203229-9c36406a3f65 21 May 2019 none Apache-2.0 — Details →
v0.0.0-20190221210632-1e9ccb565bca 21 Feb 2019 none Apache-2.0 — Details →
v2.0.0-20190221210632-1e9ccb565bca+incompatible 21 Feb 2019 none Apache-2.0 — Details →
v0.0.0-20181013152038-b2885df04310 13 Oct 2018 none Apache-2.0 — Details →
v0.0.0-20180927133620-e69668a01397 27 Sep 2018 none Apache-2.0 — Details →
v0.0.0-20180911070532-316953eb472f 11 Sep 2018 none Apache-2.0 — Details →
v0.0.0-20180813113015-16ed621cdb51 13 Aug 2018 none Apache-2.0 — Details →
v0.0.0-20180704132352-49969fe6eded 04 Jul 2018 none Apache-2.0 — Details →
v0.0.0-20180607045812-da5c847b6fb1 07 Jun 2018 none Apache-2.0 — Details →
v0.0.0-20180131143711-c45f112108a6 31 Jan 2018 none Apache-2.0 — Details →
v0.0.0-20171020105407-bf3a0bd30aae 20 Oct 2017 none Apache-2.0 — Details →
v0.0.0-20170729092202-01fdca2df2c7 29 Jul 2017 none Apache-2.0 — Details →
v0.0.0-20170610164842-67d8d2b90e74 10 Jun 2017 none Apache-2.0 — Details →
v0.0.0-20170528162302-0a96aed134c3 28 May 2017 none Apache-2.0 — Details →
v0.0.0-20170411143222-a57a291f429b 11 Apr 2017 none Apache-2.0 — Details →
v0.0.0-20170410065617-c84395e536e1 10 Apr 2017 none Apache-2.0 — Details →
v0.0.0-20170408175810-39fca9add821 08 Apr 2017 none Apache-2.0 — Details →
v0.0.0-20170330070832-34601d9f0741 30 Mar 2017 none Apache-2.0 — Details →
v0.0.0-20170325100144-228e0cecf28e 25 Mar 2017 none Apache-2.0 — Details →
v0.0.0-20170323070310-7a068d76c6b5 23 Mar 2017 none Apache-2.0 — Details →
v0.0.0-20170323065823-e4cf1dade857 23 Mar 2017 none Apache-2.0 — Details →
v0.0.0-20170323064532-9d8c9780eb47 23 Mar 2017 none Apache-2.0 — Details →
v0.0.0-20170117174356-057e6a5e9343 17 Jan 2017 none Apache-2.0 — Details →
v0.0.0-20161230211447-224d2284f4a7 30 Dec 2016 none Apache-2.0 — Details →
v0.0.0-20161211144529-609eb77bad9f 11 Dec 2016 none Apache-2.0 — Details →
v0.0.0-20161112093729-8f1f445a23d3 12 Nov 2016 none Apache-2.0 — Details →
v0.0.0-20161112093518-d2b2b059809f 12 Nov 2016 none Apache-2.0 — Details →
v0.0.0-20161029154511-7352888493e7 29 Oct 2016 none Apache-2.0 — Details →
v0.0.0-20161029154250-2d3883396e0b 29 Oct 2016 none Apache-2.0 — Details →
v0.0.0-20161028064903-069f301861c2 28 Oct 2016 none Apache-2.0 — Details →
v0.0.0-20161001073201-d4d851475233 01 Oct 2016 none Apache-2.0 — Details →
v0.0.0-20161001072122-084ab318ca38 01 Oct 2016 none Apache-2.0 — Details →
v0.0.0-20161001071049-190bd4a1bfa2 01 Oct 2016 none Apache-2.0 — Details →
v0.0.0-20160912181450-761fd5fbb34e 12 Sep 2016 none Apache-2.0 — Details →
v0.0.0-20160810151932-cafbade2d580 10 Aug 2016 none Apache-2.0 — Details →
v0.0.0-20160810073124-51372575c817 10 Aug 2016 none Apache-2.0 — Details →
v0.0.0-20160731000304-21c9596ef8ed 31 Jul 2016 none Apache-2.0 — Details →
v0.0.0-20160715125038-ceec261a3df6 15 Jul 2016 none Apache-2.0 — Details →
v0.0.0-20150616155454-7c3cf7212151 16 Jun 2015 none Apache-2.0 — Details →
v0.0.0-20150616154745-df219190d9a3 16 Jun 2015 none Apache-2.0 — Details →
v0.0.0-20150315081247-20d1f693416d 15 Mar 2015 none Apache-2.0 — Details →
v0.0.0-20150315081204-aa795c018b7b 15 Mar 2015 none Apache-2.0 — Details →
v0.0.0-20150315080757-a484da95f2b9 15 Mar 2015 none Apache-2.0 — Details →
v0.0.0-20140530091957-454bc64fdfa2 30 May 2014 none Apache-2.0 — Details →
v0.0.0-20140506181524-255110db6f2f 06 May 2014 none Apache-2.0 — Details →
v0.0.0-20130919122352-212766062629 19 Sep 2013 none Apache-2.0 — Details →
v0.0.0-20130216150401-2b080890c5b9 16 Feb 2013 none Apache-2.0 — Details →
v0.0.0-20130115082916-acf96a696f8d 15 Jan 2013 none Apache-2.0 — Details →
v0.0.0-20130115082437-8444ac3ac354 15 Jan 2013 none Apache-2.0 — Details →

All 65 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/awalterschulze/gographviz

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/awalterschulze/gographviz

Is github.com/awalterschulze/gographviz safe to use?

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

Vulert scores github.com/awalterschulze/gographviz 57/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/awalterschulze/gographviz affected?

No. v2.0.3+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/awalterschulze/gographviz should I use?

v2.0.3+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/awalterschulze/gographviz have?

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

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

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