@topgroup/diginextnpm

Verdict

Looks abandoned

@topgroup/diginext appears abandoned — no commits for 16 months. 31 of 34 open issues have had no reply. Plan a migration rather than waiting for a fix.

health 38/100

Why this verdict?

abandoned — No commits for over 365 days with unanswered issues piling up — or the registry marks it deprecated, or the repository is archived.

last commit 460 days ago
31 open issues with no reply, none closed in 90 days

Judged 23 days ago from signal heuristics. How each verdict is decided

latest 3.43.5
last known licence GPL-3.0
stars 72
assessment attempted 23 days ago
registry checked 18 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

Commits 90d

Open issues

Unanswered

Contributors

What the project says about itself

Build provenance — the latest release carries no provenance attestation. Source: the registry.
Supported runtime — node >=16.0.0. Source: the registry.
Publishers on the registry — 2. Source: the registry.
Open milestones — Diginext 3.x.x 12/26 done; Diginext 4.x.x 0/12 done. Source: the repository's milestones.

Third-party facts checked 23 days ago; registry facts on every crawl.

State history 1

When	Change
2026-10-15	first verdict: abandoned

Badge

Drop this in your README. It re-renders itself as the verdict changes.

[![maintenance](https://isitdeadyet.dev/badge/npm/@topgroup/diginext.svg)](https://isitdeadyet.dev/npm/@topgroup/diginext)

Watch it

Get told when @topgroup/diginext 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.