PAGES
← all tools
◆ Cloud Runtime Security

aya

aya-ebpf-macros-v0.4.0 open-source

Free plan: not checked yet · Open source: yes

Starting price: not checked yet

Aya is an eBPFeBPFA Linux technology for running verified programs inside the kernel without changing its source. Tools use it to observe processes, enforce rules and process network traffic. library for the Rust programming language, built with a focus on developer experience and operability.

What you can do now

Checking Plays…

Summary

aya is an open-source MIT/Apache-2.0 Rust library for building, loading, and operating eBPF programs in the Linux kernel, aimed at developers building runtime-security and observability software rather than end users running a SaaSSaaSSoftware delivered over the internet and billed by subscription, hosted and operated by the vendor so the buyer skips installation and infrastructure management.. It provides user-space loading and log consumption alongside kernel-space program and logging APIs, and can produce self-contained binaries for deployment across Linux distributions and kernel versions when using BTFBTFBPF Type Format, a metadata format in the Linux kernel that embeds type and debug information directly into eBPF programs, letting cyber tools inspect kernel structures safely without kernel headers at runtime. and musl. The project has ongoing releases covering program types, architectures, attachment, logging, and runtime statistics.

Aya is an eBPF library for the Rust programming language, built with a focus on developer experience and operability.

How aya helps

Which programs can I load into the Linux kernels running my services?

loads eBPF programs from user space, exposes their program and map information, and reports whether the target kernel supports the requested program and map types; portability depends on the kernel features and BTF available

Where can my eBPF programs attach to observe or enforce activity?

supports multiple attachment mechanisms and program types, including tracing, probes, network hooks, flow dissection, iterators, and hardware breakpoints, and reports attachment or netlink errors when the kernel rejects an operation

What is happening inside my running eBPF programs?

enables runtime statistics and exposes per-program execution counts and nanosecond totals, showing how often programs run and how much execution time they consume; these figures require runtime statistics to be enabled

What events are my kernel-space programs producing?

formats messages emitted from eBPF programs and lets user-space code consume those logs, including formatted IPv4 and IPv6 values; it reports only data the programs explicitly log

Can I inspect or reconnect to eBPF programs that are already attached?

re-attaches to previously created programs, including pinned programs and programs attached to network interfaces, and reads their logs without requiring the programs to be loaded in the current process

Will the same monitoring binary work across my Linux distributions and kernel versions?

builds a self-contained user-space binary when using BTF and musl, allowing deployment across distributions and kernel versions; compatibility still depends on the target kernels exposing the required eBPF capabilities and BTF information

all 26 features, with the evidence for each →

Languages

Not documented

Features

26 capabilities across 2 capability groups

Built from aya's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • aya covers 1 of the 3 runtime security capabilities we track.
  • aya covers 1 of the 11 endpoint investigation and controls capabilities we track.

eBPF-based runtime detection 9 features Runtime security since 2024
Cgroup and inode local storage map support Provides BPF map types for per-cgroup and per-inode local storage, including CgrpStorage (BPF_MAP_TYPE_CGRP_STORAGE, Linux 6.2+), InodeStorage (BPF_MAP_TYPE_INODE_STORAGE), CgroupStorage (deprecated per-CPU and non-per-CPU variants), allowing eBPF programs and userspace to read and write values scoped to individual cgroups or inodes. 41 other sources

Shared capability: eBPF-based runtime detection

eBPF program log formatting Provides format-string logging from eBPF programs with typed display hints for IP addresses, MAC addresses, hex numbers, pointers, and byte slices, including compile-time validation of format strings and value types. 18 releases · 2 other sources · first seen Feb 2024

Shared capability: eBPF-based runtime detection

Standalone eBPF program loading Provides a Rust library for building and loading eBPF programs into the Linux kernel without requiring libbpf or a C toolchain. 1 release · 17 other sources · first seen Oct 2026

Shared capability: eBPF-based runtime detection

Naming and API surface consistency Renames top-level types from `Bpf`/`BpfLoader`/`BpfLogger` to `Ebpf`/`EbpfLoader`/`EbpfLogger` and related identifiers, retaining deprecated aliases for backward compatibility. 8 releases · first seen Oct 2024

Shared capability: eBPF-based runtime detection

eBPF instruction bindings codegen Generates bindings covering all eBPF instructions and additional userspace constants for use in Rust code. 3 releases · first seen Jun 2026

Shared capability: eBPF-based runtime detection

ksym-based program loading Supports loading eBPF programs that reference kernel symbols (ksyms). 1 release · first seen Oct 2026

Shared capability: eBPF-based runtime detection

TC context manipulation Provides methods on TcContext and SkBuff to set TC class IDs from within eBPF programs. 1 release · first seen Oct 2026

Shared capability: eBPF-based runtime detection

Built-in compiler helper functions Implements compiler built-ins such as memmove directly, preventing eBPF load failures when the compiler emits calls to symbols not otherwise available in the BPF environment. 1 release · first seen Oct 2024

Shared capability: eBPF-based runtime detection

eBPF runtime stats collection Exposes the BPF_ENABLE_STATS syscall to enable runtime statistics tracking for benchmarking eBPF programs. 1 release · first seen Oct 2024

Shared capability: eBPF-based runtime detection

Process telemetry 1 feature Endpoint investigation and controls since 2026
Process memory map parsing Parses complete entries from /proc/$pid/maps, including fields that were previously omitted. 1 release · first seen Jun 2026

Shared capability: Process telemetry

Other / not yet classified 16 features Features we have not matched to a capability yet. A suggested match is marked.
BPF map type support Supports a range of BPF map types, including LPM trie maps for longest-prefix-match lookups suited to IP routing and CIDR matching. 11 releases · 80 other sources · first seen Mar 2022
BPF map entry manipulation Provides methods to set and unset individual entries in BPF maps, including Array maps and AF_XDP socket maps. 3 releases · 23 other sources · first seen Jun 2026
BPF program lifecycle management Provides APIs to load, unload, and manage the lifetime of BPF programs and their links, including transferring link ownership to keep programs pinned after handles are dropped. 15 releases · 10 other sources · first seen Jun 2022
BPF program type support Supports loading and managing a wide range of BPF program types, including fentry/fexit, BPF_PROG_TYPE_EXT, SK_LOOKUP, CGROUP_SYSCTL, CGROUP_SOCK_ADDR, and CGROUP_SOCKOPT programs. 15 releases · 6 other sources · first seen Mar 2022
BTF metadata handling Parses and works with BTF type metadata, including support for BTF_TYPE_KIND_TAG and BTF_TYPE_KIND_DECL_TAG annotations, and enforces read-only semantics on rodata maps by freezing them on load. 6 releases · 9 other sources · first seen Mar 2022
Multi-architecture support Supports generating and running BPF programs across multiple CPU architectures, including riscv64. 9 releases · 3 other sources · first seen Jun 2022
BPF map pinning to filesystem Allows BPF maps to be pinned to a BPF filesystem path so they remain loaded until the corresponding file is deleted. 2 releases · 2 other sources · first seen Oct 2026
uprobes with cookies Supports attaching uprobes with cookie values, allowing per-attachment data to be passed into uprobe BPF programs. 2 releases · first seen Jun 2026
Flow Dissector program support Supports loading and attaching Flow Dissector BPF programs. 1 release · 1 other source · first seen Jun 2026
Ring buffer map support Allows ring buffer maps to be created programmatically from userspace via RingBuf::create(). 1 release · first seen Oct 2026
aya-tool macro fallback Enables clang_macro_fallback in aya-tool so that macro-defined constants are captured even when direct macro expansion is unavailable. 1 release · first seen Jun 2026
Kernel version detection hardening Removes panics that occurred when the kernel version could not be determined, replacing them with recoverable errors. 1 release · first seen Jun 2026
Netlink error reporting Surfaces error messages returned from netlink operations rather than discarding them. 1 release · first seen Jun 2026
XDP interface context Exposes the ingress interface index (ifindex) inside XdpContext, making it available to XDP BPF programs. 1 release · first seen Jun 2026
Hardware breakpoint attachment Supports attaching BPF programs to hardware breakpoints (read, write, read/write, and execute) via PerfEventConfig::Breakpoint. 1 release · first seen Nov 2025
TCX link attachment Supports attaching multiple BPF programs to a TC hook via TCX links, with caller-controlled ordering relative to other attached programs. 1 release · first seen Oct 2024

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for aya, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail aya puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

19 entries

  1. October 20262
  2. June 20261
  3. November 20251
  4. October 20248
  5. April 20242
  6. February 20243
  7. June 20221
  8. March 20221
    Show

    19 entries

    Project health

    Issue, contributor and maintainer activity in aya-rs/aya, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors not measured distinct committers, last 12 months
    2. Maintainers not measured core set, last 12 months
    3. Bus factor not measured committers behind half the commits
    4. Community-filed 100% of issues opened, last 12 months
    5. Median time to close 423 days first maintainer reply 13 hours
    6. Open backlog 136 of 409 issues ever filed
    1. Issues opened / month 2 · 0 communitymaintainers
    2. Open backlog 136
    3. Contributors / month not measured
    4. Commits / month not measured
    5. Stars not measured
    Issue themes, last 12 months
    • other 100%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    Saved in this browser. Sign in to sync your tools.