A collection of SCSS-specific rules for Stylelint
88%
Total Score
100
100
100
70
50
No build attestation or trusted-publisher identity is available, so consumers cannot independently verify that the registry artifact came from the reviewed source. The transparent repository and matching package mention partly offset this gap.
The package uses a prepare install-time lifecycle script, which adds some installation complexity and supply-chain exposure, though no other evidence here indicates unsafe workflow behavior.
The repository has no published security policy, leaving vulnerability-reporting expectations less clear for users and contributors.
Two workflows declare read-only permissions, and none declare top-level write access; one code-scanning workflow lacks top-level permissions, which is a minor configuration gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
css-tree Version ^3.2.1 | — | — |
is-plain-object Version ^5.1.0 | — | — |
@csstools/css-calc Version ^3.3.0 | — | — |
known-css-properties Version ^0.37.0 | — | — |
postcss-value-parser Version ^4.2.0 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.