← Home

postcss-selector-matches

npm Repository Homepage

PostCSS plugin to transform :matches() W3C CSS pseudo class to more compatible CSS selectors

17
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

jonathantnealmooxsemigradsky

Keywords

postcsspostcss-pluginselectorsselectormatches

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): jonathantneal is a well-established PostCSS ecosystem maintainer with 677 approved packages and 0 rejected; transition to postcss org ownership is legitimate. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy is consistent with the maintainer transition from semigradsky to jonathantneal; no other risk signals present. ai

Versions (showing 17 of 17)

Version Deps Published
4.0.0 2 / 9
3.0.1 2 / 9
3.0.0 2 / 8
2.0.5 2 / 7
2.0.4 2 / 7
2.0.3 2 / 7
2.0.2 2 / 7
2.0.1 2 / 5
2.0.0 2 / 5
1.2.1 2 / 5
1.2.0 2 / 5
1.1.2 2 / 5
1.1.1 2 / 5
1.1.0 2 / 5
1.0.2 2 / 5
1.0.1 2 / 5
1.0.0 2 / 5

v4.0.0

2 findings
HIGH Publisher changed: semigradsky → jonathantneal (on 2018-09-18) provenance

This version was published by a different npm account than previous versions on 2018-09-18. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: moox → semigradsky (on 2017-05-11) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-05-11. This could indicate a legitimate maintainer transition or an account compromise.