@vuelidate/corenpm

Verdict

Finished, not abandoned

@vuelidate/core looks complete rather than neglected — no commits for 15 months. 49 of 198 open issues have had no reply. A library that has stopped changing is not the same as one that has been dropped.

health 36/100

Why this verdict?

finished — No commits for over 365 days, and almost nobody filing new issues — or the README says the project is done.

last commit 459 days ago
almost no new issues — nobody is waiting on a fix

Judged 5 days ago from signal heuristics. How each verdict is decided

latest 2.0.3
licence MIT
stars 6,870
checked 5 days ago
registry ↗
repository ↗

Vulnerabilities, end of life and next steps

Check a specific version for known advisories, documented mitigations and evidence-backed earlier-version options. Maintenance health is separate from vulnerability status.

Review remediation options →

Maintenance trends

Loading historical repository activity…

Signals · last 2 checks

Commits 90d

Open issues

198

Unanswered

Contributors

What the project says about itself

Build provenance — the latest release carries no provenance attestation. Source: the registry.
Publishers on the registry — 3. Source: the registry.
Security policy — published. Source: the repository.
OpenSSF Scorecard — 4.4 / 10 on 2026-08-24. Source: OpenSSF, via deps.dev. A third party's view of security practice, not part of the health score.

Third-party facts checked 6 days ago; registry facts on every crawl.

State history 1

When	Change
2026-09-13	first verdict: finished

Badge

Drop this in your README. It re-renders itself as the verdict changes.

[![maintenance](https://isitdeadyet.dev/badge/npm/@vuelidate/core.svg)](https://isitdeadyet.dev/npm/@vuelidate/core)

Watch it

Get told when @vuelidate/core changes state, changes licence, or is deprecated — instead of finding out during an incident.

Free for up to 25 packages. Signing in is a link sent to your email — there is no password to choose.