Vulnerability Database · Go · Package report

github.com/breml/bidichk: vulnerability history, versions and safety

github.com/breml/bidichk 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/breml/bidichk v0.3.4 i

Updated on 23 Oct 2026

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

Package health score 65/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v0.3.4 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 42 i
  • OpenSSF scorecard 2/10 i
  • Last release this month 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/breml/bidichk, 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.3.5-0.20261014202900-abe6de122631 14 Oct 2026 none MIT — Details →
v0.3.4 07 Oct 2026 none MIT — Details →
v0.3.4-0.20250812065118-2a2147d783b1 12 Aug 2025 none MIT — Details →
v0.3.4-0.20250715193904-2f9372d22618 15 Jul 2025 none MIT — Details →
v0.3.4-0.20250611183731-a57d9ae389da 11 Jun 2025 none MIT — Details →
v0.3.4-0.20250506085930-819075d8817e 06 May 2025 none MIT — Details →
v0.3.3 12 Mar 2025 none MIT — Details →
v0.3.3-0.20250211191028-c948da16f8e4 11 Feb 2025 none MIT — Details →
v0.3.3-0.20250107203558-c845d2f436f3 07 Jan 2025 none MIT — Details →
v0.3.3-0.20241211142649-85b3549f264d 11 Dec 2024 none MIT — Details →
v0.3.3-0.20241116142924-e39a7f0bba33 16 Nov 2024 none MIT — Details →
v0.3.2 16 Oct 2024 none MIT — Details →
v0.3.2-0.20241016201723-5f0e2cff589e 16 Oct 2024 none MIT — Details →
v0.3.2-0.20241007224043-e26e0e0b779f 07 Oct 2024 none MIT — Details →
v0.3.2-0.20240912195212-871cd0ab9e6d 12 Sep 2024 none MIT — Details →
v0.3.1 12 Sep 2024 none MIT — Details →
v0.3.0 12 Sep 2024 none MIT — Details →
v0.2.8-0.20240813182851-9a97f352abeb 13 Aug 2024 none MIT — Details →
v0.2.8-0.20240712194749-26885e877ce6 12 Jul 2024 none MIT — Details →
v0.2.8-0.20240611194749-8d1fbc662dfd 11 Jun 2024 none MIT — Details →
v0.2.8-0.20240507195837-81b1d27556cd 07 May 2024 none MIT — Details →
v0.2.8-0.20240413134936-6ef60e4f2219 13 Apr 2024 none MIT — Details →
v0.2.8-0.20240314192355-661fad6dbfdf 14 Mar 2024 none MIT — Details →
v0.2.8-0.20240229173113-1d6c399472d3 29 Feb 2024 none MIT — Details →
v0.2.8-0.20240117203611-c99cf5be38b5 17 Jan 2024 none MIT — Details →
v0.2.8-0.20231219203308-25f72ef9cea7 19 Dec 2023 none MIT — Details →
v0.2.8-0.20231129193309-b86bd60e8844 29 Nov 2023 none MIT — Details →
v0.2.8-0.20231120202916-22188b0dd36f 20 Nov 2023 none MIT — Details →
v0.2.8-0.20231114153645-979208a1763f 14 Nov 2023 none MIT — Details →
v0.2.8-0.20231010050224-b2432cacbddc 10 Oct 2023 none MIT — Details →
v0.2.7 19 Sep 2023 none MIT — Details →
v0.2.7-0.20230919171138-4c2970c4201e 19 Sep 2023 none MIT — Details →
v0.2.7-0.20230912051623-4014131fd30a 12 Sep 2023 none MIT — Details →
v0.2.7-0.20230911223308-f3f078dd318a 11 Sep 2023 none MIT — Details →
v0.2.6 26 Aug 2023 none MIT — Details →
v0.2.6-0.20230826121924-d966dc36bc84 26 Aug 2023 none MIT — Details →
v0.2.5 26 Aug 2023 none MIT — Details →
v0.2.5-0.20230620190031-8112759fcc82 20 Jun 2023 none MIT — Details →
v0.2.5-0.20230606185755-621f21d9b295 06 Jun 2023 none MIT — Details →
v0.2.5-0.20230530194037-230e18d426e0 30 May 2023 none MIT — Details →
v0.2.5-0.20230530193226-529323916ec8 30 May 2023 none MIT — Details →
v0.2.5-0.20230519084432-494695b386f4 19 May 2023 none MIT — Details →
v0.2.5-0.20230411192103-e81a2e34f8e7 11 Apr 2023 none MIT — Details →
v0.2.5-0.20230410230318-ce2e6e77ccff 10 Apr 2023 none MIT — Details →
v0.2.4 12 Mar 2023 none MIT — Details →
v0.2.4-0.20230312112231-2ca26a9bfd34 12 Mar 2023 none MIT — Details →
v0.2.4-0.20221001201535-62ef9e403e9d 01 Oct 2022 none MIT — Details →
v0.2.3 25 Mar 2022 none MIT — Details →
v0.2.2 08 Feb 2022 none MIT — Details →
v0.2.1 06 Nov 2021 none MIT — Details →
v0.2.1-0.20211106063815-e0c4c4ff9cf7 06 Nov 2021 none MIT — Details →
v0.2.0 05 Nov 2021 none MIT — Details →
v0.1.2-0.20211105203611-c871de864cdf 05 Nov 2021 none MIT — Details →
v0.1.2-0.20211105203234-c3567280b8a3 05 Nov 2021 none MIT — Details →
v0.1.1 02 Nov 2021 none MIT — Details →
v0.0.0-20211101220604-4726ab759ea3 01 Nov 2021 none MIT — Details →
v0.1.0 01 Nov 2021 none MIT — Details →
v0.0.0-20211101215529-9b68d04c240e 01 Nov 2021 none MIT — Details →
v0.0.0-20211101211321-e7013e04fb35 01 Nov 2021 none MIT — Details →

All 59 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/breml/bidichk

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/breml/bidichk

Is github.com/breml/bidichk safe to use?

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

Vulert scores github.com/breml/bidichk 65/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/breml/bidichk affected?

No. v0.3.4, 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/breml/bidichk should I use?

v0.3.4 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/breml/bidichk have?

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

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

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