Is It Dead Yet? dependency vitals

node-sassnpm

Signals · last 1 check

Commits 90d
0
Open issues
146
Unanswered
31
Contributors
0
What the project says about itself
  • Build provenance — the latest release carries no provenance attestation. Source: the registry.
  • Supported runtimenode >=16. Source: the registry.
  • Publishers on the registry — 2. Source: the registry.
  • Open milestonesUnknown 3/6 done; bridge.rewrite 1/3 done; 5.0 18/23 done. Source: the repository's milestones.
  • OpenSSF Scorecard3.2 / 10 on 2026-08-17. Source: OpenSSF, via deps.dev. A third party's view of security practice, not part of the health score.

Third-party facts checked yesterday; registry facts on every crawl.

State history 1
WhenChange
2026-09-03 first verdict: dead
Where to go instead 1
  1. sass Drop-in replacement

    The reference implementation; node-sass is its deprecated binding

    `npm rm node-sass && npm i -D sass`. No native build step, and no Node version to match.

    Checked by hand.

Badge

maintenance: dead

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

[![maintenance](https://isitdeadyet.dev/badge/npm/node-sass.svg)](https://isitdeadyet.dev/npm/node-sass)

Watch it

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