AI Slop Code Risk Monitor

aya-rs/aya

SlopCodeMonitor badge for aya-rs/aya Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

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

2.8 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for aya-rs/aya, a Rust project with 4,883 GitHub stars. SynthScan examined 159,415 lines of code across 496 source files, recording 454 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 2.8 (Low pattern signal); it is not an authorship estimate.

Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.

2.8
Adjusted Signal
2.8
Raw Pattern Score
100%
Time Factor
2026-11-01
Last Push
4.9K
Stars
Rust
Language
159.4K
Lines of Code
496
Files
454
Pattern Hits
2026-10-31
Scan Date
0.00
HC Hit Rate

Risk Review · Payload v1

Use each vector to guide manual verification of the underlying findings.

Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.

Cognitive Ownership Risk 12.8/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 452 finding(s).

Hallucinated Dependency & Supply Chain Risk 0.1/100 · LOW

Are imports declared and package/API names verified? 2 finding(s).

Agent Over-Engineering Ratio 0.0/100 · LOW

Are wrappers, guards, and repeated structures necessary? 0 finding(s).

PR Review Velocity Impact 13.3/100 · LOW

Which changes need focused human review? 454 finding(s).

What These Metrics Mean

Adjusted Signal
Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score
Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor
A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits
Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate
High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files
Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 0HIGH 0MEDIUM 0LOW 454

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 454 distinct pattern matches across 3 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.

Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Over-Commented Block451 hits · 436 pts
SeverityFileLineSnippetContext
LOWtest/integration-test/bpf/ksyms.bpf.c1// clang-format offCOMMENT
LOWtest/integration-test/src/tests/sk_reuseport.rs81COMMENT
LOWtest/integration-test/src/tests/fexit.rs21 _ => "HELPER_ERROR",COMMENT
LOWtest/integration-ebpf/build.rs1use std::env;COMMENT
LOWtest/integration-ebpf/src/sk_storage.rs41COMMENT
LOWtest/integration-ebpf/src/socket_filter.rs41}COMMENT
LOWaya-obj/include/linux_wrapper.h1#include <linux/bpf.h>COMMENT
LOWaya-obj/src/lib.rs1//! An eBPF object file parsing library with BTF and relocation support.COMMENT
LOWaya-obj/src/lib.rs21//! about the eBPF programs.COMMENT
LOWaya-obj/src/lib.rs41//! object.relocate_calls(&text_sections).unwrap();COMMENT
LOWaya-obj/src/maps.rs321/// for more info.COMMENT
LOWaya-obj/src/obj.rs101 pub instructions: Vec<bpf_insn>,COMMENT
LOWaya-obj/src/obj.rs121/// - The section name must conform to [Program Types and ELF Sections].COMMENT
LOWebpf-panic/src/lib.rs1//! A panic handler for eBPF rust targets.COMMENT
LOWebpf-panic/src/lib.rs21//!COMMENT
LOWaya-log/src/lib.rs1//! A logging framework for eBPF programs.COMMENT
LOWaya-log/src/lib.rs21//! // start reading aya-log records and log them using the default loggerCOMMENT
LOWaya-log/src/lib.rs41//! use aya_log_ebpf::{debug, error, info, trace, warn};COMMENT
LOWaya-ebpf-macros/src/lib.rs141///COMMENT
LOWaya-ebpf-macros/src/lib.rs201/// Marks a function as a [`CgroupSockAddr`] eBPF program.COMMENT
LOWaya-ebpf-macros/src/lib.rs221/// pub fn connect4(ctx: SockAddrContext) -> i32 {COMMENT
LOWaya-ebpf-macros/src/lib.rs261 Ok(prog) => prog.expand(),COMMENT
LOWaya-ebpf-macros/src/lib.rs281/// use aya_ebpf::{macros::raw_tracepoint, programs::RawTracePointContext};COMMENT
LOWaya-ebpf-macros/src/lib.rs301 .into()COMMENT
LOWaya-ebpf-macros/src/lib.rs321///COMMENT
LOWaya-ebpf-macros/src/lib.rs341 match Lsm::parse(attrs.into(), item.into()) {COMMENT
LOWaya-ebpf-macros/src/lib.rs361/// # Minimum kernel versionCOMMENT
LOWaya-ebpf-macros/src/lib.rs381/// ```COMMENT
LOWaya-ebpf-macros/src/lib.rs401///COMMENT
LOWaya-ebpf-macros/src/lib.rs421#[proc_macro_attribute]COMMENT
LOWaya-ebpf-macros/src/lib.rs441///COMMENT
LOWaya-ebpf-macros/src/lib.rs461/// to a `SockMap`.COMMENT
LOWaya-ebpf-macros/src/lib.rs501/// # Minimum kernel versionCOMMENT
LOWaya-ebpf-macros/src/lib.rs521 .into()COMMENT
LOWaya-ebpf-macros/src/lib.rs541/// # #[expect(non_camel_case_types)]COMMENT
LOWaya-ebpf-macros/src/lib.rs561 match FEntry::parse(attrs.into(), item.into()) {COMMENT
LOWaya-ebpf-macros/src/lib.rs581/// # ExamplesCOMMENT
LOWaya-ebpf-macros/src/lib.rs601/// let _retval: c_int = ctx.ret()?;COMMENT
LOWaya-ebpf-macros/src/lib.rs621/// `FlowDissectorContext::flow_keys`. The return code of the BPF program isCOMMENT
LOWaya-ebpf-macros/src/lib.rs641/// ```COMMENT
LOWaya-ebpf-macros/src/lib.rs661/// The minimum kernel version required to use this feature is 5.9COMMENT
LOWaya-ebpf-macros/src/lib.rs681}COMMENT
LOWaya-ebpf-macros/src/lib.rs701///COMMENT
LOWaya-ebpf-macros/src/lib.rs721/// maps::ReusePortSockArray,COMMENT
LOWaya-ebpf-macros/src/lib.rs741/// Ok(()) => SK_PASS,COMMENT
LOWaya-ebpf-macros/src/lib.rs761/// }COMMENT
LOWaya-ebpf-macros/src/lib.rs781///COMMENT
LOWaya/src/util.rs101 // backports were done to cap the patch versionCOMMENT
LOWaya/src/util.rs321 Err(ParseIntError { .. }) => None,COMMENT
LOWaya/src/util.rs381pub(crate) const fn tc_handler_make(major: u32, minor: u32) -> u32 {COMMENT
LOWaya/src/lib.rs1//! [![](https://aya-rs.dev/assets/images/aya_logo_docs.svg)](https://aya-rs.dev)COMMENT
LOWaya/src/lib.rs21//! supported by the target kernel. This allows eBPF programs compiled againstCOMMENT
LOWaya/src/bpf.rs61/// relocations. You can use `EbpfLoader` to customize some of the loadingCOMMENT
LOWaya/src/bpf.rs161 /// Sets the target [BTF](Btf) info.COMMENT
LOWaya/src/bpf.rs181 /// )?)COMMENT
LOWaya/src/bpf.rs201 /// ```no_runCOMMENT
LOWaya/src/bpf.rs221 + std::panic::RefUnwindSafeCOMMENT
LOWaya/src/bpf.rs241 ///COMMENT
LOWaya/src/bpf.rs261 /// # ExampleCOMMENT
LOWaya/src/bpf.rs281 /// From Rust eBPF, a global variable can be defined using `Global` - please refer to the `aya-ebpf` documentation.COMMENT
391 more matches not shown…
Unused Imports2 hits · 2 pts
SeverityFileLineSnippetContext
LOWscripts/rust-toolchain-pins.py5CODE
LOWscripts/rust_toolchains.py5CODE
Redundant / Tautological Comments1 hit · 2 pts
SeverityFileLineSnippetContext
LOWebpf/aya-ebpf/src/maps/xdp/mod.rs15/// # Return valueCOMMENT