The section your link pointed to isn't on aya's page any more, so we've brought you to the top.
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.
Plays4. PlaysWhat you can do nowTo doDoneDismissedDeadlinesSince you lookedChecking Plays…Plays could not be checked. This does not mean there is nothing to do.Plays are held while the actionability and safety checks are measured.Personal Plays are held until the measured rollout checks pass.Deadline reminders are held until the measured rollout checks pass.Sign in to see Plays for your saved tools.Personal Plays and Deadlines are included with Practitioner, Researcher and Business.Sign inSee plansRetrySave a tool in Your stack to see Plays for it.We have not checked every saved tool yet. There is no all-clear to report.No new action was found in the checked release sources. Checked as ofNo published Plays for this tool in the last 90 days. This is not an all-clear for the version you run.No Plays in this view.No dated Plays for your saved tools.Why it mattersDo thisBefore you startEstimated effortEffort has not been measured.Read the sourceSource evidenceAct before it breaksNot for meRemind me next weekHidden from To do until next week.That change was not saved. Try again.Keep my Play answers in my accountOptional: save Done, Not for me and reminders privately in your account. Your tools are matched in this browser. No answers are sent until you opt in.Erase my Play answersYour Play answers and private calendar link have been erased.Create a private calendar linkReplace calendar linkRevoke calendar linkAnyone with this link can read generic deadline events. It contains no tool names, versions or answers. Revoke it any time.Private calendar feedWithin 30 daysWithin 7 daysPast the published dateMore than 30 days awayAct byNo earlier visit saved for this tool.breakingtotal Plays since your last reviewReview this toolMark this tool reviewedReview dates stay in this browser. Opening this list does not mark a tool reviewed.Category moves this monthThere is not enough documented history to call a category move this month.Category history is unavailable. No monthly comparison can be made.Category moves are held until the measured rollout checks pass.The documented monthly history shows no category move.What we got wrongThere are too few reviewed Plays to report a correction rate.Play corrections have not been measured for this month.Plays reviewedcorrectedPublished in the last 90 days. Breaking changes come first.Saved tools are matched in this browser; your versions are not sent.Your Plays{count} PlaysWhat you can do with the tools you runRelease sources for {checked} of {total} saved tools checked; no new plays match this edition.Add your toolsRead the details on the webIn {count} daysWe corrected {wrong} of {count} reviewed 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.
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
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.
+Cgroup and inode local storage map supportNot checked yet · Date unknownProvides 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 formattingNot checked yet · Date unknownProvides 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 loadingNot checked yet · Date unknownProvides 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 consistencyNot checked yet · Date unknownRenames 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 codegenNot checked yet · Date unknownGenerates 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 loadingNot checked yet · Date unknownSupports loading eBPF programs that reference kernel symbols (ksyms).1 release · first seen Oct 2026▸
Shared capability: eBPF-based runtime detection
+TC context manipulationNot checked yet · Date unknownProvides 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 functionsNot checked yet · Date unknownImplements 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 collectionNot checked yet · Date unknownExposes 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 telemetry1 featureEndpoint investigation and controlssince 2026▸
+Process memory map parsingNot checked yet · Date unknownParses 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 classified16 featuresFeatures we have not matched to a capability yet. A suggested match is marked.▸
+BPF map type supportNot checked yet · Date unknownSupports 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 manipulationNot checked yet · Date unknownProvides 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 managementNot checked yet · Date unknownProvides 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 supportNot checked yet · Date unknownSupports 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 handlingNot checked yet · Date unknownParses 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 supportNot checked yet · Date unknownSupports generating and running BPF programs across multiple CPU architectures, including riscv64.9 releases · 3 other sources · first seen Jun 2022▸
+BPF map pinning to filesystemNot checked yet · Date unknownAllows 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 cookiesNot checked yet · Date unknownSupports 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 supportNot checked yet · Date unknownSupports loading and attaching Flow Dissector BPF programs.1 release · 1 other source · first seen Jun 2026▸
+Ring buffer map supportNot checked yet · Date unknownAllows ring buffer maps to be created programmatically from userspace via RingBuf::create().1 release · first seen Oct 2026▸
+aya-tool macro fallbackNot checked yet · Date unknownEnables 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 hardeningNot checked yet · Date unknownRemoves panics that occurred when the kernel version could not be determined, replacing them with recoverable errors.1 release · first seen Jun 2026▸
+Netlink error reportingNot checked yet · Date unknownSurfaces error messages returned from netlink operations rather than discarding them.1 release · first seen Jun 2026▸
+XDP interface contextNot checked yet · Date unknownExposes the ingress interface index (ifindex) inside XdpContext, making it available to XDP BPF programs.1 release · first seen Jun 2026▸
+Hardware breakpoint attachmentNot checked yet · Date unknownSupports attaching BPF programs to hardware breakpoints (read, write, read/write, and execute) via PerfEventConfig::Breakpoint.1 release · first seen Nov 2025▸
+TCX link attachmentNot checked yet · Date unknownSupports 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.
Command line
View
load a captured run
composed command
No matchesTry a different search, or clear a filter to see more.
option surface across analysed releases
options at that releaseadded, per releaseremoved, per release
option
found in
since
description
No matchesTry a different search, or clear a filter to see more.
option changes per release — drag across the rail to set a range
→
Values are placeholders taken from each option’s declared default.
Nothing is executed here — the output shown is a recording of a run
that already happened.
Score card
Shipping velocityreleases a month, last 12 months
Documentation qualityrelease-notes rubric, 0–100
Breaking-change disciplinehow rarely a release breaks users, and notice given
Maintenance riskquiet time against its own cadence, maintainers
Innovation & surfacenew capabilities, API and MCP surface
Community health
Contributor trenddistinct committers, this year against last
Maintainer concentrationbus factor now against a year ago
Issue backlog trendissues closed per issue opened, 12 months
Responsivenessmedian 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.
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.
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.
Contributorsnot measureddistinct committers, last 12 months
Maintainersnot measuredcore set, last 12 months
Bus factornot measuredcommitters behind half the commits
Community-filed100%of issues opened, last 12 months
Median time to close423 daysfirst maintainer reply 13 hours
Open backlog136of 409 issues ever filed
Issues opened / month2 · 0communitymaintainers
Open backlog136
Contributors / monthnot measured
Commits / monthnot measured
Starsnot 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.
Copy this, send it to your AI assistant, then come back with its reply.
Nothing is sent from here. You paste the reply in the next step.
1 Copy
2 Paste
3 Confirm
Paste the reply
One tool per line is best. Versions are optional, and any format works. Names we don’t track are sent to us, without versions, so we can consider adding them.