VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/ipfs/go-ds-badger2: vulnerability history, versions and safety

github.com/ipfs/go-ds-badger2 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/ipfs/go-ds-badger2 vulnerabilities

Vulert verdict on github.com/ipfs/go-ds-badger2 v0.1.5 i

Updated on 23 Oct 2026

Good news: v0.1.5, the version you would install today, has no known vulnerabilities.

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

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

  • Current release v0.1.5 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 14 i
  • OpenSSF scorecard 3/10 i
  • Last release 19 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/ipfs/go-ds-badger2, 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.1.6-0.20250318162953-816e1415c875 18 Mar 2025 none MIT — Details →
v0.1.5 04 Mar 2025 none MIT — Details →
v0.1.4 01 Mar 2025 none MIT — Details →
v0.1.4-0.20240322125434-390c03068350 22 Mar 2024 none MIT — Details →
v0.1.4-0.20240131173453-b26acbfe9b59 31 Jan 2024 none MIT — Details →
v0.1.4-0.20230815103954-a849ad43c3a9 15 Aug 2023 none MIT — Details →
v0.1.4-0.20230628085045-3837c5bba6b8 28 Jun 2023 none MIT — Details →
v0.1.4-0.20220721095641-fe9999cf93c6 21 Jul 2022 none MIT — Details →
v0.1.4-0.20220406110150-0f442ca9c4c0 06 Apr 2022 none MIT — Details →
v0.1.3 26 Jan 2022 none MIT — Details →
v0.1.3-0.20220125211402-3e3d4e05f2e7 25 Jan 2022 none MIT — Details →
v0.1.3-0.20220121203153-a6e25f0857c9 21 Jan 2022 none MIT — Details →
v0.1.3-0.20211220201324-fc3db18d8b8f 20 Dec 2021 none MIT — Details →
v0.1.2-0.20211203191834-bc6df5c2417c 03 Dec 2021 none MIT — Details →
v0.1.3-0.20211203191834-bc6df5c2417c 03 Dec 2021 none MIT — Details →
v0.1.2-0.20211126133957-2bc0150c7534 26 Nov 2021 none MIT — Details →
v0.1.3-0.20211126133957-2bc0150c7534 26 Nov 2021 none MIT — Details →
v0.1.2 19 Nov 2021 none MIT — Details →
v0.1.2-0.20211119002906-7318f1b76158 19 Nov 2021 none MIT — Details →
v0.1.1 23 Jul 2021 none MIT — Details →
v0.1.1-0.20201009224942-a4499bb2f243 09 Oct 2020 none MIT — Details →
v0.1.1-0.20201005172105-8fe207b8dc7e 05 Oct 2020 none MIT — Details →
v0.1.1-0.20200930015122-da4821a7ffe4 30 Sep 2020 none MIT — Details →
v0.1.1-0.20200929230640-9a3bc4da85ed 29 Sep 2020 none MIT — Details →
v0.1.1-0.20200708190120-187fc06f714e 08 Jul 2020 none MIT — Details →
v0.1.1-0.20200708184045-90bb0a4381e0 08 Jul 2020 none MIT — Details →
v0.1.1-0.20200708183936-90e84e2bdd73 08 Jul 2020 none MIT — Details →
v0.1.0 16 Apr 2020 none MIT — Details →
v0.0.0-20200211201106-609c9d2a39c7 11 Feb 2020 none MIT — Details →
v0.0.0-20200210153246-17ad413ffade 10 Feb 2020 none MIT — Details →
v0.0.0-20200129055420-9ed3556ef1cb 29 Jan 2020 none MIT — Details →
v0.0.0-20200123200730-d75eb2678a5d 23 Jan 2020 none MIT — Details →
v0.0.0-20200108185345-7f650e6b2521 08 Jan 2020 none MIT — Details →

All 33 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/ipfs/go-ds-badger2

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/ipfs/go-ds-badger2

Is github.com/ipfs/go-ds-badger2 safe to use?

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

Vulert scores github.com/ipfs/go-ds-badger2 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/ipfs/go-ds-badger2 affected?

No. v0.1.5, 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/ipfs/go-ds-badger2 should I use?

v0.1.5 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/ipfs/go-ds-badger2 have?

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

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

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