@form-create/arco-design
ArcoDesign版本低代码表单|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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established package with clean diff; inactivity gap without code changes is low risk for this publisher. | ai | |
| dependencies | unvetted-dep:@form-create/component-arco-frame | AI (dependencies): First-party sub-package from same monorepo/author; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@form-create/component-arco-group | AI (dependencies): First-party sub-package from same monorepo/author; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@form-create/component-arco-radio | AI (dependencies): First-party sub-package from same monorepo/author; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@form-create/component-arco-upload | AI (dependencies): First-party sub-package from same monorepo/author; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@form-create/component-arco-checkbox | AI (dependencies): First-party sub-package from same monorepo/author; stable pattern across versions. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 3.3.1 | 8 / 10 | |
| 3.3.0 | 8 / 10 | |
| 3.2.42 | 8 / 5 | |
| 3.2.41 | 8 / 5 | |
| 3.2.40 | 8 / 5 | |
| 3.2.39 | 8 / 5 | |
| 3.2.38 | 8 / 5 | |
| 3.2.37 | 8 / 5 | |
| 3.2.36 | 8 / 5 | |
| 3.2.35 | 8 / 5 | |
| 3.2.34 | 8 / 5 | |
| 3.2.33 | 8 / 5 | |
| 3.2.32 | 8 / 5 | |
| 3.2.31 | 8 / 5 | |
| 3.2.30 | 8 / 5 | |
| 3.2.29 | 8 / 5 | |
| 3.2.28 | 8 / 5 | |
| 3.2.27 | 8 / 5 | |
| 3.2.26 | 8 / 5 | |
| 3.2.25 | 8 / 5 | |
| 3.2.24 | 8 / 5 | |
| 3.2.23 | 8 / 5 |
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.