Home / martin-olivier / airgorah
AI Slop Code Risk Monitor

martin-olivier/airgorah

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

A WiFi security auditing software

1.4 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for martin-olivier/airgorah, a Rust project with 5,665 GitHub stars. SynthScan examined 8,547 lines of code across 54 source files, recording 10 pattern matches distributed across 2 syntactic categories. The legacy adjusted pattern signal is 1.4 (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.

1.4
Adjusted Signal
1.4
Raw Pattern Score
100%
Time Factor
2026-11-06
Last Push
5.7K
Stars
Rust
Language
8.5K
Lines of Code
54
Files
10
Pattern Hits
2026-11-14
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-11-14.

Cognitive Ownership Risk 6.8/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 6.8/100 · LOW

Which changes need focused human review? 10 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

Run additional scans to build a history of the legacy pattern signal. Score changes are not a measure of AI adoption or code quality.

No multi-scan history yet — run the scanner again to build trend data.

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 1LOW 9

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 10 distinct pattern matches across 2 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 Block9 hits · 9 pts
SeverityFileLineSnippetContext
LOWcrates/agent/src/backend/pcap.rs1//! Minimal pcap writer for the native capture engine.COMMENT
LOWcrates/agent/src/backend/vendors.rs1//! Vendor (OUI) resolution.COMMENT
LOWcrates/agent/src/backend/sniffer.rs1//! Native 802.11 capture engine — the in-house replacement for `airodump-ng`.COMMENT
LOWcrates/agent/src/backend/pmkid.rs1//! Native, clientless PMKID solicitation.COMMENT
LOWcrates/common/src/types.rs1//! Wire types shared across the IPC boundary.COMMENT
LOWcrates/common/src/types.rs21 /// Restore the permanent hardware MAC (`macchanger -p`).COMMENT
LOWcrates/common/src/handshake.rs1//! Native WPA crackable-material detection (4-way handshake and PMKID).COMMENT
LOWcrates/common/src/deps.rs1//! Catalog of the external command-line tools airgorah relies on.COMMENT
LOWcrates/gui/src/frontend/connections/app.rs101 app_data.app_gui.add_but.set_sensitive(false);COMMENT
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMcrates/agent/src/backend/pmkid.rs229 // the AP, but checking all three addresses is robust to direction quirks).COMMENT