VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

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

github.com/protonmail/go-crypto 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/protonmail/go-crypto vulnerabilities

Vulert verdict on github.com/protonmail/go-crypto v0.0.0-20190328221529-3ab2febdc107 i

Updated on 23 Oct 2026

Good news: v0.0.0-20190328221529-3ab2febdc107, the version you would install today, has no known vulnerabilities.

Package health score 57/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Niche
  • Community Moderate

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

  • Current release v0.0.0-20190328221529-3ab2febdc107 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 423 i
  • OpenSSF scorecard 5/10 i
  • Last release 90 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/protonmail/go-crypto, 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-20190328221529-3ab2febdc107 28 Mar 2019 none BSD-3-Clause — Details →
v0.0.0-20190220004141-25f88b74191b 20 Feb 2019 none BSD-3-Clause — Details →
v0.0.0-20190211141510-09788189bfab 11 Feb 2019 none BSD-3-Clause — Details →
v0.0.0-20181126093934-9eb0be3963ea 26 Nov 2018 none BSD-3-Clause — Details →
v0.0.0-20181112202954-3d3f9f413869 12 Nov 2018 none BSD-3-Clause — Details →
v0.0.0-20181012144002-a92615f3c490 12 Oct 2018 none BSD-3-Clause — Details →
v0.0.0-20180830192347-182538f80094 30 Aug 2018 none BSD-3-Clause — Details →
v0.0.0-20180621125126-a49355c7e3f8 21 Jun 2018 none BSD-3-Clause — Details →
v0.0.0-20180606033505-29411dc97620 06 Jun 2018 none BSD-3-Clause — Details →
v0.0.0-20180515001509-1a580b3eff78 15 May 2018 none BSD-3-Clause — Details →
v0.0.0-20180419185729-a34213f58e68 19 Apr 2018 none BSD-3-Clause — Details →
v0.0.0-20180314180259-21652f85b0fd 14 Mar 2018 none BSD-3-Clause — Details →
v0.0.0-20180227085843-8c653846df49 27 Feb 2018 none BSD-3-Clause — Details →
v0.0.0-20180206190813-d9133f546934 06 Feb 2018 none BSD-3-Clause — Details →
v0.0.0-20171021001404-edd5e9b0879d 21 Oct 2017 none BSD-3-Clause — Details →
v0.0.0-20170930161057-34d0413e1bf9 30 Sep 2017 none BSD-3-Clause — Details →
v0.0.0-20170825220121-81e90905daef 25 Aug 2017 none BSD-3-Clause — Details →
v0.0.0-20170720175935-691496433715 20 Jul 2017 none BSD-3-Clause — Details →
v0.0.0-20170703084821-368a6044bc0e 03 Jul 2017 none BSD-3-Clause — Details →
v0.0.0-20170613210332-850760c427c5 13 Jun 2017 none BSD-3-Clause — Details →
v0.0.0-20170522142959-6c586e17d90a 22 May 2017 none BSD-3-Clause — Details →
v0.0.0-20170502214700-d1464577745b 02 May 2017 none BSD-3-Clause — Details →
v0.0.0-20170409152635-6022e334c1a8 09 Apr 2017 none BSD-3-Clause — Details →
v0.0.0-20170405144039-9da0784e41a2 05 Apr 2017 none BSD-3-Clause — Details →
v0.0.0-20170209233901-453249f01cfe 09 Feb 2017 none BSD-3-Clause — Details →
v0.0.0-20170208205045-537c9dfe43c8 08 Feb 2017 none BSD-3-Clause — Details →
v0.0.0-20161215162512-01be46f62051 15 Dec 2016 none BSD-3-Clause — Details →
v0.0.0-20161025161229-ca7e7f10cb9f 25 Oct 2016 none BSD-3-Clause — Details →
v0.0.0-20161020163205-3ded668c5379 20 Oct 2016 none BSD-3-Clause — Details →
v0.0.0-20161012025441-4cd25d65a015 12 Oct 2016 none BSD-3-Clause — Details →
v0.0.0-20160930202306-568507f56e5b 30 Sep 2016 none BSD-3-Clause — Details →
v0.0.0-20160909115837-f944096df804 09 Sep 2016 none BSD-3-Clause — Details →
v0.0.0-20160902160830-9e590154d235 02 Sep 2016 none BSD-3-Clause — Details →
v0.0.0-20160812214243-6c932297e160 12 Aug 2016 none BSD-3-Clause — Details →
v0.0.0-20160704103416-0c565bf13221 04 Jul 2016 none BSD-3-Clause — Details →
v0.0.0-20160607175246-77f4136a99ff 07 Jun 2016 none BSD-3-Clause — Details →
v0.0.0-20160512132831-1e61df8d9ea4 12 May 2016 none BSD-3-Clause — Details →
v0.0.0-20160510173643-b76c864ef1dc 10 May 2016 none BSD-3-Clause — Details →
v0.0.0-20160314204918-6025851c7c2b 14 Mar 2016 none BSD-3-Clause — Details →
v0.0.0-20160126184038-1f22c0103821 26 Jan 2016 none BSD-3-Clause — Details →
v0.0.0-20151215191501-f18420efc3b4 15 Dec 2015 none BSD-3-Clause — Details →
v0.0.0-20151201002508-7b85b097bf75 01 Dec 2015 none BSD-3-Clause — Details →
v0.0.0-20150817222011-c16968172724 17 Aug 2015 none BSD-3-Clause — Details →
v0.0.0-20150730211058-7f27901cb963 30 Jul 2015 none BSD-3-Clause — Details →
v0.0.0-20150711232705-f6a608df624a 11 Jul 2015 none BSD-3-Clause — Details →
v0.0.0-20150608195034-7ac880de98a1 08 Jun 2015 none BSD-3-Clause — Details →
v0.0.0-20150530194938-ecf53cc13127 30 May 2015 none BSD-3-Clause — Details →
v0.0.0-20150521154707-644910e6da85 21 May 2015 none BSD-3-Clause — Details →
v0.0.0-20150318170425-b7d6bf2c6154 18 Mar 2015 none BSD-3-Clause — Details →
v0.0.0-20141207234113-51bc81f67951 07 Dec 2014 none BSD-3-Clause — Details →
v0.0.0-20140828173722-18c283559e20 28 Aug 2014 none BSD-3-Clause — Details →
v0.0.0-20140707002436-2aff5f12d830 07 Jul 2014 none BSD-3-Clause — Details →
v0.0.0-20140512181956-2dfe547928fd 12 May 2014 none BSD-3-Clause — Details →
v0.0.0-20140502175529-df2851958a0c 02 May 2014 none BSD-3-Clause — Details →
v0.0.0-20140212190825-f82d56354e6a 12 Feb 2014 none BSD-3-Clause — Details →
v0.0.0-20131220155729-08da9c60bc70 20 Dec 2013 none BSD-3-Clause — Details →
v0.0.0-20131023171259-105632d35b71 23 Oct 2013 none BSD-3-Clause — Details →
v0.0.0-20130930200607-153ce2a1d20a 30 Sep 2013 none BSD-3-Clause — Details →
v0.0.0-20130828150221-3780a70b7b78 28 Aug 2013 none BSD-3-Clause — Details →
v0.0.0-20130827152331-504f1d5525c6 27 Aug 2013 none BSD-3-Clause — Details →
v0.0.0-20130715220131-c4978816b9e0 15 Jul 2013 none BSD-3-Clause — Details →
v0.0.0-20130618164342-7cbb17fecb34 18 Jun 2013 none BSD-3-Clause — Details →
v0.0.0-20130529060618-0e971cde331a 29 May 2013 none BSD-3-Clause — Details →
v0.0.0-20130402144135-d52ec7351039 02 Apr 2013 none BSD-3-Clause — Details →
v0.0.0-20130322185959-0bc0bccba9c2 22 Mar 2013 none BSD-3-Clause — Details →
v0.0.0-20130204153609-db732cbcc677 04 Feb 2013 none BSD-3-Clause — Details →
v0.0.0-20121210231236-4002be2701c5 10 Dec 2012 none BSD-3-Clause — Details →
v0.0.0-20121122184459-4c5258d8b6be 22 Nov 2012 none BSD-3-Clause — Details →
v0.0.0-20121017185816-c9c0e06eed43 17 Oct 2012 none BSD-3-Clause — Details →
v0.0.0-20120921043601-750c6a9860f0 21 Sep 2012 none BSD-3-Clause — Details →
v0.0.0-20120811021854-00f60517a3ee 11 Aug 2012 none BSD-3-Clause — Details →
v0.0.0-20120724232147-327f4563716f 24 Jul 2012 none BSD-3-Clause — Details →
v0.0.0-20120618161137-cde552e05fc4 18 Jun 2012 none BSD-3-Clause — Details →
v0.0.0-20120612203446-f8bd48beccf3 12 Jun 2012 none BSD-3-Clause — Details →
v0.0.0-20120424174622-bcdd6a2fd3e3 24 Apr 2012 none BSD-3-Clause — Details →
v0.0.0-20120421004456-58afe880f197 21 Apr 2012 none BSD-3-Clause — Details →
v0.0.0-20120312145904-124e52db8dfd 12 Mar 2012 none — — Details →
v0.0.0-20120302191657-67456e2aa3d9 02 Mar 2012 none — — Details →
v0.0.0-20120125203112-470549d5029a 25 Jan 2012 none — — Details →

All 79 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/protonmail/go-crypto

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/protonmail/go-crypto

Is github.com/protonmail/go-crypto safe to use?

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

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

No. v0.0.0-20190328221529-3ab2febdc107, 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/protonmail/go-crypto should I use?

v0.0.0-20190328221529-3ab2febdc107 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/protonmail/go-crypto have?

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

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

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