← Home

node-sass

npm Repository Homepage

Wrapper around libsass

2
Versions
MIT
License
Yes
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

saperskinschonnixzyfer

Keywords

csslibsasspreprocessorsassscssstyle

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata bundled-binaries AI (npm-metadata): Bundled .node and .o files are the expected artifacts of a native libsass binding; precompiled binaries for multiple platforms are a standard distribution pattern for this package. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require uses a fully controlled __dirname-based path to load the native binding; no user-supplied input involved. Standard native addon loading pattern. ai

Versions (showing 2 of 2)

Version Deps Published
0.2.3 1 / 0
0.2.2 1 / 0

v0.2.3

2 findings
HIGH Bundled binary files (15) npm-metadata

Package contains compiled binaries that could be backdoors: • precompiled/darwin-x64/binding.node • precompiled/linux-ia32/binding.node • precompiled/linux-x64/binding.node • build/Release/binding.node • build/Release/obj.target/binding/binding.o • build/Release/obj.target/binding/libsass/context.o • build/Release/obj.target/binding/libsass/document.o • build/Release/obj.target/binding/libsass/document_parser.o • build/Release/obj.target/binding/libsass/eval_apply.o • build/Release/obj.target/binding/libsass/functions.o ... and 5 more

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.2

2 findings
HIGH Bundled binary files (14) npm-metadata

Package contains compiled binaries that could be backdoors: • precompiled/darwin/binding.node • precompiled/linux/binding.node • build/Release/binding.node • build/Release/obj.target/binding/binding.o • build/Release/obj.target/binding/libsass/context.o • build/Release/obj.target/binding/libsass/document.o • build/Release/obj.target/binding/libsass/document_parser.o • build/Release/obj.target/binding/libsass/eval_apply.o • build/Release/obj.target/binding/libsass/functions.o • build/Release/obj.target/binding/libsass/node.o ... and 4 more

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.