@emotion/babel-plugin
A recommended babel preprocessing plugin for emotion, 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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): emotion-release-bot publishes the entire emotion monorepo without Sigstore provenance; this is consistent across all emotion packages and not a risk signal. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 11.13.5 | 11 / 2 | |
| 11.12.0 | 11 / 2 | |
| 11.11.0 | 11 / 2 | |
| 11.10.8 | 11 / 2 | |
| 11.10.6 | 11 / 2 | |
| 11.10.5 | 12 / 2 | |
| 11.10.2 | 12 / 2 | |
| 11.10.0 | 12 / 2 | |
| 11.9.5 | 12 / 2 | |
| 11.9.2 | 12 / 2 | |
| 11.7.2 | 12 / 2 | |
| 11.7.1 | 12 / 2 | |
| 11.3.0 | 12 / 2 | |
| 11.2.0 | 12 / 2 | |
| 11.1.2 | 12 / 2 | |
| 11.0.0 | 12 / 2 |
v11.12.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.
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.6
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.2
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.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.7.2
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.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.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.
v11.1.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.
v11.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.