@ghayma/authnpm
- latest 0.8.1
- last known licence MIT
- stars 0
- assessment attempted 13 days ago
- GitHub evidence observed 13 days ago
- registry checked 13 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 2 checks
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node >=18.0.0. 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
-
@ghayma/sdk/client
Named by the maintainers in the deprecation notice
Use @ghayma/sdk/client instead: same API, and @ghayma/auth gets no further releases.
From the maintainers’ own deprecation notice.
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@ghayma/auth)Watch it
Get told when @ghayma/auth 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.