@vtj/materials
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/deps/@vtj/utils/index.umd.js | AI (source-diff): Long string is minified UMD bundle output; sample confirms standard utility code, not obfuscation. | ai |
Versions (showing 100 of 119)
| Version | Deps | Published |
|---|---|---|
| 0.18.27 | 0 / 20 | |
| 0.18.26 | 0 / 20 | |
| 0.18.25 | 0 / 20 | |
| 0.18.24 | 0 / 20 | |
| 0.18.23 | 0 / 20 | |
| 0.18.22 | 0 / 20 | |
| 0.18.21 | 0 / 20 | |
| 0.18.20 | 0 / 20 | |
| 0.18.19 | 0 / 20 | |
| 0.18.18 | 0 / 20 | |
| 0.18.17 | 0 / 20 | |
| 0.18.16 | 0 / 20 | |
| 0.18.15 | 0 / 20 | |
| 0.18.14 | 0 / 20 | |
| 0.18.13 | 0 / 20 | |
| 0.18.12 | 0 / 20 | |
| 0.18.11 | 0 / 20 | |
| 0.18.10 | 0 / 20 | |
| 0.18.9 | 0 / 20 | |
| 0.18.8 | 0 / 20 | |
| 0.18.7 | 0 / 20 | |
| 0.18.6 | 0 / 20 | |
| 0.18.5 | 0 / 20 | |
| 0.18.4 | 0 / 20 | |
| 0.18.3 | 0 / 20 | |
| 0.18.2 | 0 / 20 | |
| 0.18.1 | 0 / 20 | |
| 0.18.0 | 0 / 20 | |
| 0.17.8 | 0 / 20 | |
| 0.17.7 | 0 / 20 | |
| 0.17.6 | 0 / 20 | |
| 0.17.5 | 0 / 20 | |
| 0.17.4 | 0 / 20 | |
| 0.17.3 | 0 / 20 | |
| 0.17.2 | 0 / 20 | |
| 0.17.1 | 0 / 20 | |
| 0.17.0 | 0 / 20 | |
| 0.16.36 | 0 / 20 | |
| 0.16.35 | 0 / 20 | |
| 0.16.34 | 0 / 20 | |
| 0.16.33 | 0 / 20 | |
| 0.16.32 | 0 / 20 | |
| 0.16.31 | 0 / 20 | |
| 0.16.30 | 0 / 20 | |
| 0.16.29 | 0 / 20 | |
| 0.16.28 | 0 / 20 | |
| 0.16.27 | 0 / 20 | |
| 0.16.26 | 0 / 20 | |
| 0.16.25 | 0 / 20 | |
| 0.16.24 | 0 / 20 | |
| 0.16.23 | 0 / 20 | |
| 0.16.22 | 0 / 20 | |
| 0.16.21 | 0 / 20 | |
| 0.16.20 | 0 / 20 | |
| 0.16.19 | 0 / 20 | |
| 0.16.18 | 0 / 20 | |
| 0.16.17 | 0 / 20 | |
| 0.16.16 | 0 / 20 | |
| 0.16.15 | 0 / 20 | |
| 0.16.14 | 0 / 20 | |
| 0.16.13 | 0 / 20 | |
| 0.16.12 | 0 / 20 | |
| 0.16.11 | 0 / 20 | |
| 0.16.10 | 0 / 20 | |
| 0.16.9 | 0 / 20 | |
| 0.16.8 | 0 / 20 | |
| 0.16.7 | 0 / 20 | |
| 0.16.6 | 0 / 20 | |
| 0.16.5 | 0 / 20 | |
| 0.16.4 | 0 / 20 | |
| 0.16.3 | 0 / 20 | |
| 0.16.2 | 0 / 20 | |
| 0.16.1 | 0 / 20 | |
| 0.16.0 | 0 / 20 | |
| 0.15.2 | 0 / 20 | |
| 0.15.1 | 0 / 20 | |
| 0.15.0 | 0 / 20 | |
| 0.14.6 | 0 / 20 | |
| 0.14.5 | 0 / 20 | |
| 0.14.4 | 0 / 20 | |
| 0.14.3 | 0 / 20 | |
| 0.14.2 | 0 / 20 | |
| 0.14.1 | 0 / 20 | |
| 0.14.0 | 0 / 20 | |
| 0.13.41 | 0 / 20 | |
| 0.13.40 | 0 / 20 | |
| 0.13.39 | 0 / 20 | |
| 0.13.38 | 0 / 20 | |
| 0.13.37 | 0 / 20 | |
| 0.13.36 | 0 / 20 | |
| 0.13.35 | 0 / 20 | |
| 0.13.34 | 0 / 20 | |
| 0.7.27 | 0 / 10 | |
| 0.7.26 | 0 / 10 | |
| 0.7.25 | 0 / 10 | |
| 0.7.24 | 0 / 10 | |
| 0.7.23 | 0 / 10 | |
| 0.7.22 | 0 / 10 | |
| 0.7.21 | 0 / 10 | |
| 0.7.20 | 0 / 10 |
v0.18.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.