aya
Aya is an eBPF library for the Rust programming language, built with a focus on developer experience and operability.
Runssource: GitHubhomepageRustApache-2.0commit df926b48e958
Rust, Apache-2.0 licensed. The project labels itself: bpf, ebpf, observability, rust and security.
aya runs. An Argusic agent installed it in 9.8 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The aya Rust workspace builds cleanly and its full host-side test suite passes (507 tests, 0 failures) after fixing a /proc/pid/maps parser bug where 64-bit overlayfs inode numbers overflowed a u32 field;
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- cargo test failed: uprobe test panicked parsing /proc/pid/maps; overlayfs inode 9680888223 exceeds u32::MAX so ProcMapEntry::parse failed4 minutes
- eBPF/integration build path unavailable: bpftool, bindgen, clang, llvm-objcopy, bpf-linker not installed and not installable without root; nightly has no prebuilt bpfel-unknown-none target2 minutes
- Install time
- 10 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- cargo test exited 0: 507 passed, 0 failed, 0 ignored; cargo build finished dev profile in 51s; aya-tool --help printed usage and exited 0; xtask --help printed subcommands and exited 0; bash -c 'cargo +nightly xtask public-api --target x86_64-unknown-linux-gnu' exited 0
- Model tokens used
- 240,646
- Exact commit tested
- df926b48e958
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
elapsed_minutes: 9.8 Everything is verified. Let me compile the final report. **Summary of work:** - Installed Rust stable + nightly toolchains (repo pins nightly for eBPF crates) and ran the standa… - Hit one real failure: `aya::programs::uprobe::test_resolve_attach_target_basename` panicked parsi… - Verified `aya-tool --help` and `xtask --help` run (exit 0); `xtask public-api` runs to completion… - eBPF/integration paths (C eBPF via clang, `bpftool`, `bindgen`, `bpf-linker`) are gated on system… exec /bin/sh -lc true in /work/repo succeeded in 0ms: tokens used 240,646
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 9.8 minutes.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 9.8 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/aya)Questions
- Does aya run?
- Yes. aya runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test aya?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit df926b48e958. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test aya?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does aya take to install?
- 9.8 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does aya need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing aya?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for aya?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.