@medplum/reactnpm
- latest 5.2.7
- last known licence Apache-2.0
- stars 2,758
- assessment attempted 19 days ago
- GitHub evidence observed 19 days ago
- registry checked 19 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
100
Open issues
584
Unanswered
359
Contributors
18
What the project says about itself
- Build provenance — the latest release, 5.2.7, carries a signed provenance attestation. Source: the registry.
- Supported runtime — node ^22.18.0 || >=24.2.0. Source: the registry.
- Publishers on the registry — 3. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — Milestone Quality 227/624 done; v6 0/18 done; October 31, 2026 (due 2026-10-30) 70/221 done; November 30, 2026 (due 2026-11-29). Source: the repository's milestones.
- OpenSSF Scorecard — 8.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 19 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-23 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@medplum/react)Watch it
Get told when @medplum/react 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.