VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@neon-rs/load: vulnerability history, versions and safety

@neon-rs/load 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 @neon-rs/load vulnerabilities

Vulert verdict on @neon-rs/load 0.2.6 i

Updated on 23 Oct 2026

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

Package health score 73/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

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

  • Current release 0.2.6 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 12 packages i
  • Stars 9 i
  • Last release 7 months 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 @neon-rs/load, 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.6 10 Mar 2026 none MIT — Details →
0.2.5 10 Mar 2026 none MIT — Details →
0.2.4 10 Mar 2026 none MIT — Details →
0.1.82 15 Nov 2024 none MIT — Details →
0.1.81 25 Aug 2024 none MIT — Details →
0.1.80 25 Aug 2024 none MIT — Details →
0.1.79 25 Aug 2024 none MIT — Details →
0.1.78 25 Aug 2024 none MIT — Details →
0.1.77 24 Aug 2024 none MIT — Details →
0.1.76 24 Aug 2024 none MIT — Details →
0.1.75 24 Aug 2024 none MIT — Details →
0.1.74 24 Aug 2024 none MIT — Details →
0.1.73 19 May 2024 none MIT — Details →
0.1.72 18 May 2024 none MIT — Details →
0.1.71 17 May 2024 none MIT — Details →
0.1.70 17 May 2024 none MIT — Details →
0.1.69 16 May 2024 none MIT — Details →
0.1.68 06 May 2024 none MIT — Details →
0.1.67 06 May 2024 none MIT — Details →
0.1.66 15 Apr 2024 none MIT — Details →
0.1.65 15 Apr 2024 none MIT — Details →
0.1.64 25 Mar 2024 none MIT — Details →
0.1.63 25 Mar 2024 none MIT — Details →
0.1.60 25 Mar 2024 none MIT — Details →
0.1.58 25 Mar 2024 none MIT — Details →
0.1.57 25 Mar 2024 none MIT — Details →
0.1.56 25 Mar 2024 none MIT — Details →
0.1.55 25 Mar 2024 none MIT — Details →
0.1.54 24 Mar 2024 none MIT — Details →
0.1.52 24 Mar 2024 none MIT — Details →
0.1.51 24 Mar 2024 none MIT — Details →
0.1.50 24 Mar 2024 none MIT — Details →
0.1.49 24 Mar 2024 none MIT — Details →
0.1.48 24 Mar 2024 none MIT — Details →
0.1.44 23 Mar 2024 none MIT — Details →
0.1.43 23 Mar 2024 none MIT — Details →
0.1.42 23 Mar 2024 none MIT — Details →
0.1.40 23 Mar 2024 none MIT — Details →
0.1.39 21 Mar 2024 none MIT — Details →
0.1.37 19 Mar 2024 none MIT — Details →
0.1.35 18 Mar 2024 none MIT — Details →
0.1.33 17 Mar 2024 none MIT — Details →
0.1.30 17 Mar 2024 none MIT — Details →
0.1.28 17 Mar 2024 none MIT — Details →
0.1.26 10 Mar 2024 none MIT — Details →
0.1.25 06 Mar 2024 none MIT — Details →
0.1.23 05 Mar 2024 none MIT — Details →
0.1.21 05 Mar 2024 none MIT — Details →
0.1.19 05 Mar 2024 none MIT — Details →
0.1.17 05 Mar 2024 none MIT — Details →
0.1.12 04 Mar 2024 none MIT — Details →
0.1.0 26 Feb 2024 none MIT — Details →
0.0.202 28 Jan 2024 none MIT — Details →
0.0.200 28 Jan 2024 none MIT — Details →
0.0.197 08 Jan 2024 none MIT — Details →
0.0.196 06 Jan 2024 none MIT — Details →
0.0.195 06 Jan 2024 none MIT — Details →
0.0.186 01 Jan 2024 none MIT — Details →
0.0.185 31 Dec 2023 none MIT — Details →
0.0.184 24 Dec 2023 none MIT — Details →
0.0.183 24 Dec 2023 none MIT — Details →
0.0.182 24 Dec 2023 none MIT — Details →
0.0.181 23 Dec 2023 none MIT — Details →
0.0.180 16 Dec 2023 none MIT — Details →
0.0.179 12 Dec 2023 none MIT — Details →
0.0.178 12 Dec 2023 none MIT — Details →
0.0.177 12 Dec 2023 none MIT — Details →
0.0.176 11 Dec 2023 none MIT — Details →
0.0.175 11 Dec 2023 none MIT — Details →
0.0.174 11 Dec 2023 none MIT — Details →
0.0.173 11 Dec 2023 none MIT — Details →
0.0.172 11 Dec 2023 none MIT — Details →
0.0.171 11 Dec 2023 none MIT — Details →
0.0.170 11 Dec 2023 none MIT — Details →
0.0.169 10 Dec 2023 none MIT — Details →
0.0.168 27 Nov 2023 none MIT — Details →
0.0.167 24 Nov 2023 none MIT — Details →
0.0.166 21 Nov 2023 none MIT — Details →
0.0.165 11 Aug 2023 none MIT — Details →
0.0.164 11 Aug 2023 none MIT — Details →
0.0.163 11 Aug 2023 none MIT — Details →
0.0.162 26 Jul 2023 none MIT — Details →
0.0.161 26 Jul 2023 none MIT — Details →
0.0.160 21 Jul 2023 none MIT — Details →
0.0.159 21 Jul 2023 none MIT — Details →
0.0.158 21 Jul 2023 none MIT — Details →
0.0.157 21 Jul 2023 none MIT — Details →
0.0.156 21 Jul 2023 none MIT — Details →
0.0.155 20 Jul 2023 none MIT — Details →
0.0.154 19 Jul 2023 none MIT — Details →
0.0.153 19 Jul 2023 none MIT — Details →
0.0.152 18 Jul 2023 none MIT — Details →
0.0.151 17 Jul 2023 none MIT — Details →
0.0.150 17 Jul 2023 none MIT — Details →
0.0.149 17 Jul 2023 none MIT — Details →
0.0.148 17 Jul 2023 none MIT — Details →
0.0.147 17 Jul 2023 none MIT — Details →
0.0.146 17 Jul 2023 none MIT — Details →
0.0.145 17 Jul 2023 none MIT — Details →
0.0.144 16 Jul 2023 none MIT — Details →
0.0.143 16 Jul 2023 none — — Details →
0.0.142 16 Jul 2023 none — — Details →
0.0.141 16 Jul 2023 none — — Details →
0.0.140 16 Jul 2023 none — — Details →
0.0.139 15 Jul 2023 none — — Details →
0.0.137 07 Jul 2023 none — — Details →
0.0.136 06 Jul 2023 none — — Details →
0.0.135 06 Jul 2023 none — — Details →
0.0.134 04 Jul 2023 none — — Details →
0.0.133 04 Jul 2023 none — — Details →
0.0.131 04 Jul 2023 none — — Details →
0.0.130 04 Jul 2023 none — — Details →
0.0.129 03 Jul 2023 none — — Details →
0.0.128 03 Jul 2023 none — — Details →
0.0.127 03 Jul 2023 none — — Details →
0.0.126 03 Jul 2023 none — — Details →
0.0.125 03 Jul 2023 none — — Details →
0.0.124 03 Jul 2023 none — — Details →
0.0.123 02 Jul 2023 none — — Details →
0.0.121 30 Jun 2023 none — — Details →

The newest 120 of 200 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 @neon-rs/load

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 @neon-rs/load

Is @neon-rs/load safe to use?

Vulert has no vulnerabilities on record for @neon-rs/load 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 @neon-rs/load's Vulert package health score?

Vulert scores @neon-rs/load 73/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 @neon-rs/load affected?

No. 0.2.6, 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 @neon-rs/load should I use?

0.2.6 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 @neon-rs/load have?

0 vulnerabilities are recorded for @neon-rs/load 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 @neon-rs/load vulnerabilities disclosed?

0 vulnerabilities were recorded for @neon-rs/load 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 @neon-rs/load 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 @neon-rs/load for upcoming vulnerabilities?

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