Use cascade layers in CSS
78%
Total Score
healthy
Active project, but all recent commits come from one contributor and the package is not named in its linked repository.
No build attestation or trusted-publisher provenance is present, leaving publication origin less independently verifiable than it could be.
One contributor made 100% of the 436 recent commits. Organization backing provides some handoff capacity, but no second active contributor is shown.
There were 436 commits in the last 3 months, but only one active maintainer made them, so activity is high but concentrated.
The linked repository name does not match the package and its README does not mention the package, creating some uncertainty about package-to-repository identity; the monorepo context partly explains the name mismatch but not the absent mention.
All 5 workflows were analyzed successfully, all 10 action references are pinned, and 4 workflows use read-only permissions. One workflow has top-level write permissions, but no untrusted checkout, injection, or audit findings were reported.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
postcss-selector-parser Version ^7.1.1 | — | — |
@csstools/selector-specificity Version ^6.0.1 | — | — |
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.