botframework-directlinespeech-sdk
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-directlinespeech-sdk.js | AI (source-diff): Standard minified/bundled output from tsup/webpack; logic is readable in sample, no obfuscation. | ai | |
| source-diff | encoded-string-file:dist/botframework-directlinespeech-sdk.mjs | AI (source-diff): Encoded string is EMPTY_MP3_BASE64 audio stub in ESM bundle; benign. | ai | |
| source-diff | encoded-string-file:dist/botframework-directlinespeech-sdk.d.mts | AI (source-diff): Encoded string is EMPTY_MP3_BASE64 audio stub in type declaration file; benign. | ai | |
| source-diff | encoded-string-file:lib/playWhiteNoise.js | AI (source-diff): EMPTY_MP3_BASE64 is a known silent MP3 stub for white-noise playback; not a malicious payload. | ai | |
| source-diff | encoded-string-file:src/playWhiteNoise.js | AI (source-diff): Same EMPTY_MP3_BASE64 constant in source file; benign audio stub. | ai | |
| source-diff | encoded-string-file:dist/directlinespeech.development.js | AI (source-diff): Encoded string is EMPTY_MP3_BASE64 audio stub bundled into webpack output; benign. | ai | |
| source-diff | encoded-string-file:dist/directlinespeech.production.min.js | AI (source-diff): Encoded strings are base64 alphabet table and EMPTY_MP3_BASE64 audio stub; benign build artifacts. | ai | |
| phantom-deps | phantom-dep:abort-controller | AI (phantom-deps): abort-controller is a declared runtime dep used as a polyfill shim alongside abort-controller-es5; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:p-defer | AI (phantom-deps): p-defer is a declared runtime dep; phantom-dep heuristic fires because it's re-exported via p-defer-es5 wrapper, not a real missing import. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 4.19.1 | 10 / 26 | |
| 4.19.0 | 10 / 26 | |
| 4.18.2 | 12 / 27 | |
| 4.18.1 | 12 / 27 |
v4.19.1
9 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Modified file contains 1 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 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 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.
This version was published by a different npm account (microsoft1es) than the most recent previously approved version (compulim) on 2026-06-10, 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.19.0
9 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Modified file contains 1 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 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 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.
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.