babel-preset-taro
Taro babel preset
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@tarojs/helper | AI (dependencies): @tarojs/helper is a first-party sibling package in the Taro monorepo; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-syntax-jsx | AI (phantom-deps): Framework-scoped babel plugin loaded by convention in preset configuration, not directly imported. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Lodash referenced in config/helper context; stable false positive for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Reads project package.json for browserslist config; not arbitrary module loading. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a conventional runtime polyfill dependency for babel-preset packages. | ai | |
| phantom-deps | phantom-dep:@babel/runtime-corejs3 | AI (phantom-deps): Framework-scoped babel runtime; loaded by convention via @babel/plugin-transform-runtime. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 14 / 7 | |
| 4.1.11 | 14 / 7 | |
| 4.1.10 | 14 / 7 | |
| 4.1.9 | 14 / 7 | |
| 4.1.8 | 14 / 7 | |
| 4.1.7 | 14 / 7 | |
| 4.1.6 | 14 / 7 | |
| 4.1.5 | 13 / 7 | |
| 4.1.4 | 13 / 7 | |
| 4.1.3 | 13 / 7 | |
| 4.1.2 | 13 / 7 | |
| 4.1.1 | 13 / 7 | |
| 4.1.0 | 13 / 7 | |
| 4.0.13 | 13 / 7 | |
| 3.6.40 | 17 / 10 | |
| 3.6.39 | 17 / 10 |
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.