microsoft/litebox

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

Owned by Microsoft

View on GitHub ↗Jump to charts ↓Open shareable report →

microsoft/litebox has 3k+ stars and 150+ forks on GitHub, is written in Rust, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on October 11th, 2026
Created on December 11th, 2024
Open Issues & Pull Requests: 154 (+0)
GitHub issues: Enabled
Number of forks: 176
Total Stargazers: 3,168 (+2)
Total Subscribers: 30 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.2 hours
Mean response time: 13.7 days
90th percentile: 35.1 days
Tracked items: 170

Maintainer activity

4 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Roughly one issue in three opened in the past year never receives a reply. 50% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "bug" is answered fastest, typically in under an hour, while "priority-low" waits about 3 days. 61% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 37% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 128
New in 7 days: 2
Closed in 7 days: 3
Avg open age: 249 days
Stale 30+ days: 102
Stale 90+ days: 79

Recent activity

Opened in 7 days: 1
Closed in 7 days: 3
Comments in 7 days: 6
Events in 7 days: 16

Top labels

  • enhancement (76)
  • layer-litebox (36)
  • target-lvbs (36)
  • discussion (26)
  • bug (20)
  • priority-low (20)
  • layer-platform (17)
  • layer-shim (13)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Litebox is a security-focused library operating system that supports both kernel-mode and user-mode execution.

The project addresses the need for a computing environment where security properties can be enforced at the OS level while maintaining flexibility in execution contexts. Litebox implements a library OS architecture, meaning applications link against it directly rather than relying on a traditional separate kernel. This approach allows the security model to be tightly integrated with application code, reducing the attack surface by eliminating certain classes of kernel-userspace boundary vulnerabilities. The dual support for kernel-mode and user-mode execution means developers can choose the execution context that best fits their security and performance requirements.

Litebox suits projects where security guarantees are a primary concern and where the overhead of traditional OS abstractions is acceptable. Teams building systems that need strong isolation properties, verified security properties, or protection against specific kernel-level attacks should evaluate it. The library OS model means applications must be explicitly built or adapted to use Litebox rather than running unmodified binaries, so it is most appropriate for new projects or those undergoing significant refactoring rather than as a drop-in replacement for existing systems.

The project is written in Rust, which provides memory safety guarantees that complement the security-focused design. Development activity shows consistent engagement with the codebase through regular commits and active maintenance of the core implementation. The project maintains documentation and examples that support understanding its architecture and integration patterns. Issue tracking and pull request activity indicate ongoing refinement of the library OS implementation and responsiveness to technical concerns raised by users.