microsoft-cognitiveservices-speech-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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file-transition:distrib/browser/microsoft.cognitiveservices.speech.sdk.bundle-min.js | AI (source-diff): Webpack bundle boilerplate in official MS SDK; no malicious behavior. | ai | |
| source-diff | net-exec-file-transition:distrib/browser/microsoft.cognitiveservices.speech.sdk.bundle.js | AI (source-diff): Webpack bundle boilerplate in official MS SDK; no malicious behavior. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Bundled minified dependency code (buffer polyfill), not attacker-controlled eval. | ai | |
| phantom-deps | phantom-dep:@types/webrtc | AI (phantom-deps): @types/webrtc is a TypeScript type definition package loaded by convention, not direct import. This is expected behavior for all @types/* packages and is stable across versions. | ai | |
| dependencies | unvetted-dep:@types/webrtc | AI (dependencies): @types/webrtc is a DefinitelyTyped package providing WebRTC type definitions. Entirely benign and appropriate for a browser-targeting speech SDK. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 1.51.0 | 7 / 35 | |
| 1.50.0 | 7 / 36 | |
| 1.49.0 | 7 / 36 | |
| 1.48.0 | 7 / 36 | |
| 1.47.0 | 6 / 36 | |
| 1.46.0 | 6 / 36 | |
| 1.45.0 | 6 / 36 | |
| 1.44.1 | 6 / 36 | |
| 1.44.0 | 6 / 36 | |
| 1.43.1 | 6 / 33 | |
| 1.43.0 | 6 / 33 | |
| 1.42.0 | 6 / 33 | |
| 1.41.0 | 6 / 33 | |
| 1.40.0 | 7 / 33 | |
| 1.38.0 | 6 / 33 | |
| 1.33.0 | 6 / 33 | |
| 1.32.0 | 5 / 33 | |
| 1.31.0 | 5 / 33 | |
| 1.30.2 | 5 / 33 | |
| 1.30.1 | 5 / 33 | |
| 1.30.0 | 5 / 33 | |
| 1.29.0 | 5 / 33 | |
| 1.28.0 | 5 / 33 | |
| 1.27.0 | 9 / 34 | |
| 1.26.0 | 9 / 34 | |
| 1.25.1 | 9 / 35 | |
| 1.25.0 | 9 / 35 | |
| 1.18.1 | 10 / 27 | |
| 1.18.0 | 10 / 26 | |
| 1.17.0 | 10 / 26 | |
| 1.16.0 | 10 / 26 | |
| 1.15.1 | 9 / 25 | |
| 1.15.0 | 9 / 25 | |
| 1.14.1 | 9 / 25 | |
| 1.14.0 | 9 / 25 | |
| 1.13.1 | 8 / 24 | |
| 1.13.0 | 8 / 24 | |
| 1.7.0 | 5 / 20 | |
| 1.6.0 | 5 / 20 | |
| 1.4.0 | 2 / 21 | |
| 1.3.0 | 2 / 19 | |
| 1.2.1 | 2 / 18 | |
| 1.2.0 | 2 / 16 |
v1.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.43.1
2 findingsPackage 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 (brianmouncer) on 2025-04-04, 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.
v1.43.0
2 findingsPackage 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 (rhurey) on 2025-03-20, 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.
v1.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rhurey) than the most recent previously approved version (brianmouncer) on 2024-10-16, but rhurey 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.
v1.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.0
3 findingsThis file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
This file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
4 findingsThis file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
This file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
This version was published by a different npm account (brianmouncer) than the most recent previously approved version (mahilleb-msft) on 2019-09-25. It has since remained available on npm for 2491 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
4 findingsThis file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
This file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
This version was published by a different npm account (brianmouncer) than the most recent previously approved version (mahilleb-msft) on 2019-06-27. It has since remained available on npm for 2581 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
3 findingsThis file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
This file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.