markmap-clinpm
- latest 0.18.13
- last known licence MIT
- stars 13,271
- assessment attempted yesterday
- GitHub evidence observed yesterday
- registry checked 25 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 →Came back
After 17 months without a release, markmap-cli published 0.18.13 on 2026-11-06.
Usually this is a maintainer returning. It is also what a hijacked package looks like, so it is worth a glance at what changed before you upgrade.
Maintenance trends
Loading historical repository activity…
Signals · last 26 checks
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node >=18. Source: the registry.
- Publishers on the registry — 1. Source: the registry.
Third-party facts checked 23 days ago; registry facts on every crawl.
State history 2
| When | Change |
|---|---|
| 2026-11-20 | active → abandoned |
| 2026-11-06 | first verdict: active |
Where to go instead 1
-
@markmap
Named by the maintainers in the deprecation notice
Replaced by @markmap/* in 1.0.0. See https://markmap.js.org/docs/migration
From the maintainers’ own deprecation notice.
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/markmap-cli)
Watch it
Get told when markmap-cli 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.