jest-emotion
Jest utilities for emotion
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 | publisher-changed | AI (provenance): Publisher change from mitchellhamilton to emotion-release-bot reflects the emotion project's documented transition to automated releases via a dedicated bot account. Stable for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): emotion-release-bot was added as part of the emotion project's automated release workflow. Legitimate maintainer addition, stable for this package. | ai | |
| provenance | missing-githead | AI (provenance): Well-established emotion-js package from trusted publisher; missing gitHead is a minor provenance gap, not a security signal for this package. | ai | |
| phantom-deps | phantom-dep:@types/jest | AI (phantom-deps): @types/jest is a TypeScript type declaration package used for the types/ directory, not a runtime import. This is expected for a Jest utility package and stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): jest-emotion is a long-established package from the trusted emotion-js org. Lack of Sigstore provenance is expected for packages predating that tooling. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 11.0.0 | 0 / 0 | |
| 10.0.32 | 4 / 9 | |
| 10.0.27 | 4 / 9 | |
| 10.0.26 | 4 / 9 | |
| 10.0.25 | 4 / 9 | |
| 10.0.17 | 4 / 9 | |
| 10.0.14 | 4 / 9 | |
| 10.0.11 | 4 / 9 | |
| 10.0.10 | 4 / 9 | |
| 10.0.9 | 4 / 9 | |
| 10.0.8 | 4 / 9 | |
| 10.0.7 | 4 / 5 | |
| 10.0.6 | 4 / 5 | |
| 10.0.5 | 4 / 5 | |
| 10.0.4 | 4 / 5 | |
| 10.0.3 | 4 / 5 | |
| 10.0.2 | 4 / 5 | |
| 10.0.1 | 4 / 5 | |
| 10.0.0 | 4 / 5 | |
| 9.2.11 | 3 / 4 | |
| 9.2.7 | 3 / 4 | |
| 9.2.6 | 3 / 4 | |
| 9.2.5 | 3 / 4 | |
| 9.2.4 | 3 / 7 | |
| 9.2.2 | 2 / 4 | |
| 9.2.0 | 2 / 4 | |
| 9.1.3 | 1 / 4 | |
| 9.1.2 | 1 / 4 | |
| 9.0.0 | 1 / 3 |
v11.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.25
2 findingsThis version was published by a different npm account than previous versions on 2019-11-29. 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
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.4
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.
v10.0.3
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.
v10.0.2
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.
v10.0.1
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.
v10.0.0
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.