For a capability based security model for systems, the strongest matches are ponylang/ponyc (Pony is a programming language that uses a compile-time), webassembly/wasi (WASI implements a capability-based security model where WebAssembly modules) and sel4/sel4 (seL4 is a formally verified microkernel built around a). lunatic-solutions/lunatic and tauri-apps/tauri round out the shortlist. Each is ranked by relevance to your query, popularity and recent activity.
We curate open-source GitHub repositories matching “capability based security models”. Results are ranked by relevance to your query — pick filters below to narrow, or refine with AI.
Pony is an open-source, actor-model, capabilities-secure, high performance programming language
Pony is a programming language that uses a compile-time object-capability model to enforce safe concurrency, directly implementing capability-based security for secure programming, but it is a language rather than a dedicated framework, kernel, or access control library.
The WebAssembly System Interface is a standardized set of APIs that allow WebAssembly modules to interact with operating systems in a portable and platform-independent manner. It provides a portable runtime abstraction that separates high-level system calls from low-level host implementations to ensure compatibility across different operating systems. The project utilizes a component-based module system to link independent binary modules through shared interfaces, removing the requirement for a single monolithic binary. It employs a cross-language interface definition to provide a portable ty
WASI implements a capability-based security model where WebAssembly modules receive explicit, unforgeable capabilities for system resource access, directly matching the search for a capability-focused framework.
seL4 is a formally verified microkernel whose C implementation is backed by machine-checked mathematical proofs of correctness, confidentiality, integrity, and availability. It enforces strict isolation between processes through hardware-enforced address space separation and a capability-based access control system, where each process holds explicit rights only to the resources it has been granted. The kernel exposes hardware resources through a minimal API of system calls that manage threads, address spaces, and inter-process communication, with synchronous IPC supporting sender-identifying b
seL4 is a formally verified microkernel built around a capability-based access control system, making it a flagship example of a capability-based security framework with formal verification and strict isolation.
Lunatic is a WebAssembly runtime and concurrent process manager that implements an Erlang-inspired model of lightweight concurrency and fault tolerance. It functions as a distributed actor system where isolated processes communicate via message passing across a network of linked nodes. The system utilizes a WebAssembly sandbox environment to isolate memory and restrict system call permissions for each individual process. This capability-based security model ensures that processes are sandboxed to safely execute untrusted code. The platform provides a fault-tolerant supervision tree for hiera
Lunatic is a WebAssembly runtime and actor system that enforces a capability-based security model through sandboxed processes and access controls, directly addressing the interest in capability-based security implementations, though it focuses on process isolation rather than being a general-purpose security framework for operating systems.
Tauri is a cross-platform framework for building desktop applications that combine web-based user interfaces with a memory-safe systems-language backend. It functions as a secure runtime that hosts web content within native windowing containers, allowing developers to leverage existing web technologies while maintaining high-performance native logic. By compiling applications into small-footprint, platform-specific binaries, the framework avoids bundling heavy runtime environments, resulting in lightweight executables. The project distinguishes itself through a capability-based security model
Tauri is an application framework that implements a capability-based security model for controlling access to system resources in desktop apps, fitting your interest in capability-based security tools for secure programming, though it focuses on app-level permissions rather than kernel or formal verification features.
Tock is a secure embedded operating system and microcontroller kernel designed to isolate untrusted applications and drivers. It functions as a memory-safe process isolator that uses a combination of hardware memory protection and language-level type safety to execute mutually distrustful applications on bare metal. The system distinguishes itself through a hardware abstraction layer that decouples high-level components from specific microcontroller implementations using standardized traits. It further employs a virtualization layer to allow multiple independent software components to share a
Tock is a secure embedded operating system kernel that uses capability-based access controls to isolate applications and drivers, directly implementing the capability-based security model for embedded systems — the right kind of tool, though narrower in scope (embedded-only) and not covering formal verification.
Sandstorm is an open-source platform that packages and runs web applications in security-hardened sandboxes on a personal server, functioning as a self-hosted web app operating system. It provides a curated app store where users discover and install sandboxed web applications with one-click ease, while each application runs in an isolated container that uses Linux kernel security features to separate it from the host and other apps. The platform includes a centralized authentication layer so users sign in once and gain access to all installed applications without managing separate accounts per
Sandstorm is a self-hosted platform that packages web apps in sandboxes using a capability-based security model (via Cap'n Proto and Powerbox), making it a practical demonstration of capability security for application isolation rather than a kernel or library, which fits the intent for a capability-based security framework.