@form-create/component-elm-select
@form-create/element-ui 内置组件
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/index.min.js | AI (source-diff): Standard Vite UMD minified build output; same false positive pattern as ESM file. | ai | |
| source-diff | net-exec-file:dist/index.esm.js | AI (source-diff): Standard Vue/Babel ESM bundle; no actual network calls or dynamic execution in the file. | ai | |
| phantom-deps | phantom-dep:@form-create/utils | AI (phantom-deps): Same-org sibling package; phantom-dep heuristic is a stable false positive here. | ai | |
| provenance | no-provenance | AI (provenance): Mature monorepo package; no provenance is consistent across all form-create packages and poses no elevated risk. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 3.3.0 | 1 / 7 | |
| 3.2.37 | 1 / 0 | |
| 3.2.36 | 1 / 0 | |
| 2.7.17 | 1 / 0 | |
| 2.7.8 | 1 / 0 | |
| 2.7.1 | 1 / 0 | |
| 2.7.0 | 1 / 0 | |
| 2.6.3 | 1 / 0 | |
| 2.6.2 | 1 / 0 | |
| 2.6.1 | 1 / 0 | |
| 2.6.0 | 1 / 0 | |
| 2.5.36 | 1 / 0 | |
| 2.5.35 | 1 / 0 | |
| 2.5.33 | 1 / 0 | |
| 2.5.32 | 1 / 0 | |
| 2.5.31 | 1 / 0 | |
| 2.5.27 | 1 / 0 | |
| 2.5.25 | 1 / 0 | |
| 2.5.17 | 1 / 0 | |
| 2.5.15 | 1 / 0 | |
| 2.5.12 | 1 / 0 | |
| 2.5.11 | 1 / 0 | |
| 2.5.10 | 1 / 0 | |
| 2.5.9 | 1 / 0 | |
| 2.5.7 | 1 / 0 | |
| 2.5.6 | 1 / 0 | |
| 2.5.2 | 1 / 0 |
v2.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.