node-sass-package-importernpm
- latest 5.3.3
- licence MIT
- stars 294
- 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 1 check
The first observation is recorded. Trend lines appear once at least two checks have data for the same signal.
Commits 90d
0
Open issues
33
Unanswered
12
Contributors
0
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node >=6.11.1. Source: the registry.
- Publishers on the registry — 1. Source: the registry.
- Open milestones — 0.x.x (due 2016-06-06) 24/24 done; 1.x.x (due 2016-09-30) 31/31 done; 2.x.x (due 2016-12-31) 10/10 done. Source: the repository's milestones.
- OpenSSF Scorecard — 1.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
| When | Change |
|---|---|
| 2026-09-14 | first verdict: finished |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/node-sass-package-importer)Watch it
Get told when node-sass-package-importer 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.