matthart1983/netwatch

8.6

Adjusted Score

8.6

Raw Score

100%

Time Factor

2026-07-05

Last Push

2.2K

Stars

Rust

Language

47.9K

Lines of Code

114

Files

198

Pattern Hits

2026-07-14

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 102LOW 96

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 198 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 Separators97 hits · 302 pts

Severity	File	Line	Snippet	Context
MEDIUM	docs/ebpf-deep-dive.html	730	<!-- 15 ─ #38 timeline (MARQUEE INTERACTIVE) ───────────────────────────── -->	CODE
MEDIUM	docs/ebpf-deep-dive.html	1294	/* ── #38 timeline scrubber (slide 15) ────────────────────────────────────── */	COMMENT
MEDIUM	scripts/verify-tls12-decrypt.sh	24	# ── Resolve the capture interface ───────────────────────────────────────────	COMMENT
MEDIUM⚡	scripts/verify-tls12-decrypt.sh	38	# ── Preflight: python must be OpenSSL-backed ────────────────────────────────	COMMENT
MEDIUM⚡	scripts/verify-tls12-decrypt.sh	48	# ── Build the harness once ──────────────────────────────────────────────────	COMMENT
MEDIUM⚡	scripts/verify-tls12-decrypt.sh	58	# ── Run one scenario; classify the harness output ───────────────────────────	COMMENT
MEDIUM	src/graph.rs	179	// ── braille pixel-dot line plot ─────────────────────────────────────────────	COMMENT
MEDIUM	src/graph.rs	251	// ── fade + grid helpers ─────────────────────────────────────────────────────	COMMENT
MEDIUM	src/config.rs	118	// ── Defaults ───────────────────────────────────────────────	COMMENT
MEDIUM	src/config.rs	160	// ── Persistence ────────────────────────────────────────────	COMMENT
MEDIUM	src/config.rs	220	// ── Helpers to map string ↔ app types ──────────────────────	COMMENT
MEDIUM	src/config.rs	250	// ── Tests ──────────────────────────────────────────────────	COMMENT
MEDIUM⚡	src/theme.rs	8	// ── Brand / chrome ──────────────────────────────────	COMMENT
MEDIUM⚡	src/theme.rs	15	// ── Text ────────────────────────────────────────────	COMMENT
MEDIUM⚡	src/theme.rs	21	// ── Status / semantic ───────────────────────────────	COMMENT
MEDIUM⚡	src/theme.rs	27	// ── Data ────────────────────────────────────────────	COMMENT
MEDIUM⚡	src/theme.rs	32	// ── Selection ───────────────────────────────────────	COMMENT
MEDIUM	src/theme.rs	45	// ── Built-in themes ────────────────────────────────────────	COMMENT
MEDIUM	src/app.rs	1908	// ── Key event handlers ─────────────────────────────────────────────────────	COMMENT
MEDIUM	src/app.rs	3468	// ── RTT history cap tests ───────────────────────────────────────────	COMMENT
MEDIUM	src/ui/timeline.rs	32	// ── Event model ─────────────────────────────────────────────	COMMENT
MEDIUM	src/ui/timeline.rs	247	// ── Filter chip row ─────────────────────────────────────────	COMMENT
MEDIUM	src/ui/timeline.rs	316	// ── Activity strip ──────────────────────────────────────────	COMMENT
MEDIUM	src/ui/timeline.rs	467	// ── Event log ───────────────────────────────────────────────	COMMENT
MEDIUM	src/ui/timeline.rs	590	// ── helpers ─────────────────────────────────────────────────	COMMENT
MEDIUM	src/ui/interfaces.rs	660	// ── helpers ─────────────────────────────────────────────────	COMMENT
MEDIUM	src/ui/insights.rs	33	// ── Card model ──────────────────────────────────────────────	COMMENT
MEDIUM	src/ui/insights.rs	246	// ── Render: summary line ────────────────────────────────────	COMMENT
MEDIUM	src/ui/insights.rs	322	// ── Render: card stack ──────────────────────────────────────	COMMENT
MEDIUM	src/ui/insights.rs	463	// ── Empty state ─────────────────────────────────────────────	COMMENT
MEDIUM	src/ui/insights.rs	520	// ── Disclaimer + footer ─────────────────────────────────────	COMMENT
MEDIUM	src/ui/stats.rs	98	// ── Range chips row ─────────────────────────────────────────	COMMENT
MEDIUM	src/ui/stats.rs	165	// ── KPI tiles row ───────────────────────────────────────────	COMMENT
MEDIUM	src/ui/stats.rs	320	// ── Breakdowns row ──────────────────────────────────────────	COMMENT
MEDIUM	src/ui/stats.rs	681	// ── Throughput chart ────────────────────────────────────────	COMMENT
MEDIUM	src/ui/topology.rs	30	// ── Topology graph ──────────────────────────────────────────	COMMENT
MEDIUM	src/ui/topology.rs	549	// ── Hop detail table ────────────────────────────────────────	COMMENT
MEDIUM	src/ui/topology.rs	747	// ── helpers ─────────────────────────────────────────────────	COMMENT
MEDIUM	src/ui/processes.rs	78	// ── Sort chip row (reflects current sort state) ─────────────	COMMENT
MEDIUM	src/ui/processes.rs	156	// ── Table ───────────────────────────────────────────────────	COMMENT
MEDIUM	src/ui/processes.rs	321	// ── Drill-in panel ──────────────────────────────────────────	COMMENT
MEDIUM	src/ui/processes.rs	624	// ── helpers ─────────────────────────────────────────────────	COMMENT
MEDIUM	src/ui/dashboard.rs	37	// ── KPI strip ───────────────────────────────────────────────	COMMENT
MEDIUM	src/ui/dashboard.rs	221	// ── Mid section: Active Interface + Throughput ──────────────	COMMENT
MEDIUM	src/ui/dashboard.rs	565	// ── Bottom section: Top Connections + Health ────────────────	COMMENT
MEDIUM	src/ui/dashboard.rs	1057	// ── helpers ─────────────────────────────────────────────────	COMMENT
MEDIUM	src/collectors/network_intel.rs	4	// ── Configuration defaults ─────────────────────────────────	COMMENT
MEDIUM	src/collectors/network_intel.rs	25	// ── Alert types ────────────────────────────────────────────	COMMENT
MEDIUM	src/collectors/network_intel.rs	63	// ── Events fed from other collectors ───────────────────────	COMMENT
MEDIUM	src/collectors/network_intel.rs	100	// ── Anomaly detection state ────────────────────────────────	COMMENT
MEDIUM	src/collectors/network_intel.rs	125	// ── DNS analytics state ────────────────────────────────────	COMMENT
MEDIUM	src/collectors/network_intel.rs	177	// ── Bandwidth alert state ──────────────────────────────────	COMMENT
MEDIUM	src/collectors/network_intel.rs	186	// ── Main collector ─────────────────────────────────────────	COMMENT
MEDIUM	src/collectors/network_intel.rs	240	// ── Public API ─────────────────────────────────────────	COMMENT
MEDIUM	src/collectors/network_intel.rs	263	// ── Memory-stats accessors (drive the `M` debug overlay) ──────────	COMMENT
MEDIUM	src/collectors/network_intel.rs	315	// ── Event handlers ─────────────────────────────────────	COMMENT
MEDIUM	src/collectors/network_intel.rs	485	// ── Internal detection logic ───────────────────────────	COMMENT
MEDIUM	src/collectors/network_intel.rs	724	// ── Helpers ────────────────────────────────────────────────	COMMENT
MEDIUM	src/collectors/network_intel.rs	916	// ── Memory-cap stress tests ─────────────────────────────────────────	COMMENT
MEDIUM	src/collectors/health.rs	543	// ── parse_loss tests ──────────────────────────────────────────────	COMMENT
37 more matches not shown…

Over-Commented Block88 hits · 86 pts

Severity	File	Line	Snippet	Context
LOW	Cargo.toml	61	maxminddb = "0.27"	COMMENT
LOW	Cargo.toml	81	# the BPF object is missing or CAP_BPF/CAP_PERFMON aren't granted.	COMMENT
LOW	examples/ebpf_v6_smoke.rs	1	//! Live smoke for eBPF Phase 2 IPv6 attribution (`tcp_v6_connect`).	COMMENT
LOW	examples/sandbox_smoke.rs	1	//! Smoke test for `netwatch::sandbox`.	COMMENT
LOW	examples/ping_under_sandbox.rs	1	//! Verify native ICMP ping survives the sandbox.	COMMENT
LOW	examples/tls12_decrypt_live.rs	1	//! Live end-to-end verification of TLS 1.2 Application-Data decryption.	COMMENT
LOW	examples/ebpf_udp_v6_smoke.rs	1	//! Live smoke for eBPF Phase 2 connected-UDP IPv6 attribution	COMMENT
LOW	examples/tls_decrypt_live.rs	1	//! Live end-to-end verification of TLS 1.3 Application-Data decryption.	COMMENT
LOW	examples/traceroute_under_sandbox.rs	1	//! Verify native UDP+TTL traceroute survives the sandbox.	COMMENT
LOW	examples/pktap_probe.rs	1	// Manual validation tool for the macOS PKTAP attribution path.	COMMENT
LOW	scripts/verify-tls12-decrypt.sh	1	#!/usr/bin/env bash	COMMENT
LOW	src/graph.rs	1	//! Pluggable graph rendering for every chart in the app.	COMMENT
LOW	src/config.rs	61	/// the app — hero RX/TX panels, in-row sparklines, RTT history,	COMMENT
LOW	src/config.rs	81	/// secrets exported by a cooperating client (Chrome, Firefox, Node,	COMMENT
LOW	src/theme.rs	301	// Apple Terminal.app's Ocean profile background — the whole	COMMENT
LOW	src/logging.rs	1	//! File-only structured logging.	COMMENT
LOW	src/logging.rs	21		COMMENT
LOW	src/metrics.rs	1	//! Prometheus `/metrics` + `/healthz` exporter (netwatch cloud Workstream C).	COMMENT
LOW	src/state.rs	21		COMMENT
LOW	src/state.rs	41	/// Top Connections sparkline. Updated each connection-collector tick.	COMMENT
LOW	src/clipboard.rs	1	//! Cross-platform clipboard write via platform tools — `pbcopy` on	COMMENT
LOW	src/app.rs	421	/// the connection collector overlays onto lsof/ss-derived rows. None	COMMENT
LOW	src/app.rs	461	/// State of the PKTAP attribution path for status display. macOS-only;	COMMENT
LOW	src/app.rs	541	// per-connection rates. If this fails (no sudo, no interface), the	COMMENT
LOW	src/app.rs	1281	let gateway = app.config_collector.config.gateway.clone();	COMMENT
LOW	src/app.rs	1721	let content_bottom = area.height.saturating_sub(3); // above footer	COMMENT
LOW	src/collectors/health.rs	101	busy.store(false, Ordering::SeqCst);	COMMENT
LOW	src/collectors/health.rs	201	/// [`run_ping`] so the Health widget consumes both the same way.	COMMENT
LOW	src/collectors/connections.rs	41	pub handshake_rtt_us: Option<f64>,	COMMENT
LOW	src/collectors/connections.rs	421		COMMENT
LOW	src/collectors/connections.rs	961	}	COMMENT
LOW	src/collectors/quic.rs	1	//! QUIC Initial packet decryption per RFC 9001 §5.2 (and RFC 9369 §3.3.1	COMMENT
LOW	src/collectors/egress.rs	1	//! Observe-mode egress profiling (Horizon 3, phase 0).	COMMENT
LOW	src/collectors/egress.rs	41	/// change — the managed ingest keys off this.	COMMENT
LOW	src/collectors/egress.rs	781	#[serde(default)]	COMMENT
LOW	src/collectors/traceroute.rs	81	}	COMMENT
LOW	src/collectors/insights.rs	241	pub model: String,	COMMENT
LOW	src/collectors/traffic.rs	181	use super::*;	COMMENT
LOW	src/collectors/packets/mod.rs	261	pub total_bytes_b_to_a: u64,	COMMENT
LOW	src/collectors/packets/mod.rs	281	/// ClientHello is reassembled, and for non-QUIC flows.	COMMENT
LOW	src/collectors/packets/mod.rs	301	/// Count of TCP segments whose seq+len fell entirely behind the	COMMENT
LOW	src/collectors/packets/mod.rs	321	/// the wire. Used by both the TLS 1.3 and TLS 1.2 decrypt paths.	COMMENT
LOW	src/collectors/packets/mod.rs	341	/// already-received bytes). Wireshark's heuristic is similar; 64 KB is a	COMMENT
LOW	src/collectors/packets/mod.rs	781	{	COMMENT
LOW	src/collectors/packets/mod.rs	801	/// pre-handshake records, missing keys, etc.	COMMENT
LOW	src/collectors/packets/mod.rs	921	tracing::debug!(target: "netwatch::dpi::tls_decrypt", stream_index, client_to_server, "TLS K	COMMENT
LOW	src/collectors/packets/filter.rs	21	AppProto(String),	COMMENT
LOW	src/platform/macos.rs	121	/// Map BSD device name (e.g. `en0`, `en7`) to whether it's a Wi-Fi adapter.	COMMENT
LOW	src/platform/pktap.rs	1	// macOS PKTAP-based per-packet process attribution.	COMMENT
LOW	src/platform/pktap.rs	381	// offset size field	COMMENT
LOW	src/dpi/stun.rs	1	//! STUN — RFC 5389 (used by WebRTC, VoIP NAT traversal).	COMMENT
LOW	src/dpi/ja4_db.rs	1	//! JA4 → client-name lookup database.	COMMENT
LOW	src/dpi/ja4_db.rs	21	//!	COMMENT
LOW	src/dpi/http3.rs	1	//! HTTP/3 body extraction + decompression for decrypted QUIC 1-RTT	COMMENT
LOW	src/dpi/http3.rs	341	/// byte streams — request (c→s) and response (s→c) — each with its own offset	COMMENT
LOW	src/dpi/quic.rs	1	//! QUIC classifier — detects QUIC v1 Initial packets and attempts SNI	COMMENT
LOW	src/dpi/quic.rs	21	//! as QUIC v1 Initial but anything downstream fails (key derivation,	COMMENT
LOW	src/dpi/dns.rs	1	//! DNS classifier — extracts the first question's qname + qtype.	COMMENT
LOW	src/dpi/mod.rs	1	//! Deep packet inspection — application-layer protocol classification.	COMMENT
LOW	src/dpi/mod.rs	41	/// real destination is hidden from the network. We can't distinguish	COMMENT
28 more matches not shown…

AI Slop Vocabulary5 hits · 18 pts

Severity	File	Line	Snippet	Context
MEDIUM	scripts/verify-tls12-decrypt.sh	7	# harness against live traffic, across every AEAD suite we support, plus a	COMMENT
MEDIUM⚡	scripts/verify-tls12-decrypt.sh	48	# ── Build the harness once ──────────────────────────────────────────────────	COMMENT
MEDIUM⚡	scripts/verify-tls12-decrypt.sh	58	# ── Run one scenario; classify the harness output ───────────────────────────	COMMENT
MEDIUM	src/collectors/incident.rs	117	/// robust to `alert_history` being a bounded ring buffer: once it hits	COMMENT
MEDIUM	src/collectors/quic.rs	292	// be robust to multi-frame layouts in the same packet.	COMMENT

Excessive Try-Catch Wrapping6 hits · 6 pts

Severity	File	Line	Snippet	Context
LOW	examples/tls12_decrypt_live.rs	93	except Exception:	CODE
LOW	examples/tls12_decrypt_live.rs	98	except Exception: pass	CODE
LOW	examples/tls_decrypt_live.rs	83	except Exception:	CODE
LOW	examples/tls_decrypt_live.rs	88	except Exception: pass	CODE
LOW	scripts/demo/gen_tls12.py	34	except Exception as e:	CODE
LOW	scripts/demo/gen_tls12.py	40	except Exception:	CODE

Example Usage Blocks1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	scripts/verify-tls12-decrypt.sh	10	# Usage:	COMMENT

Unused Imports1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	scripts/demo/gen_tls12.py	9		CODE

Analysis Overview

What These Metrics Mean

Score History

Severity Breakdown

Directory Score Breakdown

Pattern Findings