VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@modern-js/node-bundle-require: vulnerability history, versions and safety

@modern-js/node-bundle-require 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 @modern-js/node-bundle-require vulnerabilities

Vulert verdict on @modern-js/node-bundle-require 2.70.4 i

Updated on 23 Oct 2026

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

Package health score 87/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 2.70.4 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 14 packages i
  • Stars 5,047 i
  • Last release 8 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 @modern-js/node-bundle-require, 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.71.1 06 Jul 2026 none MIT — Details →
0.0.0-next-20260702025624 02 Jul 2026 none MIT — Details →
0.0.0-next-20260702023603 02 Jul 2026 none MIT — Details →
0.0.0-next-20260615040428 15 Jun 2026 none MIT — Details →
2.71.0 14 May 2026 none MIT — Details →
0.0.0-next-20260514052542 14 May 2026 none MIT — Details →
0.0.0-next-20260415065823 15 Apr 2026 none MIT — Details →
2.70.8 26 Feb 2026 none MIT — Details →
0.0.0-next-20260225202135 25 Feb 2026 none MIT — Details →
2.70.7 11 Feb 2026 none MIT — Details →
0.0.0-next-20260211202210 11 Feb 2026 none MIT — Details →
2.70.6 05 Feb 2026 none MIT — Details →
0.0.0-next-20260205150330 05 Feb 2026 none MIT — Details →
2.70.5 04 Feb 2026 none MIT — Details →
0.0.0-next-20260204060406 04 Feb 2026 none MIT — Details →
0.0.0-nightly-20260203160345 03 Feb 2026 none MIT — Details →
0.0.0-nightly-20260202160426 02 Feb 2026 none MIT — Details →
0.0.0-nightly-20260201160409 01 Feb 2026 none MIT — Details →
0.0.0-nightly-20260129160334 29 Jan 2026 none MIT — Details →
2.70.4 28 Jan 2026 none MIT — Details →
0.0.0-next-20260128215517 28 Jan 2026 none MIT — Details →
0.0.0-nightly-20260128160319 28 Jan 2026 none MIT — Details →
0.0.0-next-20260128092347 28 Jan 2026 none MIT — Details →
0.0.0-nightly-20260127160359 27 Jan 2026 none MIT — Details →
0.0.0-nightly-20260127052159 27 Jan 2026 none MIT — Details →
0.0.0-nightly-20260126160400 26 Jan 2026 none MIT — Details →
0.0.0-nightly-20260126053141 26 Jan 2026 none MIT — Details →
0.0.0-nightly-20260125160349 25 Jan 2026 none MIT — Details →
0.0.0-nightly-20260122160415 22 Jan 2026 none MIT — Details →
0.0.0-next-20260122144051 22 Jan 2026 none MIT — Details →
0.0.0-next-20260122125004 22 Jan 2026 none MIT — Details →
2.70.3 22 Jan 2026 none MIT — Details →
0.0.0-nightly-20260122000708 22 Jan 2026 none MIT — Details →
0.0.0-nightly-20260121234925 21 Jan 2026 none MIT — Details →
0.0.0-next-20260121165527 21 Jan 2026 none MIT — Details →
0.0.0-nightly-20260120160322 20 Jan 2026 none MIT — Details →
0.0.0-nightly-20260119162100 19 Jan 2026 none MIT — Details →
0.0.0-nightly-20260118160340 18 Jan 2026 none MIT — Details →
0.0.0-nightly-20260115160344 15 Jan 2026 none MIT — Details →
2.70.2 14 Jan 2026 none MIT — Details →
0.0.0-next-20260114162313 14 Jan 2026 none MIT — Details →
0.0.0-nightly-20260114160340 14 Jan 2026 none MIT — Details →
0.0.0-nightly-20260113172643 13 Jan 2026 none MIT — Details →
0.0.0-next-20260113133219 13 Jan 2026 none MIT — Details →
0.0.0-nightly-20260112160400 12 Jan 2026 none MIT — Details →
0.0.0-nightly-20260111160345 11 Jan 2026 none MIT — Details →
2.70.1 09 Jan 2026 none MIT — Details →
0.0.0-next-20260109015237 09 Jan 2026 none MIT — Details →
0.0.0-nightly-20260108160327 08 Jan 2026 none MIT — Details →
2.70.0 08 Jan 2026 none MIT — Details →
0.0.0-next-20260107225143 07 Jan 2026 none MIT — Details →
0.0.0-nightly-20260107160346 07 Jan 2026 none MIT — Details →
0.0.0-nightly-20260106160418 06 Jan 2026 none MIT — Details →
0.0.0-nightly-20260105160414 05 Jan 2026 none MIT — Details →
0.0.0-nightly-20260104160347 04 Jan 2026 none MIT — Details →
2.69.7 04 Jan 2026 none MIT — Details →
0.0.0-next-20260104061618 04 Jan 2026 none MIT — Details →
0.0.0-nightly-20260101160407 01 Jan 2026 none MIT — Details →
0.0.0-next-20251231161841 31 Dec 2025 none MIT — Details →
0.0.0-nightly-20251231160340 31 Dec 2025 none MIT — Details →
0.0.0-nightly-20251230160354 30 Dec 2025 none MIT — Details →
0.0.0-nightly-20251229160434 29 Dec 2025 none MIT — Details →
0.0.0-nightly-20251228160749 28 Dec 2025 none MIT — Details →
0.0.0-next-20251226104929 26 Dec 2025 none MIT — Details →
2.69.6 26 Dec 2025 none MIT — Details →
0.0.0-next-20251226012313 26 Dec 2025 none MIT — Details →
0.0.0-nightly-20251225160330 25 Dec 2025 none MIT — Details →
0.0.0-next-20251225153934 25 Dec 2025 none MIT — Details →
0.0.0-next-20251225024656 25 Dec 2025 none MIT — Details →
0.0.0-next-20251224162201 24 Dec 2025 none MIT — Details →
0.0.0-nightly-20251224160326 24 Dec 2025 none MIT — Details →
0.0.0-nightly-20251223160450 23 Dec 2025 none MIT — Details →
0.0.0-nightly-20251222160506 22 Dec 2025 none MIT — Details →
0.0.0-nightly-20251221160430 21 Dec 2025 none MIT — Details →
0.0.0-nightly-20251218160339 18 Dec 2025 none MIT — Details →
0.0.0-next-20251218124644 18 Dec 2025 none MIT — Details →
2.69.5 18 Dec 2025 none MIT — Details →
0.0.0-next-20251218061830 18 Dec 2025 none MIT — Details →
0.0.0-next-20251217161906 17 Dec 2025 none MIT — Details →
0.0.0-nightly-20251217160325 17 Dec 2025 none MIT — Details →
0.0.0-nightly-20251216161304 16 Dec 2025 none MIT — Details →
0.0.0-nightly-20251216073144 16 Dec 2025 none MIT — Details →
0.0.0-nightly-20251216065633 16 Dec 2025 none MIT — Details →
0.0.0-nightly-20251215160353 15 Dec 2025 none MIT — Details →
0.0.0-nightly-20251214160359 14 Dec 2025 none MIT — Details →
2.69.4 10 Dec 2025 none MIT — Details →
0.0.0-next-20251210162220 10 Dec 2025 none MIT — Details →
0.0.0-nightly-20251210160403 10 Dec 2025 none MIT — Details →
0.0.0-nightly-20251209162031 09 Dec 2025 none MIT — Details →
0.0.0-nightly-20251208160341 08 Dec 2025 none MIT — Details →
2.69.3 08 Dec 2025 none MIT — Details →
0.0.0-next-20251208053740 08 Dec 2025 none MIT — Details →
0.0.0-nightly-20251207160349 07 Dec 2025 none MIT — Details →
0.0.0-nightly-20251204160442 04 Dec 2025 none MIT — Details →
0.0.0-canary-20251204150245 04 Dec 2025 none MIT — Details →
0.0.0-canary-20251204133729 04 Dec 2025 none MIT — Details →
2.69.2 04 Dec 2025 none MIT — Details →
0.0.0-next-20251203163643 03 Dec 2025 none MIT — Details →
0.0.0-nightly-20251203160323 03 Dec 2025 none MIT — Details →
0.0.0-canary-20251203081255 03 Dec 2025 none MIT — Details →
0.0.0-canary-20251203033413 03 Dec 2025 none — — Details →
0.0.0-nightly-20251202161653 02 Dec 2025 none — — Details →
0.0.0-canary-20251202061928 02 Dec 2025 none — — Details →
0.0.0-nightly-20251201160350 01 Dec 2025 none — — Details →
0.0.0-canary-20251201094119 01 Dec 2025 none — — Details →
0.0.0-canary-20251201034908 01 Dec 2025 none — — Details →
0.0.0-canary-20251201032222 01 Dec 2025 none — — Details →
0.0.0-nightly-20251130160348 30 Nov 2025 none — — Details →
0.0.0-canary-20251128092744 28 Nov 2025 none — — Details →
0.0.0-canary-20251128085938 28 Nov 2025 none — — Details →
0.0.0-canary-20251128032940 28 Nov 2025 none — — Details →
0.0.0-canary-20251128024150 28 Nov 2025 none — — Details →
0.0.0-canary-20251128015459 28 Nov 2025 none — — Details →
0.0.0-nightly-20251127160358 27 Nov 2025 none — — Details →
0.0.0-canary-20251127125634 27 Nov 2025 none — — Details →
0.0.0-canary-20251127075930 27 Nov 2025 none — — Details →
0.0.0-canary-20251127063701 27 Nov 2025 none — — Details →
0.0.0-next-20251127050705 27 Nov 2025 none — — Details →
0.0.0-canary-20251127032505 27 Nov 2025 none — — Details →
0.0.0-canary-20251127020934 27 Nov 2025 none — — Details →

The newest 120 of 4,219 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 @modern-js/node-bundle-require

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 @modern-js/node-bundle-require

Is @modern-js/node-bundle-require safe to use?

Vulert has no vulnerabilities on record for @modern-js/node-bundle-require 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 @modern-js/node-bundle-require's Vulert package health score?

Vulert scores @modern-js/node-bundle-require 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 @modern-js/node-bundle-require affected?

No. 2.70.4, 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 @modern-js/node-bundle-require should I use?

2.70.4 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 @modern-js/node-bundle-require have?

0 vulnerabilities are recorded for @modern-js/node-bundle-require 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 @modern-js/node-bundle-require vulnerabilities disclosed?

0 vulnerabilities were recorded for @modern-js/node-bundle-require 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 @modern-js/node-bundle-require 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 @modern-js/node-bundle-require for upcoming vulnerabilities?

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