Vulnerability Database · Go · Package report

github.com/spf13/cobra-cli: vulnerability history, versions and safety

Q: How do I monitor github.com/spf13/cobra-cli for upcoming vulnerabilities?

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

github.com/spf13/cobra-cli is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/spf13/cobra-cli vulnerabilities

Vulert verdict on github.com/spf13/cobra-cli v1.3.0 i

Updated on 23 Oct 2026

Good news: v1.3.0, the version you would install today, has no known vulnerabilities.

Package health score 59/100

Security Minor issues
Maintenance Unmaintained
Popularity Widely used
Community Quiet

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

Current release v1.3.0 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Stars 939 i
OpenSSF scorecard 3/10 i
Last release 56 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/spf13/cobra-cli, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
v0.0.0-20230819210728-1d434876c3a7	19 Aug 2023	none	Apache-2.0	—	Details →
v1.3.1-0.20230819210728-1d434876c3a7	19 Aug 2023	none	Apache-2.0	—	Details →
v1.3.1-0.20230614154854-3858115d122a	14 Jun 2023	none	Apache-2.0	—	Details →
v1.3.1-0.20230218123528-ea7926a8c5b9	18 Feb 2023	none	Apache-2.0	—	Details →
v1.3.1-0.20221031201452-d146541ba222	31 Oct 2022	none	Apache-2.0	—	Details →
v1.3.1-0.20221010172335-3116dfbc2166	10 Oct 2022	none	Apache-2.0	—	Details →
v1.3.1-0.20220728223730-fd5e124aeba7	28 Jul 2022	none	Apache-2.0	—	Details →
v1.3.1-0.20220329183958-cb54657cc0f7	29 Mar 2022	none	Apache-2.0	—	Details →
v1.3.1-0.20220325173231-541496c5b236	25 Mar 2022	none	Apache-2.0	—	Details →
v0.0.0-20220223031945-74762ac083f2	23 Feb 2022	none	Apache-2.0	—	Details →
v1.3.0	23 Feb 2022	none	Apache-2.0	—	Details →
v0.0.0-20220217191704-7c6e26ac0939	17 Feb 2022	none	Apache-2.0	—	Details →

All 12 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.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for github.com/spf13/cobra-cli

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/spf13/cobra-cli

Is github.com/spf13/cobra-cli safe to use?

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

Vulert scores github.com/spf13/cobra-cli 59/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/spf13/cobra-cli affected?

No. v1.3.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/spf13/cobra-cli should I use?

v1.3.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/spf13/cobra-cli have?

0 vulnerabilities are recorded for github.com/spf13/cobra-cli 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/spf13/cobra-cli vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/spf13/cobra-cli 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/spf13/cobra-cli 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/spf13/cobra-cli for upcoming vulnerabilities?

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