Is vue healthy, maintained, and safe?
Yes — vue looks healthy, actively maintained, and free of known advisories today.
The verdict
OSPulse scores vue at 87/100 (minimal risk), computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. Yes — vue looks healthy, actively maintained, and free of known advisories today.
Its most recent release shipped on 22 July 2026 — 5 days ago — so development is clearly active. Across 585 releases the cadence has been steady, which is a good sign of an ongoing maintenance rhythm. Two maintainers are listed; better than a lone author, but still a thin bench if one steps away.
OSV lists 1 known advisory for vue, of assorted severity. Review whether your version is in the affected range and whether a fixed release is available before depending on it. Each advisory is listed with its OSV/GHSA identifier below.
The signals are green today, but a clean snapshot is not a standing guarantee — packages drift. This is a one-time snapshot of a single package — real projects depend on dozens or hundreds of packages, and any one of them can drift or be compromised between releases. Run your own package.json through the free health check, or have OSPulse monitor your whole dependency tree continuously.
Evidence trail — deterministic, auditable
Known vulnerabilities (1)
ReDoS vulnerability in vue package that is exploitable through inefficient regex evaluation in the parseHTML function
Key facts
- Latest version
- v3.5.40
- Last release
- 22 July 2026 (5 days ago)
- Total releases
- 585
- First release
- 7 December 2013
- Package age
- 12.6 years
- Maintainers
- 2
- Known advisories
- 1
- Confidence
- High
Frequently asked
Is vue still maintained?
Yes — vue released as recently as 22 July 2026 (5 days ago), so it is actively maintained.
Does vue have known security vulnerabilities?
Yes — OSV lists 1 advisory for vue. See the advisory list on this page for the OSV/GHSA identifiers.
Is vue safe to use?
Yes — vue looks healthy, actively maintained, and free of known advisories today. OSPulse rates it 87/100 (minimal risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
vue is one package. What about the other hundreds in your tree?
Paste your own package.json into the free health check for an instant snapshot — or let OSPulse monitor your whole dependency tree continuously, before your CVE scanner wakes up.
Data from the npm registry & OSV.dev · snapshot generated 2026-07-27 · scores are deterministic and recomputed on each refresh.
