@li0ard/kupynanpm
- latest 0.1.4
- last known licence MIT
- stars 4
- assessment attempted 12 days ago
- GitHub evidence observed 12 days ago
- registry checked 12 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 →Moved
The registry still points at li0ard/kupyna, which is archived with a note saying development moved to li0ard/dstu. The verdict above is about the new home.
Maintenance trends
Loading historical repository activity…
Signals · last 3 checks
What the project says about itself
- Build provenance — the latest release, 0.1.4, carries a signed provenance attestation. Source: the registry.
- Publishers on the registry — 1. Source: the registry.
Third-party facts checked 13 days ago; registry facts on every crawl.
State history 2
| When | Change |
|---|---|
| 2026-10-25 | active → abandoned |
| 2026-09-24 | first verdict: active |
Where to go instead 1
-
@li0ard/dstu
Named by the maintainers in the deprecation notice
This package is archived. All DSTU implementations moved to @li0ard/dstu
From the maintainers’ own deprecation notice.
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@li0ard/kupyna)Watch it
Get told when @li0ard/kupyna 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.