react-emotion
This package is not relevant in Emotion 10, please use @emotion/styled
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): tkh44 is the original author of the emotion project; the publisher change from mitchellhamilton to tkh44 reflects a legitimate maintainer transition consistent with the package's documented authorship. | ai | |
| phantom-deps | phantom-dep:babel-plugin-emotion | AI (phantom-deps): babel-plugin-emotion is a companion Babel plugin from the same monorepo, referenced in config files as expected for CSS-in-JS tooling. Not a security concern. | ai | |
| dependencies | unvetted-dep:emotion-utils | AI (dependencies): emotion-utils is a sibling package within the emotion monorepo (tkh44/emotion); it is an expected internal dependency, not a suspicious third-party package. | ai | |
| dependencies | unvetted-dep:create-emotion-styled | AI (dependencies): create-emotion-styled is a sibling package in the emotion-js monorepo; its use as a dependency of react-emotion is expected and legitimate across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Package predates npm provenance attestation by years; absence is expected and not a risk signal for this established ecosystem package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): react-emotion@10+ is an intentional deprecation/redirect stub from the emotion-js ecosystem. Tiny payload, no deps, and minimal README are expected for this stub package. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 10.0.0 | 0 / 0 | |
| 9.2.12 | 2 / 3 | |
| 9.2.11 | 2 / 3 | |
| 9.2.10 | 2 / 3 | |
| 9.2.9 | 2 / 3 | |
| 9.2.8 | 2 / 3 | |
| 9.2.6 | 2 / 3 | |
| 9.2.5 | 2 / 3 | |
| 9.2.4 | 2 / 7 | |
| 9.2.3 | 2 / 7 | |
| 9.2.1 | 2 / 7 | |
| 9.2.0 | 2 / 7 | |
| 9.1.3 | 2 / 7 | |
| 9.1.2 | 2 / 7 | |
| 9.1.1 | 2 / 7 | |
| 9.1.0 | 2 / 7 | |
| 9.0.2 | 2 / 7 | |
| 9.0.1 | 2 / 7 | |
| 9.0.0 | 2 / 7 | |
| 8.0.12 | 2 / 7 | |
| 8.0.11 | 2 / 7 | |
| 8.0.10 | 2 / 7 | |
| 8.0.9 | 2 / 7 | |
| 8.0.8 | 2 / 7 | |
| 8.0.7 | 2 / 7 | |
| 8.0.6 | 2 / 5 | |
| 8.0.5 | 2 / 5 | |
| 8.0.4 | 2 / 5 | |
| 8.0.3 | 2 / 5 | |
| 8.0.2 | 2 / 5 | |
| 7.3.2 | 3 / 3 | |
| 7.3.1 | 3 / 3 | |
| 7.3.0 | 3 / 3 | |
| 7.2.2 | 3 / 3 | |
| 7.2.0 | 3 / 3 | |
| 7.1.1 | 3 / 3 | |
| 7.1.0 | 3 / 3 |
v9.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.10
2 findingsThis version was published by a different npm account than previous versions on 2017-11-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.
v8.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.8
2 findingsThis version was published by a different npm account than previous versions on 2017-10-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.
v8.0.7
2 findingsThis version was published by a different npm account than previous versions on 2017-10-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.
v8.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.5
2 findingsThis version was published by a different npm account than previous versions on 2017-10-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.
v8.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.3
2 findingsThis version was published by a different npm account than previous versions on 2017-10-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.
v8.0.2
2 findingsThis version was published by a different npm account than previous versions on 2017-10-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.
v7.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.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.
v7.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.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.
v7.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.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.