@platforma-open/milaboratories.miltenyi-tcr-clonotyping.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 |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/assets/index-B554HUMl.js | AI (source-diff): Network calls are browser fetch() for modulepreload; dynamic code is Vue reactivity — normal UI bundle behavior. | ai | |
| source-diff | obfuscated-file:dist/assets/index-B554HUMl.js | AI (source-diff): Standard Vite-minified Vue 3 bundle; long lines are expected minification output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/assets/index-CL3xOuNC.js | AI (source-diff): Standard Vite-minified Vue 3 bundle; minification is expected for this UI package. | ai | |
| source-diff | net-exec-file:dist/assets/index-CL3xOuNC.js | AI (source-diff): Network calls are browser fetch() for modulepreload; dynamic code is Vue reactivity runtime — no dropper behavior. | ai | |
| source-diff | obfuscated-file:dist/assets/index-BKgSlu8X.js | AI (source-diff): Standard Vite minified bundle; long lines are expected minification output, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/assets/index-BKgSlu8X.js | AI (source-diff): Network calls are fetch() for modulepreload; dynamic code is Vue reactivity — normal Vite/Vue bundle pattern. | ai | |
| phantom-deps | phantom-dep:@vueuse/core | AI (phantom-deps): UI bundle package; deps declared for bundler/peer resolution, not direct imports. | ai | |
| phantom-deps | phantom-dep:ag-grid-enterprise | AI (phantom-deps): UI bundle package; deps declared for bundler/peer resolution, not direct imports. | ai | |
| phantom-deps | phantom-dep:utility-types | AI (phantom-deps): UI bundle package; deps declared for bundler/peer resolution, not direct imports. | ai | |
| phantom-deps | phantom-dep:ag-grid-vue3 | AI (phantom-deps): UI bundle package; deps declared for bundler/peer resolution, not direct imports. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): UI bundle package; deps declared for bundler/peer resolution, not direct imports. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.4.6 | 10 / 8 | |
| 1.4.5 | 10 / 8 | |
| 1.4.4 | 10 / 8 | |
| 1.4.3 | 10 / 8 | |
| 1.4.2 | 10 / 8 | |
| 1.4.1 | 10 / 8 | |
| 1.4.0 | 10 / 8 |
v1.4.6
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.