@tarojs/binding-win32-x64-msvc
Native binding for taro
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): Platform-specific native binding for Taro; .node binary is the intended deliverable for this package type. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Platform-specific binary shim packages legitimately have no deps, sparse README, and no keywords. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.2.1 | 0 / 0 | |
| 4.2.0 | 0 / 0 | |
| 4.1.11 | 0 / 0 | |
| 4.1.10 | 0 / 0 | |
| 4.1.9 | 0 / 0 | |
| 4.1.8 | 0 / 0 | |
| 3.6.40 | 0 / 0 | |
| 3.6.39 | 0 / 0 |
v4.2.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.