@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 100 of 193)
| Version | Deps | Published |
|---|---|---|
| 0.2.0 | 15 / 20 | |
| 0.1.105 | 15 / 20 | |
| 0.1.104 | 15 / 20 | |
| 0.1.103 | 15 / 20 | |
| 0.1.102 | 15 / 20 | |
| 0.1.101 | 15 / 20 | |
| 0.1.100 | 15 / 20 | |
| 0.1.99 | 15 / 20 | |
| 0.1.98 | 15 / 20 | |
| 0.1.97 | 15 / 20 | |
| 0.1.96 | 15 / 20 | |
| 0.1.95 | 15 / 20 | |
| 0.1.94 | 15 / 20 | |
| 0.1.93 | 15 / 20 | |
| 0.1.92 | 15 / 20 | |
| 0.1.91 | 15 / 20 | |
| 0.1.90 | 15 / 20 | |
| 0.1.89 | 15 / 20 | |
| 0.1.88 | 15 / 15 | |
| 0.1.87 | 15 / 15 | |
| 0.1.86 | 15 / 15 | |
| 0.1.85 | 15 / 15 | |
| 0.1.84 | 15 / 15 | |
| 0.1.83 | 16 / 15 | |
| 0.1.82 | 15 / 15 | |
| 0.1.81 | 15 / 15 | |
| 0.1.80 | 16 / 15 | |
| 0.1.79 | 15 / 15 | |
| 0.1.78 | 16 / 15 | |
| 0.1.77 | 16 / 15 | |
| 0.1.76 | 16 / 15 | |
| 0.1.72 | 16 / 15 | |
| 0.1.71 | 16 / 15 | |
| 0.1.70 | 16 / 15 | |
| 0.1.69 | 16 / 15 | |
| 0.1.68 | 16 / 15 | |
| 0.1.67 | 16 / 15 | |
| 0.1.66 | 16 / 15 | |
| 0.1.65 | 16 / 15 | |
| 0.1.64 | 16 / 15 | |
| 0.1.63 | 16 / 15 | |
| 0.1.62 | 16 / 15 | |
| 0.1.61 | 16 / 15 | |
| 0.1.60 | 16 / 15 | |
| 0.1.59 | 16 / 15 | |
| 0.1.58 | 16 / 15 | |
| 0.1.57 | 16 / 15 | |
| 0.1.56 | 16 / 15 | |
| 0.1.53 | 16 / 15 | |
| 0.1.52 | 16 / 15 | |
| 0.1.51 | 16 / 15 | |
| 0.1.50 | 16 / 15 | |
| 0.1.49 | 16 / 15 | |
| 0.1.48 | 16 / 15 | |
| 0.1.47 | 16 / 15 | |
| 0.1.46 | 16 / 15 | |
| 0.1.45 | 16 / 15 | |
| 0.1.44 | 16 / 15 | |
| 0.1.43 | 16 / 15 | |
| 0.1.42 | 16 / 15 | |
| 0.1.41 | 16 / 15 | |
| 0.1.40 | 16 / 15 | |
| 0.1.39 | 16 / 15 | |
| 0.1.38 | 16 / 15 | |
| 0.1.37 | 16 / 15 | |
| 0.1.36 | 16 / 15 | |
| 0.1.35 | 16 / 15 | |
| 0.1.34 | 16 / 15 | |
| 0.1.33 | 16 / 15 | |
| 0.1.32 | 16 / 15 | |
| 0.1.31 | 16 / 15 | |
| 0.1.30 | 16 / 15 | |
| 0.1.29 | 16 / 15 | |
| 0.1.28 | 16 / 15 | |
| 0.1.27 | 16 / 15 | |
| 0.1.26 | 16 / 15 | |
| 0.1.25 | 16 / 15 | |
| 0.1.24 | 16 / 15 | |
| 0.1.23 | 16 / 15 | |
| 0.1.22 | 16 / 15 | |
| 0.1.21 | 16 / 15 | |
| 0.1.20 | 16 / 15 | |
| 0.1.19 | 16 / 15 | |
| 0.1.18 | 16 / 15 | |
| 0.1.17 | 16 / 15 | |
| 0.1.16 | 16 / 15 | |
| 0.1.15 | 16 / 15 | |
| 0.1.14 | 16 / 15 | |
| 0.1.13 | 16 / 15 | |
| 0.1.12 | 16 / 15 | |
| 0.1.11 | 16 / 15 | |
| 0.1.10 | 16 / 15 | |
| 0.1.9 | 16 / 15 | |
| 0.1.8 | 16 / 15 | |
| 0.1.7 | 16 / 15 | |
| 0.1.6 | 16 / 15 | |
| 0.1.4 | 16 / 15 | |
| 0.1.3 | 16 / 15 | |
| 0.1.2 | 16 / 15 | |
| 0.1.1 | 16 / 15 |
v0.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (geethanjali.s) than the most recent previously approved version (devops-orbi) on 2026-07-21, but geethanjali.s is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.100
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (devops-orbi) than the most recent previously approved version (geethanjali.s) on 2026-07-21, but devops-orbi is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.89
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (devops-orbi) than the most recent previously approved version (geethanjali.s) on 2026-07-03, but devops-orbi is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.47
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (devops-orbi) than the most recent previously approved version (geethanjali.s) on 2026-05-15, but devops-orbi is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (geethanjali.s) than the most recent previously approved version (devops-orbi) on 2026-03-27, but geethanjali.s is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.