postcss-jsx
PostCSS syntax for parsing CSS in JS literals
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Publisher is the package author/repo owner; missing gitHead is a benign environment difference, not a supply-chain signal. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed from gucong3000 to ai (Andrey Sitnik, PostCSS creator) in 2018 — legitimate maintainer transition within the PostCSS ecosystem. | ai | |
| phantom-deps | phantom-dep:postcss-styled | AI (phantom-deps): postcss-styled is listed in optionalDependencies and referenced in config; not a direct import but a legitimate optional peer. | ai | |
| phantom-deps | phantom-dep:@babel/generator | AI (phantom-deps): @babel/generator is explicitly declared as a runtime dependency in package.json; the phantom-dep finding is a false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Package is 2917 days old and predates Sigstore provenance; absence is expected and not a risk signal for this established package. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 0.36.4 | 1 / 10 | |
| 0.36.3 | 1 / 10 | |
| 0.36.2 | 1 / 10 | |
| 0.36.1 | 1 / 10 | |
| 0.36.0 | 1 / 10 | |
| 0.35.0 | 2 / 10 | |
| 0.34.0 | 2 / 10 | |
| 0.33.0 | 2 / 10 | |
| 0.32.0 | 5 / 10 | |
| 0.31.0 | 5 / 10 | |
| 0.30.0 | 5 / 10 | |
| 0.28.0 | 5 / 10 | |
| 0.27.0 | 5 / 10 | |
| 0.26.0 | 5 / 10 | |
| 0.25.0 | 5 / 10 | |
| 0.24.0 | 5 / 10 | |
| 0.10.0 | 5 / 10 | |
| 0.9.0 | 5 / 10 | |
| 0.8.0 | 5 / 10 | |
| 0.7.0 | 5 / 10 | |
| 0.6.0 | 5 / 10 | |
| 0.5.0 | 5 / 10 | |
| 0.4.0 | 5 / 10 | |
| 0.1.0 | 4 / 1 |
v0.36.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.1
2 findingsThis version was published by a different npm account than previous versions on 2019-06-05. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gucong.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-01-02. This could indicate a legitimate maintainer transition or an account compromise.
v0.35.0
2 findingsThis version was published by a different npm account than previous versions on 2018-10-25. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.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.