postcss-nesting
Nest rules inside each other in CSS
2
Versions
MIT-0
License
No
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
jonathantnealalagunaromainmenke
Keywords
atruleschildchildrencsscssnextcsswgnestednestingspostcsspostcss-pluginrulesselectorsspecificationsspecssyntaxw3c
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| license | uncommon-license:MIT-0 | AI (license): MIT-0 is the standard license used across the entire csstools plugin suite; it is a recognized permissive license variant and not a risk for this package. | ai | |
| phantom-deps | phantom-dep:postcss-selector-parser | AI (phantom-deps): Compiled ESM package; imports resolved at build time. postcss-selector-parser is a legitimate core PostCSS ecosystem dependency. | ai | |
| phantom-deps | phantom-dep:@csstools/selector-specificity | AI (phantom-deps): Compiled ESM package from the same csstools org; phantom detection is a build artifact, not a real risk. | ai | |
| phantom-deps | phantom-dep:@csstools/selector-resolve-nested | AI (phantom-deps): Compiled ESM package from the same csstools org; phantom detection is a build artifact, not a real risk. | ai |
v12.1.5
1 finding
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.