Repository Analysis

matthart1983/netwatch

Real-time network diagnostics in your terminal. One command, zero config, instant visibility.

9.7 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of matthart1983/netwatch, a Rust project with 2,604 GitHub stars. SynthScan v2.0 examined 60,150 lines of code across 126 source files, recording 297 pattern matches distributed across 6 syntactic categories. The overall adjusted score of 9.7 places this repository in the Low AI signal band.

The scanner applied 160+ deterministic lexical heuristics, multi-line block detectors, abstract syntax tree depth profilers, and a cross-file Jaccard similarity matrix to construct a statistically normalised synthetic code estimate. All matches are individually weighted by severity coefficient and contextual multiplier before summation, and the resulting headline score is temporally discounted to account for the repository's development history relative to the commercial emergence of large language model coding tooling (November 2022 onward).

9.7
Adjusted Score
9.7
Raw Score
100%
Time Factor
2026-08-15
Last Push
2.6K
Stars
Rust
Language
60.1K
Lines of Code
126
Files
297
Pattern Hits
2026-08-29
Scan Date
0.00
HC Hit Rate

What These Metrics Mean

Adjusted Score
Primary synthetic code indicator. Raw score normalised per 1,000 lines of code and multiplied by the temporal discount factor. This is the definitive comparative metric — use it to rank repositories by AI authorship density.
Raw Score
The unmodified sum of all severity-weighted, context-multiplied pattern match scores before temporal discounting. Reflects the absolute signal strength independent of when the repository was last active.
Time Factor
The temporal discount multiplier (0–100%) applied to the raw score. Repositories last updated before ChatGPT's launch (Nov 2022) receive a 5% factor. Full signal is only assigned to repositories active in the post-adoption era (Jan 2024+).
Pattern Hits
Total count of individual pattern matches across all files and categories. A high hit count with a low score may indicate a very large codebase with isolated AI snippets; a low count with a high score indicates dense, concentrated AI signatures.
HC Hit Rate
High+Critical pattern hits per file, averaged across the repository. This orthogonal signal catches repositories where a few files are densely packed with high-severity AI tells — a strong indicator even when the normalised score appears moderate due to codebase size.
Lines of Code / Files
Total lines and files analysed. The scanner examines 94 file extensions. These denominators are used to normalise the score, enabling fair comparison between repositories of vastly different sizes.

Score History

This chart maps the temporal evolution of the adjusted synthetic code score across successive scan runs. An upward trajectory indicates ongoing incorporation of AI-generated code or expanding LLM-assisted scaffolding; a stable or declining trajectory may reflect active human refactoring, code removal, or the adoption of stricter authorship policies. The dashed secondary line (right axis) independently tracks total raw pattern hit count, which can diverge from the normalised score when codebase size changes significantly between scans.

Severity Breakdown

Classifies detected patterns by their diagnostic confidence and structural impact. CRITICAL patterns (coefficient 10) represent definitive synthetic signatures — hallucinated imports, explicit LLM attribution metadata — virtually never produced by human authors. HIGH (5) indicates strong structural tells such as cross-file repetition or cross-linguistic idioms. MEDIUM (2) covers recognisable conversational padding and AI-specific vocabulary. LOW (1) captures subtle indicators like tautological comments and generic boilerplate that require density to carry independent signal.

CRITICAL 0HIGH 0MEDIUM 136LOW 161

Directory Score Breakdown

This horizontal bar chart decomposes the repository's raw synthetic code score by top-level directory, allowing you to pinpoint precisely which modules or components carry the highest AI authorship density. Directories with disproportionately high scores relative to their size warrant targeted manual review: concentrated AI signatures often trace back to mass-generated configuration layers, auto-ported test suites, LLM-scaffolded boilerplate classes, or entire subsystems authored under heavy copilot assistance. Use this view to prioritise your human code-review effort.

Pattern Findings

The scanner identified 297 distinct pattern matches across 6 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a statistically significant AI authorship indicator. 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 diagnostic confidence level (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — comment-context matches receive a ×1.5 weight because LLMs systematically over-annotate. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier as dense clusters constitute far stronger evidence of synthetic authorship than isolated hits.

Decorative Section Separators131 hits · 404 pts
SeverityFileLineSnippetContext
MEDIUMdocs/ebpf-deep-dive.html730 <!-- 15 ─ #38 timeline (MARQUEE INTERACTIVE) ───────────────────────────── -->CODE
MEDIUMdocs/ebpf-deep-dive.html1294/* ── #38 timeline scrubber (slide 15) ────────────────────────────────────── */COMMENT
MEDIUMscripts/verify-tls12-decrypt.sh24# ── Resolve the capture interface ───────────────────────────────────────────COMMENT
MEDIUMscripts/verify-tls12-decrypt.sh38# ── Preflight: python must be OpenSSL-backed ────────────────────────────────COMMENT
MEDIUMscripts/verify-tls12-decrypt.sh48# ── Build the harness once ──────────────────────────────────────────────────COMMENT
MEDIUMscripts/verify-tls12-decrypt.sh58# ── Run one scenario; classify the harness output ───────────────────────────COMMENT
MEDIUMsrc/graph.rs185// ── braille pixel-dot line plot ─────────────────────────────────────────────COMMENT
MEDIUMsrc/graph.rs266// ── fade + grid helpers ─────────────────────────────────────────────────────COMMENT
MEDIUMsrc/config.rs139// ── Defaults ───────────────────────────────────────────────COMMENT
MEDIUMsrc/config.rs183// ── Persistence ────────────────────────────────────────────COMMENT
MEDIUMsrc/config.rs248// ── Helpers to map string ↔ app types ──────────────────────COMMENT
MEDIUMsrc/config.rs278// ── Tests ──────────────────────────────────────────────────COMMENT
MEDIUMsrc/theme.rs8 // ── Brand / chrome ──────────────────────────────────COMMENT
MEDIUMsrc/theme.rs15 // ── Text ────────────────────────────────────────────COMMENT
MEDIUMsrc/theme.rs21 // ── Status / semantic ───────────────────────────────COMMENT
MEDIUMsrc/theme.rs27 // ── Data ────────────────────────────────────────────COMMENT
MEDIUMsrc/theme.rs32 // ── Selection ───────────────────────────────────────COMMENT
MEDIUMsrc/theme.rs80// ── Built-in themes ────────────────────────────────────────COMMENT
MEDIUMsrc/app.rs2336// ── Key event handlers ─────────────────────────────────────────────────────COMMENT
MEDIUMsrc/app.rs4151 // ── RTT history cap tests ───────────────────────────────────────────COMMENT
MEDIUMsrc/ui/connections.rs536// ── Grouped tree ────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/ui/connections.rs1920 // ── Grouped tree ────────────────────────────────────────────────────COMMENT
MEDIUMsrc/ui/timeline.rs32// ── Event model ─────────────────────────────────────────────COMMENT
MEDIUMsrc/ui/timeline.rs247// ── Filter chip row ─────────────────────────────────────────COMMENT
MEDIUMsrc/ui/timeline.rs316// ── Activity strip ──────────────────────────────────────────COMMENT
MEDIUMsrc/ui/timeline.rs467// ── Event log ───────────────────────────────────────────────COMMENT
MEDIUMsrc/ui/timeline.rs590// ── helpers ─────────────────────────────────────────────────COMMENT
MEDIUMsrc/ui/interfaces.rs660// ── helpers ─────────────────────────────────────────────────COMMENT
MEDIUMsrc/ui/insights.rs33// ── Card model ──────────────────────────────────────────────COMMENT
MEDIUMsrc/ui/insights.rs246// ── Render: summary line ────────────────────────────────────COMMENT
MEDIUMsrc/ui/insights.rs322// ── Render: card stack ──────────────────────────────────────COMMENT
MEDIUMsrc/ui/insights.rs469// ── Empty state ─────────────────────────────────────────────COMMENT
MEDIUMsrc/ui/insights.rs526// ── Disclaimer + footer ─────────────────────────────────────COMMENT
MEDIUMsrc/ui/lite.rs30// ── The grid ────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/ui/lite.rs45// ── Rows ────────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/ui/lite.rs75// ── History ─────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/ui/lite.rs116// ── Talker table ────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/ui/lite.rs185// ── Footer ──────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/ui/lite.rs219// ── Adaptive layout ─────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/ui/lite.rs308// ── Talkers ─────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/ui/lite.rs443// ── Formatting ──────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/ui/lite.rs545// ── Drawing primitives ──────────────────────────────────────────────────────COMMENT
MEDIUMsrc/ui/lite.rs618// ── Render ──────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/ui/stats.rs98// ── Range chips row ─────────────────────────────────────────COMMENT
MEDIUMsrc/ui/stats.rs165// ── KPI tiles row ───────────────────────────────────────────COMMENT
MEDIUMsrc/ui/stats.rs320// ── Breakdowns row ──────────────────────────────────────────COMMENT
MEDIUMsrc/ui/stats.rs681// ── Throughput chart ────────────────────────────────────────COMMENT
MEDIUMsrc/ui/topology.rs30// ── Topology graph ──────────────────────────────────────────COMMENT
MEDIUMsrc/ui/topology.rs549// ── Hop detail table ────────────────────────────────────────COMMENT
MEDIUMsrc/ui/topology.rs747// ── helpers ─────────────────────────────────────────────────COMMENT
MEDIUMsrc/ui/processes.rs78// ── Sort chip row (reflects current sort state) ─────────────COMMENT
MEDIUMsrc/ui/processes.rs156// ── Table ───────────────────────────────────────────────────COMMENT
MEDIUMsrc/ui/processes.rs326// ── Drill-in panel ──────────────────────────────────────────COMMENT
MEDIUMsrc/ui/processes.rs629// ── helpers ─────────────────────────────────────────────────COMMENT
MEDIUMsrc/ui/dashboard.rs37// ── KPI strip ───────────────────────────────────────────────COMMENT
MEDIUMsrc/ui/dashboard.rs221// ── Mid section: Active Interface + Throughput ──────────────COMMENT
MEDIUMsrc/ui/dashboard.rs565// ── Bottom section: Top Connections + Health ────────────────COMMENT
MEDIUMsrc/ui/dashboard.rs1057// ── helpers ─────────────────────────────────────────────────COMMENT
MEDIUMsrc/ui/dense/paint.rs36// ── ramps ───────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/ui/dense/paint.rs167// ── braille area graph ──────────────────────────────────────────────────────COMMENT
71 more matches not shown…
Over-Commented Block150 hits · 148 pts
SeverityFileLineSnippetContext
LOWCargo.toml61ring = "0.17"COMMENT
LOWCargo.toml81# via `RUST_LOG=netwatch=debug` when handing us a repro for a stuck resolver,COMMENT
LOWbuild.rs1fn main() {COMMENT
LOWexamples/ebpf_v6_smoke.rs1//! Live smoke for eBPF Phase 2 IPv6 attribution (`tcp_v6_connect`).COMMENT
LOWexamples/sandbox_smoke.rs1//! Smoke test for `netwatch::sandbox`.COMMENT
LOWexamples/ping_under_sandbox.rs1//! Verify native ICMP ping survives the sandbox.COMMENT
LOWexamples/tls12_decrypt_live.rs1//! Live end-to-end verification of TLS 1.2 Application-Data decryption.COMMENT
LOWexamples/ebpf_udp_v6_smoke.rs1//! Live smoke for eBPF Phase 2 **connected-UDP** IPv6 attributionCOMMENT
LOWexamples/tls_decrypt_live.rs1//! Live end-to-end verification of TLS 1.3 Application-Data decryption.COMMENT
LOWexamples/traceroute_under_sandbox.rs1//! Verify native UDP+TTL traceroute survives the sandbox.COMMENT
LOWexamples/pktap_probe.rs1// Manual validation tool for the macOS PKTAP attribution path.COMMENT
LOWscripts/verify-tls12-decrypt.sh1#!/usr/bin/env bashCOMMENT
LOWscripts/demo-lite-traffic.sh1#!/usr/bin/env bashCOMMENT
LOWscripts/demo-dense-traffic.sh1#!/usr/bin/env bashCOMMENT
LOWscripts/demo-dense-traffic.sh21# SNI from partway through.COMMENT
LOWscripts/demo-egress-traffic.sh1#!/usr/bin/env bashCOMMENT
LOWscripts/demo-egress-traffic.sh21# Destination names come from the TLS ClientHello, which means the handshakeCOMMENT
LOWscripts/demo-dense-env.sh1#!/usr/bin/env bashCOMMENT
LOWscripts/demo-lite-env.sh1#!/usr/bin/env bashCOMMENT
LOWsrc/graph.rs1//! Pluggable graph rendering for every chart in the app.COMMENT
LOWsrc/graph.rs41 GraphStyle::Dots => "dots",COMMENT
LOWsrc/graph.rs81/// Lowest fraction of the row's foreground color the bottommostCOMMENT
LOWsrc/config.rs61 /// Hero-panel graph style (bars, btop). Applies only to the aggregatedCOMMENT
LOWsrc/config.rs81 /// at runtime, so the live process keeps whatever mode it launchedCOMMENT
LOWsrc/lib.rs1// Clippy lints deliberately allowed crate-wide. Each is a decision, not anCOMMENT
LOWsrc/lib.rs21// `too_many_arguments` — nine rendering and collection functions take 8–14COMMENT
LOWsrc/theme.rs41 /// active tab.COMMENT
LOWsrc/theme.rs121/// Defers entirely to the terminal's own palette: ANSI slots 0–15 forCOMMENT
LOWsrc/theme.rs401}COMMENT
LOWsrc/logging.rs1//! File-only structured logging.COMMENT
LOWsrc/logging.rs21COMMENT
LOWsrc/metrics.rs1//! Prometheus `/metrics` + `/healthz` exporter (netwatch cloud Workstream C).COMMENT
LOWsrc/state.rs21use crate::ui::sort_picker::SortPickerState;COMMENT
LOWsrc/state.rs41 /// Rolling RX rate history per grouped (process, host) for the DashboardCOMMENT
LOWsrc/state.rs61/// Kept in its own substruct rather than scattered across [`AppUiState`] soCOMMENT
LOWsrc/state.rs81/// flags (help/settings/memory_stats/geo), transient status messages withCOMMENT
LOWsrc/state.rs161 /// Column the Egress tree is ordered by.COMMENT
LOWsrc/clipboard.rs1//! Cross-platform clipboard write via platform tools — `pbcopy` onCOMMENT
LOWsrc/app.rs461 intel_last_pkt_id: u64,COMMENT
LOWsrc/app.rs481 pub user_config: NetwatchConfig,COMMENT
LOWsrc/app.rs501 pktap_handle: Option<crate::platform::pktap::PktapHandle>,COMMENT
LOWsrc/app.rs581 // that ingests secrets as the cooperating client processCOMMENT
LOWsrc/app.rs1481 // Collectors run on background threads and share state via Arc<Mutex<T>>.COMMENT
LOWsrc/app.rs1741COMMENT
LOWsrc/app.rs2081 let content_top = 3 + 1; // header + table border topCOMMENT
LOWsrc/ui/connections.rs541// process column so starved of width it rendered `Google Chrome…`. These areCOMMENT
LOWsrc/ui/connections.rs581}COMMENT
LOWsrc/ui/egress.rs1//! Egress tab — per-process egress profiles and policy drift.COMMENT
LOWsrc/ui/tree.rs1//! Shared machinery for the grouped-tree tables (Egress, Connections).COMMENT
LOWsrc/ui/lite.rs1//! NetWatch Lite — the minimal single-screen view.COMMENT
LOWsrc/ui/lite.rs61pub const TALKER_ROWS: u16 = 8;COMMENT
LOWsrc/ui/lite.rs81/// configurable, so the axis label is computed by [`window_label`] rather thanCOMMENT
LOWsrc/ui/dense/paint.rs1//! Drawing primitives for the Dense view.COMMENT
LOWsrc/ui/dense/paint.rs181/// `samples` is oldest-first and must already be exactly `2 × area.width`COMMENT
LOWsrc/ui/dense/mod.rs1//! NetWatch Dense — the high-density single-screen view.COMMENT
LOWsrc/ui/dense/mod.rs61pub const GUTTER_TICK_X: u16 = 6;COMMENT
LOWsrc/ui/dense/mod.rs461 right(38 + shift, 8, "DOWN"),COMMENT
LOWsrc/ui/dense/mod.rs521}COMMENT
LOWsrc/ui/dense/mod.rs621 /// it is still a socket, it is just done.COMMENT
LOWsrc/ui/dense/mod.rs1341///COMMENT
90 more matches not shown…
AI Slop Vocabulary5 hits · 18 pts
SeverityFileLineSnippetContext
MEDIUMscripts/verify-tls12-decrypt.sh7# harness against live traffic, across every AEAD suite we support, plus aCOMMENT
MEDIUMscripts/verify-tls12-decrypt.sh48# ── Build the harness once ──────────────────────────────────────────────────COMMENT
MEDIUMscripts/verify-tls12-decrypt.sh58# ── Run one scenario; classify the harness output ───────────────────────────COMMENT
MEDIUMsrc/collectors/incident.rs117 /// robust to `alert_history` being a bounded ring buffer: once it hitsCOMMENT
MEDIUMsrc/collectors/quic.rs292 // be robust to multi-frame layouts in the same packet.COMMENT
Excessive Try-Catch Wrapping6 hits · 6 pts
SeverityFileLineSnippetContext
LOWexamples/tls12_decrypt_live.rs93 except Exception:CODE
LOWexamples/tls12_decrypt_live.rs98except Exception: passCODE
LOWexamples/tls_decrypt_live.rs83 except Exception:CODE
LOWexamples/tls_decrypt_live.rs88except Exception: passCODE
LOWscripts/demo/gen_tls12.py34 except Exception as e:CODE
LOWscripts/demo/gen_tls12.py40except Exception:CODE
Example Usage Blocks4 hits · 6 pts
SeverityFileLineSnippetContext
LOWscripts/verify-tls12-decrypt.sh10# Usage:COMMENT
LOWscripts/demo-lite-traffic.sh21# Usage:COMMENT
LOWscripts/demo-dense-traffic.sh26# Usage:COMMENT
LOWscripts/demo-egress-traffic.sh27# Usage:COMMENT
Unused Imports1 hit · 1 pts
SeverityFileLineSnippetContext
LOWscripts/demo/gen_tls12.py9CODE