@vtj/renderer MIT 31 versions

@vtj/renderer

npm Repository Homepage

VTJ 是一款基于 Vue3 + Typescript 的低代码页面可视化设计器。内置低代码引擎、渲染器和代码生成器，面向前端开发者，开箱即用。无缝嵌入本地开发工程，不改变前端开发流程和编码习惯。

31

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

chenhuachun

Keywords

低代码引擎LowCode EngineVue3低代码低代码渲染器低代码设计器代码生成器代码可视化

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:eval5	AI (phantom-deps): eval5 is a JS sandbox used by this low-code renderer; config-file-only reference is expected for conditional runtime use.	ai	2026/06/12
source-diff	encoded-string-file:dist/index.cjs	AI (source-diff): Long string is a URL assembled via array join for license/auth endpoint; stable pattern across this package's versions.	ai	2026/04/30
source-diff	encoded-string-file:dist/index.mjs	AI (source-diff): Long string is a hardcoded RSA public key for license verification; stable pattern across this package's versions.	ai	2026/04/30
dependencies	unvetted-dep:@vtj/core	AI (dependencies): Same-monorepo sibling dep; co-versioned and expected for this package.	ai	2026/04/29
dependencies	unvetted-dep:@vtj/utils	AI (dependencies): Same-monorepo sibling dep; co-versioned and expected for this package.	ai	2026/04/29

Versions (showing 31 of 231)

Version	Deps	Published
0.10.1	2 / 5	2025-02-25
0.7.30	4 / 3	2024-03-29
0.7.29	4 / 3	2024-03-26
0.7.28	4 / 3	2024-03-25
0.7.27	4 / 3	2024-03-18
0.7.26	4 / 3	2024-03-18
0.7.25	4 / 3	2024-03-13
0.7.24	4 / 3	2024-03-13
0.7.23	4 / 3	2024-03-12
0.7.22	4 / 3	2024-03-08
0.7.21	4 / 3	2024-03-07
0.7.20	4 / 3	2024-03-07
0.7.19	4 / 3	2024-03-05
0.7.18	4 / 3	2024-02-28
0.7.17	4 / 3	2024-02-28
0.7.16	4 / 3	2024-02-27
0.7.15	4 / 3	2024-02-23
0.7.14	4 / 3	2024-01-31
0.7.13	4 / 3	2024-01-30
0.7.12	4 / 3	2024-01-29
0.7.11	4 / 3	2024-01-29
0.7.10	5 / 3	2024-01-25
0.7.9	5 / 3	2024-01-25
0.7.7	5 / 3	2024-01-23
0.7.6	5 / 3	2024-01-22
0.7.5	5 / 3	2024-01-20
0.7.4	5 / 3	2024-01-19
0.7.3	5 / 3	2024-01-19
0.7.2	5 / 3	2024-01-18
0.7.1	5 / 3	2024-01-17
0.7.0	5 / 3	2024-01-17

v0.10.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.30

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.29

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.28

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.27

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.26

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.25

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.24

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.23

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.22

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.