@wix/app-settings MIT 14 versions

@wix/app-settings

npm

14

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

Keywords

wixSdkBackendModulewixSdkPageModulewixSdkPublicModule

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 module; templated naming, no description, and no repo URL are structural properties of this package family.	ai	2026/05/03
npm-metadata	no-description	AI (npm-metadata): Wix auto-generated SDK packages consistently omit descriptions; not a malware signal here.	ai	2026/05/03

Versions (showing 14 of 14)

Version	Deps	Published
1.0.24	1 / 2	2026-04-27
1.0.23	1 / 2	2026-04-20
1.0.22	1 / 2	2026-01-26
1.0.21	1 / 2	2026-01-22
1.0.20	1 / 2	2026-01-21
1.0.19	1 / 2	2025-12-02
1.0.18	1 / 2	2025-12-02
1.0.17	1 / 2	2025-12-02
1.0.16	1 / 2	2025-10-15
1.0.15	1 / 2	2025-09-11
1.0.14	1 / 2	2025-07-28
1.0.13	1 / 2	2025-06-24
1.0.12	1 / 1	2025-05-26
1.0.11	1 / 1	2025-05-24

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.18

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

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

1 finding

LOW No provenance attestation provenance

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

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.