@form-create/tdesign
TDesign版本低代码表单|FormCreate 是一个可以通过 JSON 生成具有动态渲染、数据收集、验证和提交功能的低代码表单生成组件。支持6个UI框架,适配移动端,并且支持生成任何 Vue 组件。内置20种常用表单组件和自定义组件,再复杂的表单都可以轻松搞定。
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 | 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 | |
| dependencies | unvetted-dep:@form-create/component-tdesign-frame | AI (dependencies): First-party sibling package in the form-create monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@form-create/component-tdesign-group | AI (dependencies): First-party sibling package in the form-create monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@form-create/component-tdesign-upload | AI (dependencies): First-party sibling package in the form-create monorepo; stable false positive. | ai |
Versions (showing 51 of 60)
| Version | Deps | Published |
|---|---|---|
| 3.3.1 | 6 / 9 | |
| 3.3.0 | 6 / 9 | |
| 3.2.42 | 6 / 4 | |
| 3.2.41 | 6 / 4 | |
| 3.2.40 | 6 / 4 | |
| 3.2.39 | 6 / 4 | |
| 3.2.38 | 6 / 4 | |
| 3.2.37 | 6 / 4 | |
| 3.2.36 | 6 / 4 | |
| 3.2.35 | 6 / 4 | |
| 3.2.34 | 6 / 4 | |
| 3.2.33 | 6 / 4 | |
| 3.2.32 | 6 / 4 | |
| 3.2.31 | 6 / 4 | |
| 3.2.30 | 6 / 4 | |
| 3.2.29 | 6 / 4 | |
| 3.2.28 | 6 / 4 | |
| 3.2.27 | 6 / 4 | |
| 3.2.26 | 6 / 4 | |
| 3.2.25 | 6 / 4 | |
| 3.2.24 | 6 / 4 | |
| 3.2.23 | 6 / 4 | |
| 3.2.22 | 6 / 4 | |
| 3.2.21 | 6 / 4 | |
| 3.2.20 | 6 / 4 | |
| 3.2.19 | 6 / 4 | |
| 3.2.18 | 6 / 4 | |
| 3.2.17 | 6 / 4 | |
| 3.2.16 | 6 / 4 | |
| 3.2.15 | 6 / 4 | |
| 3.2.14 | 6 / 4 | |
| 3.2.13 | 6 / 4 | |
| 3.2.12 | 6 / 4 | |
| 3.2.11 | 6 / 4 | |
| 3.2.10 | 6 / 4 | |
| 3.2.9 | 6 / 4 | |
| 3.2.8 | 6 / 4 | |
| 3.2.7 | 6 / 4 | |
| 3.2.6 | 6 / 4 | |
| 3.2.5 | 6 / 4 | |
| 3.2.4 | 6 / 4 | |
| 3.2.3 | 6 / 4 | |
| 3.2.2 | 6 / 4 | |
| 3.2.1 | 6 / 4 | |
| 3.2.0 | 6 / 4 | |
| 3.1.35 | 6 / 4 | |
| 3.1.34 | 6 / 4 | |
| 3.1.33 | 6 / 4 | |
| 3.1.32 | 6 / 4 | |
| 3.1.31 | 6 / 4 | |
| 3.1.30 | 6 / 4 |
v3.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.