Vulnerability Database · Go · Package report
github.com/swaggest/usecase: vulnerability history, versions and safety
github.com/swaggest/usecase 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/swaggest/usecase v1.3.1 i
Updated on 23 Oct 2026
Good news: v1.3.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Little adoption
- Community Inactive
What to do: Stay on v1.3.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.3.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.3.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 38 i
- OpenSSF scorecard 2/10 i
- Last release 34 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/swaggest/usecase, 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.3.1 19 Dec 2023
- v1.3.1-0.20231219011320-90e267b09e10 19 Dec 2023
- v1.2.2-0.20231207212556-a96ea69610b7 07 Dec 2023
- v1.3.0 07 Dec 2023
- v1.2.1 02 Feb 2023
- v1.2.0 12 Sep 2022
- v1.1.3 26 May 2022
- v1.1.3-0.20220227113629-4a5f115ec74f 27 Feb 2022
- v1.1.2 07 Feb 2022
- v1.1.1 07 Feb 2022
- v1.1.0 12 Oct 2021
- v1.0.2-0.20211011042326-ffc6809ec66c 11 Oct 2021
- v1.0.2-0.20211002221336-ca119b0cce05 02 Oct 2021
- v1.0.2-0.20210930194024-769bdb00be60 30 Sep 2021
- v1.0.2-0.20210927234057-fc0791462278 27 Sep 2021
- v1.0.1 08 Sep 2021
- v0.1.5 14 Apr 2021
- v1.0.0 14 Apr 2021
- v0.1.4 14 Apr 2021
- v0.1.3 20 Feb 2021
- v0.1.2 18 Feb 2021
- v0.1.1 10 Jan 2021
- v0.0.0-20200928062416-27f47131b0f8 28 Sep 2020
- v0.1.0 28 Sep 2020
- v0.0.0-20200925085926-d8468e2db07b 25 Sep 2020
- v0.0.0-20200901200902-b49018fde9cf 01 Sep 2020
- v0.0.0-20200509115704-f650ca299eb0 09 May 2020
- v0.0.0-20200102204638-25f4b7daa958 02 Jan 2020
All 28 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/swaggest/usecase
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/swaggest/usecase
Is github.com/swaggest/usecase safe to use?
Vulert has no vulnerabilities on record for github.com/swaggest/usecase 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/swaggest/usecase's Vulert package health score?
Vulert scores github.com/swaggest/usecase 50/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/swaggest/usecase affected?
No. v1.3.1, 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/swaggest/usecase should I use?
v1.3.1 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/swaggest/usecase have?
0 vulnerabilities are recorded for github.com/swaggest/usecase 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/swaggest/usecase vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/swaggest/usecase 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/swaggest/usecase 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/swaggest/usecase for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/swaggest/usecase version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.