@emotion/stylis
A custom build of Stylis
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 | missing-githead | AI (provenance): Established emotion-js package from a highly trusted publisher with 1277 approved packages; missing gitHead is a minor publish-environment change, not a security signal for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from mitchellhamilton to emotion-release-bot is a documented, intentional transition to a release bot for the emotion-js project. emotion-release-bot has 548 approved packages and 0 rejections. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): emotion-release-bot is the official release automation account for the emotion-js org; its addition as maintainer is a stable, legitimate organizational change. | ai | |
| provenance | no-provenance | AI (provenance): Package predates widespread Sigstore provenance adoption; absence is expected for this era and not a risk indicator for this well-established package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.8.5 | 0 / 5 | |
| 0.8.4 | 0 / 5 | |
| 0.8.3 | 0 / 5 | |
| 0.8.2 | 0 / 5 | |
| 0.8.1 | 0 / 5 | |
| 0.8.0 | 0 / 5 | |
| 0.7.1 | 0 / 5 | |
| 0.7.0 | 0 / 5 | |
| 0.6.12 | 0 / 5 | |
| 0.6.11 | 0 / 5 | |
| 0.6.10 | 0 / 5 | |
| 0.6.9 | 0 / 5 | |
| 0.6.8 | 0 / 4 | |
| 0.6.7 | 0 / 4 | |
| 0.6.6 | 0 / 4 | |
| 0.6.5 | 0 / 4 | |
| 0.6.4 | 0 / 4 | |
| 0.6.3 | 0 / 4 | |
| 0.6.2 | 0 / 4 |
v0.8.5
2 findingsThis version was published by a different npm account than previous versions on 2019-12-22. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
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.
v0.8.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.
v0.8.2
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.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.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.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.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.