VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

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

github.com/nbutton23/zxcvbn-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/nbutton23/zxcvbn-go vulnerabilities

Vulert verdict on github.com/nbutton23/zxcvbn-go v0.0.0-20210217022336-fa2cb2858354 i

Updated on 23 Oct 2026

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

  • Current release v0.0.0-20210217022336-fa2cb2858354 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 393 i
  • OpenSSF scorecard 2/10 i
  • Last release 68 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/nbutton23/zxcvbn-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-20210217022336-fa2cb2858354 17 Feb 2021 none MIT — Details →
v0.0.0-20210215104253-5a96a2d2b83c 15 Feb 2021 none MIT — Details →
v0.0.0-20201221231540-e56b841a3c88 21 Dec 2020 none MIT — Details →
v0.0.0-20201221222045-9345b873fcfd 21 Dec 2020 none MIT — Details →
v0.0.0-20201221221823-db81aa62d390 21 Dec 2020 none MIT — Details →
v0.0.0-20180912185939-ae427f1e4c1d 12 Sep 2018 none MIT — Details →
v0.0.0-20180912130435-fbd806564e59 12 Sep 2018 none MIT — Details →
v0.0.0-20180830211852-be3c235ccdcd 30 Aug 2018 none MIT — Details →
v0.0.0-20180830205316-0425ef0975ce 30 Aug 2018 none MIT — Details →
v0.0.0-20180829150819-3cb5938f3fc9 29 Aug 2018 none MIT — Details →
v0.0.0-20180829032531-953e4e208627 29 Aug 2018 none MIT — Details →
v0.0.0-20180510020640-780cc39d5c78 10 May 2018 none MIT — Details →
v0.0.0-20180501142207-9e5bbcd7391d 01 May 2018 none MIT — Details →
v0.0.0-20180328130122-db0cf37600f2 28 Mar 2018 none MIT — Details →
v0.0.0-20171102151520-eafdab6b0663 02 Nov 2017 none MIT — Details →
v0.0.0-20171102151151-84ad96728f16 02 Nov 2017 none MIT — Details →
v0.0.0-20171031203403-89ca90e77cb1 31 Oct 2017 none MIT — Details →
v0.0.0-20160627004424-a22cb81b2ecd 27 Jun 2016 none MIT — Details →
v0.0.0-20160619133356-f460d783b1d3 19 Jun 2016 none MIT — Details →
v0.0.0-20160529215234-09242c19343a 29 May 2016 none MIT — Details →
v0.0.0-20160308165915-5a6c89841677 08 Mar 2016 none MIT — Details →
v0.0.0-20160304220245-621312d73859 04 Mar 2016 none MIT — Details →
v0.0.0-20160303214658-ff89b72240e6 03 Mar 2016 none MIT — Details →
v0.0.0-20160129215606-5fb7f48ad191 29 Jan 2016 none MIT — Details →
v0.0.0-20160129215309-54e42d230ca0 29 Jan 2016 none MIT — Details →
v0.0.0-20160128001150-58d135148764 28 Jan 2016 none MIT — Details →
v0.0.0-20160122161837-7d8c28acb67d 22 Jan 2016 none MIT — Details →
v0.0.0-20160121224034-05b1d2de1c1b 21 Jan 2016 none MIT — Details →
v0.0.0-20160119185929-24b6c156b2c7 19 Jan 2016 none MIT — Details →
v0.0.0-20160113203658-03b3d0ef0bc7 13 Jan 2016 none MIT — Details →
v0.0.0-20151223214605-3be29968aeea 23 Dec 2015 none MIT — Details →
v0.0.0-20151014153847-a9a908cd1d63 14 Oct 2015 none MIT — Details →
v0.0.0-20151006221533-0270356a6011 06 Oct 2015 none MIT — Details →
v0.0.0-20151005195621-bcad144b2dab 05 Oct 2015 none MIT — Details →
v0.0.0-20151001133842-441bbc2241de 01 Oct 2015 none MIT — Details →
v0.0.0-20150929224516-21a0630b2e76 29 Sep 2015 none MIT — Details →

All 36 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/nbutton23/zxcvbn-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/nbutton23/zxcvbn-go

Is github.com/nbutton23/zxcvbn-go safe to use?

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

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

No. v0.0.0-20210217022336-fa2cb2858354, 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/nbutton23/zxcvbn-go should I use?

v0.0.0-20210217022336-fa2cb2858354 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/nbutton23/zxcvbn-go have?

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

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

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