@wix/crm_app-extensions No license 19 versions

@wix/crm_app-extensions

npm

19

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
bogus-package	bogus-package	AI (bogus-package): Auto-generated Wix SDK package; sparse metadata is expected for this publisher's templated packages.	ai	2026/05/12
npm-metadata	no-description	AI (npm-metadata): Consistent with Wix CI auto-generated SDK packages; not a malware signal here.	ai	2026/05/12
phantom-deps	phantom-dep:@wix/sdk-types	AI (phantom-deps): Same-org SDK dependency; likely used in build/type declarations rather than direct imports.	ai	2026/05/12
phantom-deps	phantom-dep:@wix/sdk-runtime	AI (phantom-deps): Same-org SDK dependency; likely used in build/type declarations rather than direct imports.	ai	2026/05/12

Versions (showing 19 of 19)

Version	Deps	Published
1.0.29	3 / 2	2026-04-20
1.0.28	3 / 2	2026-03-31
1.0.27	2 / 2	2026-03-23
1.0.26	2 / 2	2026-02-18
1.0.25	2 / 2	2026-02-01
1.0.24	2 / 2	2025-12-04
1.0.23	2 / 2	2025-12-02
1.0.22	2 / 2	2025-12-02
1.0.21	2 / 2	2025-12-02
1.0.20	2 / 2	2025-11-19
1.0.19	2 / 2	2025-11-10
1.0.18	2 / 2	2025-09-16
1.0.17	2 / 2	2025-07-28
1.0.16	2 / 2	2025-07-01
1.0.15	2 / 2	2025-06-22
1.0.14	2 / 2	2025-06-10
1.0.13	2 / 2	2025-06-03
1.0.12	2 / 1	2025-05-20
1.0.11	2 / 1	2025-05-19

v1.0.29

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

v1.0.27

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

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

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

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

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

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

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

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

1 finding

LOW No provenance attestation provenance

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

v1.0.18

1 finding

LOW No provenance attestation provenance

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

v1.0.17

1 finding

LOW No provenance attestation provenance

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

v1.0.16

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

1 finding

LOW No provenance attestation provenance

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

v1.0.14

1 finding

LOW No provenance attestation provenance

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

v1.0.13

1 finding

LOW No provenance attestation provenance

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

v1.0.12

1 finding

LOW No provenance attestation provenance

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

v1.0.11

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.