How popular is litebox on GitHub?

microsoft/litebox has 2,701 stars and 147 forks on GitHub, and gained 7 stars in the last 7 days.

What license does litebox use?

microsoft/litebox is released under the MIT license.

microsoft/liteboxPublic

A security-focused library OS supporting kernel- and user-mode execution

AI summary: A security-focused sandboxing library OS designed to drastically reduce host attack surface.

Star on GitHub

Stars: 2.7K; +2 today
Forks: 147
Watchers: 26
Open issues: 129
Open PRs: 30
Contributors: ~19
Commits: 767
Branches: 308

RustMITCreated Dec 11, 2024Last push 1d ago+7 stars this week+15 this month

Quick answers

What is litebox?: A security-focused sandboxing library OS designed to drastically reduce host attack surface.
What does litebox do?: LiteBox is an advanced sandboxing library operating system that minimizes the interface to the host, thereby significantly reducing the potential attack surface. It is designed for secure execution in both kernel-mode and non-kernel user-mode environments. The system's architecture focuses heavily on the seamless interoperability between 'North' shims and 'South' platforms, exposing a Rust-inspired, nix-like interface to applications. This highly flexible design allows for incredibly diverse use cases, such as running unmodified Linux binaries on Windows hosts or strictly sandboxing applications on Linux within confidential computing environments.
Who is litebox for?: LiteBox is built for systems engineers, security researchers, and developers working on sandboxing, confidential computing, and cross-platform execution. It requires a strong understanding of operating system internals and rust-based system interfaces.
How do I get started with litebox?: Please refer to the CONTRIBUTING.md file in the repository for detailed setup instructions.
How popular is litebox on GitHub?: microsoft/litebox has 2,701 stars and 147 forks on GitHub, and gained 7 stars in the last 7 days.
What license does litebox use?: microsoft/litebox is released under the MIT license.

Star history

since Jul 29, 2026

2.7K stars as of Oct 2, 2026. Measured daily since Jul 29, 2026; GitHub no longer exposes earlier star timestamps.

Contribution activity

commits per day, last 52 weeks

404 commits in the last yearLessMore

Signals and awards

derived from tracked data

Actively maintained
Pushed within 48 hours
Permissive license
MIT
Continuous integration
Automated checks passing

What litebox does

LiteBox is an advanced sandboxing library operating system that minimizes the interface to the host, thereby significantly reducing the potential attack surface. It is designed for secure execution in both kernel-mode and non-kernel user-mode environments. The system's architecture focuses heavily on the seamless interoperability between 'North' shims and 'South' platforms, exposing a Rust-inspired, nix-like interface to applications. This highly flexible design allows for incredibly diverse use cases, such as running unmodified Linux binaries on Windows hosts or strictly sandboxing applications on Linux within confidential computing environments.

LiteBox is built for systems engineers, security researchers, and developers working on sandboxing, confidential computing, and cross-platform execution. It requires a strong understanding of operating system internals and rust-based system interfaces.

Reduced attack surface: Drastically cuts down the exposed interface to the host operating system to improve overall security posture.
Flexible execution modes: Built from the ground up to support deployment in both kernel-mode and non-kernel user-mode scenarios.
Cross-platform interoperability: Facilitates seamless connections between 'North' application shims and 'South' execution platforms.
Rust-inspired interface: Exposes a modern, safe interface inspired by nix and rustix for robust application interaction.
Confidential computing support: Enables running programs securely on top of trusted execution environments like AMD SEV-SNP or OP-TEE.

Where teams use it

Cross-platform execution

Developers utilize the library OS to safely run unmodified Linux applications directly on a Windows host environment.

Strict application sandboxing

Security engineers strictly isolate untrusted Linux applications within a highly restricted Linux environment to prevent exploitation.

Confidential computing

Enterprises run highly sensitive workloads securely on hardware-backed environments like AMD SEV-SNP using the LiteBox abstraction.

Trusted execution environments

Systems developers execute specialized OP-TEE programs securely on standard Linux distributions without exposing host interfaces.

Getting started: Please refer to the CONTRIBUTING.md file in the repository for detailed setup instructions.

README

main branch

LiteBox

A security-focused library OS

Note

This project is currently actively evolving and improving. While we are working toward a stable release, some APIs and interfaces may change as the design continues to mature. You are welcome to explore and experiment, but if you need long-term stability, it may be best to wait for a stable release, or be prepared to adapt to updates along the way.

LiteBox is a sandboxing library OS that drastically cuts down the interface to the host, thereby reducing attack surface. It focuses on easy interop of various "North" shims and "South" platforms. LiteBox is designed for usage in both kernel and non-kernel scenarios.

LiteBox exposes a Rust-y nix/rustix-inspired "North" interface when it is provided a Platform interface at its "South". These interfaces allow for a wide variety of use-cases, easily allowing for connection between any of the North--South pairs.

Example use cases include:

Running unmodified Linux programs on Windows
Sandboxing Linux applications on Linux
Run programs on top of SEV SNP
Running OP-TEE programs on Linux
Running on LVBS

Contributing

See the following files for details:

License

MIT License. See ./LICENSE for details.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

View on GitHub

Recent activity

commits and pull requests

LVBS: Fix kernel extended states leakOpen
#1451 by sangho2 · updated 4d ago
[DO NOT MERGE] test commitOpen
#1344 by praveen-pk · updated 4d ago
Skip enabling SControl MSR if it is already enabled.Open
#1428 by athvu · updated 5d ago
Verify TAsOpen
#1399 by athvu · updated 5d ago
Dynamic TA SupportOpen
#1213 by praveen-pk · updated 5d ago
Fix Windows reserve-only page allocationsClosed
#1253 by CvvT · updated 5d ago
Route stdio only through the fs Devices backendOpen
#1450 by wdcui · updated 5d ago
Restart interrupted syscalls per SA_RESTARTMerged
#1442 by wdcui · updated 5d ago
Keep epoll interest alive while a duplicate of the registered fd survives (#1230)
willportnoy committed a17dfd4 · 5d ago
Relocate virtual memory management to Linux-specific layers (#1439)
CvvT committed a0736b7 · 5d ago
LVBS: Enable safe TA page table teardown (#1351)
sangho2 committed ee38609 · 6d ago
Add IDK_S PTA (#1026)
sangho2 committed dfea68d · 6d ago

Recent open issues

view all

epoll: interests are not removed when their target is closed
#1443 · 5d ago · by wdcui · 2 comments
Inherit network sockets, eventfd, epoll and Unix sockets across vfork+execve
#1438 · 6d ago · by wdcui
Move stdio, pipe and directory per-open state into the broker
#1437 · 6d ago · by wdcui · 2 comments
windows platform: let a fixed Replace take over committed pages again
#1422 · 8d ago · by dywongcloud
Fix clippy 1.98 and rustdoc failures found by CI
#1421 · 8d ago · by dywongcloud
Flaky static exec integration test closes broker association during teardown
#1412 · 10d ago · by wdcui

Discussions

all 1

C#/.NET compatible North API?
Ideas · 6mo ago · 1 comments

Code frequency

additions and deletions

+120.1K lines added, -61.6K removed over the last year.

Commits per week

last 52 weeks

404 commits in the last 52 weeks.

When work happens

weekday and hour

Commit volume by weekday and hour (UTC). Larger dots mean more commits.

Date	List	Rank	Stars gained
Feb 7, 2026	daily	#23	+155
Feb 6, 2026	daily	#20	+173

ultraworkers/claw-code
An agent-managed museum exhibit, built in Rust with Gajae-Code / LazyCodex — developed and maintained with no human intervention.
195.2K stars · Rust
farion1231/cc-switch
A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Grok Build & Hermes Agent. Only official website: ccswitch.io
140K stars · Rust
openai/codex
Lightweight coding agent that runs in your terminal
127.8K stars · Rust
denoland/deno
A modern runtime for JavaScript and TypeScript.
108.6K stars · Rust
ruvnet/RuView
π RuView turns commodity WiFi signals into real-time spatial intelligence, vital sign monitoring, and presence detection — all without a single pixel of video.
96.4K stars · Rust
oven-sh/bun
Incredibly fast JavaScript runtime, bundler, test runner, and package manager – all in one
96.1K stars · Rust