Vulnerability Database · Go · Package report
github.com/cretz/bine: vulnerability history, versions and safety
github.com/cretz/bine 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/cretz/bine v0.2.0 i
Updated on 23 Oct 2026
Good news: v0.2.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Widely used
- Community Inactive
What to do: Stay on v0.2.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.2.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.2.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 829 i
- OpenSSF scorecard 1/10 i
- Last release 64 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/cretz/bine, 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.2.1-0.20230307004429-0c9b48b8a2bd 07 Mar 2023
- v0.0.0-20221201125941-b9d31d9c7866 01 Dec 2022
- v0.2.1-0.20221201125941-b9d31d9c7866 01 Dec 2022
- v0.0.0-20220825052916-cb1f9e88dfba 25 Aug 2022
- v0.2.1-0.20220825052916-cb1f9e88dfba 25 Aug 2022
- v0.2.1-0.20220711123706-2b906e69c081 11 Jul 2022
- v0.2.1-0.20220701110934-a15773336e96 01 Jul 2022
- v0.0.0-20220211152646-874b17b5a830 11 Feb 2022
- v0.2.1-0.20220211152646-874b17b5a830 11 Feb 2022
- v0.0.0-20220128135240-9267b2d1462d 28 Jan 2022
- v0.2.1-0.20220128135240-9267b2d1462d 28 Jan 2022
- v0.2.0 31 May 2021
- v0.1.1-0.20200124154328-f9f678b84cca 24 Jan 2020
- v0.1.1-0.20200124153946-75338dbf3278 24 Jan 2020
- v0.0.0-20191105223159-1c71414a61dc 05 Nov 2019
- v0.1.1-0.20191105223159-1c71414a61dc 05 Nov 2019
- v0.1.1-0.20191105221500-5aeeb6410359 05 Nov 2019
- v0.1.1-0.20190122184456-f5c65d3eb01d 22 Jan 2019
- v0.0.0-20190117164721-452e22de4fef 17 Jan 2019
- v0.1.0 17 Jan 2019
- v0.0.0-20181205142746-62912bff1c53 05 Dec 2018
- v0.0.0-20181105175341-5c62b5e9f6a4 05 Nov 2018
- v0.0.0-20181016150912-25e2ee8b213c 16 Oct 2018
- v0.0.0-20180927173954-532dd077a6ae 27 Sep 2018
- v0.0.0-20180918200134-5223d0404b1e 18 Sep 2018
- v0.0.0-20180724154149-f77fae492fee 24 Jul 2018
All 26 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/cretz/bine
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/cretz/bine
Is github.com/cretz/bine safe to use?
Vulert has no vulnerabilities on record for github.com/cretz/bine 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/cretz/bine's Vulert package health score?
Vulert scores github.com/cretz/bine 54/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/cretz/bine affected?
No. v0.2.0, 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/cretz/bine should I use?
v0.2.0 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/cretz/bine have?
0 vulnerabilities are recorded for github.com/cretz/bine 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/cretz/bine vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/cretz/bine 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/cretz/bine 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/cretz/bine for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/cretz/bine version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.