@wix/unidriver-jsdom-react
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): Internal Wix org maintainer rotation; publisher is wix-ci-publisher with strong approval track record. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Internal Wix org maintainer rotation; no external takeover indicators. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Wix monorepo package; dormancy followed by CI-publisher release is consistent with internal tooling cadence. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Wix internal monorepo package; mass-production and sparse README are expected for this org's tooling packages. | ai | |
| dependencies | unvetted-dep:@wix/unidriver-common | AI (dependencies): Sibling package in the same Wix unidriver monorepo; stable false positive for this package. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 1.5.5 | 3 / 12 | |
| 1.5.3 | 3 / 12 | |
| 1.5.2 | 3 / 12 | |
| 1.5.1 | 3 / 12 | |
| 1.5.0 | 3 / 11 | |
| 1.4.9 | 3 / 11 | |
| 1.4.8 | 3 / 11 | |
| 1.4.7 | 3 / 11 | |
| 1.4.6 | 3 / 11 | |
| 1.4.5 | 3 / 11 | |
| 1.4.4 | 3 / 11 | |
| 1.4.3 | 3 / 11 | |
| 1.4.2 | 3 / 11 | |
| 1.4.1 | 3 / 11 | |
| 1.4.0 | 3 / 11 | |
| 1.3.14 | 3 / 11 | |
| 1.3.13 | 2 / 11 | |
| 1.3.12 | 2 / 11 | |
| 1.3.11 | 2 / 11 | |
| 1.3.10 | 2 / 11 | |
| 1.3.9 | 2 / 11 | |
| 1.3.8 | 2 / 11 | |
| 1.3.7 | 2 / 11 | |
| 1.3.6 | 2 / 11 | |
| 1.3.5 | 2 / 11 | |
| 1.3.4 | 2 / 11 | |
| 1.3.3 | 2 / 11 |
v1.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.