@wix/headless-ecom MIT 42 versions

@wix/headless-ecom

npm

E-commerce headless components for building cart, checkout, and commerce functionality in Wix-powered applications.

42

Versions

MIT

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-sessionsyurynixoferb-wixmayacoamitde007haimbrum-wixyoungshinobiethanparielhwix-org-headlessitai.bendafalconciroir-wixdorchaouat

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): yurynix is a well-established Wix org publisher; transition from netanelgilad is consistent with internal team handoff.	ai	2026/05/24
npm-metadata	suspicious-initial-version	AI (npm-metadata): Wix CI publishes many internal packages at 0.0.0; pattern is consistent across their approved catalog.	ai	2026/05/03
bogus-package	bogus-package	AI (bogus-package): Mass-production signals reflect Wix monorepo tooling, not spam/malware; publisher has 295 approved packages.	ai	2026/05/03
npm-metadata	no-description	AI (npm-metadata): Internal Wix package; missing description is a monorepo artifact, not a malice indicator.	ai	2026/05/03

Versions (showing 42 of 42)

Version	Deps	Published
0.0.45	8 / 15	2026-01-28
0.0.44	8 / 15	2026-01-22
0.0.43	8 / 15	2026-01-21
0.0.42	8 / 15	2026-01-21
0.0.41	8 / 14	2026-01-20
0.0.40	8 / 14	2026-01-11
0.0.39	8 / 14	2026-01-06
0.0.38	8 / 14	2025-12-11
0.0.37	8 / 14	2025-12-10
0.0.36	8 / 14	2025-12-02
0.0.35	8 / 13	2025-11-16
0.0.34	8 / 13	2025-11-13
0.0.33	8 / 13	2025-11-12
0.0.31	8 / 9	2025-09-21
0.0.30	8 / 9	2025-09-09
0.0.29	8 / 9	2025-09-07
0.0.28	8 / 9	2025-09-04
0.0.27	9 / 9	2025-09-02
0.0.26	9 / 9	2025-09-02
0.0.25	9 / 9	2025-08-27
0.0.24	9 / 9	2025-08-27
0.0.23	9 / 9	2025-08-26
0.0.22	9 / 9	2025-08-26
0.0.21	9 / 9	2025-08-26
0.0.20	9 / 9	2025-08-25
0.0.19	9 / 9	2025-08-25
0.0.18	9 / 9	2025-08-25
0.0.14	6 / 8	2025-08-04
0.0.13	5 / 8	2025-07-30
0.0.12	5 / 8	2025-07-28
0.0.11	5 / 8	2025-07-28
0.0.10	5 / 8	2025-07-24
0.0.9	5 / 8	2025-07-17
0.0.8	5 / 8	2025-07-17
0.0.7	5 / 8	2025-07-15
0.0.6	5 / 8	2025-07-15
0.0.5	5 / 8	2025-07-15
0.0.4	4 / 8	2025-07-14
0.0.3	4 / 8	2025-07-13
0.0.2	4 / 8	2025-07-13
0.0.1	0 / 2	2025-07-02
0.0.0	8 / 13	2025-11-12

v0.0.45

1 finding

LOW No provenance attestation provenance

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

v0.0.44

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

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

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

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

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

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

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

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

v0.0.35

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

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

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

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.

LOW No provenance attestation provenance

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

v0.0.30

2 findings

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

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

LOW No provenance attestation provenance

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

v0.0.29

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.

LOW No provenance attestation provenance

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

v0.0.28

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.

LOW No provenance attestation provenance

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

v0.0.27

2 findings

HIGH Publisher changed: netanelgilad → yurynix (on 2025-09-02) provenance

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

LOW No provenance attestation provenance

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

v0.0.26

2 findings

HIGH Publisher changed: netanelgilad → yurynix (on 2025-09-02) provenance

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

LOW No provenance attestation provenance

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

v0.0.25

2 findings

HIGH Publisher changed: netanelgilad → yurynix (on 2025-08-27) provenance

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

LOW No provenance attestation provenance

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

v0.0.24

2 findings

HIGH Publisher changed: netanelgilad → yurynix (on 2025-08-27) provenance

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

LOW No provenance attestation provenance

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

v0.0.23

2 findings

HIGH Publisher changed: netanelgilad → yurynix (on 2025-08-26) provenance

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

LOW No provenance attestation provenance

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

v0.0.22

2 findings

HIGH Publisher changed: netanelgilad → yurynix (on 2025-08-26) provenance

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

LOW No provenance attestation provenance

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

v0.0.21

2 findings

HIGH Publisher changed: netanelgilad → yurynix (on 2025-08-26) provenance

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

LOW No provenance attestation provenance

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

v0.0.20

2 findings

HIGH Publisher changed: netanelgilad → yurynix (on 2025-08-25) provenance

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

LOW No provenance attestation provenance

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

v0.0.19

2 findings

HIGH Publisher changed: netanelgilad → yurynix (on 2025-08-25) provenance

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

LOW No provenance attestation provenance

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

v0.0.18

2 findings

HIGH Publisher changed: netanelgilad → yurynix (on 2025-08-25) provenance

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

LOW No provenance attestation provenance

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

v0.0.14

1 finding

LOW No provenance attestation provenance

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

v0.0.13

1 finding

LOW No provenance attestation provenance

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

v0.0.12

1 finding

LOW No provenance attestation provenance

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

v0.0.11

1 finding

LOW No provenance attestation provenance

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

v0.0.10

1 finding

LOW No provenance attestation provenance

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

v0.0.9

1 finding

LOW No provenance attestation provenance

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

v0.0.8

1 finding

LOW No provenance attestation provenance

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

v0.0.7

1 finding

LOW No provenance attestation provenance

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

v0.0.6

1 finding

LOW No provenance attestation provenance

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

v0.0.5

1 finding

LOW No provenance attestation provenance

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

v0.0.4

2 findings

HIGH Publisher changed: netanelgilad → yurynix (on 2025-07-14) provenance

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

LOW No provenance attestation provenance

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

v0.0.3

1 finding

LOW No provenance attestation provenance

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

v0.0.2

1 finding

LOW No provenance attestation provenance

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

v0.0.1

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

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.