Vulnerability Database · Go · Package report

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

github.com/siddontang/go 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/siddontang/go v0.0.0-20180604090527-bdc77568d726 i

Updated on 23 Oct 2026

Good news: v0.0.0-20180604090527-bdc77568d726, the version you would install today, has no known vulnerabilities.

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

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

  • Current release v0.0.0-20180604090527-bdc77568d726 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 460 i
  • OpenSSF scorecard 1/10 i
  • Last release 100 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/siddontang/go, 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-20180604090527-bdc77568d726 04 Jun 2018 none MIT — Details →
v0.0.0-20180514060605-2b7082d296ba 14 May 2018 none MIT — Details →
v0.0.0-20170517070808-cb568a3e5cc0 17 May 2017 none MIT — Details →
v0.0.0-20170517063944-9f0583305145 17 May 2017 none MIT — Details →
v0.0.0-20170411011925-6463c3972685 11 Apr 2017 none MIT — Details →
v0.0.0-20170410150157-d2bc1bfd14fa 10 Apr 2017 none MIT — Details →
v0.0.0-20161005110831-1e9ce2a5ac40 05 Oct 2016 none MIT — Details →
v0.0.0-20160904050434-a30862d58df2 04 Sep 2016 none MIT — Details →
v0.0.0-20160904045750-c9455e02063a 04 Sep 2016 none MIT — Details →
v0.0.0-20151227044929-354e14e6c093 27 Dec 2015 none MIT — Details →
v0.0.0-20150505004501-b151716326d7 05 May 2015 none MIT — Details →
v0.0.0-20150331134050-530a23162549 31 Mar 2015 none MIT — Details →
v0.0.0-20150208013054-dfa1fad4a103 08 Feb 2015 none MIT — Details →
v0.0.0-20150112014430-c2b33271306f 12 Jan 2015 none MIT — Details →
v0.0.0-20150112013841-4900975709b5 12 Jan 2015 none MIT — Details →
v0.0.0-20150112013731-51d80cef1a8c 12 Jan 2015 none MIT — Details →
v0.0.0-20141122004730-8f64946c3074 22 Nov 2014 none MIT — Details →
v0.0.0-20141121015323-cdaddb8a0ed4 21 Nov 2014 none MIT — Details →
v0.0.0-20141029151222-ecf49fc07381 29 Oct 2014 none MIT — Details →
v0.0.0-20141027072458-5f5f3de07dce 27 Oct 2014 none MIT — Details →
v0.0.0-20141022013715-c7a17e4e4a1b 22 Oct 2014 none MIT — Details →
v0.0.0-20141015012035-ada3cebe1055 15 Oct 2014 none MIT — Details →
v0.0.0-20141015011801-f7ba813a54d6 15 Oct 2014 none MIT — Details →
v0.0.0-20140924045304-466d5bc779ad 24 Sep 2014 none MIT — Details →
v0.0.0-20140924022144-032f1ed536a8 24 Sep 2014 none MIT — Details →
v0.0.0-20140917051139-9b05f61506ba 17 Sep 2014 none MIT — Details →
v0.0.0-20140915005728-d1d84f2faa85 15 Sep 2014 none MIT — Details →
v0.0.0-20140911052343-8c8a794873ee 11 Sep 2014 none MIT — Details →
v0.0.0-20140904134205-7c4b75290820 04 Sep 2014 none MIT — Details →
v0.0.0-20140722084216-cde2e20315c7 22 Jul 2014 none MIT — Details →
v0.0.0-20140708064855-f9bb9e3d84b0 08 Jul 2014 none MIT — Details →
v0.0.0-20140515012330-23bd4b0ba7bf 15 May 2014 none MIT — Details →
v0.0.0-20140514010210-3dfdf380f2bd 14 May 2014 none MIT — Details →
v0.0.0-20140509014650-81840c211cc5 09 May 2014 none MIT — Details →
v0.0.0-20140508012251-0792eb6e26f5 08 May 2014 none MIT — Details →
v0.0.0-20140506023234-0eb5881662a5 06 May 2014 none MIT — Details →
v0.0.0-20140501005827-7589d8c9c055 01 May 2014 none MIT — Details →
v0.0.0-20140421082456-0c336c59bf72 21 Apr 2014 none MIT — Details →
v0.0.0-20140418065029-b9100d77aacf 18 Apr 2014 none MIT — Details →
v0.0.0-20140411062150-e02d4a31aa34 11 Apr 2014 none MIT — Details →
v0.0.0-20140403091447-e009b5fbd81b 03 Apr 2014 none MIT — Details →
v0.0.0-20140305084754-a46d1de9024d 05 Mar 2014 none MIT — Details →
v0.0.0-20140220074721-209f47d5eca1 20 Feb 2014 none MIT — Details →
v0.0.0-20140220055545-eeed48eee238 20 Feb 2014 none MIT — Details →
v0.0.0-20140103062629-eead8cb80934 03 Jan 2014 none MIT — Details →
v0.0.0-20140103062023-108b73122dbc 03 Jan 2014 none MIT — Details →

All 46 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/siddontang/go

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

Is github.com/siddontang/go safe to use?

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

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

No. v0.0.0-20180604090527-bdc77568d726, 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/siddontang/go should I use?

v0.0.0-20180604090527-bdc77568d726 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/siddontang/go have?

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

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

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