@vtj/local
VTJ 是一款基于 Vue3 + Typescript 的低代码页面可视化设计器。内置低代码引擎、渲染器和代码生成器，面向前端开发者，开箱即用。 无缝嵌入本地开发工程，不改变前端开发流程和编码习惯。
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/index.cjs | AI (source-diff): Long string is an RSA public key in __ACCESS__ config for the package's own auth service; stable pattern across versions. | ai | |
| source-diff | encoded-string-file:dist/index.mjs | AI (source-diff): Same RSA public key in ESM build; mirrors CJS finding, stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@vtj/node | AI (dependencies): @vtj/node is a first-party sibling package in the same @vtj monorepo; stable false positive for this package family. | ai | |
| provenance | no-provenance | AI (provenance): Established package family with consistent publishing history; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 100 of 467)
| Version | Deps | Published |
|---|---|---|
| 0.13.25 | 5 / 4 | |
| 0.13.24 | 5 / 4 | |
| 0.13.23 | 5 / 4 | |
| 0.13.22 | 5 / 4 | |
| 0.13.21 | 5 / 4 | |
| 0.13.20 | 5 / 4 | |
| 0.13.19 | 5 / 4 | |
| 0.13.18 | 5 / 4 | |
| 0.13.17 | 5 / 4 | |
| 0.13.16 | 5 / 4 | |
| 0.13.15 | 5 / 4 | |
| 0.13.14 | 5 / 4 | |
| 0.13.13 | 5 / 4 | |
| 0.13.12 | 5 / 4 | |
| 0.13.11 | 5 / 4 | |
| 0.13.10 | 5 / 4 | |
| 0.13.9 | 5 / 4 | |
| 0.13.8 | 5 / 4 | |
| 0.13.7 | 5 / 4 | |
| 0.13.6 | 5 / 4 | |
| 0.13.5 | 5 / 4 | |
| 0.13.4 | 5 / 4 | |
| 0.13.3 | 5 / 4 | |
| 0.13.2 | 5 / 4 | |
| 0.13.1 | 5 / 4 | |
| 0.13.0 | 5 / 4 | |
| 0.12.70 | 5 / 4 | |
| 0.12.69 | 5 / 4 | |
| 0.12.68 | 5 / 4 | |
| 0.12.67 | 5 / 4 | |
| 0.12.66 | 5 / 4 | |
| 0.12.65 | 5 / 4 | |
| 0.12.64 | 5 / 4 | |
| 0.12.63 | 5 / 4 | |
| 0.12.62 | 5 / 4 | |
| 0.12.61 | 5 / 4 | |
| 0.12.60 | 5 / 4 | |
| 0.12.59 | 5 / 4 | |
| 0.12.58 | 5 / 4 | |
| 0.12.57 | 5 / 4 | |
| 0.12.56 | 5 / 4 | |
| 0.12.55 | 5 / 4 | |
| 0.12.54 | 5 / 4 | |
| 0.12.53 | 5 / 4 | |
| 0.12.52 | 5 / 4 | |
| 0.12.51 | 5 / 4 | |
| 0.12.50 | 5 / 4 | |
| 0.12.49 | 5 / 4 | |
| 0.12.48 | 5 / 4 | |
| 0.12.47 | 5 / 4 | |
| 0.12.46 | 5 / 4 | |
| 0.12.45 | 5 / 4 | |
| 0.12.44 | 5 / 4 | |
| 0.12.43 | 5 / 4 | |
| 0.12.42 | 5 / 4 | |
| 0.12.41 | 5 / 4 | |
| 0.12.40 | 5 / 4 | |
| 0.12.39 | 5 / 4 | |
| 0.12.38 | 5 / 4 | |
| 0.12.37 | 5 / 4 | |
| 0.12.36 | 5 / 4 | |
| 0.12.35 | 5 / 4 | |
| 0.12.34 | 5 / 4 | |
| 0.12.33 | 5 / 4 | |
| 0.12.32 | 5 / 4 | |
| 0.12.31 | 5 / 4 | |
| 0.12.30 | 5 / 4 | |
| 0.12.29 | 5 / 4 | |
| 0.12.28 | 5 / 4 | |
| 0.12.27 | 5 / 4 | |
| 0.12.26 | 5 / 4 | |
| 0.12.25 | 5 / 4 | |
| 0.12.24 | 5 / 4 | |
| 0.12.23 | 5 / 4 | |
| 0.12.22 | 5 / 4 | |
| 0.12.21 | 5 / 4 | |
| 0.12.20 | 5 / 4 | |
| 0.12.19 | 5 / 4 | |
| 0.12.18 | 5 / 4 | |
| 0.12.17 | 5 / 4 | |
| 0.12.16 | 5 / 4 | |
| 0.12.15 | 5 / 4 | |
| 0.12.14 | 5 / 4 | |
| 0.12.13 | 5 / 4 | |
| 0.12.12 | 5 / 4 | |
| 0.12.11 | 5 / 4 | |
| 0.12.10 | 5 / 4 | |
| 0.12.9 | 5 / 4 | |
| 0.12.8 | 5 / 4 | |
| 0.12.7 | 5 / 4 | |
| 0.12.6 | 5 / 4 | |
| 0.12.5 | 5 / 4 | |
| 0.12.4 | 5 / 4 | |
| 0.12.3 | 5 / 4 | |
| 0.12.2 | 5 / 4 | |
| 0.12.1 | 5 / 4 | |
| 0.12.0 | 5 / 4 | |
| 0.11.16 | 5 / 4 | |
| 0.11.15 | 5 / 4 | |
| 0.11.14 | 5 / 4 |
v0.12.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.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.
v0.11.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.