VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/tyler-smith/go-bip39: vulnerability history, versions and safety

github.com/tyler-smith/go-bip39 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/tyler-smith/go-bip39 vulnerabilities

Vulert verdict on github.com/tyler-smith/go-bip39 v1.1.0 i

Updated on 23 Oct 2026

Good news: v1.1.0, the version you would install today, has no known vulnerabilities.

Package health score 69/100
  • Security No known security issues
  • Maintenance Unmaintained
  • Popularity Widely used
  • Community Moderate

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

  • Current release v1.1.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 599 i
  • Last release 71 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/tyler-smith/go-bip39, 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.1.1-0.20240817025351-0e52848eb5b9 17 Aug 2024 none MIT — Details →
v1.1.1-0.20201101231310-6e546c9b3866 01 Nov 2020 none MIT — Details →
v1.1.1-0.20201101231254-62bdbaef449d 01 Nov 2020 none MIT — Details →
v0.0.0-20201031083441-3423700f9707 31 Oct 2020 none MIT — Details →
v1.1.1-0.20201031083441-3423700f9707 31 Oct 2020 none MIT — Details →
v1.1.1-0.20201031065300-1527c01e5c8d 31 Oct 2020 none MIT — Details →
v1.1.1-0.20201031033336-417fda22e849 31 Oct 2020 none MIT — Details →
v1.1.0 27 Oct 2020 none MIT — Details →
v1.0.1-0.20200709125526-657025c35705 09 Jul 2020 none MIT — Details →
v0.0.0-20190808214741-c55f737395bc 08 Aug 2019 none MIT — Details →
v1.0.1-0.20190808214741-c55f737395bc 08 Aug 2019 none MIT — Details →
v1.0.2 08 Aug 2019 none MIT — Details →
v0.0.0-20181017060643-dbb3b84ba2ef 17 Oct 2018 none MIT — Details →
v1.0.1-0.20181017060643-dbb3b84ba2ef 17 Oct 2018 none MIT — Details →
v1.0.1-0.20181017040744-1b0988f87d25 17 Oct 2018 none MIT — Details →
v1.0.0-cli-test7 31 Jul 2018 none MIT — Details →
v1.0.0-cli-test6 31 Jul 2018 none MIT — Details →
v1.0.0-cli-test5 31 Jul 2018 none MIT — Details →
v1.0.0-cli-test4 26 Jul 2018 none MIT — Details →
v0.0.0-20180716170310-95c66720ed7a 16 Jul 2018 none MIT — Details →
v1.0.1-0.20180716170310-95c66720ed7a 16 Jul 2018 none MIT — Details →
v1.0.1-0.20180716060938-052384f652b2 16 Jul 2018 none MIT — Details →
v1.0.1-0.20180716060759-32de002caadb 16 Jul 2018 none MIT — Details →
v1.0.1-0.20180714215412-1f6c1d807838 14 Jul 2018 none MIT — Details →
v1.0.1-0.20180714213626-59d8316ef5f4 14 Jul 2018 none MIT — Details →
v1.0.0 12 Jul 2018 none MIT — Details →
v0.4.0 12 Jul 2018 none MIT — Details →
v0.3.7-0.20180711223827-bd5cb2296001 11 Jul 2018 none MIT — Details →
v0.3.7-0.20180711223654-c9b51a05c144 11 Jul 2018 none MIT — Details →
v0.3.7-0.20180711223653-54a5b75036e7 11 Jul 2018 none MIT — Details →
v0.3.6 11 Jul 2018 none MIT — Details →
v0.0.0-20180623154338-23d06dbb56b3 23 Jun 2018 none MIT — Details →
v0.0.0-20180618194314-52158e4697b8 18 Jun 2018 none MIT — Details →
v0.0.0-20171110180951-072ae48d147c 10 Nov 2017 none MIT — Details →
v0.0.0-20160629163856-8e7a99b3e716 29 Jun 2016 none MIT — Details →
v0.0.0-20160308201226-32e294b638a7 08 Mar 2016 none MIT — Details →
v0.0.0-20150831215253-24c3f2806d38 31 Aug 2015 none MIT — Details →
v0.0.0-20150408230442-08cc76846b45 08 Apr 2015 none MIT — Details →
v0.0.0-20140803005907-4c8dcfbfb90f 03 Aug 2014 none MIT — Details →

All 39 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/tyler-smith/go-bip39

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/tyler-smith/go-bip39

Is github.com/tyler-smith/go-bip39 safe to use?

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

Vulert scores github.com/tyler-smith/go-bip39 69/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/tyler-smith/go-bip39 affected?

No. v1.1.0, 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/tyler-smith/go-bip39 should I use?

v1.1.0 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/tyler-smith/go-bip39 have?

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

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

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