Vulnerability Database · npm · Package report

@callstack/repack-dev-server: vulnerability history, versions and safety

@callstack/repack-dev-server 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 @callstack/repack-dev-server 5.4.2 i

Updated on 23 Oct 2026

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

Package health score 78/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 5.4.2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 5 packages i
  • Stars 1,946 i
  • OpenSSF scorecard 4/10 i
  • Last release this month 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 @callstack/repack-dev-server, 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
5.4.3-canary-20261022172059 22 Oct 2026 none MIT — Details →
5.4.3-canary-20261022091009 22 Oct 2026 none MIT — Details →
5.4.3-canary-20261014000129 14 Oct 2026 none MIT — Details →
5.4.2 09 Oct 2026 none MIT — Details →
5.4.2-canary-20261009123537 09 Oct 2026 none MIT — Details →
5.4.1 09 Oct 2026 none MIT — Details →
5.4.1-canary-20261007103623 07 Oct 2026 none MIT — Details →
5.4.1-canary-20261005140324 05 Oct 2026 none MIT — Details →
5.4.0 26 Sep 2026 none MIT — Details →
5.4.0-canary-20260926141655 26 Sep 2026 none MIT — Details →
5.4.0-canary-20260913172854 13 Sep 2026 none MIT — Details →
5.4.0-canary-20260913161840 13 Sep 2026 none MIT — Details →
5.4.0-canary-20260831210904 31 Aug 2026 none MIT — Details →
5.4.0-canary-20260822202143 22 Aug 2026 none MIT — Details →
5.3.0 05 Aug 2026 none MIT — Details →
5.3.0-canary-20260726211922 26 Jul 2026 none MIT — Details →
5.3.0-canary-20260630204027 30 Jun 2026 none MIT — Details →
5.3.0-canary-20260603221040 03 Jun 2026 none MIT — Details →
5.2.5 13 Mar 2026 none MIT — Details →
5.2.5-canary-20260305211900 05 Mar 2026 none MIT — Details →
5.2.4 26 Feb 2026 none MIT — Details →
5.2.3 09 Dec 2025 none MIT — Details →
5.2.2 03 Nov 2025 none MIT — Details →
5.2.2-canary-20251103120553 03 Nov 2025 none MIT — Details →
5.2.1 15 Sep 2025 none MIT — Details →
5.2.0 27 Aug 2025 none MIT — Details →
6.0.0-canary-20250826200715 26 Aug 2025 none MIT — Details →
6.0.0-canary-20250826152039 26 Aug 2025 none MIT — Details →
6.0.0-canary-20250822183414 22 Aug 2025 none MIT — Details →
6.0.0-canary-20250821173620 21 Aug 2025 none MIT — Details →
6.0.0-canary-20250821134328 21 Aug 2025 none MIT — Details →
6.0.0-canary-20250807223540 07 Aug 2025 none MIT — Details →
6.0.0-canary-20250729145326 29 Jul 2025 none MIT — Details →
5.1.3 02 Jul 2025 none MIT — Details →
5.1.2 12 Jun 2025 none MIT — Details →
5.1.1 20 May 2025 none MIT — Details →
5.1.1-canary-20250519224656 19 May 2025 none MIT — Details →
5.1.0 14 May 2025 none MIT — Details →
5.1.0-rc.0 06 May 2025 none MIT — Details →
6.0.0-canary-20250430092041 30 Apr 2025 none MIT — Details →
6.0.0-canary-20250430091845 30 Apr 2025 none MIT — Details →
5.0.6 03 Apr 2025 none MIT — Details →
5.0.5 22 Mar 2025 none MIT — Details →
6.0.0-canary-20250321121727 21 Mar 2025 none MIT — Details →
5.0.4 18 Mar 2025 none MIT — Details →
5.0.3 12 Mar 2025 none MIT — Details →
5.0.2 12 Mar 2025 none MIT — Details →
5.0.1 06 Mar 2025 none MIT — Details →
5.0.0 28 Feb 2025 none MIT — Details →
5.0.0-rc.12 20 Feb 2025 none MIT — Details →
5.0.0-canary-20250219102750 19 Feb 2025 none MIT — Details →
5.0.0-rc.11 17 Feb 2025 none MIT — Details →
5.0.0-rc.10 27 Jan 2025 none MIT — Details →
5.0.0-rc.9 23 Jan 2025 none MIT — Details →
5.0.0-canary-20250123203953 23 Jan 2025 none MIT — Details →
5.0.0-canary-20250123192942 23 Jan 2025 none MIT — Details →
5.0.0-canary-20250123192635 23 Jan 2025 none MIT — Details →
5.0.0-canary-20250123174218 23 Jan 2025 none MIT — Details →
4.4.1 21 Jan 2025 none MIT — Details →
5.0.0-rc.8 21 Jan 2025 none MIT — Details →
5.0.0-canary-20250120223308 20 Jan 2025 none MIT — Details →
5.0.0-rc.7 20 Jan 2025 none MIT — Details →
5.0.0-canary-20250117101323 17 Jan 2025 none MIT — Details →
5.0.0-canary-20250115185948 15 Jan 2025 none MIT — Details →
5.0.0-rc.6 09 Jan 2025 none MIT — Details →
4.4.0 09 Jan 2025 none MIT — Details →
5.0.0-rc.5 23 Dec 2024 none MIT — Details →
5.0.0-rc.4 19 Dec 2024 none MIT — Details →
5.0.0-rc.3 10 Dec 2024 none MIT — Details →
5.0.0-rc.2 19 Nov 2024 none MIT — Details →
5.0.0-rc.1 08 Nov 2024 none MIT — Details →
5.0.0-rc.0 29 Oct 2024 none MIT — Details →
5.0.0-canary-20241010230910 10 Oct 2024 none MIT — Details →
5.0.0-alpha.0 12 Sep 2024 none MIT — Details →
5.0.0-canary-20240912125430 12 Sep 2024 none MIT — Details →
5.0.0-canary-20240912122341 12 Sep 2024 none MIT — Details →
5.0.0-canary-20240912110701 12 Sep 2024 none MIT — Details →
4.3.3 12 Sep 2024 none MIT — Details →
4.4.0-canary-20240909082848 09 Sep 2024 none MIT — Details →
4.3.2 28 Aug 2024 none MIT — Details →
4.3.1 26 Aug 2024 none MIT — Details →
4.3.0 26 Aug 2024 none MIT — Details →
4.3.0-canary-20240822091832 22 Aug 2024 none MIT — Details →
4.3.0-canary-20240822085232 22 Aug 2024 none MIT — Details →
4.3.0-canary-20240820114654 20 Aug 2024 none MIT — Details →
4.2.0 12 Aug 2024 none MIT — Details →
4.2.0-canary-20240808200412 08 Aug 2024 none MIT — Details →
4.2.0-canary-20240803162111 03 Aug 2024 none MIT — Details →
4.2.0-canary-20240803153933 03 Aug 2024 none MIT — Details →
4.2.0-canary-20240802125253 02 Aug 2024 none MIT — Details →
4.1.1 07 Jun 2024 none MIT — Details →
4.1.0 05 Jun 2024 none MIT — Details →
4.0.1-canary-20240603172122 03 Jun 2024 none MIT — Details →
4.0.1-canary-20240603152822 03 Jun 2024 none MIT — Details →
4.0.1-canary-20240603150341 03 Jun 2024 none MIT — Details →
0.0.0-canary-20240602190113 02 Jun 2024 none MIT — Details →
5.0.0-next.2 22 May 2024 none MIT — Details →
5.0.0-next.1 20 May 2024 none MIT — Details →
5.0.0-next.0 20 May 2024 none MIT — Details →
4.0.0 09 May 2024 none MIT — Details →
4.0.0-rc.2 24 Apr 2024 none — — Details →
4.0.0-rc.1 17 Apr 2024 none — — Details →
4.0.0-rc.0 05 Apr 2024 none — — Details →
1.1.0 18 Dec 2023 none — — Details →
1.0.2 10 Oct 2023 none — — Details →
1.0.1 07 Mar 2023 none — — Details →
1.0.0 16 Sep 2022 none — — Details →
1.0.0-next.3 15 Sep 2022 none — — Details →
1.0.0-next.2 07 Jul 2022 none — — Details →
1.0.0-next.1 01 Jul 2022 none — — Details →
1.0.0-next.0 01 Jul 2022 none — — Details →

All 111 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 @callstack/repack-dev-server

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 @callstack/repack-dev-server

Is @callstack/repack-dev-server safe to use?

Vulert has no vulnerabilities on record for @callstack/repack-dev-server 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 @callstack/repack-dev-server's Vulert package health score?

Vulert scores @callstack/repack-dev-server 78/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 @callstack/repack-dev-server affected?

No. 5.4.2, 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.

How many vulnerabilities does @callstack/repack-dev-server have?

0 vulnerabilities are recorded for @callstack/repack-dev-server 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 @callstack/repack-dev-server vulnerabilities disclosed?

0 vulnerabilities were recorded for @callstack/repack-dev-server 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 @callstack/repack-dev-server 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 @callstack/repack-dev-server for upcoming vulnerabilities?

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