@tarojs/plugin-vue-devtools
Taro 小程序端支持使用 Vue DevTools 的插件
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@tarojs/service | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is a stable false positive for @tarojs/* packages. | ai | |
| provenance | no-provenance | AI (provenance): Established Taro monorepo package; lack of provenance is consistent across all versions and not a security concern here. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 4.2.1 | 3 / 5 | |
| 4.2.0 | 3 / 5 | |
| 4.1.11 | 3 / 5 | |
| 4.1.10 | 3 / 5 | |
| 4.1.9 | 3 / 5 | |
| 4.1.8 | 3 / 5 | |
| 4.1.7 | 3 / 5 | |
| 4.1.6 | 3 / 5 | |
| 4.1.5 | 3 / 5 | |
| 4.1.4 | 3 / 5 | |
| 4.1.3 | 3 / 5 | |
| 4.1.2 | 3 / 5 | |
| 4.1.1 | 3 / 5 | |
| 4.1.0 | 3 / 5 | |
| 4.0.13 | 3 / 5 | |
| 4.0.12 | 3 / 5 | |
| 4.0.11 | 3 / 5 | |
| 4.0.10 | 3 / 5 | |
| 4.0.9 | 3 / 5 | |
| 4.0.8 | 3 / 5 | |
| 4.0.7 | 3 / 5 | |
| 4.0.6 | 3 / 5 | |
| 4.0.5 | 3 / 5 | |
| 4.0.4 | 3 / 5 | |
| 4.0.3 | 3 / 5 | |
| 4.0.2 | 3 / 5 | |
| 4.0.1 | 7 / 5 | |
| 4.0.0 | 3 / 5 | |
| 3.6.40 | 7 / 5 | |
| 3.6.39 | 7 / 5 |
v4.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.