VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/superfly/tokenizer: vulnerability history, versions and safety

github.com/superfly/tokenizer is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 38 releases, first recorded in Jul 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M1 U1
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/superfly/tokenizer vulnerabilities

Vulert verdict on github.com/superfly/tokenizer v0.0.2 i

Updated on 23 Oct 2026

Action needed: v0.0.2 has 2 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 78/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Quiet

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v0.0.2 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 25 Jul 2023 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 501 i
  • Last release 36 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/superfly/tokenizer, 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.3-0.20260915181033-12c9cb298b07 15 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.3-0.20260910194749-16cdeb0650c7 10 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.3-0.20260909170517-f275cdd1a5be 09 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.3-0.20260715183928-73598b36b80f 15 Jul 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.3-0.20260501184601-a60499d50d16 01 May 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.3-0.20260430172004-73d651640b03 30 Apr 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.3-0.20260404003624-cbb9524013a9 04 Apr 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.3-0.20260403135834-583c51bfc4de 03 Apr 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.3-0.20260401180323-2abecdaa92f0 01 Apr 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.3-0.20260311202159-a9e6f35b665c 11 Mar 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.3-0.20251205003208-e161ecd652bf 05 Dec 2025 M1 U1 Apache-2.0 Yes Details →
v0.0.3-0.20250311183306-648394cc322e 11 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.0.3-0.20250311175830-aae794513aa1 11 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.0.3-0.20250228164740-aca4993dcac1 28 Feb 2025 M1 U1 Apache-2.0 Yes Details →
v0.0.3-0.20250204160634-67a093948822 04 Feb 2025 M1 U1 Apache-2.0 Yes Details →
v0.0.3-0.20250127211412-56a903d3d89a 27 Jan 2025 M1 U1 Apache-2.0 Yes Details →
v0.0.3-0.20240826174224-a17a2e0a9dc0 26 Aug 2024 M1 U1 Apache-2.0 Yes Details →
v0.0.3-0.20240726184001-68cc350ed618 26 Jul 2024 M1 U1 Apache-2.0 Yes Details →
v0.0.3-0.20240110200728-912d613a765f 10 Jan 2024 M1 U1 Apache-2.0 Yes Details →
v0.0.3-0.20230926215051-f330c3713748 26 Sep 2023 M1 U1 Apache-2.0 Yes Details →
v0.0.2 26 Sep 2023 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20230713175935-369aa22645aa 13 Jul 2023 M1 U1 Apache-2.0 Yes Details →
v0.0.1 13 Jul 2023 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20230713153020-fe18ba07feec 13 Jul 2023 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20230712204135-1bcbec4f3121 12 Jul 2023 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20230712185157-1939fc3dca13 12 Jul 2023 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20230707175236-153095fc1105 07 Jul 2023 M1 U1 — Yes Details →
v0.0.0-20230706211131-74729eb6cdf4 06 Jul 2023 M1 U1 — Yes Details →
v0.0.0-20230627184617-99633aab8fef 27 Jun 2023 M1 U1 — Yes Details →
v0.0.0-20230627140624-2eedb3701d7b 27 Jun 2023 M1 U1 — Yes Details →
v0.0.0-20230623205016-6148c8ac1c80 23 Jun 2023 M1 U1 — Yes Details →
v0.0.0-20230503141021-f441030d9546 03 May 2023 M1 U1 — Yes Details →
v0.0.0-20230428193946-a0482acffdba 28 Apr 2023 M1 U1 — Yes Details →
v0.0.0-20230427203713-88ed3d3969ef 27 Apr 2023 M1 U1 — Yes Details →
v0.0.0-20230427195117-88de8a27b0fa 27 Apr 2023 M1 U1 — Yes Details →
v0.0.0-20230426220901-176e1c234d4d 26 Apr 2023 M1 U1 — Yes Details →
v0.0.0-20230424215246-af1d002a8c1d 24 Apr 2023 M1 U1 — Yes Details →
v0.0.0-20230414225120-5b67fbf931da 14 Apr 2023 M1 U1 — Yes Details →

All 38 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for github.com/superfly/tokenizer

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Vulnerability in github.com/superfly/tokenizer: Tokenizer vulnerable to client brute-force of token secrets N/A medium 0.0.1 13 Jul 2023
CVE-GO-2023-1914: Brute-force of token secrets in github.com/superfly/tokenizer N/A unrated 0.0.1 25 Jul 2023

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/superfly/tokenizer

Is github.com/superfly/tokenizer safe to use?

Vulert records 2 vulnerabilities for github.com/superfly/tokenizer in Go: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is github.com/superfly/tokenizer's Vulert package health score?

Vulert scores github.com/superfly/tokenizer 78/100, which reads as in good shape. 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/superfly/tokenizer affected?

Yes. v0.0.2, the version you would install today, has 2 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/superfly/tokenizer should I use?

v0.0.2 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/superfly/tokenizer have?

2 vulnerabilities are recorded for github.com/superfly/tokenizer in the Go ecosystem: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/superfly/tokenizer vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/superfly/tokenizer in the last 12 months, and the oldest entry in this database dates to 13 Jul 2023. 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/superfly/tokenizer 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/superfly/tokenizer for upcoming vulnerabilities?

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