← Home

@emotion/babel-plugin-jsx-pragmatic

npm Repository Homepage

Insert code to load a module corresponding to JSX pragma.

9
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

emmatowntkh44emotion-release-botandarist

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from mitchellhamilton to emotion-release-bot is a legitimate transition to the emotion-js project's dedicated release automation account, stable across all future versions. ai
maintainer-change maintainer-added AI (maintainer-change): emotion-release-bot is the official release bot for the emotion-js ecosystem; its addition as maintainer is a known legitimate organizational change. ai

Versions (showing 9 of 9)

Version Deps Published
0.3.0 1 / 2
0.2.1 1 / 1
0.2.0 1 / 1
0.1.5 1 / 1
0.1.4 1 / 1
0.1.3 1 / 0
0.1.2 1 / 0
0.1.1 1 / 0
0.1.0 1 / 0

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.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. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.5

1 finding
LOW No provenance attestation provenance

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

v0.1.4

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

This version was published by a different npm account than previous versions on 2019-10-29. 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.

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

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.