postcss-custom-media
Use Custom Media Queries in CSS
3
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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
jonathantnealalagunaromainmenkemooxsemigradsky
Keywords
at-ruleatrulecsscsswgcustommediapostcsspostcss-pluginqueriesqueryspecificationw3c
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): First-party @csstools dep declared in package.json; phantom detection is a false positive from ESM dist output analysis. | ai | |
| phantom-deps | phantom-dep:@csstools/css-parser-algorithms | AI (phantom-deps): First-party @csstools dep declared in package.json; phantom detection is a false positive from ESM dist output analysis. | ai | |
| phantom-deps | phantom-dep:@csstools/media-query-list-parser | AI (phantom-deps): First-party @csstools dep declared in package.json; phantom detection is a false positive from ESM dist output analysis. | ai | |
| phantom-deps | phantom-dep:@csstools/cascade-layer-name-parser | AI (phantom-deps): First-party @csstools dep declared in package.json; phantom detection is a false positive from ESM dist output analysis. | ai | |
| provenance | no-provenance | AI (provenance): Publisher has a strong track record (58 approved packages); lack of provenance is common and not a risk signal here. | ai |
v12.0.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.2
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.