Dependency health Workspace Pro coming soon

@antv/x6npm

Documented supply-chain history

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 →

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 →
What the project says about itself
  • Build provenance — the latest release carries no provenance attestation. Source: the registry.
  • Supported runtime — node >=20.0.0. Source: the registry.
  • Publishers on the registry — 19. Source: the registry.
  • Security policy — published. Source: the repository.
  • OpenSSF Scorecard — 4.8 / 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 today; registry facts on every crawl.

State history 1
WhenChange
2026-11-06 first verdict: active
Supply-chain history 1
  1. account hijacked 2026-05 3.2.7, 3.3.7

    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

maintenance: active

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

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

Watch it

Get told when @antv/x6 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.