botframework-webchat
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 | net-exec-file:dist/chunk-2KEOFGLH.mjs | AI (source-diff): Standard ESM build chunk from Microsoft's BotFramework-WebChat monorepo; contains Babel helpers and React code, not malware. | ai | |
| source-diff | encoded-string-file:dist/webchat-es5.js | AI (source-diff): Standard webpack minified bundle; long strings are minified JS identifiers/license text, not encoded payloads. | ai | |
| source-diff | encoded-string-file:dist/webchat-minimal.js | AI (source-diff): Standard webpack minified bundle; same pattern as webchat-es5.js. | ai | |
| source-diff | encoded-string-file:dist/webchat.js | AI (source-diff): Standard webpack minified bundle; same pattern as webchat-es5.js. | ai | |
| phantom-deps | phantom-dep:memoize-one | AI (phantom-deps): Declared runtime dep in large monorepo bundle; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:markdown-it-attrs | AI (phantom-deps): Declared runtime dep; used transitively in markdown rendering pipeline. | ai | |
| phantom-deps | phantom-dep:swiper | AI (phantom-deps): swiper is pinned in package.json as a workaround for [email protected] missing dep; not a phantom risk. | ai |
v4.18.2
5 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Modified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.