Vulnerability Database · Go · Package report
github.com/srebhan/cborquery: vulnerability history, versions and safety
github.com/srebhan/cborquery 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/srebhan/cborquery v1.0.4 i
Updated on 23 Oct 2026
Good news: v1.0.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 v1.0.4 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.0.4 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.0.4 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 2 i
- OpenSSF scorecard 2/10 i
- Last release 18 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/srebhan/cborquery, 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.
- v1.0.5-0.20250414093803-a4e1a24a4890 14 Apr 2025
- v1.0.4 14 Apr 2025
- v1.0.3 29 Jan 2025
- v1.0.3-0.20241205130721-76816e089df8 05 Dec 2024
- v1.0.3-0.20241014115506-484e14c80729 14 Oct 2024
- v1.0.2 07 Oct 2024
- v1.0.2-0.20241007213406-a5904297d506 07 Oct 2024
- v1.0.2-0.20240513105754-f12a6c5d9020 13 May 2024
- v1.0.2-0.20240312095835-b0a4eeee6ad5 12 Mar 2024
- v0.0.0-20240220171230-e890329ef1b2 20 Feb 2024
- v1.0.1 20 Feb 2024
- v0.0.0-20240104223316-9dfa2c584417 04 Jan 2024
- v0.0.0-20230727164956-5e5122f04162 27 Jul 2023
- v0.0.0-20230725150932-a310f35e07b3 25 Jul 2023
- v0.0.0-20230626165538-38be85b82316 26 Jun 2023
- v0.0.0-20230626164305-c6fc8d93febe 26 Jun 2023
- v0.0.0-20230626133726-445d152b7929 26 Jun 2023
- v0.0.0-20230626132025-a3c21b3a77f1 26 Jun 2023
- v0.0.0-20230622142053-3fdc8215ca5f 22 Jun 2023
All 19 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/srebhan/cborquery
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/srebhan/cborquery
Is github.com/srebhan/cborquery safe to use?
Vulert has no vulnerabilities on record for github.com/srebhan/cborquery 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/srebhan/cborquery's Vulert package health score?
Vulert scores github.com/srebhan/cborquery 56/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/srebhan/cborquery affected?
No. v1.0.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/srebhan/cborquery should I use?
v1.0.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/srebhan/cborquery have?
0 vulnerabilities are recorded for github.com/srebhan/cborquery 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/srebhan/cborquery vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/srebhan/cborquery 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/srebhan/cborquery 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/srebhan/cborquery for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/srebhan/cborquery version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.