VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

onnxruntime-node: vulnerability history, versions and safety

onnxruntime-node 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 onnxruntime-node vulnerabilities

Vulert verdict on onnxruntime-node 1.30.0 i

Updated on 23 Oct 2026

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

Package health score 91/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 1.30.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 2,059 packages i
  • Stars 22,129 i
  • OpenSSF scorecard 6/10 i
  • Last release 1 month ago 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 onnxruntime-node, 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.31.0-dev.20260918-bc8e7ed75 18 Sep 2026 none MIT — Details →
1.31.0-dev.20260916-2a720f925 17 Sep 2026 none MIT — Details →
1.31.0-dev.20260917-bff4fcf7d 17 Sep 2026 none MIT — Details →
1.31.0-dev.20260915-fed7f01a0 15 Sep 2026 none MIT — Details →
1.30.0 14 Sep 2026 none MIT — Details →
1.31.0-dev.20260914-8d85527a0 14 Sep 2026 none MIT — Details →
1.31.0-dev.20260911-2a43ec07e 11 Sep 2026 none MIT — Details →
1.30.0-dev.20260910-f2c39fe2f 10 Sep 2026 none MIT — Details →
1.30.0-dev.20260909-e76036b8e 10 Sep 2026 none MIT — Details →
1.30.0-dev.20260909-b905e946b 09 Sep 2026 none MIT — Details →
1.30.0-dev.20260904-d47fd8824 04 Sep 2026 none MIT — Details →
1.30.0-dev.20260901-a6e96aa798 02 Sep 2026 none MIT — Details →
1.30.0-dev.20260826-b1f76d586a 27 Aug 2026 none MIT — Details →
1.30.0-dev.20260825-9cbf665b59 25 Aug 2026 none MIT — Details →
1.29.0 24 Aug 2026 none MIT — Details →
1.30.0-dev.20260821-a88c1168ca 21 Aug 2026 none MIT — Details →
1.30.0-dev.20260819-f73b9ef807 21 Aug 2026 none MIT — Details →
1.30.0-dev.20260813-72e1c9c9b8 13 Aug 2026 none MIT — Details →
1.30.0-dev.20260812-74c8ca5b3a 12 Aug 2026 none MIT — Details →
1.29.0-dev.20260811-e415ef9afd 11 Aug 2026 none MIT — Details →
1.29.0-dev.20260810-1d69bbd631 10 Aug 2026 none MIT — Details →
1.29.0-dev.20260724-ed98916356 24 Jul 2026 none MIT — Details →
1.29.0-dev.20260723-1b1e1db7bc 23 Jul 2026 none MIT — Details →
1.28.0-dev.20260624-ba45260eed 17 Jul 2026 none MIT — Details →
1.27.0 19 Jun 2026 none MIT — Details →
1.26.0 08 May 2026 none MIT — Details →
1.27.0-dev.20260506-673c3320fc 06 May 2026 none MIT — Details →
1.27.0-dev.20260505-b81f3f8558 05 May 2026 none MIT — Details →
1.26.0-dev.20260503-763c4e3597 04 May 2026 none MIT — Details →
1.26.0-dev.20260503-9582867364 03 May 2026 none MIT — Details →
1.26.0-dev.20260502-9d1492a449 02 May 2026 none MIT — Details →
1.25.1 29 Apr 2026 none MIT — Details →
1.26.0-dev.20260416-b7804b056c 16 Apr 2026 none MIT — Details →
1.26.0-dev.20260410-5e55544225 13 Apr 2026 none MIT — Details →
1.25.0-dev.20260327-722743c0e2 28 Mar 2026 none MIT — Details →
1.25.0-dev.20260323-a99aad9d36 24 Mar 2026 none MIT — Details →
1.25.0-dev.20260307-d626b568e0 07 Mar 2026 none MIT — Details →
1.25.0-dev.20260305-65fb61b159 06 Mar 2026 none MIT — Details →
1.24.3 05 Mar 2026 none MIT — Details →
1.25.0-dev.20260303-e7e64dc112 03 Mar 2026 none MIT — Details →
1.25.0-dev.20260228-6e72d31970 01 Mar 2026 none MIT — Details →
1.25.0-dev.20260227-dce58e8711 27 Feb 2026 none MIT — Details →
1.25.0-dev.20260226-5f087c41d5 26 Feb 2026 none MIT — Details →
1.25.0-dev.20260225-bb3866cf34 25 Feb 2026 none MIT — Details →
1.25.0-dev.20260224-649a355935 24 Feb 2026 none MIT — Details →
1.25.0-dev.20260221-b2a6e69e82 22 Feb 2026 none MIT — Details →
1.25.0-dev.20260220-a98c9120db 20 Feb 2026 none MIT — Details →
1.24.2 19 Feb 2026 none MIT — Details →
1.25.0-dev.20260219-c4780e65b5 19 Feb 2026 none MIT — Details →
1.25.0-dev.20260218-19c9efc4ac 18 Feb 2026 none MIT — Details →
1.25.0-dev.20260213-bd8f781f2c 13 Feb 2026 none MIT — Details →
1.25.0-dev.20260212-1a71a5f46e 12 Feb 2026 none MIT — Details →
1.25.0-dev.20260209-a3749f1353 09 Feb 2026 none MIT — Details →
1.25.0-dev.20260206-a8ff3f3e17 07 Feb 2026 none MIT — Details →
1.24.1 05 Feb 2026 none MIT — Details →
1.25.0-dev.20260202-a5dc0f95d8 03 Feb 2026 none MIT — Details →
1.25.0-dev.20260127-f83d4d06e4 27 Jan 2026 none MIT — Details →
1.25.0-dev.20260125-727db0d3dc 25 Jan 2026 none MIT — Details →
1.25.0-dev.20260123-990ba5f0c3 23 Jan 2026 none MIT — Details →
1.24.0-dev.20260121-ef7d2f6bda 22 Jan 2026 none MIT — Details →
1.24.0-dev.20260119-36017adcf6 19 Jan 2026 none MIT — Details →
1.24.0-dev.20260118-6d34aba9e2 18 Jan 2026 none MIT — Details →
1.24.0-dev.20260117-29d9b2fc57 17 Jan 2026 none MIT — Details →
1.24.0-dev.20260116-ba11af41a3 16 Jan 2026 none MIT — Details →
1.24.0-dev.20260114-1a17f6b953 15 Jan 2026 none MIT — Details →
1.24.0-dev.20260113-f86a0ed8b8 14 Jan 2026 none MIT — Details →
1.24.0-dev.20260114-c343143a49 14 Jan 2026 none MIT — Details →
1.24.0-dev.20260112-1d149f5a4a 12 Jan 2026 none MIT — Details →
1.24.0-dev.20260111-5d24c9547f 11 Jan 2026 none MIT — Details →
1.24.0-dev.20260110-5ef551ec83 10 Jan 2026 none MIT — Details →
1.24.0-dev.20260110-1ed8fd9014 10 Jan 2026 none MIT — Details →
1.24.0-dev.20260109-c54be3c7ae 09 Jan 2026 none MIT — Details →
1.24.0-dev.20260108-56c984ffc4 08 Jan 2026 none MIT — Details →
1.24.0-dev.20260106-bfb376fdeb 07 Jan 2026 none MIT — Details →
1.24.0-dev.20260106-69d1e2d5ce 07 Jan 2026 none MIT — Details →
1.24.0-dev.20251231-94e7a1c61c 31 Dec 2025 none MIT — Details →
1.24.0-dev.20251230-aab56616a3 30 Dec 2025 none MIT — Details →
1.24.0-dev.20251227-38355ba07c 29 Dec 2025 none MIT — Details →
1.24.0-dev.20251104-75d35474d5 05 Nov 2025 none MIT — Details →
1.23.2 04 Nov 2025 none MIT — Details →
1.23.0 26 Sep 2025 none MIT — Details →
1.23.0-dev.20250906-ecb26fb775 06 Sep 2025 none MIT — Details →
1.23.0-dev.20250829-4754a1d64e 29 Aug 2025 none MIT — Details →
1.23.0-dev.20250821-75f848097e 21 Aug 2025 none MIT — Details →
1.23.0-dev.20250810-5d77b73c4e 11 Aug 2025 none MIT — Details →
1.23.0-dev.20250809-bf74e5568b 10 Aug 2025 none MIT — Details →
1.23.0-dev.20250807-33debbeea1 07 Aug 2025 none MIT — Details →
1.23.0-dev.20250802-562760a567 03 Aug 2025 none MIT — Details →
1.23.0-dev.20250802-4004a15ba7 02 Aug 2025 none MIT — Details →
1.23.0-dev.20250731-e753643480 31 Jul 2025 none MIT — Details →
1.23.0-dev.20250703-7fc6235861 03 Jul 2025 none MIT — Details →
1.23.0-dev.20250612-70f14d7670 12 Jun 2025 none MIT — Details →
1.23.0-dev.20250602-03b22ffc42 03 Jun 2025 none MIT — Details →
1.22.0-rev 02 Jun 2025 none MIT — Details →
1.23.0-dev.20250522-ad7b0e368d 24 May 2025 none MIT — Details →
1.23.0-dev.20250515-00bd398d54 16 May 2025 none MIT — Details →
1.23.0-dev.20250509-3dc91e6c31 10 May 2025 none MIT — Details →
1.22.0 09 May 2025 none MIT — Details →
1.21.1 21 Apr 2025 none MIT — Details →
1.22.0-dev.20250418-c19a49615b 18 Apr 2025 none MIT — Details →
1.22.0-dev.20250415-c18e06d5e3 15 Apr 2025 none — — Details →
1.21.0 08 Mar 2025 none — — Details →
1.21.0-dev.20250306-e0b66cad28 06 Mar 2025 none — — Details →
1.21.0-dev.20250228-beb1a9242e 03 Mar 2025 none — — Details →
1.20.1 22 Nov 2024 none — — Details →
1.21.0-dev.20241112-cdc8db9984 18 Nov 2024 none — — Details →
1.20.0 31 Oct 2024 none — — Details →
1.20.0-dev.20241022-2d00351d7b 25 Oct 2024 none — — Details →
1.19.2 03 Sep 2024 none — — Details →
1.19.0 15 Aug 2024 none — — Details →
1.19.0-dev.20240804-ee2fe87e2d 06 Aug 2024 none — — Details →
1.18.0 17 May 2024 none — — Details →
1.18.0-dev.20240430-204f1f59b9 02 May 2024 none — — Details →
1.17.3-rev.1 20 Apr 2024 none — — Details →
1.17.3 20 Apr 2024 none — — Details →
1.17.0 31 Jan 2024 none — — Details →
1.17.0-dev.20240118-a63b71eadb 22 Jan 2024 none — — Details →
1.17.0-dev.20240117-81d363045b 17 Jan 2024 none — — Details →
1.16.3 20 Nov 2023 none — — Details →
1.16.2 09 Nov 2023 none — — Details →

The newest 120 of 181 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 onnxruntime-node

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 onnxruntime-node

Is onnxruntime-node safe to use?

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

Vulert scores onnxruntime-node 91/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 onnxruntime-node affected?

No. 1.30.0, 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 onnxruntime-node should I use?

1.30.0 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 onnxruntime-node have?

0 vulnerabilities are recorded for onnxruntime-node 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 onnxruntime-node vulnerabilities disclosed?

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

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