VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

strtok3: vulnerability history, versions and safety

strtok3 is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm 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 strtok3 vulnerabilities

Vulert verdict on strtok3 10.6.2 i

Updated on 23 Oct 2026

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

Package health score 77/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Inactive

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

  • Current release 10.6.2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 16,187 packages i
  • Stars 51 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, 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 strtok3, 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
10.6.2 18 Oct 2026 none MIT — Details →
10.6.1 17 Oct 2026 none MIT — Details →
10.6.0 17 Oct 2026 none MIT — Details →
10.5.0 13 Oct 2026 none MIT — Details →
10.4.1 12 Oct 2026 none MIT — Details →
10.4.0 11 Oct 2026 none MIT — Details →
10.3.5 21 Mar 2026 none MIT — Details →
10.3.4 25 Jul 2025 none MIT — Details →
10.3.2 15 Jul 2025 none MIT — Details →
10.3.1 08 Jun 2025 none MIT — Details →
10.3.0 08 Jun 2025 none MIT — Details →
10.2.2 09 Mar 2025 none MIT — Details →
10.2.1 05 Feb 2025 none MIT — Details →
10.2.0 31 Jan 2025 none MIT — Details →
10.1.2 30 Jan 2025 none MIT — Details →
10.1.1 29 Jan 2025 none MIT — Details →
10.1.0-beta.5 19 Jan 2025 none MIT — Details →
10.1.0-beta.4 18 Jan 2025 none MIT — Details →
10.1.0-beta.3 18 Jan 2025 none MIT — Details →
10.1.0-beta.2 18 Jan 2025 none MIT — Details →
10.1.0-beta.1 18 Jan 2025 none MIT — Details →
10.1.0-beta.0 18 Jan 2025 none MIT — Details →
10.0.1 01 Dec 2024 none MIT — Details →
10.0.0 30 Nov 2024 none MIT — Details →
9.1.1 26 Nov 2024 none MIT — Details →
9.1.0 26 Nov 2024 none MIT — Details →
9.0.1 13 Oct 2024 none MIT — Details →
9.0.0 02 Sep 2024 none MIT — Details →
8.1.0 14 Aug 2024 none MIT — Details →
8.0.5 08 Aug 2024 none MIT — Details →
8.0.4 08 Aug 2024 none MIT — Details →
8.0.3 08 Aug 2024 none MIT — Details →
8.0.2 07 Aug 2024 none MIT — Details →
8.0.1 22 Jul 2024 none MIT — Details →
8.0.0 16 Jul 2024 none MIT — Details →
7.1.1 15 Jul 2024 none MIT — Details →
7.1.0 05 Jul 2024 none MIT — Details →
7.0.0 02 Aug 2022 none MIT — Details →
7.0.0-alpha.9 25 Jul 2022 none MIT — Details →
6.3.0 06 Feb 2022 none MIT — Details →
7.0.0-alpha.8 27 Jan 2022 none MIT — Details →
7.0.0-alpha.7 16 Dec 2021 none MIT — Details →
7.0.0-alpha.6 11 Dec 2021 none MIT — Details →
7.0.0-alpha.5 10 Dec 2021 none MIT — Details →
7.0.0-alpha.4 01 Aug 2021 none MIT — Details →
6.2.4 01 Aug 2021 none MIT — Details →
6.2.3 31 Jul 2021 none MIT — Details →
7.0.0-alpha.3 31 Jul 2021 none MIT — Details →
7.0.0-alpha.2 27 Jul 2021 none MIT — Details →
7.0.0-alpha.1 24 Jul 2021 none MIT — Details →
7.0.0-alpha.0 24 Jul 2021 none MIT — Details →
6.2.2 19 Jul 2021 none MIT — Details →
6.2.1 18 Jul 2021 none MIT — Details →
6.2.0 17 Jul 2021 none MIT — Details →
6.1.3 12 Jul 2021 none MIT — Details →
6.1.2 11 Jul 2021 none MIT — Details →
6.1.1 10 Jul 2021 none MIT — Details →
6.1.0 10 Jul 2021 none MIT — Details →
6.0.8 11 Jan 2021 none MIT — Details →
6.0.7 10 Jan 2021 none MIT — Details →
6.0.6 03 Jan 2021 none MIT — Details →
6.0.5 03 Jan 2021 none MIT — Details →
6.0.4 27 Jul 2020 none MIT — Details →
6.0.3 13 Jun 2020 none MIT — Details →
6.0.2 08 Jun 2020 none MIT — Details →
6.0.1 07 Jun 2020 none MIT — Details →
6.0.0 25 Jan 2020 none MIT — Details →
5.0.2 17 Jan 2020 none MIT — Details →
5.0.1 06 Jan 2020 none MIT — Details →
5.0.0 29 Dec 2019 none MIT — Details →
4.1.1 26 Dec 2019 none MIT — Details →
4.1.0 25 Dec 2019 none MIT — Details →
4.0.0 24 Dec 2019 none MIT — Details →
3.1.7 23 Dec 2019 none MIT — Details →
3.1.6 23 Dec 2019 none MIT — Details →
3.1.5 23 Dec 2019 none MIT — Details →
3.1.4 17 Dec 2019 none MIT — Details →
3.1.3 03 Dec 2019 none MIT — Details →
3.1.2 23 Nov 2019 none MIT — Details →
3.1.1 22 Nov 2019 none MIT — Details →
3.1.0 13 Nov 2019 none MIT — Details →
3.0.6 01 Nov 2019 none MIT — Details →
3.0.5 31 Oct 2019 none MIT — Details →
3.0.4 17 Oct 2019 none MIT — Details →
3.0.3 16 Oct 2019 none MIT — Details →
3.0.1 07 Sep 2019 none MIT — Details →
3.0.0 06 Jun 2019 none MIT — Details →
2.3.0 16 Dec 2018 none MIT — Details →
2.2.0 27 Nov 2018 none MIT — Details →
2.1.1 27 Oct 2018 none MIT — Details →
2.1.0 19 Sep 2018 none MIT — Details →
2.0.0 12 Sep 2018 none MIT — Details →
1.6.0 09 Sep 2018 none MIT — Details →
1.5.4 22 Aug 2018 none MIT — Details →
1.5.3 19 Jul 2018 none MIT — Details →
1.5.2 05 Jul 2018 none MIT — Details →
1.5.1 01 Jul 2018 none MIT — Details →
1.5.0 24 Jun 2018 none MIT — Details →
1.4.4 19 Jun 2018 none MIT — Details →
1.4.3 19 Jun 2018 none MIT — Details →
1.4.2 09 May 2018 none — — Details →
1.4.1 27 Apr 2018 none — — Details →
1.4.0 25 Apr 2018 none — — Details →
1.3.4 18 Apr 2018 none — — Details →
1.3.3 05 Feb 2018 none — — Details →
1.3.2 02 Sep 2017 none — — Details →
1.3.1 02 Sep 2017 none — — Details →
1.3.0 02 Sep 2017 none — — Details →
1.2.3 02 Sep 2017 none — — Details →
1.2.2 01 Sep 2017 none — — Details →
1.2.1 31 Aug 2017 none — — Details →
1.2.0 28 Aug 2017 none — — Details →
1.1.3 20 Aug 2017 none — — Details →
1.1.2 19 Aug 2017 none — — Details →
1.1.1 12 Aug 2017 none — — Details →
1.1.0 11 Aug 2017 none — — Details →
1.0.3 17 Jul 2017 none — — Details →
1.0.1 16 Jul 2017 none — — Details →
1.0.0 16 Jul 2017 none — — Details →
0.2.0 02 Jul 2017 none — — Details →

The newest 120 of 125 versions Vulert tracks. 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 strtok3

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 strtok3

Is strtok3 safe to use?

Vulert has no vulnerabilities on record for strtok3 in npm 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 strtok3's Vulert package health score?

Vulert scores strtok3 77/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 strtok3 affected?

No. 10.6.2, 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.

How many vulnerabilities does strtok3 have?

0 vulnerabilities are recorded for strtok3 in the npm 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 strtok3 vulnerabilities disclosed?

0 vulnerabilities were recorded for strtok3 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 strtok3 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 strtok3 for upcoming vulnerabilities?

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