VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

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

github.com/igm/sockjs-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.

See all github.com/igm/sockjs-go vulnerabilities

Vulert verdict on github.com/igm/sockjs-go v3.0.3+incompatible i

Updated on 23 Oct 2026

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

Package health score 60/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Inactive

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

  • Current release v3.0.3+incompatible — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 506 i
  • OpenSSF scorecard 1/10 i
  • Last release 35 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/igm/sockjs-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-20231108071437-307216b0bc17 08 Nov 2023 none BSD-3-Clause — Details →
v3.0.3+incompatible 08 Nov 2023 none BSD-3-Clause — Details →
v0.0.0-20211111200837-e2b1424d8982 11 Nov 2021 none BSD-3-Clause — Details →
v3.0.2+incompatible 11 Nov 2021 none BSD-3-Clause — Details →
v0.0.0-20211001163137-ad263845b088 01 Oct 2021 none BSD-3-Clause — Details →
v3.0.1+incompatible 01 Oct 2021 none BSD-3-Clause — Details →
v0.0.0-20200531124043-db9cf16b3bc8 31 May 2020 none BSD-3-Clause — Details →
v3.0.0+incompatible 31 May 2020 none BSD-3-Clause — Details →
v0.0.0-20200426155823-50a65008b72f 26 Apr 2020 none BSD-3-Clause — Details →
v2.0.2-0.20191127104210-d82eeafdacd6+incompatible 27 Nov 2019 none BSD-3-Clause — Details →
v0.0.0-20191119074118-cd6986df5bcc 19 Nov 2019 none BSD-3-Clause — Details →
v0.0.0-20191116140235-bd2ed36762b2 16 Nov 2019 none BSD-3-Clause — Details →
v0.0.0-20191116140159-bc95a2e3f22d 16 Nov 2019 none BSD-3-Clause — Details →
v0.0.0-20190813134216-1a1bca4e69c3 13 Aug 2019 none BSD-3-Clause — Details →
v0.0.0-20190621125103-7e107b440556 21 Jun 2019 none BSD-3-Clause — Details →
v2.0.1+incompatible 18 Jun 2019 none BSD-3-Clause — Details →
v0.0.0-20190618082940-1840ed98ab88 18 Jun 2019 none BSD-3-Clause — Details →
v0.0.0-20181115114233-fd48fe90e436 15 Nov 2018 none BSD-3-Clause — Details →
v0.0.0-20180905123038-04b42539e275 05 Sep 2018 none BSD-3-Clause — Details →
v0.0.0-20180629114527-4e63e74d3787 29 Jun 2018 none BSD-3-Clause — Details →
v0.0.0-20180629090755-4da284d2ef3a 29 Jun 2018 none BSD-3-Clause — Details →
v0.0.0-20180531182925-eb207ad87718 31 May 2018 none BSD-3-Clause — Details →
v0.0.0-20171030210102-c8a8c6429d10 30 Oct 2017 none BSD-3-Clause — Details →
v0.0.0-20170922065658-cf1c57955613 22 Sep 2017 none BSD-3-Clause — Details →
v0.0.0-20170904145442-1ab2e8fcba9d 04 Sep 2017 none BSD-3-Clause — Details →
v0.0.0-20161130122800-1f275fbd3bcc 30 Nov 2016 none BSD-3-Clause — Details →
v2.0.0+incompatible 15 Nov 2016 none BSD-3-Clause — Details →
v0.0.0-20161024065213-012a3c511ff1 24 Oct 2016 none BSD-3-Clause — Details →
v0.0.0-20160413205455-250738e8a527 13 Apr 2016 none BSD-3-Clause — Details →
v0.0.0-20160309003853-23545cb0a627 09 Mar 2016 none BSD-3-Clause — Details →
v0.0.0-20160111205803-162dbb4dc8d1 11 Jan 2016 none BSD-3-Clause — Details →
v0.0.0-20150917214413-f437f17b58fc 17 Sep 2015 none BSD-3-Clause — Details →
v1.0.0 01 Apr 2014 none BSD-3-Clause — Details →
v0.0.0-20130311171124-5c834d5192b7 11 Mar 2013 none — — 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/igm/sockjs-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/igm/sockjs-go

Is github.com/igm/sockjs-go safe to use?

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

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

No. v3.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/igm/sockjs-go should I use?

v3.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/igm/sockjs-go have?

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

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

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/igm/sockjs-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.