postcss-custom-selectors
Use Custom Selectors in CSS
2
Versions
MIT
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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
jonathantnealalagunaromainmenkeyisimooxsemigradsky
Keywords
at-ruleatrulecsscsswgcustomdeclarativeextensionspostcsspostcss-pluginruleselectorsspecificationw3c
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@csstools/css-tokenizer | AI (phantom-deps): Package is declared as a direct dependency in package.json; phantom detection reflects monorepo/config-file usage pattern, not a real risk. | ai | |
| phantom-deps | phantom-dep:postcss-selector-parser | AI (phantom-deps): Package is declared as a direct dependency in package.json; phantom detection reflects monorepo/config-file usage pattern, not a real risk. | ai | |
| phantom-deps | phantom-dep:@csstools/css-parser-algorithms | AI (phantom-deps): Package is declared as a direct dependency in package.json; phantom detection reflects monorepo/config-file usage pattern, not a real risk. | ai | |
| phantom-deps | phantom-dep:@csstools/cascade-layer-name-parser | AI (phantom-deps): Package is declared as a direct dependency in package.json; phantom detection reflects monorepo/config-file usage pattern, not a real risk. | ai |
v9.0.0
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.