node-sassnpm
- latest 9.0.0
- last known licence MIT
- stars 8,436
- assessment attempted today
- GitHub evidence observed today
- registry checked today
- 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 60 checks
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node >=16. Source: the registry.
- Publishers on the registry — 2. Source: the registry.
- Open milestones — Unknown 3/6 done; bridge.rewrite 1/3 done; 5.0 18/23 done. Source: the repository's milestones.
- OpenSSF Scorecard — 3.2 / 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 4 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-07 | first verdict: dead |
Where to go instead 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
Drop this in your README. It re-renders itself as the verdict changes.
[](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.