@csstools/postcss-scope-pseudo-class MIT-0 9 versions

@csstools/postcss-scope-pseudo-class

npm Repository Homepage

The Reference Element Pseudo-class: :scope

9

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

postcss-pluginpseudoscopeselector

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Legitimate maintainer transition within csstools org; romainmenke is a listed contributor with extensive track record (1181 approved packages).	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): romainmenke is a known csstools contributor with strong npm track record; transition is legitimate.	ai	2026/04/24
dependencies	unvetted-dep:postcss-selector-parser	AI (dependencies): postcss-selector-parser is a well-known, widely-used CSS selector parsing library; its use is expected and appropriate for any PostCSS selector manipulation plugin.	ai	2026/04/21
license	uncommon-license:MIT-0	AI (license): MIT-0 is a recognized permissive license (MIT without attribution); csstools consistently uses it across their plugin suite. Not a security concern.	ai	2026/04/21

Versions (showing 9 of 9)

Version	Deps	Published
5.0.0	1 / 0	2026-01-14
4.0.1	1 / 0	2024-10-23
4.0.0	1 / 0	2024-08-03
3.0.1	1 / 0	2023-12-15
3.0.0	1 / 1	2023-07-03
2.0.2	1 / 0	2023-02-09
2.0.1	1 / 0	2023-01-28
2.0.0	1 / 0	2023-01-24
1.0.0	1 / 0	2022-11-04

v4.0.1

1 finding

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

v3.0.1

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.

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

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

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

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.