Vulnerability Database · Go · Package report
github.com/cosmos/cosmos-db: vulnerability history, versions and safety
github.com/cosmos/cosmos-db 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/cosmos/cosmos-db v1.1.3 i
Updated on 23 Oct 2026
Good news: v1.1.3, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Maintaining
- Popularity Little adoption
- Community Quiet
What to do: Stay on v1.1.3 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.1.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.1.3 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 25 i
- OpenSSF scorecard 4/10 i
- Last release 16 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/cosmos/cosmos-db, 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.1.4-0.20260409145421-43c8a47e27a5 09 Apr 2026
- v1.1.4-0.20260211161018-c6d077317d02 11 Feb 2026
- v0.0.0-20250603224706-9221ee7e2bcc 03 Jun 2025
- v1.1.3 03 Jun 2025
- v1.1.2 29 May 2025
- v0.0.0-20250505172547-38785e92904d 05 May 2025
- v1.1.2-0.20250505172547-38785e92904d 05 May 2025
- v1.1.1 19 Dec 2024
- v1.1.1-0.20241219081702-6896d8e1b76f 19 Dec 2024
- v1.1.1-0.20241219081603-43c30c765b09 19 Dec 2024
- v1.1.1-0.20241125211508-0ed17d48baeb 25 Nov 2024
- v1.1.0 22 Nov 2024
- v1.0.3-0.20241122160441-1bdfe5430835 22 Nov 2024
- v1.0.3-0.20241122154242-de82b5a3bffd 22 Nov 2024
- v1.0.3-0.20241122152219-5a33ca29f30b 22 Nov 2024
- v1.0.3-0.20240911104526-ddc3f09bfc22 11 Sep 2024
- v1.0.3-0.20240829004618-717cba019b33 29 Aug 2024
- v1.0.3-0.20240811211305-6e8b9ee65fea 11 Aug 2024
- v1.0.3-0.20240408151834-e75f6e4b28d8 08 Apr 2024
- v1.0.2 26 Feb 2024
- v1.0.1 25 Feb 2024
- v1.0.1-0.20240225214408-d3eee7d3aa1b 25 Feb 2024
- v1.0.1-0.20240223073604-2ba32ea562f2 23 Feb 2024
- v0.0.0-20231026072645-8a5e4f599be7 26 Oct 2023
- v1.0.1-0.20231026072645-8a5e4f599be7 26 Oct 2023
- v1.0.1-0.20230823150522-81c032d38629 23 Aug 2023
- v1.0.0 25 May 2023
- v1.0.0-rc.1.0.20230228202114-313e4da3bdc5 28 Feb 2023
- v0.0.0-20230129203223-199192126292 29 Jan 2023
- v1.0.0-rc.1 29 Jan 2023
- v0.0.0-20230119180254-161cf3632b7c 19 Jan 2023
- v0.0.0-20230118144024-23e350dbbe7f 18 Jan 2023
- v0.0.0-20221228140519-2d107c64614b 28 Dec 2022
- v0.0.0-20221226095112-f3c38ecb5e32 26 Dec 2022
- v0.0.0-20221224071843-97e1443c3226 24 Dec 2022
- v0.0.0-20221222113720-cc5ba75f5dd9 22 Dec 2022
- v0.0.0-20221214151242-e491abe41a85 14 Dec 2022
- v0.0.0-20221212105642-6fa371f4739c 12 Dec 2022
- v0.0.0-20221127110041-4564dc28e22b 27 Nov 2022
- v0.0.0-20221113143545-dd9f801296cb 13 Nov 2022
- v0.0.0-20221111072340-cf484290c601 11 Nov 2022
- v0.0.0-20220915062153-9aa6a118b2ad 15 Sep 2022
- v0.0.0-20220901120321-77d98dabb5d3 01 Sep 2022
- v0.0.0-20220831082506-d49669b17ceb 31 Aug 2022
- v0.0.0-20220827084210-6a3a0338ea0e 27 Aug 2022
- v0.0.0-20220824192247-f47ae8d33c74 24 Aug 2022
- v0.0.0-20220822060143-23a8145386c0 22 Aug 2022
- v0.0.0-20220821075825-97bc8c902cf3 21 Aug 2022
All 48 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/cosmos/cosmos-db
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/cosmos/cosmos-db
Is github.com/cosmos/cosmos-db safe to use?
Vulert has no vulnerabilities on record for github.com/cosmos/cosmos-db 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/cosmos/cosmos-db's Vulert package health score?
Vulert scores github.com/cosmos/cosmos-db 61/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/cosmos/cosmos-db affected?
No. v1.1.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.
Which version of github.com/cosmos/cosmos-db should I use?
v1.1.3 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/cosmos/cosmos-db have?
0 vulnerabilities are recorded for github.com/cosmos/cosmos-db 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/cosmos/cosmos-db vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/cosmos/cosmos-db 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/cosmos/cosmos-db 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/cosmos/cosmos-db for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/cosmos/cosmos-db version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.