Vulnerability Database · npm · Package report
@parcel/runtime-react-refresh: vulnerability history, versions and safety
@parcel/runtime-react-refresh is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the npm ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on @parcel/runtime-react-refresh 2.13.3 i
Updated on 23 Oct 2026
Good news: 2.13.3, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Maintaining
- Popularity Widely used
- Community Quiet
What to do: Stay on 2.13.3 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.13.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 2.13.3 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 17 packages i
- Stars 44,006 i
- OpenSSF scorecard 2/10 i
- Last release 22 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 @parcel/runtime-react-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.
- 2.0.0-canary.1763 23 Dec 2024
- 2.0.0-canary.1761 17 Dec 2024
- 2.13.3 16 Dec 2024
- 2.0.0-dev.1795 16 Dec 2024
- 2.0.0-dev.1789 10 Dec 2024
- 2.0.0-dev.1781 09 Dec 2024
- 2.0.0-canary.1759 28 Nov 2024
- 2.13.2 25 Nov 2024
- 2.13.1 25 Nov 2024
- 2.0.0-canary.1749 13 Nov 2024
- 2.13.0 12 Nov 2024
- 2.0.0-canary.1742 11 Nov 2024
- 2.0.0-canary.1741 11 Nov 2024
- 2.0.0-canary.1736 10 Nov 2024
- 2.0.0-canary.1735 05 Nov 2024
- 2.0.0-canary.1733 15 Oct 2024
- 2.0.0-canary.1732 11 Oct 2024
- 2.0.0-canary.1731 01 Oct 2024
- 2.0.0-canary.1730 30 Sep 2024
- 2.0.0-canary.1728 29 Sep 2024
- 2.0.0-canary.1727 28 Sep 2024
- 2.0.0-canary.1722 28 Aug 2024
- 2.0.0-canary.1721 28 Aug 2024
- 2.0.0-canary.1720 22 Aug 2024
- 2.0.0-canary.1719 15 Aug 2024
- 2.0.0-canary.1718 13 Aug 2024
- 2.0.0-canary.1717 12 Aug 2024
- 2.0.0-canary.1716 12 Aug 2024
- 2.0.0-canary.1715 09 Aug 2024
- 2.0.0-canary.1714 08 Aug 2024
- 2.0.0-canary.1713 08 Aug 2024
- 2.0.0-canary.1712 06 Aug 2024
- 2.0.0-dev.1712 06 Aug 2024
- 2.0.0-canary.1710 05 Aug 2024
- 2.0.0-canary.1709 05 Aug 2024
- 2.0.0-canary.1707 02 Aug 2024
- 2.0.0-canary.1706 02 Aug 2024
- 2.0.0-canary.1705 02 Aug 2024
- 2.0.0-canary.1704 01 Aug 2024
- 2.0.0-canary.1702 31 Jul 2024
- 2.0.0-canary.1700 31 Jul 2024
- 2.0.0-canary.1699 30 Jul 2024
- 2.0.0-canary.1697 30 Jul 2024
- 2.0.0-canary.1696 29 Jul 2024
- 2.0.0-canary.1695 29 Jul 2024
- 2.0.0-canary.1694 26 Jul 2024
- 2.0.0-canary.1693 26 Jul 2024
- 2.0.0-canary.1690 24 Jul 2024
- 2.0.0-canary.1688 23 Jul 2024
- 2.0.0-canary.1687 19 Jul 2024
- 2.0.0-canary.1685 17 Jul 2024
- 2.0.0-canary.1684 17 Jul 2024
- 2.0.0-canary.1683 17 Jul 2024
- 2.0.0-canary.1681 15 Jul 2024
- 2.0.0-dev.1680 15 Jul 2024
- 2.0.0-canary.1670 11 Jul 2024
- 2.0.0-canary.1669 11 Jul 2024
- 2.0.0-canary.1667 26 Jun 2024
- 2.0.0-canary.1666 26 Jun 2024
- 2.0.0-canary.1665 25 Jun 2024
- 2.0.0-canary.1663 25 Jun 2024
- 2.0.0-canary.1662 25 Jun 2024
- 2.0.0-canary.1661 24 Jun 2024
- 2.0.0-canary.1659 21 Jun 2024
- 2.0.0-canary.1658 21 Jun 2024
- 2.0.0-canary.1656 21 Jun 2024
- 2.0.0-canary.1654 20 Jun 2024
- 2.0.0-canary.1652 19 Jun 2024
- 2.0.0-dev.1652 19 Jun 2024
- 2.0.0-canary.1650 18 Jun 2024
- 2.0.0-canary.1648 18 Jun 2024
- 2.0.0-canary.1647 18 Jun 2024
- 2.0.0-canary.1646 17 Jun 2024
- 2.0.0-canary.1644 17 Jun 2024
- 2.0.0-canary.1643 14 Jun 2024
- 2.0.0-canary.1641 14 Jun 2024
- 2.0.0-canary.1640 13 Jun 2024
- 2.0.0-canary.1639 11 Jun 2024
- 2.0.0-canary.1638 11 Jun 2024
- 2.0.0-canary.1637 07 Jun 2024
- 2.0.0-canary.1636 07 Jun 2024
- 2.0.0-canary.1635 07 Jun 2024
- 2.0.0-canary.1633 06 Jun 2024
- 2.0.0-canary.1632 06 Jun 2024
- 2.0.0-canary.1631 06 Jun 2024
- 2.0.0-canary.1630 05 Jun 2024
- 2.0.0-canary.1629 05 Jun 2024
- 2.0.0-dev.1632 05 Jun 2024
- 2.0.0-canary.1628 04 Jun 2024
- 2.0.0-canary.1627 04 Jun 2024
- 2.0.0-canary.1626 03 Jun 2024
- 2.0.0-canary.1625 02 Jun 2024
- 2.0.0-canary.1624 31 May 2024
- 2.0.0-canary.1622 30 May 2024
- 2.0.0-canary.1621 30 May 2024
- 2.0.0-canary.1620 30 May 2024
- 2.0.0-canary.1619 29 May 2024
- 2.0.0-canary.1618 29 May 2024
- 2.0.0-canary.1617 28 May 2024
- 2.0.0-canary.1616 28 May 2024
- 2.0.0-canary.1615 28 May 2024
- 2.0.0-canary.1614 28 May 2024
- 2.0.0-canary.1613 27 May 2024
- 2.0.0-canary.1612 27 May 2024
- 2.0.0-canary.1611 25 May 2024
- 2.0.0-canary.1610 24 May 2024
- 2.0.0-canary.1609 24 May 2024
- 2.0.0-canary.1608 23 May 2024
- 2.0.0-canary.1607 23 May 2024
- 2.0.0-canary.1606 23 May 2024
- 2.0.0-canary.1605 23 May 2024
- 2.0.0-dev.1605 22 May 2024
- 2.0.0-canary.1604 22 May 2024
- 2.0.0-dev.1604 22 May 2024
- 2.0.0-canary.1602 20 May 2024
- 2.0.0-canary.1601 20 May 2024
- 2.0.0-dev.1601 17 May 2024
- 2.0.0-dev.1602 17 May 2024
- 2.0.0-canary.1600 17 May 2024
- 2.0.0-canary.1599 16 May 2024
The newest 120 of 889 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 @parcel/runtime-react-refresh
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
Questions
About @parcel/runtime-react-refresh
Is @parcel/runtime-react-refresh safe to use?
Vulert has no vulnerabilities on record for @parcel/runtime-react-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 @parcel/runtime-react-refresh's Vulert package health score?
Vulert scores @parcel/runtime-react-refresh 72/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 @parcel/runtime-react-refresh affected?
No. 2.13.3, 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 @parcel/runtime-react-refresh should I use?
2.13.3 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 @parcel/runtime-react-refresh have?
0 vulnerabilities are recorded for @parcel/runtime-react-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 @parcel/runtime-react-refresh vulnerabilities disclosed?
0 vulnerabilities were recorded for @parcel/runtime-react-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 @parcel/runtime-react-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 @parcel/runtime-react-refresh for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @parcel/runtime-react-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.