@wix/stores_app-extensions No license 26 versions

@wix/stores_app-extensions

npm

26

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.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-added	AI (maintainer-change): Internal Wix org maintainer rotation; publisher is wix-ci-publisher with strong approval record.	ai	2026/05/03
maintainer-change	maintainer-removed	AI (maintainer-change): Paired with maintainer-added; consistent with internal Wix team handoff, not a takeover signal.	ai	2026/05/03
phantom-deps	phantom-dep:@wix/sdk-runtime	AI (phantom-deps): Same-org internal dependency; stable pattern for this package.	ai	2026/04/29
phantom-deps	phantom-dep:zod	AI (phantom-deps): Used in config/build; stable pattern for this internal package.	ai	2026/04/29
bogus-package	bogus-package	AI (bogus-package): Internal package; metadata signals reflect monorepo structure, not malice.	ai	2026/04/29
npm-metadata	no-description	AI (npm-metadata): Internal Wix package; missing description is common in monorepo artifacts.	ai	2026/04/29
phantom-deps	phantom-dep:@wix/sdk-types	AI (phantom-deps): Same-org internal dependency; stable pattern for this package.	ai	2026/04/29

Versions (showing 26 of 26)

Version	Deps	Published
1.0.53	3 / 2	2026-04-19
1.0.52	3 / 2	2026-04-16
1.0.51	3 / 2	2026-04-16
1.0.50	3 / 2	2026-03-31
1.0.49	2 / 2	2026-03-19
1.0.48	2 / 2	2026-02-18
1.0.47	2 / 2	2026-01-27
1.0.46	2 / 2	2025-12-04
1.0.45	2 / 2	2025-12-02
1.0.44	2 / 2	2025-12-02
1.0.43	2 / 2	2025-12-02
1.0.42	2 / 2	2025-11-13
1.0.41	2 / 2	2025-11-10
1.0.40	2 / 2	2025-09-15
1.0.39	2 / 2	2025-07-21
1.0.38	2 / 2	2025-06-30
1.0.37	2 / 2	2025-06-18
1.0.36	2 / 2	2025-06-09
1.0.35	2 / 2	2025-06-03
1.0.34	2 / 1	2025-05-29
1.0.33	2 / 1	2025-05-19
1.0.32	2 / 1	2025-05-15
1.0.31	2 / 1	2025-05-14
1.0.30	2 / 1	2025-05-11
1.0.29	2 / 2	2025-05-07
1.0.28	2 / 1	2025-05-06

v1.0.52

1 finding

LOW No provenance attestation provenance

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

v1.0.51

1 finding

LOW No provenance attestation provenance

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

v1.0.50

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.

v1.0.49

1 finding

LOW No provenance attestation provenance

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

v1.0.48

1 finding

LOW No provenance attestation provenance

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

v1.0.47

1 finding

LOW No provenance attestation provenance

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

v1.0.46

1 finding

LOW No provenance attestation provenance

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

v1.0.45

1 finding

LOW No provenance attestation provenance

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

v1.0.44

1 finding

LOW No provenance attestation provenance

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

v1.0.43

1 finding

LOW No provenance attestation provenance

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

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

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

v1.0.40

1 finding

LOW No provenance attestation provenance

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

v1.0.39

1 finding

LOW No provenance attestation provenance

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

v1.0.38

1 finding

LOW No provenance attestation provenance

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

v1.0.37

1 finding

LOW No provenance attestation provenance

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

v1.0.36

1 finding

LOW No provenance attestation provenance

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

v1.0.35

1 finding

LOW No provenance attestation provenance

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

v1.0.34

1 finding

LOW No provenance attestation provenance

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

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

v1.0.32

1 finding

LOW No provenance attestation provenance

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

v1.0.31

1 finding

LOW No provenance attestation provenance

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

v1.0.30

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.

v1.0.29

1 finding

LOW No provenance attestation provenance

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

v1.0.28

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.