VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

itk-wasm: vulnerability history, versions and safety

itk-wasm 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 itk-wasm vulnerabilities

Vulert verdict on itk-wasm 1.0.0-b.201 i

Updated on 23 Oct 2026

Good news: 1.0.0-b.201, the version you would install today, has no known vulnerabilities.

Package health score 83/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 1.0.0-b.201 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 25 packages i
  • Stars 236 i
  • Last release 2 months ago i
  • Licence Apache-2.0 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 itk-wasm, 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
1.0.0-b.201 11 Aug 2026 none Apache-2.0 — Details →
1.0.0-b.200 11 Aug 2026 none Apache-2.0 — Details →
1.0.0-b.199 23 Jul 2026 none Apache-2.0 — Details →
1.0.0-b.198 12 Jul 2026 none Apache-2.0 — Details →
1.0.0-b.197 14 Apr 2026 none Apache-2.0 — Details →
1.0.0-b.196 13 Aug 2025 none Apache-2.0 — Details →
1.0.0-b.195 07 Aug 2025 none Apache-2.0 — Details →
1.0.0-b.192 26 Jun 2025 none Apache-2.0 — Details →
1.0.0-b.188 23 Feb 2025 none Apache-2.0 — Details →
1.0.0-b.187 20 Feb 2025 none Apache-2.0 — Details →
1.0.0-b.186 12 Feb 2025 none Apache-2.0 — Details →
1.0.0-b.185 04 Jan 2025 none Apache-2.0 — Details →
1.0.0-b.184 27 Nov 2024 none Apache-2.0 — Details →
1.0.0-b.183 26 Nov 2024 none Apache-2.0 — Details →
1.0.0-b.182 20 Nov 2024 none Apache-2.0 — Details →
1.0.0-b.181 20 Nov 2024 none Apache-2.0 — Details →
1.0.0-b.180 16 Nov 2024 none Apache-2.0 — Details →
1.0.0-b.179 07 Oct 2024 none Apache-2.0 — Details →
1.0.0-b.178 11 Aug 2024 none Apache-2.0 — Details →
1.0.0-b.177 14 Jul 2024 none Apache-2.0 — Details →
1.0.0-b.176 03 Jun 2024 none Apache-2.0 — Details →
1.0.0-b.175 19 May 2024 none Apache-2.0 — Details →
1.0.0-b.174 18 May 2024 none Apache-2.0 — Details →
1.0.0-b.173 13 Apr 2024 none Apache-2.0 — Details →
1.0.0-b.172 04 Apr 2024 none Apache-2.0 — Details →
1.0.0-b.171 11 Mar 2024 none Apache-2.0 — Details →
1.0.0-b.170 11 Mar 2024 none Apache-2.0 — Details →
1.0.0-b.169 04 Mar 2024 none Apache-2.0 — Details →
1.0.0-b.168 23 Feb 2024 none Apache-2.0 — Details →
1.0.0-b.167 21 Feb 2024 none Apache-2.0 — Details →
1.0.0-b.166 13 Feb 2024 none Apache-2.0 — Details →
1.0.0-b.165 03 Feb 2024 none Apache-2.0 — Details →
1.0.0-b.164 02 Feb 2024 none Apache-2.0 — Details →
1.0.0-b.163 23 Jan 2024 none Apache-2.0 — Details →
1.0.0-b.162 08 Jan 2024 none Apache-2.0 — Details →
1.0.0-b.161 08 Jan 2024 none Apache-2.0 — Details →
1.0.0-b.160 19 Dec 2023 none Apache-2.0 — Details →
1.0.0-b.159 16 Dec 2023 none Apache-2.0 — Details →
1.0.0-b.158 06 Dec 2023 none Apache-2.0 — Details →
1.0.0-b.157 29 Nov 2023 none Apache-2.0 — Details →
1.0.0-b.156 13 Nov 2023 none Apache-2.0 — Details →
1.0.0-b.155 09 Nov 2023 none Apache-2.0 — Details →
1.0.0-b.154 06 Nov 2023 none Apache-2.0 — Details →
1.0.0-b.153 05 Nov 2023 none Apache-2.0 — Details →
1.0.0-b.152 29 Oct 2023 none Apache-2.0 — Details →
1.0.0-b.151 27 Oct 2023 none Apache-2.0 — Details →
1.0.0-b.150 27 Oct 2023 none Apache-2.0 — Details →
1.0.0-b.149 13 Oct 2023 none Apache-2.0 — Details →
1.0.0-b.148 13 Oct 2023 none Apache-2.0 — Details →
1.0.0-b.147 11 Oct 2023 none Apache-2.0 — Details →
1.0.0-b.146 30 Sep 2023 none Apache-2.0 — Details →
1.0.0-b.145 27 Sep 2023 none Apache-2.0 — Details →
1.0.0-b.144 26 Sep 2023 none Apache-2.0 — Details →
1.0.0-b.143 26 Sep 2023 none Apache-2.0 — Details →
1.0.0-b.142 24 Sep 2023 none Apache-2.0 — Details →
1.0.0-b.141 22 Sep 2023 none Apache-2.0 — Details →
1.0.0-b.140 19 Sep 2023 none Apache-2.0 — Details →
1.0.0-b.139 18 Sep 2023 none Apache-2.0 — Details →
1.0.0-b.138 11 Sep 2023 none Apache-2.0 — Details →
1.0.0-b.137 10 Sep 2023 none Apache-2.0 — Details →
1.0.0-b.136 07 Sep 2023 none Apache-2.0 — Details →
1.0.0-b.135 07 Sep 2023 none Apache-2.0 — Details →
1.0.0-b.134 05 Sep 2023 none Apache-2.0 — Details →
1.0.0-b.133 30 Aug 2023 none Apache-2.0 — Details →
1.0.0-b.132 28 Aug 2023 none Apache-2.0 — Details →
1.0.0-b.131 26 Aug 2023 none Apache-2.0 — Details →
1.0.0-b.130 25 Aug 2023 none Apache-2.0 — Details →
1.0.0-b.129 24 Aug 2023 none Apache-2.0 — Details →
1.0.0-b.128 22 Aug 2023 none Apache-2.0 — Details →
1.0.0-b.127 16 Aug 2023 none Apache-2.0 — Details →
1.0.0-b.126 16 Aug 2023 none Apache-2.0 — Details →
1.0.0-b.125 14 Aug 2023 none Apache-2.0 — Details →
1.0.0-b.124 14 Aug 2023 none Apache-2.0 — Details →
1.0.0-b.123 14 Aug 2023 none Apache-2.0 — Details →
1.0.0-b.122 10 Aug 2023 none Apache-2.0 — Details →
1.0.0-b.121 06 Aug 2023 none Apache-2.0 — Details →
1.0.0-b.120 06 Aug 2023 none Apache-2.0 — Details →
1.0.0-b.119 10 Jul 2023 none Apache-2.0 — Details →
1.0.0-b.118 25 Jun 2023 none Apache-2.0 — Details →
1.0.0-b.117 21 Jun 2023 none Apache-2.0 — Details →
1.0.0-b.116 17 Jun 2023 none Apache-2.0 — Details →
1.0.0-b.115 07 Jun 2023 none Apache-2.0 — Details →
1.0.0-b.114 06 Jun 2023 none Apache-2.0 — Details →
1.0.0-b.113 02 Jun 2023 none Apache-2.0 — Details →
1.0.0-b.112 31 May 2023 none Apache-2.0 — Details →
1.0.0-b.111 26 May 2023 none Apache-2.0 — Details →
1.0.0-b.110 23 May 2023 none Apache-2.0 — Details →
1.0.0-b.109 18 May 2023 none Apache-2.0 — Details →
1.0.0-b.108 16 May 2023 none Apache-2.0 — Details →
1.0.0-b.107 11 May 2023 none Apache-2.0 — Details →
1.0.0-b.106 07 May 2023 none Apache-2.0 — Details →
1.0.0-b.105 06 May 2023 none Apache-2.0 — Details →
1.0.0-b.104 05 May 2023 none Apache-2.0 — Details →
1.0.0-b.103 05 May 2023 none Apache-2.0 — Details →
1.0.0-b.102 04 May 2023 none Apache-2.0 — Details →
1.0.0-b.101 26 Apr 2023 none Apache-2.0 — Details →
1.0.0-b.100 25 Apr 2023 none Apache-2.0 — Details →
1.0.0-b.99 25 Apr 2023 none Apache-2.0 — Details →
1.0.0-b.98 24 Apr 2023 none Apache-2.0 — Details →
1.0.0-b.97 22 Apr 2023 none Apache-2.0 — Details →
1.0.0-b.96 20 Apr 2023 none — — Details →
1.0.0-b.95 17 Apr 2023 none — — Details →
1.0.0-b.94 14 Apr 2023 none — — Details →
1.0.0-b.93 13 Apr 2023 none — — Details →
1.0.0-b.92 06 Apr 2023 none — — Details →
1.0.0-b.91 29 Mar 2023 none — — Details →
1.0.0-b.90 29 Mar 2023 none — — Details →
1.0.0-b.89 24 Mar 2023 none — — Details →
1.0.0-b.88 16 Mar 2023 none — — Details →
1.0.0-b.87 16 Mar 2023 none — — Details →
1.0.0-b.86 10 Mar 2023 none — — Details →
1.0.0-b.85 10 Mar 2023 none — — Details →
1.0.0-b.84 09 Mar 2023 none — — Details →
1.0.0-b.83 03 Mar 2023 none — — Details →
1.0.0-b.82 03 Mar 2023 none — — Details →
1.0.0-b.81 02 Mar 2023 none — — Details →
1.0.0-b.80 02 Mar 2023 none — — Details →
1.0.0-b.79 01 Mar 2023 none — — Details →
1.0.0-b.78 28 Feb 2023 none — — Details →
1.0.0-b.77 27 Feb 2023 none — — Details →

The newest 120 of 204 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 itk-wasm

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 itk-wasm

Is itk-wasm safe to use?

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

Vulert scores itk-wasm 83/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 itk-wasm affected?

No. 1.0.0-b.201, 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 itk-wasm should I use?

1.0.0-b.201 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 itk-wasm have?

0 vulnerabilities are recorded for itk-wasm 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 itk-wasm vulnerabilities disclosed?

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

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