@csstools/postcss-is-pseudo-class MIT-0 30 versions

@csstools/postcss-is-pseudo-class

npm Repository Homepage

A pseudo-class for matching elements in a selector list

30

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

cssismatchespolyfillpostcsspostcss-pluginpseudoselector

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): romainmenke is a known csstools core contributor with a strong track record (1073 approved, 0 rejected). The transition from alaguna is a legitimate org maintainer change within the csstools/postcss-plugins monorepo.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): romainmenke is an established csstools maintainer; addition is consistent with legitimate project ownership transfer within the csstools org.	ai	2026/04/24
license	uncommon-license:MIT-0	AI (license): MIT-0 is a well-known permissive license variant (MIT without attribution); not a security concern and stable for this package.	ai	2026/04/21
phantom-deps	phantom-dep:postcss-selector-parser	AI (phantom-deps): postcss-selector-parser is a standard PostCSS ecosystem dependency; phantom finding is a monorepo artifact, not a risk.	ai	2026/04/21
phantom-deps	phantom-dep:@csstools/selector-specificity	AI (phantom-deps): Same-org dependency from csstools; phantom finding is a monorepo artifact, not a risk.	ai	2026/04/21

Versions (showing 30 of 30)

Version	Deps	Published
6.0.0	2 / 0	2026-01-14
5.0.3	2 / 0	2025-06-11
5.0.2	2 / 0	2025-06-10
5.0.1	2 / 0	2024-10-23
5.0.0	2 / 0	2024-08-03
4.0.8	2 / 0	2024-05-13
4.0.7	2 / 0	2024-05-11
4.0.6	2 / 0	2024-03-31
4.0.5	2 / 0	2024-02-19
4.0.4	2 / 0	2023-12-15
4.0.3	2 / 2	2023-10-02
4.0.2	2 / 2	2023-09-18
4.0.1	2 / 2	2023-09-02
4.0.0	2 / 2	2023-07-03
3.2.1	2 / 2	2023-05-19
3.2.0	2 / 2	2023-04-10
3.1.1	2 / 1	2023-02-08
3.1.0	2 / 1	2023-02-02
3.0.1	2 / 1	2023-01-28
3.0.0	2 / 1	2023-01-24
2.0.7	2 / 1	2022-07-08
2.0.6	2 / 1	2022-06-23
2.0.5	2 / 1	2022-06-04
2.0.4	2 / 1	2022-05-17
2.0.3	2 / 1	2022-05-11
2.0.2	1 / 1	2022-04-04
2.0.1	1 / 1	2022-03-04
2.0.0	1 / 1	2022-01-31
1.0.1	1 / 2	2022-01-17
1.0.0	1 / 2	2022-01-13

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

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

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

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

v4.0.8

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.

v4.0.7

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.

v4.0.6

2 findings

HIGH Publisher changed: alaguna → romainmenke (on 2024-03-31) provenance

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

v4.0.5

2 findings

HIGH Publisher changed: alaguna → romainmenke (on 2024-02-19) provenance

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

v4.0.4

2 findings

HIGH Publisher changed: alaguna → romainmenke (on 2023-12-15) provenance

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

v4.0.3

2 findings

HIGH Publisher changed: alaguna → romainmenke (on 2023-10-02) provenance

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

v4.0.2

2 findings

HIGH Publisher changed: alaguna → romainmenke (on 2023-09-18) provenance

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

v4.0.1

2 findings

HIGH Publisher changed: alaguna → romainmenke (on 2023-09-02) provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v3.2.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.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

1 finding

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

1 finding

LOW No provenance attestation provenance

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

v2.0.7

1 finding

LOW No provenance attestation provenance

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

v2.0.6

1 finding

LOW No provenance attestation provenance

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

v2.0.5

1 finding

LOW No provenance attestation provenance

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

v2.0.4

1 finding

LOW No provenance attestation provenance

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

v2.0.3

1 finding

LOW No provenance attestation provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.1

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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.