Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
vArmor is a cloud-native container hardening system that leverages AppArmor/BPF/Seccomp and NetworkProxy technologies to enforce access control from system calls to application protocols — protecting workloads including AI Agents.
| Date | Stars |
|---|---|
| 2026-07-31 | 489 |
| 2026-08-06 | 493 |
Today
+4 stars today
This week
— stars this week
This month
— stars this month
Momentum
31.0
growth rate 0.00%/day
<div>
<picture>
<source media="(prefers-color-scheme: light)" srcset="docs/img/logo.svg" width="400">
<img src="docs/img/logo-dark.svg" alt="Logo" width="400">
</picture>
</div>
<br />
[](https://goreportcard.com/report/github.com/bytedance/vArmor)
[](https://opensource.org/licenses/Apache-2.0)
[](https://opensource.org/license/gpl-2-0)
[](https://github.com/bytedance/vArmor/releases)
English | [简体中文](README.zh_CN.md) | [日本語](README.ja.md)
vArmor is a cloud-native container hardening system. It leverages Linux's [AppArmor LSM](https://en.wikipedia.org/wiki/AppArmor), [BPF LSM](https://docs.kernel.org/bpf/prog_lsm.html), [Seccomp](https://en.wikipedia.org/wiki/Seccomp), and **Network Proxy** ([Envoy](https://www.envoyproxy.io/)-based sidecar) technologies to implement enforcers. It can be used to strengthen container isolation, reduce the kernel attack surface, enforce network egress access control at L4/L7 levels — including TLS MITM for decrypted HTTPS inspection, HTTP header injection, and anti-Domain-Fronting protection — and increase the difficulty and cost of container escape or lateral movement attacks. You can leverage vArmor in the following scenarios to provide sandbox protection for containers within a Kubernetes cluster.
* In multi-tenant environments, hardware-virtualized container solutions cannot be employed due to factors such as cost and technical conditions.
* You want to enhance the security of critical business containers, making it more difficult for attackers to escalate privileges, escape, or laterally move.
* When high-risk vulnerabilities are present but immediate remediation is not possible due to the difficulty or lengthy process of patching, vArmor can be used to mitigate the risks (depending on the vulnerability type or exploitation vector) to block or increase the difficulty of exploitation.
* You are deploying AI Agents or LLM-based applications and need to precisely control their outbound network access — preventing data exfiltration, unauthorized API calls, or abuse induced by prompt injection attacks.
*Note:*
*<br />- The core of security defense lies in balancing risks and benefits, transforming uncontrollable risks into controllable costs by choosing different types of security boundaries and defense technologies.*
*<br />- runc + vArmor does not provide an isolation level equivalent to that of hardware virtualization containers (such as Kata Containers and other lightweight virtual machines). If you require a high-intensity isolation solution, please consider using hardware virtualization containers for compute isolation, and utilize CNI's NetworkPolicy for network isolation.*
*<br />- vArmor's NetworkProxy enforcer further complements NetworkPolicy by providing L7 access control for both HTTP and HTTPS (via TLS MITM), TLS SNI-based domain filtering, per-domain HTTP header injection, anti-Domain-Fronting protection, and comprehensive audit logging — capabilities that NetworkPolicy does not offer.*
**vArmor Features:**
* **Cloud-Native**. vArmor follows the Kubernetes Operator design pattern, allowing users to harden specific workloads by manipulating the [CRD API](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/). This approach enables sandboxing of containerized microservices from a perspective closely aligned with business needs.
* **Multiple Enforcers**. vArmor abstracts AppArmor, BPF, Seccomp, and NetworkProxy as enforcers, supporting their use individually or in combination. This enables enforcing access control on container file access, process execution, network outbound (L3–L7), syscExcerpt of 8,169 characters
Read on GitHubWould you bet a product on this? Bounded 0–100 and slow moving.
matched fp:3c54260207c6a85f, llm:Repository topics: ai-security, apparmor, apparmor-profiles, bpf, containers, hardening, kubernetes, lsm, policy, sandbox, seccomp, security. Description: cloud-native container hardening system leveraging AppArmor/BPF/Seccomp/NetworkProxy to enforce access control — protecting workloads including AI Agents.
matched fp:3c54260207c6a85f, llm:Repository topics: ai-security, apparmor, apparmor-profiles, bpf, containers, hardening, kubernetes, lsm, policy, sandbox, seccomp, security. Description: cloud-native container hardening system leveraging AppArmor/BPF/Seccomp/NetworkProxy to enforce access control — protecting workloads including AI Agents.