babel-plugin-emotion MIT 50 versions

babel-plugin-emotion

npm Repository Homepage

A recommended babel preprocessing plugin for emotion, The Next Generation of CSS-in-JS.

50

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

andaristemotion-release-bottkh44mitchellhamilton

Keywords

stylesemotionreactcsscss-in-js

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher changed to emotion-release-bot, the official Emotion project release automation account (24 pkgs, 560 approvals, 0 rejections). Legitimate transition.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package predates Sigstore provenance; publisher is a trusted long-standing maintainer of the emotion ecosystem.	ai	2026/04/23
provenance	missing-githead	AI (provenance): Major version bump (9→10) with restructured build; missing gitHead is common for this era and publisher.	ai	2026/04/23

Versions (showing 50 of 50)

Version	Deps	Published
11.0.0	0 / 0	2020-11-12
10.2.2	10 / 2	2021-02-09
10.0.33	10 / 2	2020-04-03
10.0.29	10 / 2	2020-03-02
10.0.28	10 / 2	2020-02-27
10.0.27	10 / 2	2019-12-22
10.0.23	10 / 2	2019-10-29
10.0.22	10 / 2	2019-10-23
10.0.21	10 / 2	2019-10-05
10.0.20	10 / 2	2019-10-02
10.0.19	10 / 2	2019-09-17
10.0.17	10 / 2	2019-08-31
10.0.16	10 / 2	2019-08-16
10.0.15	10 / 2	2019-08-02
10.0.14	10 / 2	2019-06-25
10.0.13	10 / 2	2019-06-09
10.0.9	10 / 2	2019-03-11
10.0.8	10 / 2	2019-03-11
10.0.7	10 / 2	2019-02-04
10.0.6	10 / 2	2019-01-06
10.0.5	10 / 2	2018-12-14
10.0.4	10 / 2	2018-12-05
10.0.3	10 / 2	2018-12-05
10.0.2	10 / 2	2018-12-03
10.0.0	10 / 2	2018-11-27
9.2.11	12 / 2	2018-09-30
9.2.10	13 / 1	2018-09-19
9.2.9	13 / 1	2018-09-16
9.2.8	13 / 1	2018-08-28
9.2.6	13 / 1	2018-07-15
9.2.5	12 / 1	2018-07-06
9.2.4	12 / 5	2018-06-21
9.2.0	12 / 4	2018-06-07
9.1.2	11 / 4	2018-04-17
9.1.0	9 / 4	2018-03-23
9.0.1	8 / 4	2018-02-13
9.0.0	8 / 4	2018-02-04
8.0.12	8 / 4	2017-11-30
8.0.11	7 / 4	2017-11-24
8.0.10	7 / 4	2017-11-07
8.0.9	7 / 3	2017-10-23
8.0.6	7 / 3	2017-10-14
8.0.4	7 / 3	2017-10-07
8.0.3	7 / 3	2017-10-06
8.0.2	7 / 3	2017-10-05
7.3.2	8 / 3	2017-09-14
7.3.1	8 / 3	2017-09-13
7.3.0	8 / 3	2017-09-13
7.2.2	7 / 3	2017-09-05
7.1.0	7 / 3	2017-08-17

v10.2.2

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.33

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.29

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.28

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.27

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.23

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.22

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.21

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.20

2 findings

HIGH Publisher changed: mitchellhamilton → emotion-release-bot (on 2019-10-02) provenance

This version was published by a different npm account than previous versions on 2019-10-02. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.19

2 findings

HIGH Publisher changed: mitchellhamilton → emotion-release-bot (on 2019-09-17) provenance

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.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.17

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.16

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.15

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.14

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.13

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.9

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.8

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.7

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.6

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.5

2 findings

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[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.4

2 findings

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[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.3

2 findings

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[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.2

2 findings

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[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 findings

HIGH Missing gitHead — previous versions had it provenance

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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.