babel-plugin-syntax-jsx
Allow parsing of jsx
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): The sebmck→hzoo transition in 2016 is the well-documented, legitimate handoff of Babel maintainership from its creator to Henry Zhu. Stable for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Babel plugin packages from this era commonly omit descriptions; not a risk signal for this established package. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance by years; absence of attestation is expected for 2016-era Babel packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Minimal syntax plugin is legitimately tiny; inflated semver is false positive for established package with 33 prior versions. | ai | |
| phantom-deps | phantom-dep:babel-runtime | AI (phantom-deps): babel-runtime is expected config/peer dependency for Babel v6 plugins; not a security issue. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 6.18.0 | 0 / 0 | |
| 6.13.0 | 0 / 0 | |
| 6.8.0 | 1 / 1 | |
| 6.5.0 | 1 / 1 | |
| 6.3.13 | 1 / 1 | |
| 6.2.4 | 1 / 1 | |
| 6.1.18 | 1 / 1 | |
| 6.1.17 | 1 / 1 | |
| 6.1.16 | 1 / 1 | |
| 6.1.13 | 1 / 1 | |
| 6.1.10 | 1 / 1 | |
| 6.1.6 | 1 / 1 | |
| 6.1.5 | 1 / 1 | |
| 6.1.4 | 1 / 1 | |
| 6.0.14 | 1 / 0 | |
| 6.0.2 | 1 / 0 |
v6.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
2 findingsThis version was published by a different npm account than previous versions on 2016-02-07. 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.
v6.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.