Repository Analysis

quickshell-mirror/quickshell

Flexible toolkit for making desktop shells with QtQuick, for Wayland and X11

5.8 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of quickshell-mirror/quickshell, a C++ project with 2,654 GitHub stars. SynthScan v2.0 examined 63,984 lines of code across 535 source files, recording 369 pattern matches distributed across 1 syntactic category. The overall adjusted score of 5.8 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.8
Adjusted Score
5.8
Raw Score
100%
Time Factor
2026-07-10
Last Push
2.7K
Stars
C++
Language
64.0K
Lines of Code
535
Files
369
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 0LOW 369

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 369 distinct pattern matches across 1 syntactic category. 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 Block369 hits · 369 pts
SeverityFileLineSnippetContext
LOWsrc/core/elapsedtimer.hpp1#pragma onceCOMMENT
LOWsrc/core/region.hpp1#pragma onceCOMMENT
LOWsrc/core/region.hpp61 /// Defaults to 0. Does nothing if @@item is set.COMMENT
LOWsrc/core/region.hpp81 /// Defaults to @@radius, and may be reset by assigning `undefined`.COMMENT
LOWsrc/core/variants.cpp1#include "variants.hpp"COMMENT
LOWsrc/core/popupanchor.hpp1#pragma onceCOMMENT
LOWsrc/core/popupanchor.hpp21#include "doc.hpp"COMMENT
LOWsrc/core/popupanchor.hpp81 /// The item to anchor / attach the popup to. Setting this property unsets @@window.COMMENT
LOWsrc/core/popupanchor.hpp101 ///COMMENT
LOWsrc/core/toolsupport.cpp1#include "toolsupport.hpp"COMMENT
LOWsrc/core/doc.hpp1#pragma onceCOMMENT
LOWsrc/core/colorquantizer.hpp1#pragma onceCOMMENT
LOWsrc/core/transformwatcher.hpp1#pragma onceCOMMENT
LOWsrc/core/transformwatcher.hpp21class TransformWatcher: public QObject {COMMENT
LOWsrc/core/scan.cpp1#include "scan.hpp"COMMENT
LOWsrc/core/logging.cpp1#include "logging.hpp"COMMENT
LOWsrc/core/logging.cpp21#include <qpair.h>COMMENT
LOWsrc/core/boundcomponent.cpp1#include "boundcomponent.hpp"COMMENT
LOWsrc/core/qmlglobal.hpp1#pragma onceCOMMENT
LOWsrc/core/qmlglobal.hpp81COMMENT
LOWsrc/core/qmlglobal.hpp101 Q_PROPERTY(QDateTime launchTime READ launchTime CONSTANT)COMMENT
LOWsrc/core/qmlglobal.hpp121 /// As screens are added or removed your window will be created or destroyed on those screens.COMMENT
LOWsrc/core/qmlglobal.hpp141 /// The per-shell data directory.COMMENT
LOWsrc/core/qmlglobal.hpp181 Q_INVOKABLE void reload(bool hard);COMMENT
LOWsrc/core/qmlglobal.hpp201 /// > e.g. `["sh", "script.sh"]` instead of `["script.sh"]` unless the scriptCOMMENT
LOWsrc/core/qmlglobal.hpp221 Q_INVOKABLE static QString iconPath(const QString& icon, bool check);COMMENT
LOWsrc/core/qmlglobal.hpp241 Q_INVOKABLE void inhibitReloadPopup() { this->mInhibitReloadPopup = true; }COMMENT
LOWsrc/core/logging_qtprivate.cpp1// The logging rule parser from qloggingregistry_p.h and qloggingregistry.cpp.COMMENT
LOWsrc/core/qsintercept.cpp1#include "qsintercept.hpp"COMMENT
LOWsrc/core/scriptmodel.cpp1#include "scriptmodel.hpp"COMMENT
LOWsrc/core/incubator.cpp1#include "incubator.hpp"COMMENT
LOWsrc/core/retainable.hpp1#pragma onceCOMMENT
LOWsrc/core/retainable.hpp41 /// and it will not be unlocked until the same number of unlocks as locks have occurred.COMMENT
LOWsrc/core/retainable.hpp101 bool retaining = false;COMMENT
LOWsrc/core/lazyloader.hpp1#pragma onceCOMMENT
LOWsrc/core/lazyloader.hpp21/// load synchronously so windows can be reused.COMMENT
LOWsrc/core/lazyloader.hpp41/// left: trueCOMMENT
LOWsrc/core/lazyloader.hpp61///COMMENT
LOWsrc/core/lazyloader.hpp81/// >COMMENT
LOWsrc/core/lazyloader.hpp101 /// If the component is not loaded, setting this property to true will startCOMMENT
LOWsrc/core/desktopentry.cpp1#include "desktopentry.hpp"COMMENT
LOWsrc/core/easingcurve.hpp1#pragma onceCOMMENT
LOWsrc/core/model.hpp1#pragma onceCOMMENT
LOWsrc/core/model.hpp21/// components that act on models. It has a single role named `modelData`, to match theCOMMENT
LOWsrc/core/generation.hpp1#pragma onceCOMMENT
LOWsrc/core/platformmenu.hpp1#pragma onceCOMMENT
LOWsrc/core/qsmenu.hpp1#pragma onceCOMMENT
LOWsrc/core/qsmenu.hpp61 ///COMMENT
LOWsrc/core/debuginfo.cpp1#include "debuginfo.hpp"COMMENT
LOWsrc/core/iconprovider.cpp1#include "iconprovider.hpp"COMMENT
LOWsrc/core/clock.hpp1#pragma onceCOMMENT
LOWsrc/core/clock.hpp21/// @@QtQuick.Text {COMMENT
LOWsrc/core/qmlscreen.hpp1#pragma onceCOMMENT
LOWsrc/core/lazyloader.cpp1#include "lazyloader.hpp"COMMENT
LOWsrc/core/desktopentry.hpp1#pragma onceCOMMENT
LOWsrc/core/desktopentry.hpp61 /// If true, this application should not be displayed in menus and launchers.COMMENT
LOWsrc/core/desktopentry.hpp181 Q_PROPERTY(QString icon READ default WRITE default NOTIFY iconChanged BINDABLE bindableIcon);COMMENT
LOWsrc/core/generation.cpp1#include "generation.hpp"COMMENT
LOWsrc/core/platformmenu.cpp1#include "platformmenu.hpp"COMMENT
LOWsrc/core/persistentprops.hpp1#pragma onceCOMMENT
309 more matches not shown…