@emotion/babel-preset-css-prop
A babel preset to automatically enable emotion's css prop
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 | publisher-changed | AI (provenance): Publisher change from mitchellhamilton to emotion-release-bot reflects the emotion-js project's legitimate adoption of a dedicated release bot; stable across all future versions of this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): emotion-release-bot was added as a maintainer as part of the emotion-js project's automated release workflow; this is a legitimate and documented transition. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 11.12.0 | 4 / 1 | |
| 11.11.0 | 4 / 1 | |
| 11.10.0 | 4 / 1 | |
| 11.2.0 | 4 / 1 | |
| 11.0.0 | 4 / 1 | |
| 10.2.1 | 5 / 1 | |
| 10.2.0 | 5 / 1 | |
| 10.1.0 | 5 / 1 | |
| 10.0.27 | 4 / 1 | |
| 10.0.23 | 4 / 1 | |
| 10.0.22 | 4 / 1 | |
| 10.0.17 | 4 / 0 | |
| 10.0.14 | 4 / 0 | |
| 10.0.9 | 4 / 0 | |
| 10.0.8 | 4 / 0 | |
| 10.0.7 | 4 / 0 | |
| 10.0.6 | 4 / 0 | |
| 10.0.5 | 4 / 0 |
v11.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.22
2 findingsThis version was published by a different npm account than previous versions on 2019-10-23. 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.
v10.0.17
1 findingPackage 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.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.8
1 findingPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.