vue-class-componentnpm

Verdict

Looks abandoned

vue-class-component is abandoned by its maintainers' own account — the README says it is no longer maintained, no commits for over 3 years. Plan a migration rather than waiting for a fix.

health 37/100

Why this verdict?

abandoned — No commits for over 365 days with unanswered issues piling up — or the registry marks it deprecated, or the repository is archived.

README says the project is no longer maintained

Judged today from signal heuristics. How each verdict is decided

latest 7.2.6
licence MIT
stars 5,754
checked today
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 3 checks

Commits 90d

Open issues

Unanswered

Contributors

What the project says about itself

Build provenance — the latest release carries no provenance attestation. Source: the registry.
Publishers on the registry — 2. Source: the registry.
OpenSSF Scorecard — 2.3 / 10 on 2026-08-17. Source: OpenSSF, via deps.dev. A third party's view of security practice, not part of the health score.

Third-party facts checked yesterday; registry facts on every crawl.

State history 2

When	Change
2026-09-06	finished → abandoned
2026-09-03	first verdict: finished

Badge

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

[![maintenance](https://isitdeadyet.dev/badge/npm/vue-class-component.svg)](https://isitdeadyet.dev/npm/vue-class-component)

Watch it

Get told when vue-class-component 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.