styled-jsx
Full CSS support for JSX without compromises
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:browser-env | AI (phantom-deps): browser-env is referenced only in test helpers (ava config); it was mistakenly placed in dependencies instead of devDependencies. Not a security concern for this package. | ai | |
| dependencies | unvetted-dep:browser-env | AI (dependencies): browser-env is a legitimate test-environment utility; its presence in dependencies (vs devDependencies) is a packaging mistake, not a security risk for styled-jsx. | ai | |
| phantom-deps | phantom-dep:babel-core | AI (phantom-deps): babel-core is declared as a runtime dep and referenced in config; standard Babel 6 tooling pattern for a JSX transformation library. | ai | |
| phantom-deps | phantom-dep:babel | AI (phantom-deps): babel is declared as a runtime dep and referenced in the babel config block in package.json; this is a normal Babel 6 setup pattern, not a real phantom dependency issue. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (timneutkens, timer, zeit-bot) are known Vercel team members; consistent with org-level maintainer consolidation. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change to zeit-bot reflects Vercel's standard bot-publishing practice for their OSS packages; consistent with vercel/styled-jsx repo ownership. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are @babel/types and @babel/plugin-syntax-jsx, direct scoped replacements for the removed legacy babel-types and babel-plugin-syntax-jsx packages. Routine Babel migration. | ai | |
| dependencies | unvetted-dep:stylis-rule-sheet | AI (dependencies): stylis-rule-sheet is a legitimate companion plugin to the stylis CSS preprocessor, used as documented in styled-jsx's CSS processing pipeline. Stable false positive for this package. | ai | |
| dependencies | unvetted-dep:convert-source-map | AI (dependencies): convert-source-map is a standard, widely-used source map utility with no known malicious history. Its use here for source map handling is expected and benign. | ai | |
| dependencies | unvetted-dep:client-only | AI (dependencies): client-only is a Vercel-published marker package intentionally used in Vercel ecosystem packages like styled-jsx; this is expected and benign. | ai | |
| provenance | no-provenance | AI (provenance): vercel-release-bot has a strong track record (1521 approved packages); lack of Sigstore provenance is not a concern for this established publisher. | ai |
Versions (showing 51 of 102)
| Version | Deps | Published |
|---|---|---|
| 5.1.7 | 1 / 31 | |
| 5.1.5 | 2 / 30 | |
| 5.1.4 | 1 / 29 | |
| 5.1.3 | 1 / 29 | |
| 5.1.2 | 1 / 29 | |
| 5.1.1 | 1 / 29 | |
| 5.1.0 | 1 / 29 | |
| 5.0.7 | 0 / 29 | |
| 5.0.6 | 0 / 29 | |
| 5.0.5 | 0 / 29 | |
| 5.0.4 | 0 / 29 | |
| 5.0.3 | 0 / 29 | |
| 5.0.2 | 0 / 29 | |
| 5.0.1 | 0 / 29 | |
| 5.0.0 | 0 / 29 | |
| 4.0.1 | 8 / 20 | |
| 4.0.0 | 8 / 21 | |
| 3.4.7 | 8 / 22 | |
| 3.4.6 | 9 / 22 | |
| 3.4.5 | 9 / 22 | |
| 3.4.4 | 9 / 22 | |
| 3.4.3 | 9 / 22 | |
| 3.4.2 | 9 / 22 | |
| 3.4.1 | 9 / 22 | |
| 3.4.0 | 9 / 22 | |
| 3.3.3 | 9 / 22 | |
| 3.3.2 | 8 / 22 | |
| 3.3.1 | 8 / 21 | |
| 3.3.0 | 8 / 21 | |
| 3.2.5 | 8 / 21 | |
| 3.2.4 | 8 / 21 | |
| 3.2.3 | 8 / 22 | |
| 3.2.2 | 8 / 22 | |
| 3.2.1 | 8 / 22 | |
| 3.2.0 | 8 / 22 | |
| 3.1.3 | 8 / 21 | |
| 3.1.2 | 8 / 21 | |
| 3.1.1 | 8 / 21 | |
| 3.1.0 | 8 / 21 | |
| 3.0.2 | 8 / 21 | |
| 3.0.1 | 8 / 21 | |
| 3.0.0 | 8 / 21 | |
| 2.2.7 | 8 / 23 | |
| 2.2.6 | 7 / 23 | |
| 2.2.5 | 7 / 23 | |
| 2.2.4 | 7 / 23 | |
| 2.2.3 | 7 / 23 | |
| 2.2.2 | 7 / 23 | |
| 2.2.1 | 7 / 23 | |
| 2.2.0 | 7 / 23 | |
| 2.1.3 | 7 / 23 |
v3.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
2 findings[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 2021-02-16. This could indicate a legitimate maintainer transition or an account compromise.
v3.4.2
2 findings[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 2021-02-07. This could indicate a legitimate maintainer transition or an account compromise.
v3.4.1
2 findings[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 2021-01-15. This could indicate a legitimate maintainer transition or an account compromise.
v3.4.0
2 findings[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 2021-01-15. This could indicate a legitimate maintainer transition or an account compromise.
v3.3.3
2 findings[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 2021-01-14. This could indicate a legitimate maintainer transition or an account compromise.
v3.3.2
2 findings[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 2020-11-17. This could indicate a legitimate maintainer transition or an account compromise.
v3.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
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. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.