Dependency health Workspace

@mui/mcpnpm

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 →
What the project says about itself
  • Build provenance — the latest release, 0.1.6, carries a signed provenance attestation. Source: the registry.
  • Supported runtime — node >=22.12. Source: the registry.
  • Publishers on the registry — 10. Source: the registry.
  • Security policy — published. Source: the repository.
  • Open milestones — Date and Time Pickers v8 post stable launch 10/11 done; v9.0.0 3/3 done; October Monthly Meeting Scheduler video (due 2025-09-29) 4/4 done; Scheduler beta.0 (due 2026-06-03) 33/37 done; Scheduler stable (due 2026-07-08) 25/28 done. Source: the repository's milestones.
  • OpenSSF Scorecard — 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 today; registry facts on every crawl.

State history 1
WhenChange
2026-09-27 first verdict: active

Badge

maintenance: active

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

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

Watch it

Get told when @mui/mcp 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.