VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/charlievieth/strcase: vulnerability history, versions and safety

github.com/charlievieth/strcase is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/charlievieth/strcase vulnerabilities

Vulert verdict on github.com/charlievieth/strcase v0.0.6 i

Updated on 23 Oct 2026

Good news: v0.0.6, the version you would install today, has no known vulnerabilities.

Package health score 68/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

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

  • Current release v0.0.6 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 16 i
  • OpenSSF scorecard 4/10 i
  • Last release 3 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/charlievieth/strcase, 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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.0.0-20260922235821-467ff66a2e06 22 Sep 2026 none MIT — Details →
v0.0.7-0.20260922235821-467ff66a2e06 22 Sep 2026 none MIT — Details →
v0.0.0-20260724054737-52b303d0d501 24 Jul 2026 none MIT — Details →
v0.0.7-0.20260724054737-52b303d0d501 24 Jul 2026 none MIT — Details →
v0.0.6 18 Jul 2026 none MIT — Details →
v0.0.0-20251114185648-ccdc7cd70f67 14 Nov 2025 none MIT — Details →
v0.0.6-0.20251114185648-ccdc7cd70f67 14 Nov 2025 none MIT — Details →
v0.0.0-20250515024321-9b6dc01f7e8d 15 May 2025 none MIT — Details →
v0.0.6-0.20250515024321-9b6dc01f7e8d 15 May 2025 none MIT — Details →
v0.0.6-0.20250502004256-da7db2d760a7 02 May 2025 none MIT — Details →
v0.0.6-0.20250325155021-23533a10f603 25 Mar 2025 none MIT — Details →
v0.0.6-0.20250223000025-56e6350e0c1d 23 Feb 2025 none MIT — Details →
v0.0.6-0.20250220234844-b5013c5eaeef 20 Feb 2025 none MIT — Details →
v0.0.0-20241205233409-760393b3bc16 05 Dec 2024 none MIT — Details →
v0.0.6-0.20241205233409-760393b3bc16 05 Dec 2024 none MIT — Details →
v0.0.0-20241123042708-f2e627455ef3 23 Nov 2024 none MIT — Details →
v0.0.5 23 Nov 2024 none MIT — Details →
v0.0.5-0.20241123042708-f2e627455ef3 23 Nov 2024 none MIT — Details →
v0.0.0-20240912211632-f9ea18ce03f8 12 Sep 2024 none MIT — Details →
v0.0.5-0.20240912211632-f9ea18ce03f8 12 Sep 2024 none MIT — Details →
v0.0.5-0.20240912050444-30484f9b1432 12 Sep 2024 none MIT — Details →
v0.0.4 12 Sep 2024 none MIT — Details →
v0.0.0-20240822133653-cd166f6bb587 22 Aug 2024 none MIT — Details →
v0.0.4-0.20240822133653-cd166f6bb587 22 Aug 2024 none MIT — Details →
v0.0.0-20240209044217-c844fec2d964 09 Feb 2024 none MIT — Details →
v0.0.3 09 Feb 2024 none MIT — Details →
v0.0.3-0.20240209044217-c844fec2d964 09 Feb 2024 none MIT — Details →
v0.0.2 28 Jan 2024 none MIT — Details →
v0.0.2-0.20231014211040-9a6a8516f432 14 Oct 2023 none MIT — Details →
v0.0.0-20230525051349-1e933dc24367 25 May 2023 none MIT — Details →
v0.0.1 25 May 2023 none MIT — Details →
v0.0.0-20230414235412-b29dea3eef51 14 Apr 2023 none MIT — Details →
v0.0.0-20230409233158-aaed0a680516 09 Apr 2023 none MIT — Details →
v0.0.0-20230409213003-053ded1eef3d 09 Apr 2023 none MIT — Details →
v0.0.0-20230408224314-a8a7cb692f2c 08 Apr 2023 none MIT — Details →
v0.0.0-20230408212506-8b4c3bb127c9 08 Apr 2023 none MIT — Details →
v0.0.0-20230408163416-fcaf603fed95 08 Apr 2023 none MIT — Details →
v0.0.0-20230408161757-585daaf60b31 08 Apr 2023 none MIT — Details →
v0.0.0-20230408055017-e5e84c56303f 08 Apr 2023 none MIT — Details →
v0.0.0-20230408052443-ce5f7d030210 08 Apr 2023 none MIT — Details →
v0.0.0-20230408035223-3b41d45fab86 08 Apr 2023 none MIT — Details →
v0.0.0-20230408032721-b46d4a7ce90d 08 Apr 2023 none MIT — Details →
v0.0.0-20230407195946-3d2f028aa2a5 07 Apr 2023 none MIT — Details →
v0.0.0-20230407192010-e647d654d941 07 Apr 2023 none MIT — Details →
v0.0.0-20230407184954-c70a92365bb6 07 Apr 2023 none MIT — Details →
v0.0.0-20230406172819-9cb6ef707409 06 Apr 2023 none MIT — Details →
v0.0.0-20230406024251-9f3343122c7a 06 Apr 2023 none MIT — Details →
v0.0.0-20230406002844-1b108bd7be18 06 Apr 2023 none MIT — Details →
v0.0.0-20230406001327-89f4b40b1aa1 06 Apr 2023 none MIT — Details →
v0.0.0-20230405212529-2615f7fe74b3 05 Apr 2023 none MIT — Details →
v0.0.0-20230405205808-ce8f9fb2a5c5 05 Apr 2023 none MIT — Details →
v0.0.0-20230405193227-1d4d35bd7469 05 Apr 2023 none MIT — Details →
v0.0.0-20230405190815-6d4a4e3a8557 05 Apr 2023 none MIT — Details →
v0.0.0-20230405184239-256e3436bfd9 05 Apr 2023 none MIT — Details →
v0.0.0-20230404175634-62018d1fe1b1 04 Apr 2023 none MIT — Details →
v0.0.0-20230404153922-4965b74739e3 04 Apr 2023 none MIT — Details →
v0.0.0-20230402001339-4a16c97f5cc4 02 Apr 2023 none MIT — Details →
v0.0.0-20230324222707-222ba72b8de7 24 Mar 2023 none MIT — Details →
v0.0.0-20230324195658-e12deb14dc23 24 Mar 2023 none MIT — Details →
v0.0.0-20230324155219-2ea5e0166b5d 24 Mar 2023 none MIT — Details →
v0.0.0-20230324025314-28d7194e0c7a 24 Mar 2023 none MIT — Details →
v0.0.0-20230323215232-4f536aa3dc41 23 Mar 2023 none MIT — Details →
v0.0.0-20230323212905-7e58be6b12c7 23 Mar 2023 none MIT — Details →
v0.0.0-20230323211237-d76742657d1b 23 Mar 2023 none MIT — Details →
v0.0.0-20230323194505-9835aa68d9ad 23 Mar 2023 none MIT — Details →
v0.0.0-20230323185801-8f02e3f03d00 23 Mar 2023 none MIT — Details →
v0.0.0-20230323182049-4aae71793b27 23 Mar 2023 none MIT — Details →
v0.0.0-20230323153530-71ca64692004 23 Mar 2023 none MIT — Details →
v0.0.0-20230322163409-f42b045a6660 22 Mar 2023 none MIT — Details →
v0.0.0-20230322034443-4142f753858b 22 Mar 2023 none MIT — Details →
v0.0.0-20230322033128-22e26433c605 22 Mar 2023 none MIT — Details →
v0.0.0-20230322030815-be07e92c1b50 22 Mar 2023 none MIT — Details →
v0.0.0-20230321200915-2cc985333a58 21 Mar 2023 none MIT — Details →
v0.0.0-20230321191136-61ad9103e7bc 21 Mar 2023 none MIT — Details →
v0.0.0-20230321190836-ea9b45445150 21 Mar 2023 none MIT — Details →
v0.0.0-20230321184305-cd94c178ae06 21 Mar 2023 none MIT — Details →
v0.0.0-20230321183731-5794b788c4e3 21 Mar 2023 none MIT — Details →
v0.0.0-20230321180800-b2451e302a7b 21 Mar 2023 none MIT — Details →
v0.0.0-20230321175040-f0f7ad12fda0 21 Mar 2023 none MIT — Details →
v0.0.0-20230321170554-8cd176871766 21 Mar 2023 none MIT — Details →
v0.0.0-20230321165843-47c43af97932 21 Mar 2023 none MIT — Details →
v0.0.0-20230321154243-6f2a59c442fa 21 Mar 2023 none MIT — Details →
v0.0.0-20230321152302-716ea45ad557 21 Mar 2023 none MIT — Details →
v0.0.0-20230321143611-03d6f128187c 21 Mar 2023 none MIT — Details →
v0.0.0-20230321051224-c62dd85f0573 21 Mar 2023 none MIT — Details →
v0.0.0-20230321045422-a3db5fdc5ec5 21 Mar 2023 none MIT — Details →
v0.0.0-20230321040241-6d8c5f10c503 21 Mar 2023 none MIT — Details →
v0.0.0-20230321033418-fe78d5d5598f 21 Mar 2023 none MIT — Details →
v0.0.0-20230321022717-aef1cf06840e 21 Mar 2023 none MIT — Details →
v0.0.0-20230321020306-999d1bac6243 21 Mar 2023 none MIT — Details →
v0.0.0-20230319045850-7138b3ed815f 19 Mar 2023 none MIT — Details →
v0.0.0-20230319041747-8e09ee519053 19 Mar 2023 none MIT — Details →
v0.0.0-20230319023423-a4b5d7bcae64 19 Mar 2023 none MIT — Details →
v0.0.0-20230319014125-257f5dbf91b8 19 Mar 2023 none MIT — Details →
v0.0.0-20230106014550-13b611a780f1 06 Jan 2023 none MIT — Details →

All 95 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/charlievieth/strcase

No vulnerability write-ups match this view

Search all 0 in the database →

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/charlievieth/strcase

Is github.com/charlievieth/strcase safe to use?

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

Vulert scores github.com/charlievieth/strcase 68/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/charlievieth/strcase affected?

No. v0.0.6, 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/charlievieth/strcase should I use?

v0.0.6 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/charlievieth/strcase have?

0 vulnerabilities are recorded for github.com/charlievieth/strcase 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/charlievieth/strcase vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/charlievieth/strcase 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/charlievieth/strcase 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/charlievieth/strcase for upcoming vulnerabilities?

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