@wix/blog_app-extensions No license 25 versions

@wix/blog_app-extensions

npm

25

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-wixyoungshinobiethanpshlomitc-wixarielhwix-org-headlessfalconcinadavlacroir-wixdorchaouat

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:zod	AI (phantom-deps): zod is a declared runtime dependency; phantom-dep heuristic fires but it's legitimately used by this Wix SDK package.	ai	2026/05/30
bogus-package	bogus-package	AI (bogus-package): Wix auto-generated SDK package; templated name/no-description/no-repo are expected patterns across this publisher's 63 packages.	ai	2026/05/06
npm-metadata	no-description	AI (npm-metadata): Wix auto-generated SDK packages consistently omit descriptions; not a malware signal here.	ai	2026/05/06
phantom-deps	phantom-dep:@wix/sdk-types	AI (phantom-deps): Same-org SDK dependency; phantom-dep heuristic unreliable for type-only or re-exported deps.	ai	2026/05/06
phantom-deps	phantom-dep:@wix/sdk-runtime	AI (phantom-deps): Same-org SDK dependency; phantom-dep heuristic unreliable for runtime peer deps in SDK packages.	ai	2026/05/06

Versions (showing 25 of 25)

Version	Deps	Published
1.0.52	3 / 2	2026-05-29
1.0.51	3 / 2	2026-04-20
1.0.50	3 / 2	2026-04-01
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-08
1.0.45	2 / 2	2025-12-02
1.0.44	2 / 2	2025-11-13
1.0.43	2 / 2	2025-11-11
1.0.42	2 / 2	2025-09-15
1.0.41	2 / 2	2025-07-22
1.0.40	2 / 2	2025-06-30
1.0.39	2 / 2	2025-06-18
1.0.38	2 / 2	2025-06-09
1.0.37	2 / 2	2025-06-03
1.0.36	2 / 1	2025-05-29
1.0.35	2 / 1	2025-05-19
1.0.34	2 / 1	2025-05-14
1.0.33	2 / 1	2025-05-14
1.0.32	2 / 1	2025-05-14
1.0.31	2 / 1	2025-05-14
1.0.30	2 / 1	2025-05-09
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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.50

1 finding

LOW No provenance attestation provenance

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

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. Consider requesting the maintainer enable provenance via CI/CD.

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

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

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. Consider requesting the maintainer enable provenance via CI/CD.

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. Consider requesting the maintainer enable provenance via CI/CD.

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.