postcss-syntax — Greenflagged

Automatically switch PostCSS syntax by file extensions

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

aigucong

Keywords

postcsssyntaxswitchextension

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): Established package with trusted publisher; missing gitHead is a minor provenance gap, not a security concern for this package.	ai	2026/04/24
phantom-deps	phantom-dep:htmlparser2	AI (phantom-deps): Used indirectly for HTML parsing in syntax detection; legitimate architecture.	ai	2026/04/24
phantom-deps	phantom-dep:postcss-jsx	AI (phantom-deps): Optional dep loaded dynamically via require() based on file extension; core design pattern of postcss-syntax.	ai	2026/04/24
phantom-deps	phantom-dep:postcss-html	AI (phantom-deps): Optional dep loaded dynamically via require() based on file extension; core design pattern of postcss-syntax.	ai	2026/04/24
phantom-deps	phantom-dep:postcss-less	AI (phantom-deps): Optional dep loaded dynamically via require() based on file extension; core design pattern of postcss-syntax.	ai	2026/04/24
phantom-deps	phantom-dep:postcss-sass	AI (phantom-deps): Optional dep loaded dynamically via require() based on file extension; core design pattern of postcss-syntax.	ai	2026/04/24
phantom-deps	phantom-dep:postcss-scss	AI (phantom-deps): Optional dep loaded dynamically via require() based on file extension; core design pattern of postcss-syntax.	ai	2026/04/24
phantom-deps	phantom-dep:postcss-markdown	AI (phantom-deps): Optional dep loaded dynamically via require() based on file extension; core design pattern of postcss-syntax.	ai	2026/04/24
phantom-deps	phantom-dep:postcss-safe-parser	AI (phantom-deps): Optional dep loaded dynamically via require() based on file extension; core design pattern of postcss-syntax.	ai	2026/04/24
phantom-deps	phantom-dep:sugarss	AI (phantom-deps): Optional dep loaded dynamically via require() based on file extension; core design pattern of postcss-syntax.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require() is the core design of postcss-syntax — it resolves PostCSS syntax plugin names to modules. This is intentional and documented behavior, not a security risk for this package.	ai	2026/04/23

Versions (showing 25 of 25)

Version	Deps	Published
0.36.2	0 / 13	2019-01-03
0.36.0	0 / 13	2019-01-02
0.34.0	0 / 13	2018-09-18
0.33.0	0 / 13	2018-08-15
0.32.0	0 / 13	2018-07-27
0.31.0	0 / 13	2018-06-29
0.30.0	0 / 13	2018-06-20
0.28.0	0 / 12	2018-06-11
0.27.0	0 / 12	2018-06-07
0.26.1	0 / 12	2018-05-28
0.26.0	0 / 12	2018-05-28
0.25.0	0 / 12	2018-05-25
0.24.0	0 / 12	2018-05-24
0.10.0	0 / 12	2018-05-18
0.9.1	0 / 12	2018-05-18
0.9.0	0 / 12	2018-05-08
0.8.0	0 / 12	2018-05-08
0.7.0	9 / 7	2018-05-07
0.6.0	9 / 7	2018-05-04
0.3.1	9 / 7	2018-05-04
0.3.0	8 / 3	2018-05-03
0.2.0	8 / 3	2018-04-28
0.1.0	0 / 20	2018-04-14
0.0.2	0 / 20	2018-04-13
0.0.1	0 / 20	2018-04-12

v0.36.2

1 finding

LOW No provenance attestation provenance

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

v0.36.0

1 finding

LOW No provenance attestation provenance

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

v0.34.0

1 finding

LOW No provenance attestation provenance

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

v0.33.0

1 finding

LOW No provenance attestation provenance

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

v0.32.0

1 finding

LOW No provenance attestation provenance

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

v0.31.0

1 finding

LOW No provenance attestation provenance

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

v0.30.0

1 finding

LOW No provenance attestation provenance

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

v0.28.0

1 finding

LOW No provenance attestation provenance

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

v0.27.0

1 finding

LOW No provenance attestation provenance

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

v0.26.1

1 finding

LOW No provenance attestation provenance

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

v0.26.0

1 finding

LOW No provenance attestation provenance

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

v0.25.0

1 finding

LOW No provenance attestation provenance

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

v0.24.0

1 finding

LOW No provenance attestation provenance

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

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.1

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gucong.

LOW No provenance attestation provenance

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

v0.6.0

2 findings

LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gucong.

v0.3.1

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gucong.

LOW No provenance attestation provenance

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

v0.3.0

2 findings

LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gucong.

v0.2.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gucong.

LOW No provenance attestation provenance

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

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