Vulnerability Database · Go · Package report

github.com/mistifyio/go-zfs: vulnerability history, versions and safety

github.com/mistifyio/go-zfs 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.

Vulert verdict on github.com/mistifyio/go-zfs v2.1.1+incompatible i

Updated on 23 Oct 2026

Good news: v2.1.1+incompatible, the version you would install today, has no known vulnerabilities.

Package health score 52/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Niche
  • Community Quiet

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

  • Current release v2.1.1+incompatible — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 138 i
  • OpenSSF scorecard 3/10 i
  • Last release 136 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/mistifyio/go-zfs, 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.0.1-0.20210521130936-d3ead99562a8 21 May 2021 none Apache-2.0 — Details →
v2.1.2-0.20210521130936-d3ead99562a8+incompatible 21 May 2021 none Apache-2.0 — Details →
v2.1.1-0.20191106125213-c6a6a34a207d+incompatible 06 Nov 2019 none Apache-2.0 — Details →
v2.1.2-0.20191106125213-c6a6a34a207d+incompatible 06 Nov 2019 none Apache-2.0 — Details →
v0.0.0-20190413222219-f784269be439 13 Apr 2019 none Apache-2.0 — Details →
v1.0.1-0.20190413222219-f784269be439 13 Apr 2019 none Apache-2.0 — Details →
v2.1.1-0.20190413222219-f784269be439+incompatible 13 Apr 2019 none Apache-2.0 — Details →
v2.1.2-0.20190413222219-f784269be439+incompatible 13 Apr 2019 none Apache-2.0 — Details →
v2.1.2-0.20190318212943-b6cafe7fb92e+incompatible 18 Mar 2019 none Apache-2.0 — Details →
v0.0.0-20180321011823-d5b163290a48 21 Mar 2018 none Apache-2.0 — Details →
v1.0.1-0.20180321011823-d5b163290a48 21 Mar 2018 none Apache-2.0 — Details →
v2.1.2-0.20180321011823-d5b163290a48+incompatible 21 Mar 2018 none Apache-2.0 — Details →
v2.1.2-0.20180321011541-91939dc75c54+incompatible 21 Mar 2018 none Apache-2.0 — Details →
v2.1.2-0.20180312032512-7c306044d02e+incompatible 12 Mar 2018 none Apache-2.0 — Details →
v2.1.2-0.20180312023828-21d369c0679f+incompatible 12 Mar 2018 none Apache-2.0 — Details →
v2.1.2-0.20180312022635-ebadc9b651b2+incompatible 12 Mar 2018 none Apache-2.0 — Details →
v0.0.0-20171122051224-166add352731 22 Nov 2017 none Apache-2.0 — Details →
v2.1.2-0.20171122051224-166add352731+incompatible 22 Nov 2017 none Apache-2.0 — Details →
v2.1.2-0.20171122050129-0883fc6ec790+incompatible 22 Nov 2017 none Apache-2.0 — Details →
v2.1.2-0.20171122050129-0c4a6b3c8bb1+incompatible 22 Nov 2017 none Apache-2.0 — Details →
v2.1.2-0.20171121035256-736f44e13893+incompatible 21 Nov 2017 none Apache-2.0 — Details →
v0.0.0-20170901132433-166dd29edf05 01 Sep 2017 none Apache-2.0 — Details →
v1.0.1-0.20170901132433-166dd29edf05 01 Sep 2017 none Apache-2.0 — Details →
v2.1.2-0.20170901132433-166dd29edf05+incompatible 01 Sep 2017 none Apache-2.0 — Details →
v2.1.2-0.20170901084707-0f809be04a72+incompatible 01 Sep 2017 none Apache-2.0 — Details →
v2.1.2-0.20170517204310-386bffe89f42+incompatible 17 May 2017 none Apache-2.0 — Details →
v2.1.2-0.20170517195450-592e27cc8541+incompatible 17 May 2017 none Apache-2.0 — Details →
v2.1.2-0.20170206193830-def8a0433d44+incompatible 06 Feb 2017 none Apache-2.0 — Details →
v2.1.2-0.20161212162346-a072d3320073+incompatible 12 Dec 2016 none Apache-2.0 — Details →
v2.1.2-0.20161208094419-4a9c7e5cde4c+incompatible 08 Dec 2016 none Apache-2.0 — Details →
v0.0.0-20161103015429-c0224de804d4 03 Nov 2016 none Apache-2.0 — Details →
v2.1.2-0.20161103015429-c0224de804d4+incompatible 03 Nov 2016 none Apache-2.0 — Details →
v2.1.2-0.20161024115038-effac785698f+incompatible 24 Oct 2016 none Apache-2.0 — Details →
v2.1.2-0.20161023022307-8b82d2e702d3+incompatible 23 Oct 2016 none Apache-2.0 — Details →
v2.1.2-0.20161021000423-d39fcc7ff816+incompatible 21 Oct 2016 none Apache-2.0 — Details →
v2.1.2-0.20161020215312-44a61d108b4a+incompatible 20 Oct 2016 none Apache-2.0 — Details →
v2.1.2-0.20161020215040-8059e2078938+incompatible 20 Oct 2016 none Apache-2.0 — Details →
v0.0.0-20160425201758-22c9b32c84eb 25 Apr 2016 none Apache-2.0 — Details →
v1.0.1-0.20160425201758-22c9b32c84eb 25 Apr 2016 none Apache-2.0 — Details →
v2.1.2-0.20160425201758-22c9b32c84eb+incompatible 25 Apr 2016 none Apache-2.0 — Details →
v2.1.2-0.20160425193917-ae41c47571ab+incompatible 25 Apr 2016 none Apache-2.0 — Details →
v0.0.0-20160331203038-67e6c1df1c39 31 Mar 2016 none Apache-2.0 — Details →
v2.1.2-0.20160331203038-67e6c1df1c39+incompatible 31 Mar 2016 none Apache-2.0 — Details →
v2.1.2-0.20160328220935-f61b635089dc+incompatible 28 Mar 2016 none Apache-2.0 — Details →
v2.1.2-0.20160211153403-16f923e29c02+incompatible 11 Feb 2016 none Apache-2.0 — Details →
v2.1.2-0.20160211153327-35ad200fe18b+incompatible 11 Feb 2016 none Apache-2.0 — Details →
v2.1.2-0.20160210034200-8f7de5af3b1e+incompatible 10 Feb 2016 none Apache-2.0 — Details →
v2.1.2-0.20160209231755-16b13ca84978+incompatible 09 Feb 2016 none Apache-2.0 — Details →
v2.1.2-0.20160209231532-10ff60b63f4a+incompatible 09 Feb 2016 none Apache-2.0 — Details →
v2.1.2-0.20160209231431-76d77cd013c0+incompatible 09 Feb 2016 none Apache-2.0 — Details →
v2.1.2-0.20160209231431-b9ed2684837e+incompatible 09 Feb 2016 none Apache-2.0 — Details →
v2.1.2-0.20160209231431-c0490e6af84a+incompatible 09 Feb 2016 none Apache-2.0 — Details →
v0.0.0-20151009155749-1b4ae6fb4e77 09 Oct 2015 none Apache-2.0 — Details →
v1.0.1-0.20151009155749-1b4ae6fb4e77 09 Oct 2015 none Apache-2.0 — Details →
v2.1.2-0.20151009155749-1b4ae6fb4e77+incompatible 09 Oct 2015 none Apache-2.0 — Details →
v2.1.2-0.20151006152814-6a527b482944+incompatible 06 Oct 2015 none Apache-2.0 — Details →
v2.1.2-0.20150902162840-d60a9acae042+incompatible 02 Sep 2015 none Apache-2.0 — Details →
v2.1.2-0.20150902161338-234bbd3b7292+incompatible 02 Sep 2015 none Apache-2.0 — Details →
v2.1.2-0.20150902160713-5e2d1e0637fe+incompatible 02 Sep 2015 none Apache-2.0 — Details →
v0.0.0-20150529142751-cdc0f941c4d0 29 May 2015 none Apache-2.0 — Details →
v2.1.1+incompatible 29 May 2015 none Apache-2.0 — Details →
v2.1.1-0.20150526154046-ee0b8834f2ed+incompatible 26 May 2015 none Apache-2.0 — Details →
v2.1.1-0.20150126153638-695450312eea+incompatible 26 Jan 2015 none Apache-2.0 — Details →
v2.1.1-0.20150116141932-049a637cbce9+incompatible 16 Jan 2015 none Apache-2.0 — Details →
v0.0.0-20141209150540-dda1f4cd04dc 09 Dec 2014 none Apache-2.0 — Details →
v1.0.1-0.20141209150540-dda1f4cd04dc 09 Dec 2014 none Apache-2.0 — Details →
v2.1.1-0.20141209150540-dda1f4cd04dc+incompatible 09 Dec 2014 none Apache-2.0 — Details →
v2.1.1-0.20141209150155-5790c4a93c10+incompatible 09 Dec 2014 none Apache-2.0 — Details →
v2.1.0+incompatible 08 Dec 2014 none Apache-2.0 — Details →
v2.0.1-0.20141208212939-196ab1380ac4+incompatible 08 Dec 2014 none Apache-2.0 — Details →
v2.0.1-0.20141202113953-1140792fafce+incompatible 02 Dec 2014 none Apache-2.0 — Details →
v2.0.0+incompatible 02 Dec 2014 none Apache-2.0 — Details →
v1.0.1-0.20141201152314-c51af95e09a4 01 Dec 2014 none Apache-2.0 — Details →
v1.0.1-0.20141130115431-b21e11a74796 30 Nov 2014 none Apache-2.0 — Details →
v1.0.1-0.20141129155311-129db50d27e1 29 Nov 2014 none Apache-2.0 — Details →
v1.0.1-0.20141124140345-13c517ec4af6 24 Nov 2014 none Apache-2.0 — Details →
v1.0.1-0.20141114133448-b62505bc019d 14 Nov 2014 none Apache-2.0 — Details →
v1.0.0 12 Nov 2014 none Apache-2.0 — Details →
v0.0.1-0.20141024172009-d956b54681ec 24 Oct 2014 none Apache-2.0 — Details →
v0.0.1-0.20140905205558-18bd80b5e2ce 05 Sep 2014 none Apache-2.0 — Details →
v0.0.1-0.20140904160537-68e05089ea3b 04 Sep 2014 none Apache-2.0 — Details →
v0.0.0 15 Aug 2014 none Apache-2.0 — Details →

All 82 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/mistifyio/go-zfs

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/mistifyio/go-zfs

Is github.com/mistifyio/go-zfs safe to use?

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

Vulert scores github.com/mistifyio/go-zfs 52/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/mistifyio/go-zfs affected?

No. v2.1.1+incompatible, 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/mistifyio/go-zfs should I use?

v2.1.1+incompatible 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/mistifyio/go-zfs have?

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

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

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