Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

mxc

mxc: A sandboxed code execution system for running untrusted code behind a unified containment model and typed SDKs.

What problem it solves

Applications need to run untrusted code while controlling its access to files, networks, user interfaces, and host capabilities. This requires an isolation approach that works across platforms, supports multiple containment mechanisms, and can be integrated without changing application architecture.

Key features

  • Cross-platform containment — MXC supports Windows, Linux, and macOS with platform-appropriate containment backends.

    Source: README, docs

  • Policy-driven sandboxing — Versioned requests and security policies define filesystem, network, and UI access for contained workloads.

    Source: README, schemas

  • Multiple containment backends — Applications can select from process sandboxes, full virtual machines, and other platform-specific isolation mechanisms through a common model.

    Source: README, src

  • SDK and lifecycle support — Typed Rust, .NET, and Node SDKs support create-and-run execution and persistent container lifecycle operations.

    Source: README, sdk

  • Access diagnostics — Diagnostic modes and tools help identify access-denied failures and support policy authoring.

    Source: README, docs

Quick start

Copied verbatim from the project's README.

import { spawn, type ContainerRequest } from '@microsoft/mxc-sdk/v1';

const request: ContainerRequest = {
  command: 'node -e "console.log(\'hello from container\')"',
  network: { egress: { default: 'deny' } },
  timeoutMs: 30_000,
};

const child = await spawn(request);

Who it may suit

This project may suit application teams that need to execute model output, plugins, tools, or other untrusted workloads within configurable isolation. It may also suit developers integrating containment through Rust, .NET, or Node SDKs.

Topics to discuss

  • Which containment backend should be the default for each supported platform?

  • How can policy authoring workflows better expose the minimum capabilities required by a workload?

  • What should community projects cover first in runnable Rust, .NET, and Node examples?


Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/microsoft/mxc#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.

github.comhttps://github.com/microsoft/mxc

Comments

…