@wix/essentials
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
Keywords
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 established CI publisher; not indicative of takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Paired with maintainer-added; consistent with routine Wix team rotation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Published by long-standing wix-ci-publisher with strong approval history; dormancy reflects product cadence, not takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Wix monorepo pattern; mass-produced templated names and sparse metadata are normal for this publisher. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across Wix SDK packages; not a malware indicator for this publisher. | ai | |
| phantom-deps | phantom-dep:intl-messageformat | AI (phantom-deps): intl-messageformat is a declared runtime dep used transitively via i18next-icu; stable false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.0.8 | 9 / 14 | |
| 1.0.7 | 9 / 14 | |
| 1.0.6 | 9 / 14 | |
| 1.0.5 | 9 / 13 | |
| 1.0.4 | 9 / 13 | |
| 1.0.3 | 8 / 13 | |
| 1.0.2 | 9 / 13 | |
| 1.0.1 | 9 / 13 | |
| 1.0.0 | 8 / 13 |
v1.0.8
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.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.