@emotion/serialize
serialization utils for emotion
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
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): emotion-utils is a core package within the emotion ecosystem; its addition as a dependency is expected and benign for @emotion/serialize. | ai | |
| provenance | missing-githead | AI (provenance): Established emotion-js package with clean history; missing gitHead reflects a publish environment change, not a security concern, given no other suspicious signals. | ai | |
| dependencies | unvetted-dep:@emotion/memoize | AI (dependencies): @emotion/memoize is a first-party Emotion org package published by the same trusted emotion-release-bot publisher; not a real risk for this package. | ai | |
| dependencies | unvetted-dep:@emotion/unitless | AI (dependencies): @emotion/unitless is a first-party Emotion org package published by the same trusted emotion-release-bot publisher; not a real risk for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Emotion project transitioned to emotion-release-bot with known maintainers (andarist, emmatown). Bot publisher has 162 approved / 0 rejected packages. Legitimate, documented transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (emmatown, emotion-release-bot, andarist) are known, trusted Emotion ecosystem contributors. This is a legitimate project governance change. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): mitchellhamilton stepping back is part of the documented Emotion project maintainer transition. No compromise indicators present. | ai | |
| provenance | no-provenance | AI (provenance): emotion-js packages are published via a release bot from the official monorepo; lack of Sigstore provenance is consistent across the ecosystem and not a risk signal here. | ai |
Versions (showing 51 of 56)
| Version | Deps | Published |
|---|---|---|
| 1.3.3 | 5 / 2 | |
| 1.3.2 | 5 / 2 | |
| 1.3.1 | 5 / 2 | |
| 1.3.0 | 5 / 2 | |
| 1.2.0 | 5 / 2 | |
| 1.1.4 | 5 / 2 | |
| 1.1.3 | 5 / 2 | |
| 1.1.2 | 5 / 2 | |
| 1.1.1 | 5 / 2 | |
| 1.1.0 | 5 / 2 | |
| 1.0.4 | 5 / 2 | |
| 1.0.3 | 5 / 2 | |
| 1.0.2 | 5 / 1 | |
| 1.0.1 | 5 / 1 | |
| 1.0.0 | 5 / 1 | |
| 0.11.16 | 5 / 1 | |
| 0.11.15 | 5 / 1 | |
| 0.11.14 | 5 / 1 | |
| 0.11.13 | 5 / 1 | |
| 0.11.12 | 5 / 1 | |
| 0.11.11 | 5 / 1 | |
| 0.11.10 | 5 / 1 | |
| 0.11.9 | 5 / 1 | |
| 0.11.8 | 5 / 1 | |
| 0.11.7 | 5 / 1 | |
| 0.11.6 | 5 / 1 | |
| 0.11.5 | 5 / 1 | |
| 0.11.4 | 5 / 1 | |
| 0.11.3 | 5 / 1 | |
| 0.11.2 | 5 / 1 | |
| 0.11.1 | 5 / 1 | |
| 0.11.0 | 5 / 1 | |
| 0.10.6 | 5 / 1 | |
| 0.10.5 | 5 / 1 | |
| 0.10.4 | 5 / 1 | |
| 0.10.3 | 5 / 1 | |
| 0.10.2 | 5 / 1 | |
| 0.10.1 | 5 / 1 | |
| 0.10.0 | 4 / 1 | |
| 0.9.1 | 4 / 0 | |
| 0.9.0 | 4 / 0 | |
| 0.8.6 | 4 / 0 | |
| 0.8.5 | 4 / 0 | |
| 0.8.4 | 4 / 0 | |
| 0.8.3 | 4 / 0 | |
| 0.8.2 | 4 / 0 | |
| 0.8.1 | 3 / 0 | |
| 0.8.0 | 3 / 0 | |
| 0.7.0 | 3 / 0 | |
| 0.6.2 | 3 / 0 | |
| 0.5.0 | 1 / 0 |
v1.3.2
2 findingsThis version was published by a different npm account than previous versions on 2024-09-21. 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.
v1.3.1
2 findingsThis version was published by a different npm account than previous versions on 2024-08-21. 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.
v1.3.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.
v1.2.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.
v1.1.4
2 findingsThis version was published by a different npm account than previous versions on 2024-03-29. 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.
v1.1.3
2 findingsThis version was published by a different npm account than previous versions on 2023-12-23. 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.
v1.1.2
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.
v1.1.1
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.
v1.1.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.
v1.0.4
2 findingsThis version was published by a different npm account than previous versions on 2022-06-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.
v1.0.3
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.
v1.0.2
2 findingsThis version was published by a different npm account than previous versions on 2021-04-08. 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.
v1.0.1
2 findingsThis version was published by a different npm account than previous versions on 2021-03-07. 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.
v1.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.
v0.11.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.15
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.
v0.11.14
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-29. This could indicate a legitimate maintainer transition or an account compromise.
v0.11.13
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-24. This could indicate a legitimate maintainer transition or an account compromise.
v0.11.12
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.
v0.11.11
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-09-17. This could indicate a legitimate maintainer transition or an account compromise.
v0.11.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mitchellhamilton.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.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.10.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
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.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.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
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.5.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.