Vulnerability Database · npm · Package report

@astrojs/react: vulnerability history, versions and safety

@astrojs/react 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 @astrojs/react 7.1.1 i

Updated on 23 Oct 2026

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

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

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

  • Current release 7.1.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 11 packages i
  • Stars 63,299 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 @astrojs/react, 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
7.1.1 21 Oct 2026 none MIT — Details →
7.1.0 15 Oct 2026 none MIT — Details →
7.0.1 06 Oct 2026 none MIT — Details →
7.0.0 22 Sep 2026 none MIT — Details →
6.0.6 16 Sep 2026 none MIT — Details →
6.0.5 31 Aug 2026 none MIT — Details →
6.0.4 19 Aug 2026 none MIT — Details →
6.0.3 18 Aug 2026 none MIT — Details →
6.0.2 28 Jul 2026 none MIT — Details →
6.0.1 02 Jul 2026 none MIT — Details →
6.0.0 22 Jun 2026 none MIT — Details →
6.0.0-beta.2 18 Jun 2026 none MIT — Details →
6.0.0-beta.1 13 Jun 2026 none MIT — Details →
5.0.7 02 Jun 2026 none MIT — Details →
5.0.6 28 May 2026 none MIT — Details →
5.0.5 13 May 2026 none MIT — Details →
6.0.0-alpha.0 30 Apr 2026 none MIT — Details →
5.0.4 22 Apr 2026 none MIT — Details →
5.0.3 06 Apr 2026 none MIT — Details →
5.0.2 26 Mar 2026 none MIT — Details →
5.0.1 18 Mar 2026 none MIT — Details →
5.0.0 10 Mar 2026 none MIT — Details →
5.0.0-beta.4 06 Mar 2026 none MIT — Details →
5.0.0-beta.3 27 Jan 2026 none MIT — Details →
5.0.0-beta.2 23 Jan 2026 none MIT — Details →
5.0.0-beta.1 13 Jan 2026 none MIT — Details →
5.0.0-alpha.0 10 Nov 2025 none MIT — Details →
4.4.2 06 Nov 2025 none MIT — Details →
4.4.1 28 Oct 2025 none MIT — Details →
4.4.0 25 Sep 2025 none MIT — Details →
4.3.1 08 Sep 2025 none MIT — Details →
4.3.0 22 May 2025 none MIT — Details →
4.2.7 30 Apr 2025 none MIT — Details →
4.2.6 29 Apr 2025 none MIT — Details →
4.2.5 23 Apr 2025 none MIT — Details →
4.2.4 14 Apr 2025 none MIT — Details →
4.2.3 31 Mar 2025 none MIT — Details →
4.2.2 26 Mar 2025 none MIT — Details →
4.2.1 27 Feb 2025 none MIT — Details →
0.0.0-router-noexec-20250129135648 29 Jan 2025 none MIT — Details →
4.2.0 27 Jan 2025 none MIT — Details →
4.1.6 20 Jan 2025 none MIT — Details →
4.1.5 15 Jan 2025 none MIT — Details →
4.1.4 13 Jan 2025 none MIT — Details →
4.1.3 10 Jan 2025 none MIT — Details →
4.1.2 20 Dec 2024 none MIT — Details →
4.1.1 16 Dec 2024 none MIT — Details →
0.0.0-atomic-writes-20241212091949 12 Dec 2024 none MIT — Details →
0.0.0-atomic-writes-20241211120224 11 Dec 2024 none MIT — Details →
0.0.0-atomic-writes-20241211112453 11 Dec 2024 none MIT — Details →
4.1.0 11 Dec 2024 none MIT — Details →
4.0.0 03 Dec 2024 none MIT — Details →
0.0.0-sessions-20241128172109 28 Nov 2024 none MIT — Details →
0.0.0-sessions-20241128161723 28 Nov 2024 none MIT — Details →
0.0.0-sessions-20241128134018 28 Nov 2024 none MIT — Details →
0.0.0-sessions-20241128091859 28 Nov 2024 none MIT — Details →
4.0.0-beta.2 27 Nov 2024 none MIT — Details →
0.0.0-sessions-20241127112400 27 Nov 2024 none MIT — Details →
3.7.0-beta.1 26 Nov 2024 none MIT — Details →
0.0.0-sessions-20241125115314 25 Nov 2024 none MIT — Details →
0.0.0-sessions-20241125113325 25 Nov 2024 none MIT — Details →
0.0.0-sessions-20241122143330 22 Nov 2024 none MIT — Details →
0.0.0-sessions-20241122114539 22 Nov 2024 none MIT — Details →
3.6.3 21 Nov 2024 none MIT — Details →
3.6.3-beta.0 21 Nov 2024 none MIT — Details →
3.6.2 09 Aug 2024 none MIT — Details →
3.6.1 30 Jul 2024 none MIT — Details →
3.6.0 17 Jun 2024 none MIT — Details →
0.0.0-experimental-container-20240613104104 13 Jun 2024 none MIT — Details →
3.5.0 06 Jun 2024 none MIT — Details →
0.0.0-container-20240524172326 24 May 2024 none MIT — Details →
0.0.0-container-20240524171635 24 May 2024 none MIT — Details →
0.0.0-container-20240524165819 24 May 2024 none MIT — Details →
0.0.0-container-20240524153820 24 May 2024 none MIT — Details →
0.0.0-container-20240524151016 24 May 2024 none MIT — Details →
3.4.0 23 May 2024 none MIT — Details →
0.0.0-astro-env-20240522153443 22 May 2024 none MIT — Details →
3.3.4 09 May 2024 none MIT — Details →
3.3.3 09 May 2024 none MIT — Details →
0.0.0-astro-env-20240508155554 08 May 2024 none MIT — Details →
0.0.0-react-19-20240503180451 03 May 2024 none MIT — Details →
0.0.0-react-19-20240503135357 03 May 2024 none MIT — Details →
0.0.0-cc-preserve-cache-20240502141405 02 May 2024 none MIT — Details →
3.3.2 02 May 2024 none MIT — Details →
3.3.1 23 Apr 2024 none MIT — Details →
3.3.0 11 Apr 2024 none MIT — Details →
0.0.0-10745-20240410180016 10 Apr 2024 none MIT — Details →
3.2.0 09 Apr 2024 none MIT — Details →
0.0.0-toolbar-improvements-20240405144822 05 Apr 2024 none MIT — Details →
3.1.1 02 Apr 2024 none MIT — Details →
3.1.0 11 Mar 2024 none MIT — Details →
0.0.0-non-admin-test-20240308195029 08 Mar 2024 none MIT — Details →
3.0.10 07 Feb 2024 none MIT — Details →
3.0.9 27 Dec 2023 none MIT — Details →
0.0.0-dupicate-content-entry-improved-message-20231220220040 20 Dec 2023 none MIT — Details →
3.0.8 20 Dec 2023 none MIT — Details →
3.0.7 05 Dec 2023 none MIT — Details →
3.0.7-beta.0 27 Nov 2023 none MIT — Details →
3.0.6 21 Nov 2023 none MIT — Details →
0.0.0-self-closing-children-20231120173528 20 Nov 2023 none MIT — Details →
0.0.0-self-closing-children-20231120171409 20 Nov 2023 none — — Details →
0.0.0-self-closing-children-20231120164333 20 Nov 2023 none — — Details →
3.0.5 16 Nov 2023 none — — Details →
3.0.4 24 Oct 2023 none — — Details →
0.0.0-react-children-client-20231023164643 23 Oct 2023 none — — Details →
3.0.3 05 Oct 2023 none — — Details →
3.0.2 08 Sep 2023 none — — Details →
0.0.0-perf-20230907211643 07 Sep 2023 none — — Details →
0.0.0-perf-20230907211008 07 Sep 2023 none — — Details →
3.0.1 06 Sep 2023 none — — Details →
3.0.0 30 Aug 2023 none — — Details →
3.0.0-rc.6 29 Aug 2023 none — — Details →
3.0.0-rc.5 25 Aug 2023 none — — Details →
3.0.0-rc.4 22 Aug 2023 none — — Details →
2.3.2 18 Aug 2023 none — — Details →
3.0.0-beta.3 18 Aug 2023 none — — Details →
2.3.1 18 Aug 2023 none — — Details →
2.3.0 18 Aug 2023 none — — Details →
2.2.2 15 Aug 2023 none — — Details →
3.0.0-beta.2 14 Aug 2023 none — — Details →

The newest 120 of 168 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 @astrojs/react

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 @astrojs/react

Is @astrojs/react safe to use?

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

Vulert scores @astrojs/react 94/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 @astrojs/react affected?

No. 7.1.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.

How many vulnerabilities does @astrojs/react have?

0 vulnerabilities are recorded for @astrojs/react 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 @astrojs/react vulnerabilities disclosed?

0 vulnerabilities were recorded for @astrojs/react 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 @astrojs/react 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 @astrojs/react for upcoming vulnerabilities?

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