@botfabrik/engine-webclient
Webclient for Botfabriks Bot Engine
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is explicitly declared in package.json dependencies; phantom-dep heuristic fires incorrectly here. | ai | |
| source-diff | net-exec-file:dist/client/assets/index-kLumE_Is.js | AI (source-diff): Network calls (fetch for modulepreload) and dynamic module loading are standard in bundled SPA code; not dropper behavior. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-kLumE_Is.js | AI (source-diff): Vite-bundled frontend asset; minification is expected for this webclient package across all versions. | ai | |
| dependencies | unvetted-dep:@botfabrik/engine-transcript-export | AI (dependencies): Internal sibling package from the same @botfabrik org; versioned in lockstep with this package. | ai | |
| dependencies | unvetted-dep:@botfabrik/engine-utils | AI (dependencies): Internal sibling package from the same @botfabrik org; versioned in lockstep with this package. | ai | |
| dependencies | unvetted-dep:@botfabrik/engine-domain | AI (dependencies): Internal sibling package from the same @botfabrik org; versioned in lockstep with this package. | ai | |
| provenance | no-provenance | AI (provenance): Long-established package with 535 versions; lack of provenance is consistent across all prior releases. | ai | |
| phantom-deps | phantom-dep:@types/cors | AI (phantom-deps): @types/cors is a TypeScript type package; not imported at runtime by convention. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 4.117.2 | 13 / 8 | |
| 4.116.11 | 13 / 8 | |
| 4.116.10 | 13 / 8 | |
| 4.116.8 | 13 / 8 | |
| 4.116.7 | 13 / 8 | |
| 4.116.5 | 13 / 8 | |
| 4.116.3 | 13 / 8 | |
| 4.116.2 | 13 / 8 | |
| 4.116.1 | 13 / 8 | |
| 4.116.0 | 13 / 8 | |
| 4.115.18 | 13 / 8 | |
| 4.115.16 | 13 / 8 | |
| 4.115.11 | 13 / 8 | |
| 4.115.9 | 13 / 8 | |
| 4.115.8 | 13 / 8 | |
| 4.115.7 | 13 / 8 | |
| 4.115.5 | 13 / 8 | |
| 4.106.0 | 9 / 7 | |
| 4.105.0 | 9 / 7 | |
| 4.104.23 | 9 / 7 | |
| 4.104.19 | 9 / 7 | |
| 4.103.3 | 10 / 8 | |
| 4.102.0 | 10 / 10 | |
| 4.101.2 | 10 / 10 | |
| 4.101.0 | 10 / 10 | |
| 4.89.0 | 7 / 9 | |
| 4.86.1 | 9 / 8 |
v4.117.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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.116.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.116.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.116.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.116.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.116.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.116.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.116.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.116.0
4 findingsThis version was published by a different npm account than previous versions on 2026-04-14. This could indicate a legitimate maintainer transition or an account compromise.
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.115.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.115.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.115.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.115.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.115.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.115.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.115.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.106.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.105.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.104.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.104.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.103.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.102.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.101.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.101.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.89.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.86.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.