← Home

@microsoft/mxc-sdk

npm

TypeScript SDK for MXC (Microsoft eXecution Containers)

8
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

microsoft1esmicrosoft-oss-releases

Keywords

wxcsandboxsecurityprocesscontainerwindowsnode-pty

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata bundled-binaries AI (npm-metadata): Native container/sandbox execution binaries are core to this SDK's purpose; consistent with Microsoft publisher track record. ai

Versions (showing 8 of 8)

Version Deps Published
0.6.1 2 / 5
0.6.0 2 / 5
0.3.0 2 / 5
0.2.1 2 / 5
0.2.0 2 / 4
0.1.8 2 / 4
0.1.7 2 / 4
0.1.6 2 / 4

v0.6.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.6

2 findings
HIGH Bundled binary files (14) npm-metadata

Package contains compiled binaries that could be backdoors: • bin/arm64/lxc-exec • bin/x64/lxc-exec • bin/arm64/wslcsdk.dll • bin/x64/wslcsdk.dll • bin/arm64/winhttp-proxy-shim.exe • bin/x64/winhttp-proxy-shim.exe • bin/arm64/wxc-exec.exe • bin/x64/wxc-exec.exe • bin/arm64/wxc-test-proxy.exe • bin/x64/wxc-test-proxy.exe ... and 4 more

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.