Repository Analysis

QuipNetwork/quip-protocol-rs

A rust implementation of the Quip Protocol forked from Substrate

5.4 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of QuipNetwork/quip-protocol-rs, a Rust project with 5,653 GitHub stars. SynthScan v2.0 examined 16,823 lines of code across 89 source files, recording 76 pattern matches distributed across 6 syntactic categories. The overall adjusted score of 5.4 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).

5.4
Adjusted Score
5.4
Raw Score
100%
Time Factor
2026-07-04
Last Push
5.7K
Stars
Rust
Language
16.8K
Lines of Code
89
Files
76
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 7LOW 69

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 76 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.

Over-Commented Block66 hits · 66 pts
SeverityFileLineSnippetContext
LOWdocker-compose.yml1# Local dev only. Three Aura validators (Alice/Bob/Charlie) peer over aCOMMENT
LOW.gitlab-ci.yml1# SPDX-License-Identifier: AGPL-3.0-or-laterCOMMENT
LOWcrates/quantum-validation/tests/python_parity.rs1//! Cross-language parity vectors against the Python reference implementation.COMMENT
LOWcrates/quantum-validation/src/packed.rs1//! Bit-packed solution payloads.COMMENT
LOWcrates/quantum-validation/src/lib.rs1//! Deterministic, `no_std` quantum/Ising validation primitives for QUIP.COMMENT
LOWcrates/quantum-validation/src/ising.rs21/// hash of the most recent winning block. Stable across the entire roundCOMMENT
LOWcrates/quantum-validation/src/puzzle_spec.rs21/// Sampling distribution for a single puzzle parameter (h, j, or spin).COMMENT
LOWcrates/quantum-validation/src/validation.rs61}COMMENT
LOWcrates/quantum-validation/src/errors.rs1//! Error types for structural and arithmetic validation failures.COMMENT
LOWcrates/quantum-validation/src/energy.rs1//! Exact Ising energy computation in fixed-point milli precision.COMMENT
LOWcrates/quantum-validation/src/energy.rs81COMMENT
LOW…tes/transaction-crypto/examples/derive_genesis_keys.rs1//! Derive hybrid genesis public material (BABE, GRANDPA, TX account) from aCOMMENT
LOWcrates/transaction-crypto/src/lib.rs1#![cfg_attr(not(feature = "std"), no_std)]COMMENT
LOWcrates/transaction-crypto/src/lib.rs21//! catastrophic silent failure the runtime cannot detect.COMMENT
LOWcrates/transaction-crypto/src/lib.rs61///COMMENT
LOWcrates/transaction-crypto/src/lib.rs141/// runtime verification can:COMMENT
LOWruntime/src/genesis_config_presets.rs1// This file is part of Substrate.COMMENT
LOWruntime/src/lib.rs61// To learn more about runtime versioning, see:COMMENT
LOWruntime/src/benchmarks.rs1// This is free and unencumbered software released into the public domain.COMMENT
LOWruntime/src/apis.rs1// This is free and unencumbered software released into the public domain.COMMENT
LOWruntime/src/configs/mod.rs1// This is free and unencumbered software released into the public domain.COMMENT
LOWruntime/src/configs/mod.rs81COMMENT
LOWruntime/src/configs/mod.rs281 /// does NOT move the rate bands, so revisit both together.COMMENT
LOW.cargo/config.toml1# macOS-only fix for librocksdb-sys + bindgen build:COMMENT
LOWscripts/derive-operator-keys.sh1#!/usr/bin/env bashCOMMENT
LOWpallets/quantum-pow/src/difficulty.rs1use codec::Encode;COMMENT
LOWpallets/quantum-pow/src/difficulty.rs21// `TARGET_PROOF_BLOCKS` is deliberately co-located with the runtime'sCOMMENT
LOWpallets/quantum-pow/src/difficulty.rs41/// `apply_min_adjustment(min_adj=3.0)` (whole energy units -> milli) forCOMMENT
LOWpallets/quantum-pow/src/difficulty.rs61///COMMENT
LOWpallets/quantum-pow/src/difficulty.rs261COMMENT
LOWpallets/quantum-pow/src/difficulty.rs301 }COMMENT
LOWpallets/quantum-pow/src/types.rs1use codec::{Decode, DecodeWithMemTracking, Encode, MaxEncodedLen};COMMENT
LOWpallets/quantum-pow/src/types.rs61}COMMENT
LOWpallets/quantum-pow/src/types.rs161 pub edges: Edges,COMMENT
LOWpallets/quantum-pow/src/lib.rs61COMMENT
LOWpallets/quantum-pow/src/lib.rs121 type Currency: ReservableCurrency<Self::AccountId>;COMMENT
LOWpallets/quantum-pow/src/lib.rs141 #[pallet::constant]COMMENT
LOWpallets/quantum-pow/src/lib.rs181 #[pallet::storage]COMMENT
LOWpallets/quantum-pow/src/lib.rs201COMMENT
LOWpallets/quantum-pow/src/lib.rs221 /// `(last_proof_block_hash, miner, salt)` with BLAKE3, or call theCOMMENT
LOWpallets/quantum-pow/src/lib.rs281 InsufficientDiversity,COMMENT
LOWpallets/quantum-pow/src/lib.rs301 }COMMENT
LOWpallets/quantum-pow/src/lib.rs541 Self::check_spec(&allowed_j_values)?;COMMENT
LOWpallets/quantum-pow/src/lib.rs781 /// 32-byte representation of an account, suitable for use as a fixed-sizeCOMMENT
LOWpallets/quantum-pow/src/lib.rs841 let sorted = AllowedValueSetOf::<T>::try_from(inner)COMMENT
LOWpallets/xqvm/src/weights.rs1COMMENT
LOWpallets/xqvm/src/weights.rs41impl<T: frame_system::Config> crate::WeightInfo for SubstrateWeight<T> {COMMENT
LOWpallets/template/src/lib.rs1//! # Template PalletCOMMENT
LOWpallets/template/src/lib.rs21//!COMMENT
LOWpallets/template/src/lib.rs41COMMENT
LOWpallets/template/src/lib.rs61pub use weights::*;COMMENT
LOWpallets/template/src/lib.rs81 #[pallet::config]COMMENT
LOWpallets/template/src/lib.rs101 /// documentation for each event field and its parameters is added to a node's metadata so itCOMMENT
LOWpallets/template/src/lib.rs121 /// Errors tell users that something went wrong so it's important that their naming isCOMMENT
LOWpallets/template/src/lib.rs141 /// The [`call_index`] macro is used to explicitlyCOMMENT
LOWpallets/template/src/lib.rs161 Something::<T>::put(something);COMMENT
LOWpallets/template/src/weights.rs1COMMENT
LOWpallets/template/src/weights.rs41/// Weights for pallet_template using the Substrate node and recommended hardware.COMMENT
LOWpallets/quantum-compute-mempool/src/lib.rs61type JobSolutionOf<T> = types::JobSolution<AccountIdOf<T>, BlockNumberOf<T>, SolutionsOf<T>>;COMMENT
LOWpallets/quantum-compute-mempool/src/lib.rs141 #[pallet::constant]COMMENT
6 more matches not shown…
Decorative Section Separators6 hits · 18 pts
SeverityFileLineSnippetContext
MEDIUMpallets/xqvm/src/lib.rs62 // ── Storage ──────────────────────────────────────────────────────────COMMENT
MEDIUMpallets/xqvm/src/lib.rs73 // ── Events ───────────────────────────────────────────────────────────COMMENT
MEDIUMpallets/xqvm/src/lib.rs94 // ── Errors ───────────────────────────────────────────────────────────COMMENT
MEDIUMpallets/xqvm/src/lib.rs137 // ── Extrinsics ───────────────────────────────────────────────────────COMMENT
MEDIUMpallets/xqvm/src/tests.rs21// ── store_program ────────────────────────────────────────────────────────COMMENT
MEDIUMpallets/xqvm/src/tests.rs80// ── execute ──────────────────────────────────────────────────────────────COMMENT
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMscripts/derive-operator-keys.sh75# but we recover it via inspect-node-key below for a robust capture.COMMENT
Example Usage Blocks1 hit · 2 pts
SeverityFileLineSnippetContext
LOWscripts/derive-operator-keys.sh4# Usage:COMMENT
Hyper-Verbose Identifiers1 hit · 1 pts
SeverityFileLineSnippetContext
LOWdocs/quantum-compute-mempool.md231def event_name_from_storage_record(record):CODE
Unused Imports1 hit · 1 pts
SeverityFileLineSnippetContext
LOWscripts/generate_quantum_validation_fixtures.py25CODE