@wix/dashboard
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 |
|---|---|---|---|---|
| license | uncommon-license:UNLICENSED | AI (license): Internal Wix package; UNLICENSED is expected for proprietary internal packages. | ai | |
| provenance | no-provenance | AI (provenance): Wix CI publisher with strong track record; provenance absence is consistent across their packages. | ai | |
| dependencies | unvetted-dep:@wix/media | AI (dependencies): Internal Wix namespace dep; consistent with this package's ecosystem. | ai | |
| dependencies | unvetted-dep:@wix/communication-channel | AI (dependencies): Internal Wix namespace dep; consistent with this package's ecosystem. | ai | |
| dependencies | unvetted-dep:@wix/feedback-loop-structure | AI (dependencies): Internal Wix namespace dep; consistent with this package's ecosystem. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Wix scoped package; missing public metadata is expected for org-internal packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal package; no public description needed. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.3.45 | 9 / 13 | |
| 1.3.43 | 9 / 13 | |
| 1.3.42 | 9 / 13 | |
| 1.3.41 | 8 / 13 | |
| 1.3.40 | 8 / 16 | |
| 1.3.39 | 7 / 16 | |
| 1.3.38 | 7 / 16 | |
| 1.3.37 | 7 / 16 |
v1.3.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.