postcss-modules-scope
A CSS Modules transform to extract export statements from local-scope classes
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:postcss-selector-parser | AI (dependencies): postcss-selector-parser is a core, widely-used PostCSS ecosystem package; flagging it as unvetted is a stable false positive for this package. | ai | |
| dependencies | unvetted-dep:css-selector-tokenizer | AI (dependencies): css-selector-tokenizer is a legitimate, well-known CSS tooling dependency appropriate for a CSS modules scope transform; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established css-modules org package; lack of provenance attestation is common and not a risk signal for this well-known project. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 3.2.1 | 1 / 8 | |
| 3.2.0 | 1 / 8 | |
| 3.1.2 | 1 / 8 | |
| 3.1.1 | 1 / 8 | |
| 3.1.0 | 1 / 8 | |
| 3.0.0 | 1 / 8 | |
| 2.2.0 | 2 / 7 | |
| 2.1.1 | 2 / 7 | |
| 2.1.0 | 2 / 6 | |
| 2.0.1 | 2 / 7 | |
| 2.0.0 | 2 / 7 | |
| 1.1.0 | 2 / 10 | |
| 1.0.2 | 2 / 10 | |
| 1.0.1 | 2 / 10 | |
| 1.0.0 | 2 / 10 | |
| 0.0.8 | 2 / 10 | |
| 0.0.7 | 2 / 10 | |
| 0.0.6 | 2 / 10 | |
| 0.0.5 | 1 / 10 | |
| 0.0.4 | 1 / 10 | |
| 0.0.3 | 1 / 10 | |
| 0.0.2 | 1 / 9 | |
| 0.0.1 | 1 / 9 |
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 finding[Accepted risk] 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[Accepted risk] 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[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 finding[Accepted risk] 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[Accepted risk] 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[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.