Vulnerability Database · npm · Package report

@rspack/plugin-preact-refresh: vulnerability history, versions and safety

@rspack/plugin-preact-refresh 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.

Vulert verdict on @rspack/plugin-preact-refresh 2.0.1 i

Updated on 23 Oct 2026

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

Package health score 80/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

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

  • Current release 2.0.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 4 packages i
  • Last release 4 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 @rspack/plugin-preact-refresh, 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
2.0.1 02 Jun 2026 none MIT — Details →
2.0.0 01 Jun 2026 none MIT — Details →
1.1.6 29 May 2026 none MIT — Details →
1.1.5 20 Jan 2026 none MIT — Details →
1.1.4 22 Oct 2025 none MIT — Details →
1.1.3 28 Sep 2025 none MIT — Details →
1.1.2 02 Dec 2024 none MIT — Details →
1.1.1 03 Nov 2024 none MIT — Details →
1.1.0 25 Oct 2024 none MIT — Details →
1.0.1 23 Sep 2024 none MIT — Details →
0.7.6-canary-fd6c40d-20240918093542 18 Sep 2024 none MIT — Details →
1.0.0 22 Aug 2024 none MIT — Details →
1.0.0-beta.5 08 Aug 2024 none MIT — Details →
1.0.0-beta.4 08 Aug 2024 none MIT — Details →
1.0.0-beta.3 06 Aug 2024 none MIT — Details →
1.0.0-beta.2 02 Aug 2024 none MIT — Details →
1.0.0-beta.1 30 Jul 2024 none MIT — Details →
1.0.0-beta.0 26 Jul 2024 none MIT — Details →
1.0.0-alpha.5 17 Jul 2024 none MIT — Details →
1.0.0-alpha.4 16 Jul 2024 none MIT — Details →
1.0.0-alpha.3 11 Jul 2024 none MIT — Details →
0.7.6-canary-7121b83-20240709064601 09 Jul 2024 none MIT — Details →
1.0.0-alpha.2 08 Jul 2024 none MIT — Details →
1.0.0-alpha.1 04 Jul 2024 none MIT — Details →
1.0.0-alpha.0 28 Jun 2024 none MIT — Details →
0.7.6-canary-1a0d77d-20240627143904 27 Jun 2024 none MIT — Details →
0.7.6-canary-f272bd8-20240625122346 25 Jun 2024 none MIT — Details →
0.7.5 25 Jun 2024 none MIT — Details →
0.7.3-canary-e3de538-20240625072228 25 Jun 2024 none MIT — Details →
0.7.5-canary-0d03907-20240624125011 24 Jun 2024 none MIT — Details →
0.7.5-canary-1ab2ea8-20240624100353 24 Jun 2024 none MIT — Details →
0.7.5-canary-910259c-20240624004455 24 Jun 2024 none MIT — Details →
0.7.5-canary-910259c-20240623004502 23 Jun 2024 none MIT — Details →
0.7.5-canary-910259c-20240622004334 22 Jun 2024 none MIT — Details →
0.7.5-canary-c7fe67a-20240621075559 21 Jun 2024 none MIT — Details →
0.7.5-canary-d73b4fa-20240621004417 21 Jun 2024 none MIT — Details →
0.7.5-canary-b89dbb3-20240620182932 20 Jun 2024 none MIT — Details →
0.7.5-canary-129960e-20240620181737 20 Jun 2024 none MIT — Details →
0.7.5-canary-9ec73cf-20240620092522 20 Jun 2024 none MIT — Details →
0.7.5-canary-87a73c3a-20240620004559 20 Jun 2024 none MIT — Details →
0.7.5-canary-35f8542-20240619004508 19 Jun 2024 none MIT — Details →
0.7.4-canary-c24c83f-20240618120853 18 Jun 2024 none MIT — Details →
0.7.5-canary-08f2925-20240618102814 18 Jun 2024 none MIT — Details →
0.7.4 18 Jun 2024 none MIT — Details →
0.7.4-canary-bdc2037-20240617004808 17 Jun 2024 none MIT — Details →
0.7.4-canary-bdc2037-20240616004950 16 Jun 2024 none MIT — Details →
0.7.4-canary-bdc2037-20240615004834 15 Jun 2024 none MIT — Details →
0.7.4-canary-de24e64-20240614130907 14 Jun 2024 none MIT — Details →
0.7.3-canary-a17997a-20240614063055 14 Jun 2024 none MIT — Details →
0.7.4-canary-fd91d69-20240614004431 14 Jun 2024 none MIT — Details →
0.7.4-canary-8ea6579-20240613100825 13 Jun 2024 none MIT — Details →
0.7.3 13 Jun 2024 none MIT — Details →
0.7.3-canary-607ec67-20240612123914 12 Jun 2024 none MIT — Details →
0.7.2-canary-0aba80f-20240612004429 12 Jun 2024 none MIT — Details →

All 54 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 @rspack/plugin-preact-refresh

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 @rspack/plugin-preact-refresh

Is @rspack/plugin-preact-refresh safe to use?

Vulert has no vulnerabilities on record for @rspack/plugin-preact-refresh 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 @rspack/plugin-preact-refresh's Vulert package health score?

Vulert scores @rspack/plugin-preact-refresh 80/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 @rspack/plugin-preact-refresh affected?

No. 2.0.1, 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 @rspack/plugin-preact-refresh should I use?

2.0.1 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 @rspack/plugin-preact-refresh have?

0 vulnerabilities are recorded for @rspack/plugin-preact-refresh 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 @rspack/plugin-preact-refresh vulnerabilities disclosed?

0 vulnerabilities were recorded for @rspack/plugin-preact-refresh 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 @rspack/plugin-preact-refresh 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 @rspack/plugin-preact-refresh for upcoming vulnerabilities?

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