← Home

@form-create/core

npm Repository Homepage

FormCreate低代码表单渲染引擎，可以通过 JSON 生成具有动态渲染、数据收集、验证和提交功能的低代码表单。支持6个UI框架，适配移动端，并且支持生成任何 Vue 组件。

46
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

xaboy

Keywords

动态表单@form-createform-builderformcomponentsvue3json-formdynamic-form

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff net-exec-file:dist/index.min.js AI (source-diff): Standard UMD bundle for a low-code form renderer; no actual network/dropper behavior present. ai
source-diff obfuscated-file:dist/index.js AI (source-diff): Standard minified UMD bundle with clear copyright header; not obfuscated malware. ai
source-diff net-exec-file:dist/index.js AI (source-diff): UMD require('vue') + new Function for conditional logic; expected pattern for this form-rendering library. ai
source-diff net-exec-file:dist/index.esm.min.js AI (source-diff): Minified Vue form-engine bundle; network calls are Vue reactivity/fetch patterns, not dropper behavior. Stable for this package. ai
semgrep semgrep:new-function-constructor AI (semgrep): new Function() used for evaluating form condition expressions — expected pattern in a low-code form engine. ai
typosquat typosquat.levenshtein:cors AI (typosquat): Scoped package in established form-create ecosystem; name similarity to 'cors' is coincidental. ai

Versions (showing 46 of 46)

Version Deps Published
3.3.1 1 / 7
3.3.0 1 / 7
3.2.42 1 / 0
3.2.41 1 / 0
3.2.40 1 / 0
3.2.39 1 / 0
3.2.37 1 / 0
3.2.36 1 / 0
3.2.35 1 / 0
3.2.34 1 / 0
3.2.33 1 / 0
2.7.27 1 / 1
2.7.26 1 / 1
2.7.25 1 / 1
2.7.24 1 / 1
2.7.23 1 / 1
2.7.22 1 / 1
2.7.21 1 / 1
2.7.20 1 / 1
2.7.19 1 / 1
2.7.18 1 / 1
2.7.17 1 / 1
2.7.16 1 / 1
2.7.15 1 / 1
2.7.14 1 / 1
2.7.12 1 / 1
2.7.11 1 / 1
2.7.10 1 / 1
2.7.9 1 / 1
2.7.8 1 / 1
2.7.7 1 / 1
2.7.6 1 / 1
2.7.5 1 / 1
2.7.4 1 / 1
2.7.3 1 / 1
2.7.2 1 / 1
2.7.1 1 / 1
2.7.0 1 / 1
2.6.3 1 / 1
2.5.37 1 / 0
2.5.36 1 / 0
2.5.13 1 / 0
2.5.12 1 / 0
2.5.11 1 / 0
2.5.10 1 / 0
2.5.9 1 / 0

v2.7.6

1 finding
LOW No provenance attestation provenance

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

v2.7.5

1 finding
LOW No provenance attestation provenance

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

v2.7.4

1 finding
LOW No provenance attestation provenance

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

v2.7.3

1 finding
LOW No provenance attestation provenance

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

v2.7.2

1 finding
LOW No provenance attestation provenance

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

v2.7.1

1 finding
LOW No provenance attestation provenance

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

v2.7.0

1 finding
LOW No provenance attestation provenance

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

v2.5.37

1 finding
LOW No provenance attestation provenance

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

v2.5.36

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

1 finding
LOW No provenance attestation provenance

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

v2.5.12

1 finding
LOW No provenance attestation provenance

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

v2.5.11

1 finding
LOW No provenance attestation provenance

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

v2.5.10

1 finding
LOW No provenance attestation provenance

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

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