@form-create/tdesign MIT 30 versions

@form-create/tdesign

npm Repository Homepage

TDesign版本低代码表单|FormCreate 是一个可以通过 JSON 生成具有动态渲染、数据收集、验证和提交功能的低代码表单生成组件。支持6个UI框架，适配移动端，并且支持生成任何 Vue 组件。内置20种常用表单组件和自定义组件，再复杂的表单都可以轻松搞定。

30

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

xaboy

Keywords

动态表单低代码@form-createform-builderformcomponentsvue3tdesignlowcodedynamic-form

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	net-exec-file:dist/form-create.esm.min.js	AI (source-diff): Standard minified Vue ESM build bundle; network+exec pattern is a false positive on bundled Vue reactivity code.	ai	2026/05/04
dependencies	unvetted-dep:@form-create/component-tdesign-frame	AI (dependencies): First-party sibling package in the form-create monorepo; stable false positive.	ai	2026/05/04
dependencies	unvetted-dep:@form-create/component-tdesign-group	AI (dependencies): First-party sibling package in the form-create monorepo; stable false positive.	ai	2026/05/04
dependencies	unvetted-dep:@form-create/component-tdesign-upload	AI (dependencies): First-party sibling package in the form-create monorepo; stable false positive.	ai	2026/05/04

Versions (showing 30 of 30)

Version	Deps	Published
3.3.1	6 / 9	2026-06-02
3.3.0	6 / 9	2026-05-16
3.2.42	6 / 4	2026-04-30
3.2.41	6 / 4	2026-04-20
3.2.40	6 / 4	2026-04-16
3.2.39	6 / 4	2026-04-16
3.2.38	6 / 4	2026-03-06
3.2.37	6 / 4	2026-01-07
3.2.36	6 / 4	2026-01-07
3.2.35	6 / 4	2025-12-30
3.2.34	6 / 4	2025-12-30
3.2.33	6 / 4	2025-11-11
3.2.32	6 / 4	2025-10-27
3.2.31	6 / 4	2025-09-11
3.2.30	6 / 4	2025-08-26
3.2.29	6 / 4	2025-08-25
3.2.28	6 / 4	2025-07-29
3.2.27	6 / 4	2025-07-06
3.2.26	6 / 4	2025-06-25
3.2.25	6 / 4	2025-06-06
3.2.24	6 / 4	2025-05-29
3.2.23	6 / 4	2025-05-22
2.7.27	3 / 5	2026-05-16
2.7.26	3 / 5	2026-04-30
2.7.25	3 / 5	2026-04-20
2.7.24	3 / 5	2026-04-16
2.7.23	3 / 5	2026-04-16
2.7.22	3 / 5	2025-12-30
2.7.21	3 / 5	2025-12-30
2.7.20	3 / 5	2025-11-11

v3.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.42

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.

v3.2.41

2 findings

HIGH New file with network + code execution: dist/form-create.esm.min.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.40

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.39

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.

v3.2.38

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.37

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.36

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.35

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.34

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.33

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.

v3.2.32

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.31

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.30

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.29

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.28

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.27

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.26

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.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.

v3.2.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.

v3.2.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.

v2.7.27

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.7.26

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.7.25

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.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.

v2.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.

v2.7.22

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.7.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.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.