Vulnerability Database · Go · Package report

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

github.com/go-stomp/stomp 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-stomp/stomp v2.1.4+incompatible i

Updated on 23 Oct 2026

Good news: v2.1.4+incompatible, 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.1.4+incompatible or newer. This can change: a vulnerability disclosed tomorrow can affect v2.1.4+incompatible too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v2.1.4+incompatible — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 326 i
  • OpenSSF scorecard 2/10 i
  • Last release 66 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/go-stomp/stomp, 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
v1.0.2-0.20210411005500-100d4b78cf8b 11 Apr 2021 none Apache-2.0 — Details →
v2.1.4+incompatible 11 Apr 2021 none Apache-2.0 — Details →
v1.0.2 11 Apr 2021 none Apache-2.0 — Details →
v1.0.2-0.20210411003658-8e3adf42f9cc 11 Apr 2021 none Apache-2.0 — Details →
v0.0.0-20210313175427-15090673a6a8 13 Mar 2021 none Apache-2.0 — Details →
v2.1.3+incompatible 13 Mar 2021 none Apache-2.0 — Details →
v0.0.0-20210113043914-0036ca2347e3 13 Jan 2021 none Apache-2.0 — Details →
v2.1.2+incompatible 13 Jan 2021 none Apache-2.0 — Details →
v2.1.1-0.20210107172234-9c81a64d9859+incompatible 07 Jan 2021 none Apache-2.0 — Details →
v2.1.0+incompatible 13 Dec 2020 none Apache-2.0 — Details →
v2.0.9-0.20201211160449-29df28dd8003+incompatible 11 Dec 2020 none Apache-2.0 — Details →
v2.0.9-0.20201129183434-72d46eb6edcc+incompatible 29 Nov 2020 none Apache-2.0 — Details →
v0.0.0-20201027151125-a96d395162dc 27 Oct 2020 none Apache-2.0 — Details →
v2.0.8+incompatible 27 Oct 2020 none Apache-2.0 — Details →
v2.0.7-0.20201025202417-e5783d178add+incompatible 25 Oct 2020 none Apache-2.0 — Details →
v2.0.7-0.20200915200526-fa6ced728439+incompatible 15 Sep 2020 none Apache-2.0 — Details →
v2.0.7-0.20200914113021-805ba77106c7+incompatible 14 Sep 2020 none Apache-2.0 — Details →
v2.0.6+incompatible 28 Apr 2020 none Apache-2.0 — Details →
v2.0.6-0.20200428035007-ebec40d991c1+incompatible 28 Apr 2020 none Apache-2.0 — Details →
v2.0.5+incompatible 12 Feb 2020 none Apache-2.0 — Details →
v0.0.0-20190719042331-123cce4269fc 19 Jul 2019 none Apache-2.0 — Details →
v2.0.4+incompatible 19 Jul 2019 none Apache-2.0 — Details →
v2.0.4-0.20190719042331-123cce4269fc+incompatible 19 Jul 2019 none Apache-2.0 — Details →
v2.0.4-0.20190714163115-f75aff2c9353+incompatible 14 Jul 2019 none Apache-2.0 — Details →
v2.0.3+incompatible 23 Apr 2019 none Apache-2.0 — Details →
v0.0.0-20190212165159-51f02fb02f28 12 Feb 2019 none Apache-2.0 — Details →
v2.0.3-0.20190212165159-51f02fb02f28+incompatible 12 Feb 2019 none Apache-2.0 — Details →
v2.0.3-0.20190208095923-a9641845aa77+incompatible 08 Feb 2019 none Apache-2.0 — Details →
v2.0.3-0.20190112005706-cb0ea28e5ced+incompatible 12 Jan 2019 none Apache-2.0 — Details →
v2.0.2+incompatible 02 Jan 2019 none Apache-2.0 — Details →
v2.0.2-0.20190102182828-684aa687fc71+incompatible 02 Jan 2019 none Apache-2.0 — Details →
v2.0.2-0.20181224230040-45514f7e32e9+incompatible 24 Dec 2018 none Apache-2.0 — Details →
v2.0.2-0.20181218054627-ed3f92b69db5+incompatible 18 Dec 2018 none Apache-2.0 — Details →
v2.0.2-0.20181211001431-bfe3a16de886+incompatible 11 Dec 2018 none Apache-2.0 — Details →
v2.0.2-0.20181110012836-7ed7cfe401c1+incompatible 10 Nov 2018 none Apache-2.0 — Details →
v0.0.0-20180919164225-8a8033db5472 19 Sep 2018 none Apache-2.0 — Details →
v2.0.1+incompatible 19 Sep 2018 none Apache-2.0 — Details →
v1.0.2-0.20180905105702-e3737c9a4230 05 Sep 2018 none Apache-2.0 — Details →
v0.0.0-20180709201621-10a97affa878 09 Jul 2018 none Apache-2.0 — Details →
v1.0.2-0.20180709201621-10a97affa878 09 Jul 2018 none Apache-2.0 — Details →
v1.0.2-0.20180627195044-b37463816ab1 27 Jun 2018 none Apache-2.0 — Details →
v0.0.0-20171106151823-ba860900ef33 06 Nov 2017 none Apache-2.0 — Details →
v1.0.2-0.20171106151823-ba860900ef33 06 Nov 2017 none Apache-2.0 — Details →
v1.0.2-0.20171102064943-dd1f8b732431 02 Nov 2017 none Apache-2.0 — Details →
v1.0.2-0.20171025153734-bc833d325d02 25 Oct 2017 none Apache-2.0 — Details →
v1.0.2-0.20161104184806-1c7d284575f8 04 Nov 2016 none Apache-2.0 — Details →
v1.0.2-0.20161025154445-098c741051b6 25 Oct 2016 none Apache-2.0 — Details →
v1.0.2-0.20161014214712-154e039f5352 14 Oct 2016 none Apache-2.0 — Details →
v0.0.0-20160921161119-4c35b42bed92 21 Sep 2016 none Apache-2.0 — Details →
v1.0.2-0.20160921161119-4c35b42bed92 21 Sep 2016 none Apache-2.0 — Details →
v1.0.2-0.20160907031752-b994bda931e1 07 Sep 2016 none Apache-2.0 — Details →
v1.0.2-0.20160810030454-e301e7f28d93 10 Aug 2016 none Apache-2.0 — Details →
v1.0.2-0.20160714231319-364e36fe2129 14 Jul 2016 none Apache-2.0 — Details →
v1.0.2-0.20150714012038-64f6322840b9 14 Jul 2015 none Apache-2.0 — Details →
v0.0.0-20150711080444-45a2c24c3bc4 11 Jul 2015 none Apache-2.0 — Details →
v1.0.2-0.20150503015335-a812e9048aa5 03 May 2015 none Apache-2.0 — Details →
v1.0.1 23 Aug 2014 none Apache-2.0 — Details →
v0.0.0-20140110132555-217060b77517 10 Jan 2014 none Apache-2.0 — Details →

All 58 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-stomp/stomp

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-stomp/stomp

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

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

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

No. v2.1.4+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/go-stomp/stomp should I use?

v2.1.4+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/go-stomp/stomp have?

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

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

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