VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/btcsuite/btclog: vulnerability history, versions and safety

github.com/btcsuite/btclog 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/btcsuite/btclog vulnerabilities

Vulert verdict on github.com/btcsuite/btclog v1.0.0 i

Updated on 23 Oct 2026

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

Package health score 58/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Quiet

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

  • Current release v1.0.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 25 i
  • OpenSSF scorecard 2/10 i
  • Last release 24 months ago i
  • Licence ISC 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/btcsuite/btclog, 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-20251104021119-45b2a330758d 04 Nov 2025 none ISC — Details →
v1.0.1-0.20251104021119-45b2a330758d 04 Nov 2025 none ISC — Details →
v0.0.0-20250728225537-6090e87c6c5b 28 Jul 2025 none ISC — Details →
v1.0.1-0.20250728225537-6090e87c6c5b 28 Jul 2025 none ISC — Details →
v1.0.1-0.20250724141616-28e42d275d46 24 Jul 2025 none ISC — Details →
v1.0.1-0.20250602222548-9967d19bb084 02 Jun 2025 none ISC — Details →
v1.0.1-0.20250207005031-f8e212ae7f5a 07 Feb 2025 none ISC — Details →
v1.0.1-0.20250202044341-9c45c9bcd78e 02 Feb 2025 none ISC — Details →
v1.0.1-0.20250110154127-3ae4bf1cb318 10 Jan 2025 none ISC — Details →
v1.0.1-0.20241210103131-0ace8f51fb60 10 Dec 2024 none ISC — Details →
v0.0.0-20241127020708-e4cba5de17df 27 Nov 2024 none ISC — Details →
v1.0.1-0.20241127020708-e4cba5de17df 27 Nov 2024 none ISC — Details →
v1.0.1-0.20241126071913-21ac47203798 26 Nov 2024 none ISC — Details →
v0.0.0-20241017175713-3428138b75c7 17 Oct 2024 none ISC — Details →
v1.0.1-0.20241017175713-3428138b75c7 17 Oct 2024 none ISC — Details →
v1.0.1-0.20241017080329-66304edcc856 17 Oct 2024 none ISC — Details →
v0.0.0-20241003133417-09c4e92e319c 03 Oct 2024 none ISC — Details →
v1.0.0 03 Oct 2024 none ISC — Details →
v0.0.0-20170628155309-84c8d2346e9f 28 Jun 2017 none ISC — Details →
v0.0.0-20170620135537-30bef3d5a6b4 20 Jun 2017 none ISC — Details →
v0.0.0-20170620000549-266a29b6e5ad 20 Jun 2017 none ISC — Details →
v0.0.0-20170619204223-96c2a91a67da 19 Jun 2017 none ISC — Details →
v0.0.0-20170525175852-1dfb68239632 25 May 2017 none ISC — Details →
v0.0.0-20160817181405-73889fb79bd6 17 Aug 2016 none ISC — Details →
v0.0.0-20160812014556-68a4060bdfd8 12 Aug 2016 none ISC — Details →
v0.0.0-20160407183224-f96df2375f37 07 Apr 2016 none ISC — Details →
v0.0.0-20150501171603-5005b7240f31 01 May 2015 none ISC — Details →
v0.0.0-20150227182536-baa3c5ace990 27 Feb 2015 none ISC — Details →
v0.0.0-20150226182145-5e232556c06b 26 Feb 2015 none ISC — Details →
v0.0.0-20150116171115-53d016a62ec5 16 Jan 2015 none ISC — Details →
v0.0.0-20150116042208-b71bb99a90ea 16 Jan 2015 none ISC — Details →
v0.0.0-20140912201131-7e65e0a3e1fe 12 Sep 2014 none ISC — Details →
v0.0.0-20140703004151-8ab6c88bcd06 03 Jul 2014 none ISC — Details →
v0.0.0-20140314195727-9caaed73fd7b 14 Mar 2014 none ISC — Details →
v0.0.0-20140109055027-1cd4812f9be0 09 Jan 2014 none ISC — Details →
v0.0.0-20131211000256-fa3217f76bac 11 Dec 2013 none ISC — Details →
v0.0.0-20131122010945-f8b005c0a71a 22 Nov 2013 none ISC — Details →
v0.0.0-20131121195803-13bd6ec361c4 21 Nov 2013 none ISC — Details →

All 38 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/btcsuite/btclog

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/btcsuite/btclog

Is github.com/btcsuite/btclog safe to use?

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

Vulert scores github.com/btcsuite/btclog 58/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/btcsuite/btclog affected?

No. v1.0.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/btcsuite/btclog should I use?

v1.0.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/btcsuite/btclog have?

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

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

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