VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

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

github.com/emersion/go-sasl 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/emersion/go-sasl vulnerabilities

Vulert verdict on github.com/emersion/go-sasl v0.0.0-20241020182733-b788ff22d5a6 i

Updated on 23 Oct 2026

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

Package health score 61/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Inactive

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

  • Current release v0.0.0-20241020182733-b788ff22d5a6 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 106 i
  • OpenSSF scorecard 1/10 i
  • Last release 24 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/emersion/go-sasl, 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-20241020182733-b788ff22d5a6 20 Oct 2024 none MIT — Details →
v0.0.0-20241020182425-8dc394dad6a7 20 Oct 2024 none MIT — Details →
v0.0.0-20231106173351-e73c9f7bad43 06 Nov 2023 none MIT — Details →
v0.0.0-20220912192320-0145f2c60ead 12 Sep 2022 none MIT — Details →
v0.0.0-20211008083017-0b9dcfb154ac 08 Oct 2021 none MIT — Details →
v0.0.0-20211008081904-6c5998016b51 08 Oct 2021 none MIT — Details →
v0.0.0-20200509203442-7bfe0ed36a21 09 May 2020 none MIT — Details →
v0.0.0-20200509202850-4132e15e133d 09 May 2020 none MIT — Details →
v0.0.0-20200509190222-6fe53deab1f6 09 May 2020 none MIT — Details →
v0.0.0-20200509190011-062d72687cc3 09 May 2020 none MIT — Details →
v0.0.0-20191210011802-430746ea8b9b 10 Dec 2019 none MIT — Details →
v0.0.0-20190817083125-240c8404624e 17 Aug 2019 none MIT — Details →
v0.0.0-20190704090222-36b50694675c 04 Jul 2019 none MIT — Details →
v0.0.0-20190627194319-50516a8a415d 27 Jun 2019 none MIT — Details →
v0.0.0-20190627194230-1172510eb7c8 27 Jun 2019 none MIT — Details →
v0.0.0-20190627194230-3ae3e5312055 27 Jun 2019 none MIT — Details →
v0.0.0-20190627194230-8f0b9bf8caf6 27 Jun 2019 none MIT — Details →
v0.0.0-20190520160400-47d427600317 20 May 2019 none MIT — Details →
v0.0.0-20190520160149-0ca2ec062c75 20 May 2019 none MIT — Details →
v0.0.0-20190517184301-63aa71ca65a3 17 May 2019 none MIT — Details →
v0.0.0-20161116183048-7e096a0a6197 16 Nov 2016 none MIT — Details →
v0.0.0-20161103184741-9e6baec496a0 03 Nov 2016 none MIT — Details →
v0.0.0-20161031173500-1e2af45c974c 31 Oct 2016 none MIT — Details →
v0.0.0-20161023131755-cbbe410b4768 23 Oct 2016 none MIT — Details →
v0.0.0-20161023131332-04897e66fcc8 23 Oct 2016 none MIT — Details →
v0.0.0-20161019065805-6f8a6e2ee429 19 Oct 2016 none MIT — Details →
v0.0.0-20161019064044-61afe53d0427 19 Oct 2016 none MIT — Details →
v0.0.0-20160529081006-2284173d9d57 29 May 2016 none MIT — Details →
v0.0.0-20160518115306-35dc109eafbf 18 May 2016 none MIT — Details →
v0.0.0-20160517193808-32aa4461f68b 17 May 2016 none MIT — Details →
v0.0.0-20160517165137-fbae702bdc98 17 May 2016 none MIT — Details →

All 31 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/emersion/go-sasl

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/emersion/go-sasl

Is github.com/emersion/go-sasl safe to use?

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

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

No. v0.0.0-20241020182733-b788ff22d5a6, 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/emersion/go-sasl should I use?

v0.0.0-20241020182733-b788ff22d5a6 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/emersion/go-sasl have?

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

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

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