postcss-selector-parser

> Selector parser with built in methods for working with selector strings.

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

aichriseppsteinjonathantnealevilebottnawi

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): evilebottnawi is a long-standing postcss ecosystem maintainer (2863 days, 1816 approved). Legitimate maintainer transition within the postcss org.	ai	2026/04/23
maintainer-change	maintainer-added	AI (maintainer-change): evilebottnawi is a trusted postcss/webpack ecosystem maintainer with extensive track record.	ai	2026/04/23
maintainer-change	maintainer-removed	AI (maintainer-change): Maintainer list cleanup consistent with postcss org transition; no signs of hostile takeover.	ai	2026/04/23
publish-pattern	new-deps-added	AI (publish-pattern): util-deprecate is a widely-used, tiny utility (~50M downloads/week); benign addition for deprecation warnings.	ai	2026/04/23
dependencies	unvetted-dep:cssesc	AI (dependencies): cssesc is a well-known, stable CSS escaping utility in the PostCSS ecosystem; no security concerns associated with it.	ai	2026/04/21

Versions (showing 53 of 53)

Version	Deps	Published
7.1.0	2 / 19	2025-02-07
7.0.0	2 / 19	2024-10-23
6.1.2	2 / 19	2024-08-12
6.1.1	2 / 19	2024-07-11
6.1.0	2 / 19	2024-05-22
6.0.16	2 / 19	2024-03-13
6.0.15	2 / 19	2023-12-29
6.0.14	2 / 19	2023-12-25
6.0.13	2 / 19	2023-05-15
6.0.12	2 / 19	2023-04-29
6.0.11	2 / 19	2022-11-20
6.0.10	2 / 19	2022-03-30
6.0.9	2 / 19	2022-01-20
6.0.8	2 / 19	2021-12-22
6.0.7	2 / 19	2021-12-09
6.0.6	2 / 19	2021-05-11
6.0.5	2 / 19	2021-04-19
6.0.4	4 / 19	2020-09-25
6.0.3	4 / 18	2020-09-21
6.0.2	3 / 18	2019-03-06
6.0.1	3 / 18	2019-03-05
6.0.0	3 / 18	2019-02-25
5.0.0	3 / 20	2018-12-22
4.0.0	3 / 20	2018-04-24
3.1.2	3 / 19	2020-02-14
3.1.1	3 / 19	2017-11-07
3.1.0	3 / 19	2017-10-24
3.0.0	3 / 19	2017-10-23
2.2.3	3 / 18	2017-02-23
2.2.2	3 / 18	2016-11-10
2.2.1	3 / 18	2016-08-26
2.2.0	3 / 18	2016-08-06
2.1.1	3 / 18	2016-07-10
2.1.0	3 / 15	2016-06-19
2.0.0	3 / 15	2016-05-03
1.3.3	3 / 13	2016-03-04
1.3.2	3 / 13	2016-02-26
1.3.1	3 / 11	2016-02-01
1.3.0	3 / 4	2015-09-29
1.2.1	3 / 4	2015-09-28
1.2.0	3 / 4	2015-09-06
1.1.4	3 / 4	2015-08-19
1.1.3	3 / 4	2015-08-17
1.1.2	3 / 4	2015-07-02
1.1.1	3 / 4	2015-06-23
1.1.0	3 / 4	2015-06-23
1.0.1	3 / 4	2015-06-15
1.0.0	3 / 4	2015-06-14
0.0.5	3 / 4	2015-06-08
0.0.4	3 / 4	2015-06-07
0.0.3	3 / 4	2015-06-02
0.0.2	3 / 4	2015-05-29
0.0.1	3 / 4	2015-05-29

v7.1.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.

v7.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.

v6.1.2

2 findings

HIGH Publisher changed: jonathantneal → evilebottnawi (on 2024-08-12) provenance

This version was published by a different npm account than previous versions on 2024-08-12. 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.

v6.1.1

2 findings

HIGH Publisher changed: jonathantneal → evilebottnawi (on 2024-07-11) provenance

This version was published by a different npm account than previous versions on 2024-07-11. 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.

v6.1.0

2 findings

HIGH Publisher changed: jonathantneal → evilebottnawi (on 2024-05-22) provenance

This version was published by a different npm account than previous versions on 2024-05-22. 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.

v6.0.16

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: jonathantneal → evilebottnawi (on 2024-03-13) provenance

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

v6.0.15

2 findings

HIGH Publisher changed: jonathantneal → evilebottnawi (on 2023-12-29) provenance

This version was published by a different npm account than previous versions on 2023-12-29. 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.

v6.0.14

2 findings

HIGH Publisher changed: jonathantneal → evilebottnawi (on 2023-12-25) provenance

This version was published by a different npm account than previous versions on 2023-12-25. 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.

v6.0.13

2 findings

HIGH Publisher changed: jonathantneal → evilebottnawi (on 2023-05-15) provenance

This version was published by a different npm account than previous versions on 2023-05-15. 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.

v6.0.12

2 findings

HIGH Publisher changed: jonathantneal → evilebottnawi (on 2023-04-29) provenance

This version was published by a different npm account than previous versions on 2023-04-29. 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.

v6.0.11

2 findings

HIGH Publisher changed: jonathantneal → evilebottnawi (on 2022-11-20) provenance

This version was published by a different npm account than previous versions on 2022-11-20. 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.

v6.0.10

2 findings

HIGH Publisher changed: jonathantneal → evilebottnawi (on 2022-03-30) provenance

This version was published by a different npm account than previous versions on 2022-03-30. 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.

v6.0.9

2 findings

HIGH Publisher changed: jonathantneal → evilebottnawi (on 2022-01-20) provenance

This version was published by a different npm account than previous versions on 2022-01-20. 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.

v6.0.8

2 findings

HIGH Publisher changed: jonathantneal → evilebottnawi (on 2021-12-22) provenance

This version was published by a different npm account than previous versions on 2021-12-22. 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.

v6.0.7

2 findings

HIGH Publisher changed: jonathantneal → evilebottnawi (on 2021-12-09) provenance

This version was published by a different npm account than previous versions on 2021-12-09. 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.

v6.0.6

2 findings

HIGH Publisher changed: jonathantneal → evilebottnawi (on 2021-05-11) provenance

This version was published by a different npm account than previous versions on 2021-05-11. 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.

v6.0.5

2 findings

HIGH Publisher changed: jonathantneal → evilebottnawi (on 2021-04-19) provenance

This version was published by a different npm account than previous versions on 2021-04-19. 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.

v6.0.4

2 findings

HIGH Publisher changed: jonathantneal → evilebottnawi (on 2020-09-25) provenance

This version was published by a different npm account than previous versions on 2020-09-25. 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.

v6.0.3

2 findings

HIGH Publisher changed: jonathantneal → evilebottnawi (on 2020-09-21) provenance

This version was published by a different npm account than previous versions on 2020-09-21. 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.

v6.0.2

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.

v6.0.1

1 finding

LOW No provenance attestation provenance

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

v6.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.

v5.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: chriseppstein → jonathantneal (on 2018-12-22) provenance

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

v4.0.0

1 finding

LOW No provenance attestation provenance

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

v3.1.2

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: jonathantneal → evilebottnawi (on 2020-02-14) provenance

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

v3.1.1

1 finding

LOW No provenance attestation provenance

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

v3.1.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: beneb → chriseppstein (on 2017-10-24) provenance

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

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: beneb → chriseppstein (on 2017-10-23) provenance

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

v2.2.3

1 finding

LOW No provenance attestation provenance

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

v2.2.2

1 finding

LOW No provenance attestation provenance

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

v2.2.1

1 finding

LOW No provenance attestation provenance

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

v2.2.0

1 finding

LOW No provenance attestation provenance

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

v2.1.1

1 finding

LOW No provenance attestation provenance

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

v2.1.0

1 finding

LOW No provenance attestation provenance

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

v2.0.0

1 finding

LOW No provenance attestation provenance

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

v1.3.3

1 finding

LOW No provenance attestation provenance

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

v1.3.2

1 finding

LOW No provenance attestation provenance

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

v1.3.1

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.1

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.4

1 finding

LOW No provenance attestation provenance

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

v1.1.3

1 finding

LOW No provenance attestation provenance

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

v1.1.2

1 finding

LOW No provenance attestation provenance

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.1

1 finding

LOW No provenance attestation provenance

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

v1.0.0

1 finding

LOW No provenance attestation provenance

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

v0.0.5

1 finding

LOW No provenance attestation provenance

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

v0.0.4

1 finding

LOW No provenance attestation provenance

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

v0.0.3

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.

v0.0.2

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.

v0.0.1

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.