@solidjs/signalsnpm
- latest 2.0.0-rc.0
- last known licence MIT
- stars 36,264
- assessment attempted today
- GitHub evidence observed yesterday
- registry checked 22 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 22 checks
Commits 90d
37
Open issues
19
Unanswered
3
Contributors
27
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.
- Open milestones — 0.18.0 7/7 done; 1.0.0 7/7 done; 1.4.0 8/8 done; 1.5.0 12/12 done; 1.6.0 1/1 done. Source: the repository's milestones.
- OpenSSF Scorecard — 5.8 / 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 25 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-13 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@solidjs/signals)Watch it
Get told when @solidjs/signals 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.