@wix/unidriver-jsdom-react-legacy UNLICENSED 27 versions

@wix/unidriver-jsdom-react-legacy

npm Homepage

27

Versions

UNLICENSED

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

yoavwix-cishahatawixnpmwix-ambassadorwix-ci-publisherwix-bi-publishergalil-teamusability-sessionsyurynixydanivmayacoamitde007haimbrum-wixyoungshinobiethanparielhwix-org-headlessitai.bendafalconcinadavlacroir-wixdorchaouat

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 org internal rotation via CI publisher; consistent with org-level maintainer management.	ai	2026/05/04
maintainer-change	maintainer-removed	AI (maintainer-change): Wix org internal rotation; no signs of hostile takeover given CI publisher with strong track record.	ai	2026/05/04
bogus-package	bogus-package	AI (bogus-package): Internal Wix monorepo package; sparse metadata is expected for org-internal tooling, not a spam indicator.	ai	2026/04/29
phantom-deps	phantom-dep:@wix/unidriver-common	AI (phantom-deps): Same-org dependency; phantom-dep heuristic unreliable for re-exported or type-only deps in monorepos.	ai	2026/04/29

Versions (showing 27 of 27)

Version	Deps	Published
1.5.5	2 / 10	2026-05-15
1.5.3	2 / 10	2026-05-06
1.5.2	2 / 10	2026-05-04
1.5.1	2 / 10	2026-02-02
1.5.0	2 / 9	2026-01-22
1.4.9	2 / 9	2025-12-12
1.4.8	2 / 9	2025-11-24
1.4.7	2 / 9	2025-10-07
1.4.6	2 / 9	2025-10-01
1.4.5	2 / 9	2025-09-26
1.4.4	2 / 9	2025-09-05
1.4.3	2 / 9	2025-09-05
1.4.2	2 / 9	2025-08-22
1.4.1	2 / 9	2025-08-12
1.4.0	2 / 9	2025-07-30
1.3.14	2 / 9	2025-07-15
1.3.13	2 / 8	2025-07-10
1.3.12	2 / 8	2025-07-08
1.3.11	2 / 8	2025-06-16
1.3.10	2 / 8	2025-06-06
1.3.9	2 / 8	2025-06-04
1.3.8	2 / 8	2025-06-03
1.3.7	2 / 8	2025-05-27
1.3.6	2 / 8	2025-05-12
1.3.5	2 / 8	2025-05-08
1.3.4	2 / 8	2025-05-07
1.3.3	2 / 8	2025-05-06

v1.5.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.