postcss-prefix-selector MIT 23 versions

postcss-prefix-selector

npm Repository Homepage

Prefix all CSS rules with a selector

23

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

jongleberryndpntvalentin-radulescu-hs

Keywords

postcssprefixselectorspostcss-plugincssselectorplugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change occurred in 2015; new publisher has 10+ year clean track record with 23 approved versions. Legitimate maintainer transition.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): Maintainer additions occurred years ago; both have long clean histories. Legitimate project handoff.	ai	2026/04/24

Versions (showing 23 of 23)

Version	Deps	Published
2.1.1	0 / 7	2025-03-27
2.1.0	0 / 7	2024-10-10
2.0.0	0 / 7	2024-10-03
1.16.1	0 / 7	2024-04-20
1.16.0	0 / 7	2022-06-17
1.15.0	0 / 7	2022-03-16
1.14.0	0 / 7	2021-12-06
1.13.0	1 / 6	2021-09-05
1.12.0	1 / 6	2021-08-19
1.11.0	1 / 6	2021-08-19
1.10.0	1 / 5	2021-06-16
1.9.0	1 / 5	2021-03-12
1.8.0	1 / 5	2021-03-02
1.7.2	1 / 5	2019-05-03
1.7.1	1 / 5	2019-02-23
1.7.0	1 / 5	2019-02-23
1.6.0	1 / 5	2017-03-06
1.5.0	1 / 2	2016-12-04
1.4.0	1 / 2	2016-03-25
1.3.0	1 / 2	2015-10-01
1.2.0	0 / 3	2015-09-30
1.1.0	0 / 3	2015-02-03
1.0.0	0 / 3	2015-02-03

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

1 finding

LOW No provenance attestation provenance

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

v1.16.0

1 finding

LOW No provenance attestation provenance

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

v1.15.0

1 finding

LOW No provenance attestation provenance

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

v1.14.0

1 finding

LOW No provenance attestation provenance

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

v1.13.0

1 finding

LOW No provenance attestation provenance

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

v1.12.0

1 finding

LOW No provenance attestation provenance

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

v1.11.0

1 finding

LOW No provenance attestation provenance

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

v1.10.0

1 finding

LOW No provenance attestation provenance

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

v1.9.0

1 finding

LOW No provenance attestation provenance

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

v1.8.0

1 finding

LOW No provenance attestation provenance

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

v1.7.2

1 finding

LOW No provenance attestation provenance

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

v1.7.1

1 finding

LOW No provenance attestation provenance

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

v1.7.0

1 finding

LOW No provenance attestation provenance

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

v1.6.0

1 finding

LOW No provenance attestation provenance

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

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.0

2 findings

HIGH Publisher changed: jongleberry → valentin-radulescu-hs (on 2016-03-25) provenance

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

v1.3.0

2 findings

HIGH Publisher changed: jongleberry → valentin-radulescu-hs (on 2015-10-01) provenance

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

v1.2.0

2 findings

HIGH Publisher changed: jongleberry → valentin-radulescu-hs (on 2015-09-30) provenance

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

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