Is node-sass healthy, maintained, and safe?

The verdict

node-sass earns a health score of 19/100, a critical risk rating, computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. No. node-sass looks abandoned and still has open security advisories.

The last sign of life was 20 May 2023, more than 3 years ago (1214 days). By any practical measure the package looks abandoned. Historically it released far more frequently, so the current silence reads as a genuine collapse in velocity rather than a natural gap. Two maintainers are listed, better than a lone author, but still a thin bench if one steps away.

OSV lists 2 known advisories for node-sass, of assorted severity. Review whether your version is in the affected range and whether a fixed release is available before depending on it. Each advisory is listed with its OSV/GHSA identifier below.

The safest reading is to replace, fork, or tightly pin node-sass and stop taking on new exposure to it. This is a one-time snapshot of a single package. Real projects depend on dozens or hundreds of packages, and any one of them can drift or be compromised between releases. Run your own package.json through the free health check, or have OSPulse monitor your whole dependency tree continuously.