@wistia/ui
Wistia UI React component library
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@wistia/type-guards | AI (dependencies): First-party Wistia scoped package; stable false positive for this package. | ai | |
| license | uncommon-license:UNLICENSED | AI (license): Intentionally UNLICENSED private Wistia internal library; stable across versions. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-hover-card | AI (dependencies): Radix UI primitive; consistent with existing @radix-ui/* deps in this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a well-known Radix UI primitive, not a suspicious addition. | ai | |
| phantom-deps | phantom-dep:@mdx-js/mdx | AI (phantom-deps): Config-file reference; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:yup | AI (phantom-deps): Config-file reference; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:react-is | AI (phantom-deps): Config-file reference; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:type-fest | AI (phantom-deps): Config-file reference; stable pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Wistia component library; sparse README and no keywords are expected for a private org package. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions CI; provenance attestation not yet enabled but publisher is consistent across versions. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-popover | AI (phantom-deps): Component library pattern; deps referenced in config files. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-tooltip | AI (phantom-deps): Component library pattern; deps referenced in config files. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-progress | AI (phantom-deps): Component library pattern; deps referenced in config files. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-hover-card | AI (phantom-deps): Component library pattern; deps referenced in config files. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped @wistia org package; Levenshtein match to uuid is a false positive. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-radio-group | AI (phantom-deps): Component library pattern; deps referenced in config files. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-toggle-group | AI (phantom-deps): Component library pattern; deps referenced in config files. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-dropdown-menu | AI (phantom-deps): Component library pattern; deps referenced in config files. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-collapsible | AI (phantom-deps): Component library pattern; deps referenced in config files. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @wistia org package; Levenshtein match to pg is a false positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @wistia org package; Levenshtein match to qs is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @wistia org package; Levenshtein match to joi is a false positive. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @wistia org package; Levenshtein match to yup is a false positive. | ai | |
| phantom-deps | phantom-dep:react-day-picker | AI (phantom-deps): Component library; Radix/UI deps referenced in config/type files, not direct imports. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-tabs | AI (phantom-deps): Component library pattern; deps referenced in config files. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-dialog | AI (phantom-deps): Component library pattern; deps referenced in config files. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-select | AI (phantom-deps): Component library pattern; deps referenced in config files. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-slider | AI (phantom-deps): Component library pattern; deps referenced in config files. | ai |
Versions (showing 100 of 207)
| Version | Deps | Published |
|---|---|---|
| 0.16.0 | 22 / 45 | |
| 0.15.14 | 22 / 45 | |
| 0.15.13 | 22 / 45 | |
| 0.15.12 | 22 / 45 | |
| 0.15.11 | 22 / 45 | |
| 0.15.10 | 22 / 45 | |
| 0.15.9 | 22 / 45 | |
| 0.15.8 | 22 / 45 | |
| 0.15.7 | 22 / 45 | |
| 0.15.6 | 22 / 45 | |
| 0.15.5 | 22 / 45 | |
| 0.15.3 | 22 / 45 | |
| 0.15.2 | 22 / 45 | |
| 0.15.1 | 22 / 45 | |
| 0.15.0 | 22 / 45 | |
| 0.14.41 | 22 / 45 | |
| 0.14.40 | 22 / 45 | |
| 0.14.39 | 22 / 45 | |
| 0.14.38 | 22 / 45 | |
| 0.14.37 | 22 / 45 | |
| 0.14.36 | 22 / 45 | |
| 0.14.35 | 22 / 45 | |
| 0.14.34 | 22 / 45 | |
| 0.14.33 | 22 / 45 | |
| 0.14.32 | 22 / 45 | |
| 0.14.31 | 22 / 45 | |
| 0.14.30 | 22 / 44 | |
| 0.14.29 | 22 / 44 | |
| 0.14.28 | 22 / 44 | |
| 0.14.27 | 22 / 44 | |
| 0.14.26 | 22 / 44 | |
| 0.14.25 | 22 / 44 | |
| 0.14.23 | 23 / 43 | |
| 0.14.22 | 23 / 43 | |
| 0.14.21 | 23 / 43 | |
| 0.14.20 | 23 / 43 | |
| 0.14.19 | 23 / 43 | |
| 0.14.18 | 23 / 43 | |
| 0.14.17 | 23 / 43 | |
| 0.14.16 | 23 / 43 | |
| 0.14.15 | 23 / 43 | |
| 0.14.13 | 23 / 43 | |
| 0.14.12 | 23 / 43 | |
| 0.14.11 | 23 / 43 | |
| 0.14.10 | 23 / 43 | |
| 0.14.9 | 23 / 43 | |
| 0.14.8 | 23 / 43 | |
| 0.14.7 | 23 / 43 | |
| 0.14.6 | 23 / 43 | |
| 0.14.5 | 23 / 43 | |
| 0.14.4 | 23 / 43 | |
| 0.14.3 | 23 / 43 | |
| 0.14.2 | 23 / 43 | |
| 0.14.1 | 23 / 43 | |
| 0.14.0 | 23 / 43 | |
| 0.13.13 | 23 / 43 | |
| 0.13.12 | 23 / 43 | |
| 0.13.11 | 23 / 43 | |
| 0.13.10 | 23 / 43 | |
| 0.13.9 | 23 / 43 | |
| 0.13.8 | 23 / 43 | |
| 0.13.7 | 23 / 43 | |
| 0.13.6 | 23 / 43 | |
| 0.13.5 | 23 / 43 | |
| 0.13.4 | 23 / 43 | |
| 0.13.3 | 23 / 43 | |
| 0.13.2 | 21 / 42 | |
| 0.13.1 | 21 / 42 | |
| 0.13.0 | 21 / 42 | |
| 0.12.1 | 21 / 42 | |
| 0.12.0 | 21 / 42 | |
| 0.11.7 | 21 / 42 | |
| 0.11.6 | 21 / 42 | |
| 0.11.5 | 21 / 42 | |
| 0.11.4 | 21 / 42 | |
| 0.11.3 | 21 / 42 | |
| 0.11.2 | 21 / 49 | |
| 0.11.1 | 21 / 49 | |
| 0.11.0 | 21 / 49 | |
| 0.10.18 | 21 / 49 | |
| 0.10.17 | 21 / 49 | |
| 0.10.16 | 21 / 49 | |
| 0.10.15 | 21 / 49 | |
| 0.10.14 | 21 / 49 | |
| 0.10.13 | 21 / 49 | |
| 0.10.12 | 21 / 49 | |
| 0.10.11 | 21 / 49 | |
| 0.10.10 | 21 / 49 | |
| 0.10.9 | 21 / 49 | |
| 0.10.8 | 21 / 49 | |
| 0.10.7 | 21 / 49 | |
| 0.10.6 | 21 / 49 | |
| 0.10.5 | 20 / 49 | |
| 0.10.4 | 20 / 49 | |
| 0.10.3 | 20 / 49 | |
| 0.10.2 | 18 / 49 | |
| 0.10.0 | 18 / 49 | |
| 0.9.7 | 18 / 49 | |
| 0.9.6 | 18 / 49 | |
| 0.9.5 | 18 / 49 |
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.