@vtj/designer
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 | obfuscated-file:dist/index-CsUYbbAN.js | AI (source-diff): Vite/rollup bundled dist output, not obfuscation; no malicious behavior present. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package convention; not indicative of malicious intent. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): mockjs is a well-established, widely-used mocking library, not a supply-chain risk. | ai | |
| source-diff | obfuscated-file:dist/index-DIpZt6oq.js | AI (source-diff): Standard Vite minified bundle for a Vue3 low-code designer; long lines are minified ES module code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-dmpcFWLr.js | AI (source-diff): Vite content-hashed bundle; minified but not obfuscated — readable imports visible in sample. | ai | |
| source-diff | obfuscated-file:dist/index-BmBAxe9U.js | AI (source-diff): Standard Vite minified bundle for a Vue3 low-code designer; content matches expected vue/element-plus imports, not malicious obfuscation. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 491 versions; no provenance is consistent across all releases. | ai | |
| dependencies | unvetted-dep:mockjs | AI (dependencies): mockjs is a standard mock data library expected in a low-code designer tool; stable use across this package family. | ai | |
| phantom-deps | phantom-dep:highlight.js | AI (phantom-deps): Declared as runtime dep, likely bundled or loaded by convention in a low-code designer; stable false positive. | ai | |
| phantom-deps | phantom-dep:@vue/devtools-core | AI (phantom-deps): Framework-scoped Vue devtools package loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@vue/devtools-kit | AI (phantom-deps): Framework-scoped Vue devtools package loaded by convention; stable false positive for this package. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 0.18.18 | 14 / 4 | |
| 0.16.36 | 14 / 4 | |
| 0.16.33 | 14 / 4 | |
| 0.16.32 | 14 / 4 | |
| 0.16.30 | 14 / 4 | |
| 0.16.24 | 14 / 4 | |
| 0.16.23 | 14 / 4 | |
| 0.16.22 | 14 / 4 | |
| 0.16.20 | 14 / 4 | |
| 0.16.18 | 14 / 4 | |
| 0.16.16 | 14 / 4 | |
| 0.16.15 | 14 / 4 | |
| 0.16.7 | 14 / 4 | |
| 0.7.31 | 7 / 4 | |
| 0.7.30 | 6 / 3 | |
| 0.7.29 | 6 / 3 | |
| 0.7.28 | 6 / 3 | |
| 0.7.27 | 6 / 3 | |
| 0.7.26 | 6 / 3 | |
| 0.7.25 | 6 / 3 | |
| 0.7.24 | 6 / 3 | |
| 0.7.23 | 6 / 3 | |
| 0.7.22 | 6 / 3 | |
| 0.7.21 | 6 / 3 | |
| 0.7.20 | 6 / 3 | |
| 0.7.19 | 6 / 3 | |
| 0.7.18 | 6 / 3 | |
| 0.7.17 | 6 / 3 | |
| 0.7.16 | 6 / 3 | |
| 0.7.15 | 6 / 3 | |
| 0.7.14 | 6 / 3 | |
| 0.7.13 | 6 / 3 | |
| 0.7.12 | 6 / 3 | |
| 0.7.11 | 6 / 3 | |
| 0.7.10 | 6 / 3 | |
| 0.7.9 | 6 / 3 | |
| 0.7.7 | 6 / 3 | |
| 0.7.6 | 6 / 3 | |
| 0.7.5 | 6 / 3 | |
| 0.7.4 | 6 / 3 | |
| 0.7.3 | 6 / 3 | |
| 0.7.2 | 6 / 3 | |
| 0.7.1 | 6 / 3 | |
| 0.7.0 | 6 / 3 |
v0.18.18
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.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.7.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.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.