@tarojs/taroize
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:babel-generator | AI (phantom-deps): babel-generator is a declared dep used indirectly via better-babel-generator; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:better-babel-generator | AI (phantom-deps): Declared dep used as a drop-in replacement for babel-generator; phantom-dep heuristic misfires here. | ai | |
| phantom-deps | phantom-dep:@babel/preset-typescript | AI (phantom-deps): Babel preset loaded by convention; stable false positive for this package. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used only to validate identifier strings (new Function(str, 'var ' + str)); not arbitrary code execution. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-proposal-optional-chaining | AI (phantom-deps): Babel plugin loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-syntax-flow | AI (phantom-deps): Babel plugin loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@babel/preset-react | AI (phantom-deps): Babel preset loaded by convention, not directly imported; stable false positive for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 12 / 3 | |
| 4.1.11 | 12 / 3 | |
| 4.1.10 | 12 / 3 | |
| 4.1.9 | 12 / 3 | |
| 4.1.8 | 12 / 3 | |
| 4.1.7 | 12 / 3 | |
| 4.1.6 | 12 / 3 | |
| 4.1.5 | 12 / 3 | |
| 4.1.4 | 12 / 3 | |
| 4.1.3 | 12 / 3 | |
| 4.1.2 | 12 / 3 | |
| 4.1.1 | 12 / 3 | |
| 4.1.0 | 12 / 3 | |
| 4.0.13 | 12 / 3 | |
| 3.6.40 | 14 / 4 | |
| 3.6.39 | 14 / 4 | |
| 3.5.4 | 11 / 1 |
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.