@emotion/css
The Next Generation of CSS-in-JS.
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): All new deps (@emotion/cache, @emotion/sheet, @emotion/babel-plugin) are first-party emotion scoped packages. Replacing babel-plugin-emotion with @emotion/babel-plugin is the documented v11 migration. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): mitchellhamilton's removal is part of the documented emotion-js org transition to a release bot model. No compromise indicators. | ai | |
| source-diff | large-new-source-files | AI (source-diff): v10→v11 major version adds multiple dist formats (CJS/ESM/UMD, dev/prod, create-instance entrypoint). Size increase is structural, not injected payload. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase from 3KB to 60KB reflects the v11 multi-format distribution (CJS, ESM, UMD, TypeScript types, create-instance). Fully explained by legitimate packaging changes. | ai | |
| provenance | publisher-changed | AI (provenance): emotion-release-bot is the official release account for the emotion-js org; transition from mitchellhamilton is documented and legitimate. Stable for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): emmatown, emotion-release-bot, and andarist are recognized emotion-js contributors. This is a legitimate team transition, not a takeover. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @emotion/css is the legitimate Emotion CSS-in-JS library, not a typosquat of 'qs'. The scoped package name and completely different domain make this a clear false positive. | ai | |
| provenance | no-provenance | AI (provenance): Emotion packages are published via a release bot without Sigstore provenance; this is consistent across all their packages and is not a risk signal for this well-established publisher. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @emotion/css is the legitimate Emotion CSS-in-JS library, not a typosquat of 'cors'. The scoped package name and completely different domain make this a clear false positive. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 11.13.5 | 5 / 2 | |
| 11.13.4 | 5 / 2 | |
| 11.13.0 | 5 / 2 | |
| 11.12.0 | 5 / 2 | |
| 11.11.2 | 5 / 2 | |
| 11.11.0 | 5 / 2 | |
| 11.10.8 | 5 / 2 | |
| 11.10.6 | 5 / 2 | |
| 11.10.5 | 5 / 3 | |
| 11.10.0 | 5 / 3 | |
| 11.9.0 | 5 / 3 | |
| 11.7.1 | 5 / 2 | |
| 11.5.0 | 5 / 2 | |
| 11.1.3 | 5 / 2 | |
| 11.0.0 | 5 / 2 | |
| 10.0.27 | 3 / 1 | |
| 10.0.22 | 3 / 1 | |
| 10.0.14 | 3 / 1 | |
| 10.0.12 | 3 / 1 | |
| 10.0.9 | 3 / 1 | |
| 10.0.8 | 3 / 1 | |
| 10.0.7 | 3 / 1 | |
| 10.0.6 | 3 / 1 | |
| 10.0.5 | 3 / 1 | |
| 10.0.4 | 3 / 1 | |
| 10.0.3 | 3 / 1 | |
| 10.0.2 | 3 / 1 | |
| 10.0.0 | 3 / 1 | |
| 0.9.8 | 2 / 0 | |
| 0.9.7 | 2 / 0 | |
| 0.9.6 | 3 / 0 | |
| 0.9.5 | 3 / 0 | |
| 0.9.4 | 3 / 0 | |
| 0.9.3 | 3 / 0 | |
| 0.9.2 | 3 / 0 | |
| 0.9.1 | 3 / 0 | |
| 0.9.0 | 3 / 0 | |
| 0.8.0 | 3 / 0 | |
| 0.7.0 | 3 / 0 | |
| 0.6.2 | 3 / 0 | |
| 0.6.0 | 3 / 0 | |
| 0.5.0 | 3 / 0 | |
| 0.4.1 | 3 / 0 | |
| 0.2.3 | 3 / 0 | |
| 0.2.1 | 3 / 0 | |
| 0.2.0 | 3 / 0 | |
| 0.0.5 | 3 / 0 | |
| 0.0.4 | 3 / 0 |
v11.13.4
2 findingsThis version was published by a different npm account than previous versions on 2024-10-01. 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.
v11.13.0
2 findingsThis version was published by a different npm account than previous versions on 2024-07-20. 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.
v11.12.0
2 findingsThis version was published by a different npm account than previous versions on 2024-07-19. 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.
v11.11.2
2 findingsThis version was published by a different npm account than previous versions on 2023-06-16. 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.
v11.11.0
2 findingsThis version was published by a different npm account than previous versions on 2023-05-06. 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.
v11.10.8
2 findingsThis version was published by a different npm account than previous versions on 2023-04-28. 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.
v11.10.6
2 findingsThis version was published by a different npm account than previous versions on 2023-02-16. 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.
v11.10.5
2 findingsThis version was published by a different npm account than previous versions on 2022-10-27. 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.
v11.10.0
2 findingsThis version was published by a different npm account than previous versions on 2022-07-31. 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.
v11.9.0
2 findingsThis version was published by a different npm account than previous versions on 2022-04-06. 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.
v11.7.1
2 findingsThis version was published by a different npm account than previous versions on 2021-12-12. 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.
v11.5.0
2 findingsThis version was published by a different npm account than previous versions on 2021-10-17. 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.
v11.1.3
2 findingsThis version was published by a different npm account than previous versions on 2020-12-20. 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.
v11.0.0
2 findingsThis version was published by a different npm account than previous versions on 2020-11-12. 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.
v10.0.27
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 2019-12-22. This could indicate a legitimate maintainer transition or an account compromise.
v10.0.22
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 2019-10-23. This could indicate a legitimate maintainer transition or an account compromise.
v10.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.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.
v0.9.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package 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.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.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.
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.