@platforma-open/milaboratories.samples-and-data.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-BgfBnOu5.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-BgfBnOu5.js | AI (source-diff): Network calls and dynamic code are Vue/Vite runtime patterns (modulepreload, fetch); no dropper behavior present. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.9.2 | 0 / 20 | |
| 2.9.1 | 0 / 20 | |
| 2.9.0 | 0 / 20 | |
| 2.8.0 | 0 / 20 | |
| 2.7.0 | 0 / 20 |
v2.9.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.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
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.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.