VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/gen2brain/beeep: vulnerability history, versions and safety

github.com/gen2brain/beeep 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/gen2brain/beeep vulnerabilities

Vulert verdict on github.com/gen2brain/beeep v0.11.3 i

Updated on 23 Oct 2026

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

Package health score 78/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release v0.11.3 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,770 i
  • OpenSSF scorecard 2/10 i
  • Last release this month i
  • Licence BSD-2-Clause 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/gen2brain/beeep, 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.11.3 20 Oct 2026 none BSD-2-Clause — Details →
v0.0.0-20251211124340-ab78edd6bb10 11 Dec 2025 none BSD-2-Clause — Details →
v0.11.2 11 Dec 2025 none BSD-2-Clause — Details →
v0.0.0-20250616101831-d3081115491c 16 Jun 2025 none BSD-2-Clause — Details →
v0.11.1 16 Jun 2025 none BSD-2-Clause — Details →
v0.11.0 12 Jun 2025 none BSD-2-Clause — Details →
v0.0.0-20250611201336-9e7a423263cc 11 Jun 2025 none BSD-2-Clause — Details →
v0.10.0 11 Jun 2025 none BSD-2-Clause — Details →
v0.0.0-20250611201237-1ad3b3f9d9de 11 Jun 2025 none BSD-2-Clause — Details →
v0.0.0-20250610192652-6ed72bba6ca0 10 Jun 2025 none BSD-2-Clause — Details →
v0.0.0-20240516210008-9c006672e7f4 16 May 2024 none BSD-2-Clause — Details →
v0.0.0-20240112042604-c7bb2cd88fea 12 Jan 2024 none BSD-2-Clause — Details →
v0.0.0-20240111162928-58fd03cb545c 11 Jan 2024 none BSD-2-Clause — Details →
v0.0.0-20230907135156-1a38885a97fc 07 Sep 2023 none BSD-2-Clause — Details →
v0.0.0-20230812223410-3e1549ef0811 12 Aug 2023 none BSD-2-Clause — Details →
v0.0.0-20230812223359-b45d012acd9a 12 Aug 2023 none BSD-2-Clause — Details →
v0.0.0-20230602101333-f384c29b62dd 02 Jun 2023 none BSD-2-Clause — Details →
v0.0.0-20230307103607-6e717729cb4f 07 Mar 2023 none BSD-2-Clause — Details →
v0.0.0-20220909211152-5a9ec94374f6 09 Sep 2022 none BSD-2-Clause — Details →
v0.0.0-20220518085355-d7852edf42fc 18 May 2022 none BSD-2-Clause — Details →
v0.0.0-20220402123239-6a3042f4b71a 02 Apr 2022 none BSD-2-Clause — Details →
v0.0.0-20220331123900-142b39fbecaf 31 Mar 2022 none BSD-2-Clause — Details →
v0.0.0-20220322123227-629384b5779c 22 Mar 2022 none BSD-2-Clause — Details →
v0.0.0-20210529141713-5586760f0cc1 29 May 2021 none BSD-2-Clause — Details →
v0.0.0-20210529075721-d288f509e492 29 May 2021 none BSD-2-Clause — Details →
v0.0.0-20200526185328-e9c15c258e28 26 May 2020 none BSD-2-Clause — Details →
v0.0.0-20200526175003-a39c83093cdc 26 May 2020 none BSD-2-Clause — Details →
v0.0.0-20200420150314-13046a26d502 20 Apr 2020 none BSD-2-Clause — Details →
v0.0.0-20200305193625-ff0f4a39397e 05 Mar 2020 none BSD-2-Clause — Details →
v0.0.0-20200131162055-1f001e98c9e1 31 Jan 2020 none BSD-2-Clause — Details →
v0.0.0-20200131084056-12264767908e 31 Jan 2020 none BSD-2-Clause — Details →
v0.0.0-20190719094215-ece0cb67ca77 19 Jul 2019 none BSD-2-Clause — Details →
v0.0.0-20190719093626-599a89af5189 19 Jul 2019 none BSD-2-Clause — Details →
v0.0.0-20190603194150-07ff5e574111 03 Jun 2019 none BSD-2-Clause — Details →
v0.0.0-20190602215359-780b3b8eb88c 02 Jun 2019 none BSD-2-Clause — Details →
v0.0.0-20190317152856-aa3d7c1499fd 17 Mar 2019 none BSD-2-Clause — Details →
v0.0.0-20190317145426-1d421a9af66a 17 Mar 2019 none BSD-2-Clause — Details →
v0.0.0-20190226134152-2cb437b15ebe 26 Feb 2019 none BSD-2-Clause — Details →
v0.0.0-20190213053753-3c525818aff0 13 Feb 2019 none BSD-2-Clause — Details →
v0.0.0-20180718162406-4e430518395f 18 Jul 2018 none BSD-2-Clause — Details →
v0.0.0-20180702145955-ca431f21ed04 02 Jul 2018 none BSD-2-Clause — Details →
v0.0.0-20180629122927-86120b2972b3 29 Jun 2018 none BSD-2-Clause — Details →
v0.0.0-20180629115304-c46b7c026a22 29 Jun 2018 none BSD-2-Clause — Details →
v0.0.0-20180415130043-b98497f37c80 15 Apr 2018 none BSD-2-Clause — Details →
v0.0.0-20180415112712-9c833b762c46 15 Apr 2018 none BSD-2-Clause — Details →
v0.0.0-20180209034106-982e34175ed3 09 Feb 2018 none BSD-2-Clause — Details →
v0.0.0-20180209032327-42ba3d86083a 09 Feb 2018 none BSD-2-Clause — Details →
v0.0.0-20180111122706-6c0b03e27760 11 Jan 2018 none BSD-2-Clause — Details →
v0.0.0-20171212191350-50a63a26474c 12 Dec 2017 none BSD-2-Clause — Details →
v0.0.0-20171211091503-18c2053ded48 11 Dec 2017 none BSD-2-Clause — Details →

All 50 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/gen2brain/beeep

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/gen2brain/beeep

Is github.com/gen2brain/beeep safe to use?

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

Vulert scores github.com/gen2brain/beeep 78/100, which reads as in good shape. 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/gen2brain/beeep affected?

No. v0.11.3, 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.

How many vulnerabilities does github.com/gen2brain/beeep have?

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

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

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