@wix/auto_sdk_rich-content_ricos-embeddables
Supply chain provenance
Status for the latest visible version.
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
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): Wix internal team rotation via trusted wix-ci-publisher; not a third-party takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Wix internal team rotation; removal paired with addition is consistent with org-level handoff. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): zod is a well-known, widely-used validation library with no malicious history. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Wix auto-generated SDK packages intentionally lack descriptions, repos, and keywords — this is a stable pattern across the entire @wix/auto_sdk_* namespace. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Wix auto-generated SDK packages consistently omit descriptions; not a malware signal here. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.0.17 | 3 / 2 | |
| 1.0.16 | 3 / 2 | |
| 1.0.15 | 2 / 2 | |
| 1.0.14 | 2 / 2 | |
| 1.0.13 | 2 / 2 | |
| 1.0.12 | 2 / 2 | |
| 1.0.11 | 2 / 2 | |
| 1.0.10 | 2 / 2 | |
| 1.0.9 | 2 / 2 | |
| 1.0.8 | 2 / 2 | |
| 1.0.7 | 2 / 2 | |
| 1.0.6 | 2 / 2 | |
| 1.0.5 | 2 / 2 | |
| 1.0.4 | 2 / 2 | |
| 1.0.3 | 2 / 2 | |
| 1.0.2 | 2 / 2 | |
| 1.0.1 | 2 / 2 | |
| 1.0.0 | 2 / 2 |
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.