← Home

@wix/create-app

Create Wix apps

32
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

yoavwix-cishahatawixnpmwix-ambassadorwix-ci-publisherwix-bi-publishergalil-teamusability-sessionsyurynixydanivmayacoamitde007haimbrum-wixyoungshinobiethanpshlomitc-wixarielhwix-org-headlessfalconcinadavlacroir-wixdorchaouat

Keywords

wixwix-cli

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff net-exec-file:build/generator-JYID4IWD.js AI (source-diff): Bundled build artifact for Wix app scaffolding tool; network+exec pattern is EJS templating + git clone, not dropper malware. ai
source-diff net-exec-file:build/generator-NUSZVX2B.js AI (source-diff): Bundled CLI generator using ejs/globby/gitClone; network+exec pattern is expected for a scaffolding tool, not dropper behavior. ai
source-diff net-exec-file:build/generator-64M7WKXO.js AI (source-diff): Bundled generator artifact with EJS templating; consistent with app scaffolding tool, not malware. ai
source-diff net-exec-file:build/generator-DP6EOIQM.js AI (source-diff): Bundled scaffolding tool; network+exec pattern is EJS templating + git-clone, not dropper behavior. ai
source-diff net-exec-file:build/generator-XLHVMQCA.js AI (source-diff): Bundled EJS + git-clone tooling for a CLI scaffolder; no dropper behavior, standard build artifact. ai
source-diff net-exec-file:build/generator-GFT3B4NL.js AI (source-diff): Bundled CLI generator using ejs templating and git operations; no malicious payload in sample. ai
source-diff net-exec-file:build/generator-5JDRSM56.js AI (source-diff): Bundled build artifact with EJS templating and git-clone utilities; no malicious network+exec pattern. ai
source-diff encoded-string-file:build/index.js AI (source-diff): Base64 string is Sentry's bundled worker script (@sentry/node local-variables); stable false positive for this package. ai

Versions (showing 32 of 32)

Version Deps Published
0.0.213 0 / 35
0.0.212 0 / 35
0.0.211 0 / 35
0.0.210 0 / 35
0.0.208 0 / 35
0.0.207 0 / 35
0.0.206 0 / 35
0.0.205 0 / 35
0.0.204 0 / 35
0.0.203 0 / 35
0.0.202 0 / 35
0.0.201 0 / 35
0.0.200 0 / 35
0.0.199 0 / 35
0.0.198 0 / 35
0.0.197 0 / 35
0.0.196 0 / 35
0.0.195 0 / 35
0.0.194 0 / 35
0.0.193 0 / 35
0.0.192 0 / 35
0.0.191 0 / 35
0.0.190 0 / 35
0.0.189 0 / 35
0.0.188 0 / 35
0.0.187 0 / 35
0.0.186 0 / 35
0.0.185 0 / 35
0.0.184 0 / 34
0.0.183 0 / 34
0.0.182 0 / 34
0.0.181 0 / 34

v0.0.213

2 findings
HIGH New file with network + code execution: build/generator-NUSZVX2B.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.0.212

2 findings
HIGH New file with network + code execution: build/generator-NUSZVX2B.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.0.211

2 findings
HIGH New file with network + code execution: build/generator-NUSZVX2B.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.0.210

2 findings
HIGH New file with network + code execution: build/generator-NUSZVX2B.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.0.208

2 findings
HIGH New file with network + code execution: build/generator-JYID4IWD.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.0.207

2 findings
HIGH New file with network + code execution: build/generator-JYID4IWD.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.0.206

2 findings
HIGH New file with network + code execution: build/generator-JYID4IWD.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.0.205

2 findings
HIGH New file with network + code execution: build/generator-JYID4IWD.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.0.204

2 findings
HIGH New file with network + code execution: build/generator-64M7WKXO.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.0.203

2 findings
HIGH New file with network + code execution: build/generator-64M7WKXO.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.0.202

2 findings
HIGH New file with network + code execution: build/generator-DP6EOIQM.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.0.201

1 finding
LOW No provenance attestation provenance

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

v0.0.200

1 finding
LOW No provenance attestation provenance

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

v0.0.199

3 findings
HIGH New file with network + code execution: build/generator-XLHVMQCA.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH Long encoded string in modified file: build/index.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.0.198

3 findings
HIGH New file with network + code execution: build/generator-GFT3B4NL.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH Long encoded string in modified file: build/index.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.0.197

3 findings
HIGH New file with network + code execution: build/generator-GFT3B4NL.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH Long encoded string in modified file: build/index.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.0.196

3 findings
HIGH New file with network + code execution: build/generator-GFT3B4NL.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH Long encoded string in modified file: build/index.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.0.195

2 findings
HIGH Long encoded string in modified file: build/index.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.0.194

2 findings
HIGH Long encoded string in modified file: build/index.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.0.193

2 findings
HIGH Long encoded string in modified file: build/index.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.0.192

2 findings
HIGH Long encoded string in modified file: build/index.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.0.191

2 findings
HIGH Long encoded string in modified file: build/index.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.0.190

2 findings
HIGH Long encoded string in modified file: build/index.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.0.189

2 findings
HIGH Long encoded string in modified file: build/index.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.0.188

2 findings
HIGH Long encoded string in modified file: build/index.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.0.187

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.

v0.0.186

3 findings
HIGH New file with network + code execution: build/generator-5JDRSM56.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH Long encoded string in modified file: build/index.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.0.185

3 findings
HIGH New file with network + code execution: build/generator-5JDRSM56.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH Long encoded string in modified file: build/index.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.0.184

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.

v0.0.183

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.

v0.0.182

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.

v0.0.181

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.