Repository Analysis

QuipNetwork/quip-node-manager

A simple GUI client to manage a Quip Network node

17.7 Moderate AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of QuipNetwork/quip-node-manager, a Rust project with 5,492 GitHub stars. SynthScan v2.0 examined 22,730 lines of code across 49 source files, recording 177 pattern matches distributed across 5 syntactic categories. The overall adjusted score of 17.7 places this repository in the Moderate 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).

17.7
Adjusted Score
17.7
Raw Score
100%
Time Factor
2026-08-13
Last Push
5.5K
Stars
Rust
Language
22.7K
Lines of Code
49
Files
177
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 128LOW 49

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 177 distinct pattern matches across 5 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 Separators126 hits · 350 pts
SeverityFileLineSnippetContext
MEDIUM.gitlab-ci.yml15# ---------------------------------------------------------------------------COMMENT
MEDIUM.gitlab-ci.yml17# ---------------------------------------------------------------------------COMMENT
MEDIUM.gitlab-ci.yml41# ---------------------------------------------------------------------------COMMENT
MEDIUM.gitlab-ci.yml43# ---------------------------------------------------------------------------COMMENT
MEDIUM.gitlab-ci.yml72# ---------------------------------------------------------------------------COMMENT
MEDIUM.gitlab-ci.yml74# ---------------------------------------------------------------------------COMMENT
MEDIUM.gitlab-ci.yml95# ---------------------------------------------------------------------------COMMENT
MEDIUM.gitlab-ci.yml97# ---------------------------------------------------------------------------COMMENT
MEDIUM.gitlab-ci.yml143# ---------------------------------------------------------------------------COMMENT
MEDIUM.gitlab-ci.yml145# ---------------------------------------------------------------------------COMMENT
MEDIUM.gitlab-ci.yml172# ---------------------------------------------------------------------------COMMENT
MEDIUM.gitlab-ci.yml174# ---------------------------------------------------------------------------COMMENT
MEDIUMscripts/install.sh13# ── Detect platform ──────────────────────────────────────────────────────────COMMENT
MEDIUMscripts/install.sh29# ── Fetch latest release tag ────────────────────────────────────────────────COMMENT
MEDIUMscripts/install.sh35# ── Build artifact URL ──────────────────────────────────────────────────────COMMENT
MEDIUMscripts/install.sh49# ── Download ────────────────────────────────────────────────────────────────COMMENT
MEDIUMscripts/install.sh55# ── Install ─────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/tui_ui.rs471// ─── Log panel (bottom drawer) ────────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/tui_ui.rs519// ─── Footer ───────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/tui_ui.rs529// ─── Widget helpers ───────────────────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/cmd.rs19// ── known tool-install directories (safety net) ───────────────────────────COMMENT
MEDIUMsrc-tauri/src/cmd.rs60// ── login-shell PATH discovery ─────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/cmd.rs120// ── manual override (modal / settings integration point) ──────────────────COMMENT
MEDIUMsrc-tauri/src/cmd.rs139// ── PATH assembly + cache ─────────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/cmd.rs185// ── public command constructor ─────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/lib.rs124 // ── One-time cleanup of pre-v0.2 native binaries ──────COMMENT
MEDIUMsrc-tauri/src/lib.rs131 // ── System tray ──────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/lib.rs235 // ── Background update monitor ────────────────────────COMMENT
MEDIUMsrc-tauri/src/lib.rs239 // ── Node health monitor (15 s poll loop) ─────────────COMMENT
MEDIUMsrc-tauri/src/compose.rs30// ── logging helpers (moved verbatim from docker.rs) ────────────────────────COMMENT
MEDIUMsrc-tauri/src/compose.rs66// ── host uid/gid (moved verbatim from docker.rs) ───────────────────────────COMMENT
MEDIUMsrc-tauri/src/compose.rs89// ── profile + services selection ───────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/compose.rs131// ── compose command builder ────────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/compose.rs191// ── postgres identity ──────────────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/compose.rs207// ── .env generation ────────────────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/compose.rs355// ── streaming compose output ───────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/compose.rs491// ── image registry paths ───────────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/compose.rs515// ── Tauri commands ─────────────────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/checklist.rs12// ─── Types ────────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/checklist.rs81// ─── Shared state ─────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/checklist.rs119// ─── Per-check context ────────────────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/checklist.rs186// ─── Low-level probes ─────────────────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/checklist.rs599// ─── public_host start precondition ───────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/checklist.rs669// ─── Check registry ───────────────────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/checklist.rs763// ─── Per-check async runners ──────────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/checklist.rs1064// ─── Event emission ───────────────────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/checklist.rs1104// ─── Recheck dispatcher ───────────────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/checklist.rs1204// ─── Tauri commands ───────────────────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/checklist.rs1235// ─── TUI helpers ──────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/update.rs148// ── Update channel resolution ──────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/update.rs333// ── Shared update-check path (periodic monitor + manual button) ────────────COMMENT
MEDIUMsrc-tauri/src/log_stream.rs203// ─── File tailing ────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/log_stream.rs273// ─── Multi-source fan-in ─────────────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/log_stream.rs412// ─── Public API ──────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/log_stream.rs488 // ── parse_compose_prefix ───────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/log_stream.rs524 // ── map_compose_service_to_source ──────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/log_stream.rs576 // ── entry_from_compose_line (prefix + last-source carry) ───────────────COMMENT
MEDIUMsrc-tauri/src/log_stream.rs613 // ── parse_log_line ─────────────────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/validator_rpc.rs47// ── Task 3: read-only JSON-RPC client ────────────────────────────────────────COMMENT
MEDIUMsrc-tauri/src/validator_rpc.rs146// ── Task 4: Account id from keystore ─────────────────────────────────────────COMMENT
66 more matches not shown…
Over-Commented Block38 hits · 36 pts
SeverityFileLineSnippetContext
LOW.gitlab-ci.yml41# ---------------------------------------------------------------------------COMMENT
LOWsrc-tauri/src/stack_assets.rs1// SPDX-License-Identifier: AGPL-3.0-or-laterCOMMENT
LOWsrc-tauri/src/stack_assets.rs21//! `config::FAUCET_URL` in the rendered config.toml.COMMENT
LOWsrc-tauri/src/stack_assets.rs61COMMENT
LOWsrc-tauri/src/stack_assets.rs81COMMENT
LOWsrc-tauri/src/native.rs81/// itself, per the `[cpu]`/`[metal]` sections of the config it is given.COMMENT
LOWsrc-tauri/src/native.rs621/// most recent release that ships this platform's asset, so release-candidateCOMMENT
LOWsrc-tauri/src/native.rs861 let msg = start_native_node_core(Arc::clone(&sink), &state).await?;COMMENT
LOWsrc-tauri/src/native.rs1101 let rc_app = app.clone();COMMENT
LOWsrc-tauri/src/registry.rs1// SPDX-License-Identifier: AGPL-3.0-or-laterCOMMENT
LOWsrc-tauri/src/config.rs1// SPDX-License-Identifier: AGPL-3.0-or-laterCOMMENT
LOWsrc-tauri/src/config.rs81///COMMENT
LOWsrc-tauri/src/cmd.rs1// SPDX-License-Identifier: AGPL-3.0-or-laterCOMMENT
LOWsrc-tauri/src/compose.rs201/// and we run under `--project-name quip` with a `pgdata` volume key (the fixedCOMMENT
LOWsrc-tauri/src/compose.rs341COMMENT
LOWsrc-tauri/src/compose.rs361/// How to surface a compose command's output.COMMENT
LOWsrc-tauri/src/compose.rs661 _ => {}COMMENT
LOWsrc-tauri/src/compose.rs681#[tauri::command]COMMENT
LOWsrc-tauri/src/compose.rs941 }COMMENT
LOWsrc-tauri/src/compose.rs1021/// destroy containers; recreating from a clean slate is the Start path's jobCOMMENT
LOWsrc-tauri/src/compose.rs1041}COMMENT
LOWsrc-tauri/src/checklist.rs301/// Outcome of `probe_port_forwarding`. v0.2 uses `checkport` TCP probes forCOMMENT
LOWsrc-tauri/src/checklist.rs341/// the host at all" from "host responded, just not as expected" and fromCOMMENT
LOWsrc-tauri/src/checklist.rs361///COMMENT
LOWsrc-tauri/src/checklist.rs681 "port-validator",COMMENT
LOWsrc-tauri/src/migration_v2.rs181/// v0.1 native-mode node artifacts that live alongside manager state in theCOMMENT
LOWsrc-tauri/src/update.rs101 name: String,COMMENT
LOWsrc-tauri/src/update.rs141/// `rc.2` → 2). Used only to order pre-releases against each other; theCOMMENT
LOWsrc-tauri/src/log_stream.rs341fn stream_compose_all<F>(stop: &Arc<Mutex<bool>>, child_pid: &Arc<Mutex<Option<u32>>>, emit: Arc<F>)COMMENT
LOWsrc-tauri/src/progress.rs1// SPDX-License-Identifier: AGPL-3.0-or-laterCOMMENT
LOWsrc-tauri/src/tui_app.rs701 /// This MUST be derived rather than stored. `FormState.image_tag` used toCOMMENT
LOWsrc-tauri/src/settings.rs21 }COMMENT
LOWsrc-tauri/src/settings.rs221 // NetworkCOMMENT
LOWsrc-tauri/src/settings.rs281COMMENT
LOWsrc-tauri/src/network.rs1// SPDX-License-Identifier: AGPL-3.0-or-laterCOMMENT
LOWsrc/app.js41 // debounced value used for matching so typing does not thrash the DOM.COMMENT
LOWsrc/app.js261 // would otherwise override `hidden` and keep both elements visible.COMMENT
LOWsrc/app.js901 sub.textContent = 'Node not running';COMMENT
Structural Annotation Overuse6 hits · 9 pts
SeverityFileLineSnippetContext
LOWOSX.md18## Step 1: Create a Developer ID CertificateCOMMENT
LOWOSX.md37## Step 2: Build the AppCOMMENT
LOWOSX.md52## Step 3: Code Sign the App BundleCOMMENT
LOWOSX.md76## Step 4: Create a DMGCOMMENT
LOWOSX.md96## Step 5: Notarize the DMGCOMMENT
LOWOSX.md119## Step 6: Staple the Notarization TicketCOMMENT
Modern AI Meta-Vocabulary2 hits · 4 pts
SeverityFileLineSnippetContext
MEDIUMAGENTS.md46 ├── compose.rs # docker compose orchestration: miner +CODE
MEDIUMdocs/superpowers/plans/2026-07-04-tui-gui-parity.md7**Architecture:** The GUI's orchestration functions (`start_stack`, `stop_stack`, `pull_compose_images`, `start_native_nCODE
Hyper-Verbose Identifiers5 hits · 2 pts
SeverityFileLineSnippetContext
LOWsrc/app.js95function dashboardHostnameForSettings(settings) {CODE
LOWsrc/app.js1181function allLogEntriesInArrivalOrder() {CODE
LOWsrc/app.js1230function updateLogFilterClearButton() {CODE
LOWsrc/app.js1325function scheduleLogTextFilterApply() {CODE
LOWsrc/app.js1596function handleBinaryDownloadProgress(ev) {CODE