@emotion/cache
emotion's cache
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): emotion-release-bot is the official release automation account for the emotion-js monorepo; the publisher transition from mitchellhamilton is a known legitimate change, not a compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): emotion-release-bot was added as part of the official emotion-js release automation workflow; stable and legitimate for this package. | ai | |
| provenance | missing-githead | AI (provenance): Established emotion-js package from a highly trusted publisher; missing gitHead reflects a publish environment change, not a malicious signal. No other risk indicators present. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance; established emotion-js package with trusted publisher. Stable false positive for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @emotion/weak-memoize is a first-party emotion namespace package by the same publisher — a legitimate internal refactor, not a supply chain risk. | ai |
Versions (showing 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 11.14.0 | 5 / 4 | |
| 11.13.5 | 5 / 3 | |
| 11.13.1 | 5 / 3 | |
| 11.13.0 | 5 / 3 | |
| 11.12.0 | 5 / 3 | |
| 11.11.0 | 5 / 3 | |
| 11.10.8 | 5 / 3 | |
| 11.10.7 | 5 / 3 | |
| 11.10.5 | 5 / 3 | |
| 11.10.3 | 5 / 3 | |
| 11.10.2 | 5 / 3 | |
| 11.10.1 | 5 / 3 | |
| 11.10.0 | 5 / 3 | |
| 11.9.3 | 5 / 3 | |
| 11.7.1 | 5 / 2 | |
| 11.6.0 | 5 / 2 | |
| 11.5.0 | 5 / 2 | |
| 11.4.0 | 5 / 2 | |
| 11.1.3 | 5 / 2 | |
| 11.0.0 | 5 / 2 | |
| 10.0.29 | 4 / 2 | |
| 10.0.27 | 4 / 2 | |
| 10.0.19 | 4 / 2 | |
| 10.0.17 | 4 / 2 | |
| 10.0.15 | 4 / 2 | |
| 10.0.14 | 4 / 2 | |
| 10.0.9 | 4 / 2 | |
| 10.0.8 | 4 / 2 | |
| 10.0.7 | 4 / 2 | |
| 10.0.0 | 4 / 2 | |
| 0.8.8 | 3 / 0 | |
| 0.8.7 | 3 / 0 | |
| 0.8.6 | 3 / 0 | |
| 0.8.5 | 3 / 0 | |
| 0.8.4 | 3 / 0 | |
| 0.8.3 | 3 / 0 | |
| 0.8.2 | 4 / 0 | |
| 0.8.1 | 4 / 0 | |
| 0.8.0 | 4 / 0 | |
| 0.7.1 | 4 / 0 | |
| 0.7.0 | 4 / 0 | |
| 0.6.5 | 4 / 0 | |
| 0.6.4 | 4 / 0 | |
| 0.6.3 | 4 / 0 | |
| 0.6.2 | 4 / 0 | |
| 0.6.0 | 4 / 0 | |
| 0.5.0 | 4 / 0 | |
| 0.4.1 | 4 / 0 | |
| 0.4.0 | 4 / 0 | |
| 0.2.3 | 4 / 0 | |
| 0.2.1 | 4 / 0 |
v11.13.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.10.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.10.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.29
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: emotion-release-bot.
This version was published by a different npm account than previous versions on 2020-03-02. 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 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.19
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.17
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.
v10.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.14
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.
v10.0.9
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.
v10.0.8
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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: mitchellhamilton.
v10.0.7
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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: mitchellhamilton.
v10.0.0
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.