VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

wasm-bindgen-backend: vulnerability history, versions and safety

wasm-bindgen-backend is a package in the crates.io ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the crates.io 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 wasm-bindgen-backend vulnerabilities

Vulert verdict on wasm-bindgen-backend 0.2.104 i

Updated on 23 Oct 2026

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

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

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

  • Current release 0.2.104 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 8 packages i
  • Stars 9,197 i
  • Last release 12 months ago i
  • Licence Apache-2.0 OR MIT i

Version list, release dates, licence and dependants published by crates.io, 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 wasm-bindgen-backend, 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
0.2.104 24 Sep 2025 none Apache-2.0 OR MIT — Details →
0.2.103 17 Sep 2025 none Apache-2.0 OR MIT — Details →
0.2.102 16 Sep 2025 none Apache-2.0 OR MIT — Details →
0.2.101 04 Sep 2025 none Apache-2.0 OR MIT — Details →
0.2.100 12 Jan 2025 none Apache-2.0 OR MIT — Details →
0.2.99 07 Dec 2024 none Apache-2.0 OR MIT — Details →
0.2.98 07 Dec 2024 none Apache-2.0 OR MIT — Details →
0.2.97 30 Nov 2024 none Apache-2.0 OR MIT — Details →
0.2.96 29 Nov 2024 none Apache-2.0 OR MIT — Details →
0.2.95 10 Oct 2024 none Apache-2.0 OR MIT — Details →
0.2.94 09 Oct 2024 none Apache-2.0 OR MIT — Details →
0.2.93 12 Aug 2024 none Apache-2.0 OR MIT — Details →
0.2.92 04 Mar 2024 none Apache-2.0 OR MIT — Details →
0.2.91 06 Feb 2024 none Apache-2.0 OR MIT — Details →
0.2.90 12 Jan 2024 none Apache-2.0 OR MIT — Details →
0.2.89 27 Nov 2023 none Apache-2.0 OR MIT — Details →
0.2.88 01 Nov 2023 none Apache-2.0 OR MIT — Details →
0.2.87 12 Jun 2023 none Apache-2.0 OR MIT — Details →
0.2.86 15 May 2023 none Apache-2.0 OR MIT — Details →
0.2.85 09 May 2023 none Apache-2.0 OR MIT — Details →
0.2.84 01 Feb 2023 none Apache-2.0 OR MIT — Details →
0.2.83 12 Sep 2022 none Apache-2.0 OR MIT — Details →
0.2.82 25 Jul 2022 none Apache-2.0 OR MIT — Details →
0.2.81 14 Jun 2022 none Apache-2.0 OR MIT — Details →
0.2.80 07 Apr 2022 none Apache-2.0 OR MIT — Details →
0.2.79 19 Jan 2022 none Apache-2.0 OR MIT — Details →
0.2.78 15 Sep 2021 none Apache-2.0 OR MIT — Details →
0.2.77 08 Sep 2021 none Apache-2.0 OR MIT — Details →
0.2.76 19 Aug 2021 none Apache-2.0 OR MIT — Details →
0.2.75 02 Aug 2021 none Apache-2.0 OR MIT — Details →
0.2.74 10 May 2021 none Apache-2.0 OR MIT — Details →
0.2.73 29 Mar 2021 none Apache-2.0 OR MIT — Details →
0.2.72 18 Mar 2021 none Apache-2.0 OR MIT — Details →
0.2.71 26 Feb 2021 none Apache-2.0 OR MIT — Details →
0.2.70 25 Jan 2021 none Apache-2.0 OR MIT — Details →
0.2.69 30 Nov 2020 none Apache-2.0 OR MIT — Details →
0.2.68 09 Sep 2020 none Apache-2.0 OR MIT — Details →
0.2.67 28 Jul 2020 none Apache-2.0 OR MIT — Details →
0.2.66 28 Jul 2020 none Apache-2.0 OR MIT — Details →
0.2.65 15 Jul 2020 none Apache-2.0 OR MIT — Details →
0.2.64 29 Jun 2020 none Apache-2.0 OR MIT — Details →
0.2.63 28 May 2020 none Apache-2.0 OR MIT — Details →
0.2.62 01 May 2020 none Apache-2.0 OR MIT — Details →
0.2.61 29 Apr 2020 none Apache-2.0 OR MIT — Details →
0.2.60 26 Mar 2020 none Apache-2.0 OR MIT — Details →
0.2.59 03 Mar 2020 none Apache-2.0 OR MIT — Details →
0.2.58 07 Jan 2020 none Apache-2.0 OR MIT — Details →
0.2.57 06 Jan 2020 none Apache-2.0 OR MIT — Details →
0.2.56 20 Dec 2019 none Apache-2.0 OR MIT — Details →
0.2.55 19 Nov 2019 none Apache-2.0 OR MIT — Details →
0.2.54 07 Nov 2019 none Apache-2.0 OR MIT — Details →
0.2.53 29 Oct 2019 none Apache-2.0 OR MIT — Details →
0.2.52 24 Oct 2019 none Apache-2.0 OR MIT — Details →
0.2.51 26 Sep 2019 none Apache-2.0 OR MIT — Details →
0.2.50 19 Aug 2019 none Apache-2.0 OR MIT — Details →
0.2.49 14 Aug 2019 none Apache-2.0 OR MIT — Details →
0.2.48 11 Jul 2019 none Apache-2.0 OR MIT — Details →
0.2.47 19 Jun 2019 none Apache-2.0 OR MIT — Details →
0.2.46 14 Jun 2019 none Apache-2.0 OR MIT — Details →
0.2.45 20 May 2019 none Apache-2.0 OR MIT — Details →
0.2.44 16 May 2019 none Apache-2.0 OR MIT — Details →
0.2.43 29 Apr 2019 none Apache-2.0 OR MIT — Details →
0.2.42 11 Apr 2019 none Apache-2.0 OR MIT — Details →
0.2.41 10 Apr 2019 none Apache-2.0 OR MIT — Details →
0.2.40 22 Mar 2019 none Apache-2.0 OR MIT — Details →
0.2.39 13 Mar 2019 none Apache-2.0 OR MIT — Details →
0.2.38 04 Mar 2019 none Apache-2.0 OR MIT — Details →
0.2.37 15 Feb 2019 none Apache-2.0 OR MIT — Details →
0.2.36 12 Feb 2019 none Apache-2.0 OR MIT — Details →
0.2.35 12 Feb 2019 none Apache-2.0 OR MIT — Details →
0.2.34 12 Feb 2019 none Apache-2.0 OR MIT — Details →
0.2.33 18 Jan 2019 none Apache-2.0 OR MIT — Details →
0.2.32 16 Jan 2019 none Apache-2.0 OR MIT — Details →
0.2.31 09 Jan 2019 none Apache-2.0 OR MIT — Details →
0.2.30 07 Jan 2019 none Apache-2.0 OR MIT — Details →
0.2.29 04 Dec 2018 none Apache-2.0 OR MIT — Details →
0.2.28 12 Nov 2018 none Apache-2.0 OR MIT — Details →
0.2.27 29 Oct 2018 none Apache-2.0 OR MIT — Details →
0.2.26 29 Oct 2018 none Apache-2.0 OR MIT — Details →
0.2.25 10 Oct 2018 none Apache-2.0 OR MIT — Details →
0.2.24 05 Oct 2018 none Apache-2.0 OR MIT — Details →
0.2.23 26 Sep 2018 none Apache-2.0 OR MIT — Details →
0.2.22 21 Sep 2018 none Apache-2.0 OR MIT — Details →
0.2.21 07 Sep 2018 none Apache-2.0 OR MIT — Details →
0.2.20 06 Sep 2018 none Apache-2.0 OR MIT — Details →
0.2.19 27 Aug 2018 none Apache-2.0 OR MIT — Details →
0.2.18 27 Aug 2018 none Apache-2.0 OR MIT — Details →
0.2.17 17 Aug 2018 none Apache-2.0 OR MIT — Details →
0.2.16 13 Aug 2018 none Apache-2.0 OR MIT — Details →
0.2.15 26 Jul 2018 none Apache-2.0 OR MIT — Details →
0.2.14 25 Jul 2018 none Apache-2.0 OR MIT — Details →
0.2.13 22 Jul 2018 none Apache-2.0 OR MIT — Details →
0.2.12 19 Jul 2018 none Apache-2.0 OR MIT — Details →
0.2.11 24 May 2018 none Apache-2.0 OR MIT — Details →
0.2.10 17 May 2018 none Apache-2.0 OR MIT — Details →
0.2.9 11 May 2018 none Apache-2.0 OR MIT — Details →
0.2.8 01 May 2018 none Apache-2.0 OR MIT — Details →
0.2.7 28 Apr 2018 none Apache-2.0 OR MIT — Details →
0.2.6 27 Apr 2018 none Apache-2.0 OR MIT — Details →
0.2.5 20 Apr 2018 none Apache-2.0 OR MIT — Details →
0.2.4 18 Apr 2018 none — — Details →
0.2.3 17 Apr 2018 none — — Details →
0.2.2 13 Apr 2018 none — — Details →
0.2.1 09 Apr 2018 none — — Details →
0.2.0 03 Apr 2018 none — — Details →

All 105 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 wasm-bindgen-backend

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 wasm-bindgen-backend

Is wasm-bindgen-backend safe to use?

Vulert has no vulnerabilities on record for wasm-bindgen-backend in crates.io 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 wasm-bindgen-backend's Vulert package health score?

Vulert scores wasm-bindgen-backend 87/100, which reads as healthy. 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 wasm-bindgen-backend affected?

No. 0.2.104, 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 wasm-bindgen-backend should I use?

0.2.104 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 wasm-bindgen-backend have?

0 vulnerabilities are recorded for wasm-bindgen-backend in the crates.io 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 wasm-bindgen-backend vulnerabilities disclosed?

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

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