@budibase/bbui
A UI solution used in the different Budibase projects.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/easymde-DaiYpPXu.mjs | AI (source-diff): Standard Vite bundle of EasyMDE; minified output is expected for this UI library's dist files. | ai | |
| source-diff | obfuscated-file:dist/index-BB1K0Rvt.mjs | AI (source-diff): Standard Vite/Svelte build output; samples show recognizable Svelte runtime code, not obfuscated malware. | ai | |
| source-diff | net-exec-file:dist/index-BB1K0Rvt.mjs | AI (source-diff): Network calls and dynamic code in a UI component library bundle are expected (fetch for data, dynamic component rendering); no dropper pattern visible in samples. | ai | |
| source-diff | obfuscated-file:dist/easymde-Dv4B3HQK.mjs | AI (source-diff): Standard Vite/Rollup minified bundle of EasyMDE; content-hashed filename is normal build output for this UI library. | ai | |
| source-diff | obfuscated-file:dist/index-DAI87kUe.mjs | AI (source-diff): Standard Vite/Rollup minified Svelte bundle; content-hashed filename is normal build output for this UI library. | ai | |
| source-diff | net-exec-file:dist/index-DAI87kUe.mjs | AI (source-diff): Svelte runtime legitimately uses dynamic patterns; no actual network fetch + exec payload visible in samples. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 3.37.5 | 48 / 2 | |
| 3.37.3 | 48 / 2 | |
| 3.37.2 | 48 / 2 | |
| 3.37.1 | 48 / 2 | |
| 3.36.4 | 48 / 2 | |
| 3.36.3 | 48 / 2 | |
| 3.36.2 | 48 / 2 | |
| 3.36.1 | 48 / 2 | |
| 3.35.10 | 48 / 2 | |
| 3.35.3 | 48 / 2 | |
| 3.35.1 | 48 / 2 | |
| 3.35.0 | 48 / 2 | |
| 3.27.5 | 52 / 2 | |
| 3.23.29 | 52 / 2 | |
| 3.23.26 | 52 / 2 | |
| 3.23.19 | 51 / 2 | |
| 3.23.12 | 51 / 2 | |
| 3.23.2 | 51 / 2 | |
| 3.23.1 | 51 / 2 | |
| 3.17.4 | 51 / 2 |
v3.37.5
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v3.37.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.2
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v3.35.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.