@misskey-dev/node-http-message-signaturesnpm
- latest 1.1.2
- last known licence MIT
- stars 0
- assessment attempted 23 days ago
- GitHub evidence observed 23 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 →Came back
After 2 years without a release, @misskey-dev/node-http-message-signatures published 1.1.2 on 2026-10-05.
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 2 checks
What the project says about itself
- Build provenance — the latest release, 1.1.2, carries a signed provenance attestation. Source: the registry.
- Supported runtime — node >=18.4.0. Source: the registry.
- Publishers on the registry — 6. Source: the registry.
Third-party facts checked 23 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-20 | first verdict: finished |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@misskey-dev/node-http-message-signatures)Watch it
Get told when @misskey-dev/node-http-message-signatures 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.