botframework-webchat-core
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/botframework-webchat-core.js | AI (source-diff): Standard tsup/esbuild minified bundle output for this Microsoft package; not obfuscation. | ai | |
| source-diff | net-exec-file:dist/botframework-webchat-core.js | AI (source-diff): Minified bundle with require() calls; no actual network+exec dropper pattern in sampled code. | ai | |
| source-diff | net-exec-file:dist/chunk-RUERYYZO.js | AI (source-diff): Legitimate bundled chunk with valibot/uuid/iter-fest imports; no dropper behavior. | ai | |
| source-diff | net-exec-file:dist/chunk-ICNZKQJW.mjs | AI (source-diff): ESM chunk with valibot schema validation; standard build artifact. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is a declared runtime dep used by Babel transform output; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:p-defer | AI (phantom-deps): p-defer is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 4.19.0 | 12 / 20 | |
| 4.18.2 | 11 / 14 | |
| 4.18.1 | 11 / 14 | |
| 4.17.1 | 11 / 14 |
v4.19.0
6 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.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
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.
This version was published by a different npm account (microsoft1es) than the most recent previously approved version (compulim) on 2026-05-25, but microsoft1es is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.