← Home

@wix/headless-stores

npm
51
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-wixyoungshinobiethanparielhwix-org-headlessitai.bendafalconciroir-wixdorchaouat

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Wix org publisher rotation; yurynix has strong track record and no code changes accompany the transition. ai
provenance no-provenance AI (provenance): Wix CI publisher consistently publishes without Sigstore provenance; stable false positive for this org. ai
npm-metadata suspicious-initial-version AI (npm-metadata): Wix SDK packages consistently use 0.0.0 versioning; not indicative of malicious intent. ai
phantom-deps phantom-dep:@wix/auto_sdk_stores_read-only-variants-v-3 AI (phantom-deps): Same-org Wix SDK dep; stable false positive. ai
bogus-package bogus-package AI (bogus-package): Wix auto-generated SDK package; mass-production and missing metadata are structural, not malicious. ai
phantom-deps phantom-dep:@wix/auto_sdk_bookings_availability-calendar AI (phantom-deps): Same-org Wix SDK dep; stable false positive. ai
npm-metadata no-description AI (npm-metadata): Wix SDK packages consistently omit descriptions; stable false positive for this org. ai
phantom-deps phantom-dep:@wix/auto_sdk_stores_customizations-v-3 AI (phantom-deps): Same-org Wix SDK dep; phantom detection likely a heuristic miss on indirect usage patterns. ai

Versions (showing 51 of 69)

View all versions
Version Deps Published
0.0.116 13 / 13
0.0.110 13 / 12
0.0.109 13 / 12
0.0.99 15 / 11
0.0.97 15 / 9
0.0.96 15 / 9
0.0.95 15 / 9
0.0.94 15 / 9
0.0.93 15 / 9
0.0.92 15 / 9
0.0.91 15 / 9
0.0.90 15 / 9
0.0.89 15 / 9
0.0.88 15 / 9
0.0.87 15 / 9
0.0.58 15 / 9
0.0.57 15 / 9
0.0.56 14 / 9
0.0.55 14 / 9
0.0.54 14 / 9
0.0.53 14 / 9
0.0.52 13 / 8
0.0.51 13 / 8
0.0.50 13 / 8
0.0.49 13 / 8
0.0.48 13 / 8
0.0.47 13 / 8
0.0.46 13 / 8
0.0.45 13 / 8
0.0.44 13 / 8
0.0.43 13 / 8
0.0.42 13 / 8
0.0.41 13 / 8
0.0.40 13 / 8
0.0.39 13 / 8
0.0.38 13 / 8
0.0.37 13 / 8
0.0.36 13 / 8
0.0.35 13 / 8
0.0.34 13 / 8
0.0.33 13 / 8
0.0.32 13 / 8
0.0.31 13 / 8
0.0.30 13 / 8
0.0.29 13 / 8
0.0.28 13 / 8
0.0.27 13 / 8
0.0.26 13 / 8
0.0.25 13 / 8
0.0.24 13 / 8
0.0.23 13 / 8

v0.0.116

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

2 findings
HIGH Low-value / spam package indicators (5 signals, score 7) bogus-package

Matched 5 signal(s), weighted score 7: • [S_PUBLISHER_MASS_PRODUCTION] Maintainer 'oferb-wix' owns 63 packages, ≥70% share a templated name shape. • [S_DESC_MATCHES_NAME] Description is empty or just restates the package name. • [S_NO_REPO_NO_HOME] No repository, homepage, or bugs URL — genuine packages almost always link somewhere. • [S_NO_KEYWORDS] No keywords declared. • [S_EMPTY_MAIN] Entry point (cjs/dist/astro/actions/index.js) is 38 bytes — effectively empty.

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

2 findings
HIGH Low-value / spam package indicators (5 signals, score 7) bogus-package

Matched 5 signal(s), weighted score 7: • [S_PUBLISHER_MASS_PRODUCTION] Maintainer 'oferb-wix' owns 63 packages, ≥70% share a templated name shape. • [S_DESC_MATCHES_NAME] Description is empty or just restates the package name. • [S_NO_REPO_NO_HOME] No repository, homepage, or bugs URL — genuine packages almost always link somewhere. • [S_NO_KEYWORDS] No keywords declared. • [S_EMPTY_MAIN] Entry point (cjs/dist/astro/actions/index.js) is 38 bytes — effectively empty.

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

2 findings
HIGH Low-value / spam package indicators (5 signals, score 7) bogus-package

Matched 5 signal(s), weighted score 7: • [S_PUBLISHER_MASS_PRODUCTION] Maintainer 'oferb-wix' owns 63 packages, ≥70% share a templated name shape. • [S_DESC_MATCHES_NAME] Description is empty or just restates the package name. • [S_NO_REPO_NO_HOME] No repository, homepage, or bugs URL — genuine packages almost always link somewhere. • [S_NO_KEYWORDS] No keywords declared. • [S_EMPTY_MAIN] Entry point (cjs/dist/astro/actions/index.js) is 38 bytes — effectively empty.

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

2 findings
HIGH Low-value / spam package indicators (5 signals, score 7) bogus-package

Matched 5 signal(s), weighted score 7: • [S_PUBLISHER_MASS_PRODUCTION] Maintainer 'oferb-wix' owns 63 packages, ≥70% share a templated name shape. • [S_DESC_MATCHES_NAME] Description is empty or just restates the package name. • [S_NO_REPO_NO_HOME] No repository, homepage, or bugs URL — genuine packages almost always link somewhere. • [S_NO_KEYWORDS] No keywords declared. • [S_EMPTY_MAIN] Entry point (cjs/dist/astro/actions/index.js) is 38 bytes — effectively empty.

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

2 findings
HIGH Publisher changed: netanelgilad → arielh (on 2025-09-28) provenance

This version was published by a different npm account than previous versions on 2025-09-28. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v0.0.95

2 findings
HIGH Publisher changed: netanelgilad → arielh (on 2025-09-28) provenance

This version was published by a different npm account than previous versions on 2025-09-28. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v0.0.94

2 findings
HIGH Publisher changed: netanelgilad → arielh (on 2025-09-28) provenance

This version was published by a different npm account than previous versions on 2025-09-28. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v0.0.93

2 findings
HIGH Publisher changed: netanelgilad → yurynix (on 2025-09-25) provenance

This version was published by a different npm account than previous versions on 2025-09-25. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v0.0.92

2 findings
HIGH Publisher changed: netanelgilad → yurynix (on 2025-09-21) provenance

This version was published by a different npm account than previous versions on 2025-09-21. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v0.0.91

2 findings
HIGH Publisher changed: netanelgilad → yurynix (on 2025-09-17) provenance

This version was published by a different npm account than previous versions on 2025-09-17. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v0.0.90

2 findings
HIGH Publisher changed: netanelgilad → yurynix (on 2025-09-17) provenance

This version was published by a different npm account than previous versions on 2025-09-17. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v0.0.89

2 findings
HIGH Publisher changed: netanelgilad → yurynix (on 2025-09-15) provenance

This version was published by a different npm account than previous versions on 2025-09-15. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v0.0.88

2 findings
HIGH Publisher changed: netanelgilad → yurynix (on 2025-09-07) provenance

This version was published by a different npm account than previous versions on 2025-09-07. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v0.0.87

2 findings
HIGH Publisher changed: netanelgilad → yurynix (on 2025-09-04) provenance

This version was published by a different npm account than previous versions on 2025-09-04. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v0.0.58

1 finding
INFO No provenance attestation provenance

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

v0.0.57

1 finding
INFO No provenance attestation provenance

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

v0.0.56

1 finding
INFO No provenance attestation provenance

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

v0.0.55

1 finding
INFO No provenance attestation provenance

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

v0.0.54

1 finding
INFO No provenance attestation provenance

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

v0.0.53

1 finding
INFO No provenance attestation provenance

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

v0.0.52

1 finding
INFO No provenance attestation provenance

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

v0.0.51

1 finding
INFO No provenance attestation provenance

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

v0.0.50

1 finding
INFO No provenance attestation provenance

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

v0.0.49

1 finding
INFO No provenance attestation provenance

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

v0.0.48

1 finding
INFO No provenance attestation provenance

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

v0.0.47

1 finding
INFO No provenance attestation provenance

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

v0.0.46

1 finding
INFO No provenance attestation provenance

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

v0.0.45

1 finding
INFO No provenance attestation provenance

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

v0.0.44

1 finding
INFO No provenance attestation provenance

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

v0.0.43

1 finding
INFO No provenance attestation provenance

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

v0.0.42

1 finding
INFO No provenance attestation provenance

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

v0.0.41

1 finding
INFO No provenance attestation provenance

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

v0.0.40

1 finding
INFO No provenance attestation provenance

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

v0.0.39

1 finding
INFO No provenance attestation provenance

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

v0.0.38

1 finding
INFO No provenance attestation provenance

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

v0.0.37

1 finding
INFO No provenance attestation provenance

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

v0.0.36

1 finding
INFO No provenance attestation provenance

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

v0.0.35

1 finding
INFO No provenance attestation provenance

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

v0.0.34

1 finding
INFO No provenance attestation provenance

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

v0.0.33

1 finding
INFO No provenance attestation provenance

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

v0.0.32

1 finding
INFO No provenance attestation provenance

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

v0.0.31

1 finding
INFO No provenance attestation provenance

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

v0.0.30

1 finding
INFO No provenance attestation provenance

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

v0.0.29

1 finding
INFO No provenance attestation provenance

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

v0.0.28

1 finding
INFO No provenance attestation provenance

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

v0.0.27

1 finding
INFO No provenance attestation provenance

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

v0.0.26

1 finding
INFO No provenance attestation provenance

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

v0.0.25

1 finding
INFO No provenance attestation provenance

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

v0.0.24

1 finding
INFO No provenance attestation provenance

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

v0.0.23

1 finding
INFO No provenance attestation provenance

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