@asyncapi/clinpm
This package has dated incident reports relevant to its trust history. Check the affected releases and the response before drawing conclusions about its current version.
Read the incident coverage →- latest 6.2.1
- last known licence Apache-2.0
- stars 273
- assessment attempted 25 days ago
- registry checked 20 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 10 checks
What the project says about itself
- Build provenance — the latest release, 6.2.1, carries a signed provenance attestation. Source: the registry.
- Supported runtime — node >=24.0.0. Source: the registry.
- Publishers on the registry — 1. Source: the registry.
Third-party facts checked 25 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-12 | first verdict: active |
Supply-chain history 1
-
account hijacked 2025-11
Republished by the second Shai-Hulud worm with a pre-install step that stole npm, GitHub and cloud credentials and used them to backdoor the victim’s own packages.
Contained by npm within a day; the worm reached 796 packages.
Source: Datadog Security Labs analysis of Shai-Hulud 2.0, 25 November 2025. History, not a warning about today — the verdict above is about maintenance now.
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@asyncapi/cli)Watch it
Get told when @asyncapi/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.