Dependency health Workspace Solo coming soon

alasqlnpm

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 >=15. Source: the registry.
  • Publishers on the registry — 2. Source: the registry.
  • Security policy — published. Source: the repository.
  • Open milestones — ES6 src 1/1 done; Breaking change (for v5.0.0) 4/85 done; The Back Burner 0/7 done; v4.x Focus 24/55 done; v5.x Focus 0/68 done. Source: the repository's milestones.

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

State history 1
WhenChange
2026-11-16 first verdict: active

Badge

maintenance: active

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

[![maintenance](https://isitdeadyet.dev/badge/npm/alasql.svg)](https://isitdeadyet.dev/npm/alasql)

Watch it

Get told when alasql 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.