@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 |
|---|---|---|
| 1.0.0 | 13 / 48 | |
| 0.26.16 | 13 / 44 | |
| 0.26.15 | 13 / 49 | |
| 0.26.14 | 13 / 49 | |
| 0.26.13 | 13 / 49 | |
| 0.26.12 | 13 / 49 | |
| 0.26.11 | 13 / 49 | |
| 0.26.10 | 13 / 49 | |
| 0.26.9 | 13 / 49 | |
| 0.26.8 | 13 / 49 | |
| 0.26.7 | 13 / 49 | |
| 0.26.6 | 13 / 49 | |
| 0.26.5 | 13 / 49 | |
| 0.26.4 | 13 / 49 | |
| 0.26.3 | 13 / 49 | |
| 0.26.2 | 13 / 49 | |
| 0.26.1 | 13 / 49 | |
| 0.26.0 | 13 / 49 | |
| 0.25.10 | 13 / 49 | |
| 0.25.9 | 13 / 49 | |
| 0.25.8 | 13 / 49 | |
| 0.25.7 | 13 / 49 | |
| 0.25.6 | 13 / 49 | |
| 0.25.5 | 13 / 49 | |
| 0.25.4 | 13 / 49 | |
| 0.25.3 | 13 / 49 | |
| 0.25.2 | 13 / 49 | |
| 0.25.1 | 13 / 49 | |
| 0.25.0 | 25 / 49 | |
| 0.24.0 | 25 / 49 | |
| 0.23.0 | 24 / 49 | |
| 0.22.10 | 23 / 49 | |
| 0.22.9 | 23 / 49 | |
| 0.22.8 | 23 / 49 | |
| 0.22.7 | 23 / 49 | |
| 0.22.6 | 22 / 49 | |
| 0.22.5 | 22 / 49 | |
| 0.22.4 | 22 / 49 | |
| 0.22.3 | 22 / 49 | |
| 0.22.2 | 22 / 49 | |
| 0.22.1 | 22 / 48 | |
| 0.22.0 | 22 / 48 | |
| 0.21.12 | 22 / 48 | |
| 0.21.11 | 22 / 48 | |
| 0.21.10 | 22 / 48 | |
| 0.21.9 | 23 / 47 | |
| 0.21.8 | 23 / 47 | |
| 0.21.7 | 23 / 47 | |
| 0.21.6 | 23 / 47 | |
| 0.21.1 | 23 / 47 | |
| 0.21.0 | 22 / 47 | |
| 0.20.22 | 22 / 47 | |
| 0.20.21 | 22 / 47 | |
| 0.20.20 | 22 / 47 | |
| 0.20.19 | 22 / 47 | |
| 0.20.18 | 22 / 47 | |
| 0.20.17 | 22 / 47 | |
| 0.20.16 | 22 / 47 | |
| 0.20.15 | 22 / 47 | |
| 0.20.14 | 22 / 47 | |
| 0.20.13 | 22 / 47 | |
| 0.20.12 | 22 / 47 | |
| 0.20.11 | 22 / 47 | |
| 0.20.10 | 22 / 47 | |
| 0.20.9 | 22 / 47 | |
| 0.20.8 | 21 / 47 | |
| 0.20.6 | 21 / 47 | |
| 0.20.5 | 21 / 47 | |
| 0.20.4 | 21 / 47 | |
| 0.20.3 | 21 / 45 | |
| 0.20.2 | 21 / 45 | |
| 0.20.1 | 21 / 43 | |
| 0.20.0 | 21 / 43 | |
| 0.19.4 | 21 / 43 | |
| 0.19.3 | 21 / 43 | |
| 0.19.2 | 21 / 43 | |
| 0.19.1 | 21 / 43 | |
| 0.19.0 | 21 / 43 | |
| 0.18.18 | 21 / 43 | |
| 0.18.17 | 21 / 43 | |
| 0.18.16 | 21 / 43 | |
| 0.18.15 | 21 / 43 | |
| 0.18.14 | 21 / 43 | |
| 0.18.13 | 21 / 43 | |
| 0.18.12 | 21 / 43 | |
| 0.18.11 | 21 / 43 | |
| 0.18.10 | 21 / 43 | |
| 0.18.9 | 21 / 43 | |
| 0.18.8 | 21 / 44 | |
| 0.18.7 | 21 / 44 | |
| 0.18.6 | 21 / 44 | |
| 0.18.5 | 21 / 44 | |
| 0.18.4 | 21 / 44 | |
| 0.18.3 | 21 / 44 | |
| 0.18.2 | 21 / 44 | |
| 0.18.1 | 21 / 44 | |
| 0.18.0 | 21 / 44 | |
| 0.17.1 | 22 / 45 | |
| 0.17.0 | 22 / 45 | |
| 0.16.1 | 22 / 45 |
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.