@vaadin/vaadin-control-state-mixinnpm
- latest 21.0.5
- licence Apache-2.0
- stars 3
- 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 1 check
The first observation is recorded. Trend lines appear once at least two checks have data for the same signal.
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Publishers on the registry — 12. Source: the registry.
- Open milestones — 2.0.0 1/1 done; Polymer 3 (due 2018-05-09) 1/1 done; Typedefs for P3 components (due 2020-05-31). Source: the repository's milestones.
- OpenSSF Scorecard — 3.7 / 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 5 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-09-13 | first verdict: coasting |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@vaadin/vaadin-control-state-mixin)Watch it
Get told when @vaadin/vaadin-control-state-mixin 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.