@platforma-open/milaboratories.mixcr-scfv-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 | obfuscated-file:dist/assets/index-BWMma7mu.js | AI (source-diff): Vite-minified frontend bundle; standard output for this UI package pattern. | ai | |
| source-diff | net-exec-file:dist/assets/index-BWMma7mu.js | AI (source-diff): Network calls are fetch() for modulepreload in a browser UI bundle; not dropper behavior. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped UI package in platforma-open org; missing metadata is expected for org-internal packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across this org's packages; not indicative of malice. | ai | |
| phantom-deps | phantom-dep:ag-grid-vue3 | AI (phantom-deps): Config-referenced build dependency; stable pattern for Vue UI component packages. | ai | |
| phantom-deps | phantom-dep:ag-grid-enterprise | AI (phantom-deps): Config-referenced build dependency; stable pattern for Vue UI component packages. | ai | |
| phantom-deps | phantom-dep:@zip.js/zip.js | AI (phantom-deps): Config-referenced build dependency; stable pattern for Vue UI component packages. | ai | |
| phantom-deps | phantom-dep:@milaboratories/helpers | AI (phantom-deps): Config-referenced build dependency; stable pattern for Vue UI component packages. | ai |
v2.8.2
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.
v2.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.