Vulnerability Database · Go · Package report
github.com/couchbase/gocbcoreps: vulnerability history, versions and safety
github.com/couchbase/gocbcoreps 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/couchbase/gocbcoreps v0.1.4 i
Updated on 23 Oct 2026
Good news: v0.1.4, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Maintaining
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.1.4 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.1.4 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.1.4 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 1 i
- OpenSSF scorecard 3/10 i
- Last release 13 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/couchbase/gocbcoreps, 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.1.5-0.20261005161736-7de374b343fa 05 Oct 2026
- v0.1.5-0.20260907165847-d3784e3e2bb0 07 Sep 2026
- v0.1.5-0.20260901124438-310e55bf10d8 01 Sep 2026
- v0.1.5-0.20260413093139-b38df312dd87 13 Apr 2026
- v0.1.5-0.20260203190221-c87313f60fb9 03 Feb 2026
- v0.1.5-0.20260129115606-5fc746cfa5d6 29 Jan 2026
- v0.1.5-0.20260107140814-1c3a03f888f8 07 Jan 2026
- v0.1.5-0.20260106140233-024b20fb0d3c 06 Jan 2026
- v0.1.5-0.20251120111817-fa952f7a9e3f 20 Nov 2025
- v0.1.5-0.20251013131415-8f7ff2e2b7bf 13 Oct 2025
- v0.1.4 15 Sep 2025
- v0.1.4-0.20250911203224-a191c3236a6a 11 Sep 2025
- v0.1.4-0.20250410085904-6e3ef5905388 10 Apr 2025
- v0.1.4-0.20250410085904-f2562f14f0f2 10 Apr 2025
- v0.0.0-20240617133621-1e49c1181694 17 Jun 2024
- v0.1.3 17 Jun 2024
- v0.1.3-0.20240617133621-1e49c1181694 17 Jun 2024
- v0.1.3-0.20240320150422-d3fac347f72b 20 Mar 2024
- v0.1.2 20 Feb 2024
- v0.1.2-0.20240220162624-a5451fae8f57 20 Feb 2024
- v0.1.2-0.20240215120132-74c8921e4135 15 Feb 2024
- v0.1.2-0.20240123092254-fc2a1d28f615 23 Jan 2024
- v0.1.1 17 Jan 2024
- v0.1.1-0.20231220162712-aa366fd7df65 20 Dec 2023
- v0.1.0 21 Nov 2023
- v0.0.0-20231113141308-5f0347744035 13 Nov 2023
- v0.0.0-20231031081914-427437bce69f 31 Oct 2023
- v0.0.0-20231023093743-6083e7f360d0 23 Oct 2023
- v0.0.0-20230807073947-b16d0c10005d 07 Aug 2023
- v0.0.0-20230706124203-19b70604b872 06 Jul 2023
- v0.0.0-20230524134052-9824000bbef3 24 May 2023
- v0.0.0-20230523184901-b4958f1714dd 23 May 2023
All 32 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/couchbase/gocbcoreps
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/couchbase/gocbcoreps
Is github.com/couchbase/gocbcoreps safe to use?
Vulert has no vulnerabilities on record for github.com/couchbase/gocbcoreps 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/couchbase/gocbcoreps's Vulert package health score?
Vulert scores github.com/couchbase/gocbcoreps 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/couchbase/gocbcoreps affected?
No. v0.1.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/couchbase/gocbcoreps should I use?
v0.1.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/couchbase/gocbcoreps have?
0 vulnerabilities are recorded for github.com/couchbase/gocbcoreps 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/couchbase/gocbcoreps vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/couchbase/gocbcoreps 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/couchbase/gocbcoreps 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/couchbase/gocbcoreps for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/couchbase/gocbcoreps version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.