Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for advanced teams that want agent safety controls to live below prompts and MCP gateways, where subprocesses, file opens, and network connects still have to pass through the kernel.
Who should use it
Who should skip it
Pass on eunomia-bpf/ActPlane if your environment cannot support the access controls and sandboxing this risk profile requires.
About this signal
eunomia-bpf/ActPlane is tracked by RepoRadar as a infrastructure tool in the Agent Security / Runtime section. It was first seen on 2026-06-30 and last updated on 2026-06-30. The current verdict is 'try now' with a Gold tier and hard setup difficulty. Across RepoRadar's eight signals, eunomia-bpf/ActPlane is strongest on workflow potential (9.5) and novelty (9.0) and weakest on setup ease (4.2) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned eunomia-bpf/ActPlane a composite score of 8.0 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'medium' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
It loads kernel-level eBPF enforcement and usually needs root or elevated Linux capabilities, so first evaluation belongs on a disposable host rather than a primary workstation; Whether a rule can block before an action commits depends on your kernel and BPF-LSM support, so verify the enforcement mode before treating it as hard prevention.