@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, so a manually published version cannot be tied back to a reviewed commit.
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 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 1.3.47 | 9 / 13 | |
| 1.3.46 | 9 / 13 | |
| 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 | |
| 1.3.36 | 7 / 16 | |
| 1.3.35 | 7 / 16 | |
| 1.3.34 | 7 / 16 | |
| 1.3.33 | 7 / 16 | |
| 1.3.32 | 7 / 16 | |
| 1.3.31 | 7 / 16 | |
| 1.3.30 | 7 / 16 | |
| 1.3.29 | 7 / 16 | |
| 1.3.28 | 7 / 16 | |
| 1.3.27 | 6 / 16 | |
| 1.3.26 | 6 / 16 | |
| 1.3.25 | 6 / 16 | |
| 1.3.24 | 6 / 16 | |
| 1.3.23 | 6 / 16 | |
| 1.3.22 | 6 / 16 | |
| 1.3.21 | 6 / 16 | |
| 1.3.20 | 6 / 9 | |
| 1.3.19 | 4 / 9 | |
| 1.3.18 | 4 / 9 | |
| 1.3.17 | 4 / 9 | |
| 1.3.16 | 4 / 9 | |
| 1.3.15 | 4 / 9 | |
| 1.3.14 | 4 / 9 | |
| 1.3.13 | 4 / 9 |
v1.3.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.