@eka-care/medassist-widget
MedAssist Widget react application
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:preact | AI (phantom-deps): UI framework dep, likely used in bundled dist not scanned source. | ai | |
| phantom-deps | phantom-dep:markdown-to-jsx | AI (phantom-deps): Rendering lib consistent with widget's chat UI purpose. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Frequent releases are this package's established pattern (234+ versions). | ai | |
| source-diff | obfuscated-file:dist/medassist-widget-html2canvas.esm-CphxV6YW.js | AI (source-diff): Minified html2canvas ESM bundle; standard Vite build output for this widget package. | ai | |
| source-diff | encoded-string-file:dist/medassist-widget.js | AI (source-diff): Long strings are minified bundle output from remark/rehype/React deps, not obfuscation. Stable pattern for this bundled widget. | ai | |
| phantom-deps | phantom-dep:lucide-react | AI (phantom-deps): Build-time bundled dep in Vite widget. | ai | |
| phantom-deps | phantom-dep:react-markdown | AI (phantom-deps): Build-time bundled dep in Vite widget. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): Build-time bundled dep in Vite widget. | ai | |
| phantom-deps | phantom-dep:tailwindcss-animate | AI (phantom-deps): Build-time bundled dep in Vite widget. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-slot | AI (phantom-deps): Build-time bundled dep in Vite widget. | ai | |
| phantom-deps | phantom-dep:react | AI (phantom-deps): Bundled Vite/React widget; deps resolved at build time, not via Node imports. | ai | |
| phantom-deps | phantom-dep:@eka-care/medassist-core | AI (phantom-deps): Same-org dep bundled at build time. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-checkbox | AI (phantom-deps): Build-time bundled dep in Vite widget. | ai | |
| phantom-deps | phantom-dep:class-variance-authority | AI (phantom-deps): Build-time bundled dep in Vite widget. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-scroll-area | AI (phantom-deps): Build-time bundled dep in Vite widget. | ai | |
| phantom-deps | phantom-dep:@types/html2canvas | AI (phantom-deps): Type-only dep, not imported at runtime. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-avatar | AI (phantom-deps): Build-time bundled dep in Vite widget. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Same as react — build-time bundled dep. | ai | |
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): Build-time bundled dep in Vite widget. | ai | |
| phantom-deps | phantom-dep:zustand | AI (phantom-deps): Build-time bundled dep in Vite widget. | ai | |
| phantom-deps | phantom-dep:html2canvas | AI (phantom-deps): Build-time bundled dep in Vite widget. | ai |
Versions (showing 93 of 193)
| Version | Deps | Published |
|---|---|---|
| 0.1.0 | 16 / 15 | |
| 0.0.99 | 16 / 15 | |
| 0.0.98 | 16 / 15 | |
| 0.0.97 | 16 / 15 | |
| 0.0.96 | 16 / 15 | |
| 0.0.95 | 16 / 15 | |
| 0.0.94 | 16 / 15 | |
| 0.0.92 | 16 / 15 | |
| 0.0.91 | 16 / 15 | |
| 0.0.90 | 16 / 15 | |
| 0.0.89 | 16 / 15 | |
| 0.0.88 | 16 / 15 | |
| 0.0.87 | 16 / 15 | |
| 0.0.86 | 16 / 15 | |
| 0.0.85 | 16 / 15 | |
| 0.0.84 | 14 / 15 | |
| 0.0.83 | 14 / 15 | |
| 0.0.82 | 14 / 15 | |
| 0.0.81 | 14 / 15 | |
| 0.0.80 | 14 / 15 | |
| 0.0.79 | 14 / 15 | |
| 0.0.78 | 14 / 15 | |
| 0.0.77 | 14 / 15 | |
| 0.0.76 | 14 / 15 | |
| 0.0.75 | 14 / 15 | |
| 0.0.74 | 14 / 15 | |
| 0.0.73 | 14 / 15 | |
| 0.0.72 | 14 / 15 | |
| 0.0.70 | 14 / 15 | |
| 0.0.68 | 14 / 15 | |
| 0.0.67 | 14 / 15 | |
| 0.0.66 | 14 / 15 | |
| 0.0.65 | 14 / 15 | |
| 0.0.64 | 14 / 15 | |
| 0.0.63 | 14 / 15 | |
| 0.0.62 | 14 / 15 | |
| 0.0.60 | 14 / 15 | |
| 0.0.59 | 14 / 15 | |
| 0.0.58 | 14 / 15 | |
| 0.0.57 | 14 / 15 | |
| 0.0.56 | 14 / 15 | |
| 0.0.54 | 14 / 15 | |
| 0.0.53 | 14 / 15 | |
| 0.0.52 | 14 / 15 | |
| 0.0.50 | 14 / 15 | |
| 0.0.49 | 14 / 15 | |
| 0.0.48 | 14 / 15 | |
| 0.0.47 | 14 / 15 | |
| 0.0.46 | 14 / 15 | |
| 0.0.45 | 14 / 15 | |
| 0.0.44 | 14 / 15 | |
| 0.0.43 | 14 / 15 | |
| 0.0.42 | 14 / 15 | |
| 0.0.41 | 14 / 15 | |
| 0.0.40 | 14 / 15 | |
| 0.0.39 | 14 / 15 | |
| 0.0.38 | 14 / 15 | |
| 0.0.37 | 14 / 15 | |
| 0.0.36 | 14 / 15 | |
| 0.0.35 | 14 / 15 | |
| 0.0.34 | 14 / 15 | |
| 0.0.33 | 14 / 15 | |
| 0.0.32 | 14 / 15 | |
| 0.0.31 | 14 / 15 | |
| 0.0.30 | 14 / 15 | |
| 0.0.29 | 14 / 15 | |
| 0.0.28 | 14 / 15 | |
| 0.0.27 | 14 / 15 | |
| 0.0.26 | 14 / 15 | |
| 0.0.25 | 14 / 15 | |
| 0.0.24 | 14 / 15 | |
| 0.0.23 | 14 / 15 | |
| 0.0.22 | 14 / 15 | |
| 0.0.21 | 14 / 15 | |
| 0.0.20 | 14 / 15 | |
| 0.0.18 | 14 / 15 | |
| 0.0.17 | 14 / 15 | |
| 0.0.16 | 14 / 15 | |
| 0.0.15 | 14 / 15 | |
| 0.0.14 | 14 / 15 | |
| 0.0.13 | 14 / 15 | |
| 0.0.12 | 14 / 15 | |
| 0.0.11 | 14 / 15 | |
| 0.0.10 | 14 / 15 | |
| 0.0.9 | 14 / 15 | |
| 0.0.8 | 14 / 15 | |
| 0.0.7 | 14 / 15 | |
| 0.0.6 | 14 / 15 | |
| 0.0.5 | 14 / 15 | |
| 0.0.4 | 14 / 15 | |
| 0.0.3 | 14 / 15 | |
| 0.0.2 | 14 / 15 | |
| 0.0.1 | 14 / 15 |
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.