@emotion/core — Greenflagged

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): Package predates Sigstore provenance on npm by years; absence is expected and not a risk signal for this publisher.	ai	2026/04/22
npm-metadata	no-description	AI (npm-metadata): Early monorepo package version; missing description is a cosmetic issue, not a security signal for this well-established Emotion library package.	ai	2026/04/22
provenance	publisher-changed	AI (provenance): emotion-release-bot is the official release automation account for the emotion-js monorepo; publisher change from mitchellhamilton is a documented, legitimate transition stable across all versions.	ai	2026/04/22
maintainer-change	maintainer-added	AI (maintainer-change): emotion-release-bot addition is a known legitimate maintainer transition for the emotion-js project; stable across all future versions of this package.	ai	2026/04/22
dependencies	unvetted-dep:@emotion/css	AI (dependencies): @emotion/css is a sibling package in the emotion monorepo, published by the same trusted publisher. This dependency relationship is stable and expected across all versions.	ai	2026/04/22
source-diff	large-new-source-files	AI (source-diff): New files are build artifacts and source maps for multiple entrypoints (jsx-runtime, jsx-dev-runtime); consistent with legitimate multi-entrypoint package structure.	ai	2026/04/22
publish-pattern	new-deps-added	AI (publish-pattern): All new deps are @emotion/* first-party scoped packages or @babel/runtime — consistent with emotion monorepo restructuring, not a supply-chain risk.	ai	2026/04/22
source-diff	source-size-tripled	AI (source-diff): Size increase reflects full v10 distribution with multiple build targets and source maps; diff baseline is v11 (newer), making this comparison misleading. No injected payloads.	ai	2026/04/22
typosquat	typosquat.levenshtein:cors	AI (typosquat): @emotion/core is a scoped package in the well-known emotion CSS-in-JS ecosystem; the Levenshtein match to 'cors' is a clear false positive.	ai	2026/04/21

Versions (showing 57 of 57)

Version	Deps	Published
11.0.0	0 / 0	2020-11-12
10.3.1	6 / 9	2021-12-08
10.3.0	6 / 9	2021-11-26
10.1.1	6 / 9	2020-11-02
10.1.0	6 / 9	2020-11-01
10.0.35	6 / 9	2020-08-18
10.0.34	6 / 9	2020-08-10
10.0.28	6 / 9	2020-02-27
10.0.27	6 / 9	2019-12-22
10.0.22	6 / 9	2019-10-23
10.0.21	6 / 9	2019-10-05
10.0.20	6 / 9	2019-10-02
10.0.17	6 / 8	2019-08-31
10.0.16	6 / 8	2019-08-16
10.0.15	6 / 8	2019-08-02
10.0.14	6 / 8	2019-06-25
10.0.10	5 / 8	2019-03-25
10.0.9	5 / 8	2019-03-11
10.0.8	5 / 8	2019-03-11
10.0.7	5 / 8	2019-02-04
10.0.6	5 / 8	2019-01-06
10.0.5	5 / 8	2018-12-14
10.0.4	5 / 8	2018-12-05
10.0.3	5 / 8	2018-12-05
10.0.2	5 / 8	2018-12-03
10.0.1	5 / 8	2018-12-01
10.0.0	5 / 8	2018-11-27
0.13.1	5 / 2	2018-09-20
0.13.0	5 / 2	2018-08-04
0.12.0	5 / 2	2018-07-29
0.11.1	5 / 2	2018-07-15
0.11.0	5 / 2	2018-07-14
0.10.4	5 / 2	2018-07-04
0.10.3	5 / 2	2018-06-21
0.10.2	6 / 2	2018-06-16
0.10.1	6 / 2	2018-05-20
0.10.0	6 / 2	2018-05-19
0.9.0	6 / 2	2018-05-13
0.8.1	5 / 2	2018-05-05
0.8.0	5 / 2	2018-05-04
0.7.0	3 / 2	2018-04-28
0.6.5	3 / 2	2018-04-15
0.6.4	3 / 2	2018-04-14
0.6.3	3 / 2	2018-04-14
0.6.2	3 / 2	2018-04-14
0.6.0	5 / 2	2018-04-07
0.5.1	5 / 2	2018-04-01
0.5.0	5 / 2	2018-03-30
0.4.1	5 / 2	2018-03-04
0.4.0	5 / 2	2018-02-23
0.3.0	5 / 2	2018-02-22
0.2.3	5 / 2	2018-02-17
0.2.1	5 / 2	2018-02-14
0.2.0	5 / 2	2018-02-10
0.1.0	4 / 2	2018-02-10
0.0.5	4 / 2	2018-02-10
0.0.4	4 / 2	2018-02-09

v10.3.1

1 finding

LOW No provenance attestation provenance

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

v10.3.0

1 finding

LOW No provenance attestation provenance

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

v10.1.1

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.1.0

1 finding

LOW No provenance attestation provenance

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

v10.0.34

1 finding

LOW No provenance attestation provenance

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

v10.0.28

1 finding

LOW No provenance attestation provenance

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

v10.0.27

1 finding

LOW No provenance attestation provenance

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

v10.0.22

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.0.21

2 findings

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

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

LOW No provenance attestation provenance

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.

LOW No provenance attestation provenance

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

v10.0.17

1 finding

LOW No provenance attestation provenance

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

v10.0.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.0.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.0.14

1 finding

LOW No provenance attestation provenance

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

v10.0.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.0.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.0.8

1 finding

LOW No provenance attestation provenance

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

v10.0.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.0.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.13.1

1 finding

LOW No provenance attestation provenance

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

v0.13.0

1 finding

LOW No provenance attestation provenance

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

v0.12.0

1 finding

LOW No provenance attestation provenance

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

v0.11.1

1 finding

LOW No provenance attestation provenance

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

v0.11.0

1 finding

LOW No provenance attestation provenance

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

v0.10.4

1 finding

LOW No provenance attestation provenance

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

v0.10.3

1 finding

LOW No provenance attestation provenance

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

v0.10.2

1 finding

LOW No provenance attestation provenance

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

v0.10.1

1 finding

LOW No provenance attestation provenance

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

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.1

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.5

1 finding

LOW No provenance attestation provenance

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

v0.6.4

1 finding

LOW No provenance attestation provenance

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

v0.6.3

1 finding

LOW No provenance attestation provenance

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

v0.6.2

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.3

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.