@antv/g2npm
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 5.4.8
- last known licence MIT
- stars 12,654
- assessment attempted yesterday
- GitHub evidence observed yesterday
- 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 27 checks
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Publishers on the registry — 20. Source: the registry.
- OpenSSF Scorecard — 5.5 / 10 on 2026-08-24. Source: OpenSSF, via deps.dev. A third party's view of security practice, not part of the health score.
Third-party facts checked 30 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-05 | first verdict: active |
Supply-chain history 1
-
account hijacked 2026-05 5.5.8, 5.6.8
One maintainer account with broad publishing rights republished hundreds of packages in twenty minutes with a pre-install step that ran a credential-stealing worm.
Removed; the stolen tokens had already created over 2,700 rogue repositories.
Source: Aikido analysis, 19 May 2026. 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/@antv/g2)Watch it
Get told when @antv/g2 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.