Vulnerability Database · Go · Package report
github.com/dennwc/btrfs: vulnerability history, versions and safety
github.com/dennwc/btrfs is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on github.com/dennwc/btrfs v0.0.0-20260222081608-edfb8b9e4f55 i
Updated on 23 Oct 2026
Good news: v0.0.0-20260222081608-edfb8b9e4f55, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Niche
- Community Inactive
What to do: Stay on v0.0.0-20260222081608-edfb8b9e4f55 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20260222081608-edfb8b9e4f55 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20260222081608-edfb8b9e4f55 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 71 i
- OpenSSF scorecard 1/10 i
- Last release 8 months ago i
- Licence Apache-2.0 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/dennwc/btrfs, 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.
- v0.0.0-20260222081608-edfb8b9e4f55 22 Feb 2026
- v0.0.0-20260221084536-a7c0e15b15a1 21 Feb 2026
- v0.0.0-20260220093445-f14aea5cf267 20 Feb 2026
- v0.0.0-20260218124101-0ad32fb2fcba 18 Feb 2026
- v0.0.0-20241002142654-12ae127e0bf6 02 Oct 2024
- v0.0.0-20240418142341-0167142bde7a 18 Apr 2024
- v0.0.0-20230312211831-a1f570bd01a1 12 Mar 2023
- v0.0.0-20221026161108-3097362dc072 26 Oct 2022
- v0.0.0-20220403080356-b3db0b2dedac 03 Apr 2022
- v0.0.0-20210629195749-90a0320aae50 29 Jun 2021
- v0.0.0-20210625083239-ee67271a4cb4 25 Jun 2021
- v0.0.0-20190517175702-d917b30ff035 17 May 2019
- v0.0.0-20181021180244-694b569856e3 21 Oct 2018
All 13 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/dennwc/btrfs
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
Questions
About github.com/dennwc/btrfs
Is github.com/dennwc/btrfs safe to use?
Vulert has no vulnerabilities on record for github.com/dennwc/btrfs 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/dennwc/btrfs's Vulert package health score?
Vulert scores github.com/dennwc/btrfs 64/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/dennwc/btrfs affected?
No. v0.0.0-20260222081608-edfb8b9e4f55, 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/dennwc/btrfs should I use?
v0.0.0-20260222081608-edfb8b9e4f55 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/dennwc/btrfs have?
0 vulnerabilities are recorded for github.com/dennwc/btrfs 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/dennwc/btrfs vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/dennwc/btrfs 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/dennwc/btrfs 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/dennwc/btrfs for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/dennwc/btrfs version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.