@ohif/ui-next
Next version of OHIF Viewers UI, more customizable using shadcn/ui
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): UI component library bundles deps into UMD; phantom-dep false positives are structural for this package. | ai | |
| phantom-deps | phantom-dep:react | AI (phantom-deps): Bundled UMD output; phantom-dep heuristic consistently misfires for this package. | ai | |
| phantom-deps | phantom-dep:tailwindcss | AI (phantom-deps): Bundled UMD output; phantom-dep heuristic consistently misfires for this package. | ai | |
| source-diff | encoded-string-file:dist/ohif-ui-next.umd.js | AI (source-diff): Sample shows standard base64 codec (toByteArray/fromByteArray) in bundled UMD output, not malicious payload. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.12.4 | 35 / 1 | |
| 3.12.2 | 35 / 1 | |
| 3.12.1 | 35 / 1 | |
| 3.12.0 | 35 / 1 | |
| 3.11.1 | 35 / 1 | |
| 3.10.2 | 34 / 1 |
v3.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.1
2 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.