@form-create/ant-design-vue
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.js | AI (source-diff): Bundled build output (webpack/vite style), not obfuscation; no malicious behavior in sample. | ai | |
| phantom-deps | phantom-dep:vite-plugin-antdv-fix | AI (phantom-deps): Used in vite config files, not source imports; expected for build plugin. | ai | |
| dependencies | unvetted-dep:vite-plugin-antdv-fix | AI (dependencies): Small vite build plugin matching added build scripts; not fetch/exec at install. | ai | |
| source-diff | net-exec-file:dist/form-create.esm.min.js | AI (source-diff): Minified Vue component bundle; network+exec pattern is normal for a form lib shipping dist files. | ai | |
| dependencies | unvetted-dep:@form-create/component-antdv-upload | AI (dependencies): First-party scoped package from same author/monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@form-create/component-antdv-group | AI (dependencies): First-party scoped package from same author/monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@form-create/component-antdv-frame | AI (dependencies): First-party scoped package from same author/monorepo; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 3.3.1 | 6 / 11 | |
| 3.3.0 | 6 / 11 | |
| 3.2.42 | 6 / 6 | |
| 3.2.41 | 6 / 6 | |
| 3.2.40 | 6 / 6 | |
| 3.2.39 | 6 / 6 | |
| 3.2.38 | 6 / 6 | |
| 3.2.37 | 6 / 6 | |
| 3.2.36 | 6 / 6 | |
| 3.2.35 | 6 / 6 | |
| 3.2.34 | 6 / 6 | |
| 3.2.33 | 6 / 6 | |
| 2.7.28 | 6 / 6 | |
| 2.7.27 | 6 / 6 | |
| 2.7.26 | 6 / 6 | |
| 2.7.25 | 6 / 6 | |
| 2.7.24 | 6 / 6 | |
| 2.7.23 | 6 / 6 | |
| 2.7.22 | 6 / 6 | |
| 2.7.21 | 6 / 6 | |
| 2.7.20 | 6 / 6 | |
| 2.7.19 | 6 / 6 | |
| 2.7.18 | 6 / 6 | |
| 2.7.17 | 6 / 6 | |
| 2.7.16 | 6 / 6 | |
| 2.7.15 | 6 / 6 | |
| 2.7.14 | 6 / 6 | |
| 2.7.12 | 6 / 6 | |
| 2.7.11 | 6 / 6 | |
| 2.7.10 | 6 / 6 | |
| 2.7.9 | 6 / 6 | |
| 2.7.8 | 6 / 6 | |
| 2.7.7 | 6 / 6 | |
| 2.7.6 | 6 / 6 | |
| 2.7.5 | 6 / 6 | |
| 2.7.4 | 6 / 6 | |
| 2.7.3 | 6 / 6 | |
| 2.7.2 | 6 / 6 | |
| 2.7.1 | 6 / 6 | |
| 2.7.0 | 6 / 6 | |
| 2.6.3 | 6 / 6 | |
| 2.6.2 | 6 / 6 | |
| 2.6.1 | 6 / 6 | |
| 2.6.0 | 7 / 4 | |
| 2.5.37 | 6 / 6 | |
| 2.5.36 | 6 / 6 |
v2.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.