Repository Analysis

noah-nuebling/mac-mouse-fix

Mac Mouse Fix - Make Your $10 Mouse Better Than an Apple Trackpad!

6.1 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of noah-nuebling/mac-mouse-fix, a Objective-C project with 10,429 GitHub stars. SynthScan v2.0 examined 152,932 lines of code across 780 source files, recording 853 pattern matches distributed across 8 syntactic categories. The overall adjusted score of 6.1 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).

6.1
Adjusted Score
6.1
Raw Score
100%
Time Factor
2026-07-14
Last Push
10.4K
Stars
Objective-C
Language
152.9K
Lines of Code
780
Files
853
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 1HIGH 1MEDIUM 33LOW 818

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 853 distinct pattern matches across 8 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 Block786 hits · 774 pts
SeverityFileLineSnippetContext
LOWXCStringsDummyApp/AppDelegate.h1//COMMENT
LOWXCStringsDummyApp/main.m1//COMMENT
LOWApp/AppDelegate.h1//COMMENT
LOWApp/AppState.h1//COMMENT
LOWApp/AppDelegate.m1//COMMENT
LOWApp/AppDelegate.m161COMMENT
LOWApp/AppState.m1//COMMENT
LOWApp/UI/Unused/Overrides/OverridePanel.m21#import "OverridePanel.h"COMMENT
LOWApp/UI/UIExtensions/NSBox+Additions.m1//COMMENT
LOWApp/UI/UIExtensions/NSColor+Additions.m1//COMMENT
LOWApp/UI/UIExtensions/NSBox+Additions.h1//COMMENT
LOWApp/UI/UIExtensions/CoolNSTextField.swift81 configureForAttributedString()COMMENT
LOWApp/UI/UIExtensions/NSTextField+Additions.m1//COMMENT
LOWApp/UI/UIExtensions/NSTextField+Additions.m21// NSLigatureAttributeName: NSNull.null,COMMENT
LOWApp/UI/UIExtensions/NSTextField+Additions.m61 NSFontAttributeName: self.font,COMMENT
LOWApp/UI/LicenseSheet/LicenseSheetController.swift81 /// Server validationCOMMENT
LOWApp/UI/LicenseSheet/LicenseSheetController.swift101 /// Determine if this is a licenseKey *activation* or just a *check*COMMENT
LOWApp/UI/LicenseSheet/LicenseSheetController.swift281 /// Define errorsCOMMENT
LOWApp/UI/Main/TabViewController.swift1//COMMENT
LOWApp/UI/Main/TabViewController.swift21/// - Update: [Sep 2025] You can actually easily define the views in code while still using a StoryboardCOMMENT
LOWApp/UI/Main/TabViewController.swift281 ///COMMENT
LOWApp/UI/Main/TabViewController.swift521 /// Zoom outCOMMENT
LOWApp/UI/Main/ResizingTabWindow.swift161 /// Get position deltaCOMMENT
LOWApp/UI/Main/ResizingTabWindow.swift181 /// Get animation duration for position deltaCOMMENT
LOWApp/UI/Main/Tabs/GeneralTabController.swift101 /// Due to this, the instructions on the `enable-timeout-toast` and the `is-strange-helpCOMMENT
LOWApp/UI/Main/Tabs/GeneralTabController.swift241 /// Notes:COMMENT
LOWApp/UI/Main/Tabs/GeneralTabController.swift261// guard let window = MainAppState.shared.window else { return }COMMENT
LOWApp/UI/Main/Tabs/AboutTabController.swift101 /// The manager swaps out the trialSection and stuff, so always access the trialSection through the manager!COMMENT
LOWApp/UI/Main/Tabs/ScrollTabController.swift121 /// Notes:COMMENT
LOWApp/UI/Main/Tabs/ScrollTabController.swift181 /// Create explicit width constraints, that match the natural width of the preciseSectionCOMMENT
LOWApp/UI/Main/Tabs/TabControllerUtility.swift1//COMMENT
LOWApp/UI/Main/Tabs/TabControllerUtility.swift21 /// Problem: But that means localizers need to 'design' the tab width – but without being able to see what tCOMMENT
LOWApp/UI/Main/Tabs/ButtonTab/ButtonTabController.swift1//COMMENT
LOWApp/UI/Main/Tabs/ButtonTab/ButtonTabController.swift261 do {COMMENT
LOWApp/UI/Main/Tabs/ButtonTab/ButtonTabController.swift301 /// Notes:COMMENT
LOWApp/UI/Main/Tabs/ButtonTab/ButtonTabController.swift501 COMMENT
LOWApp/UI/Main/Tabs/ButtonTab/AddField.swift1//COMMENT
LOWApp/UI/Main/Tabs/ButtonTab/AddField.swift21 /// StorageCOMMENT
LOWApp/UI/Main/Tabs/ButtonTab/AddField.swift61 }COMMENT
LOWApp/UI/Main/Tabs/ButtonTab/AddField.swift81 /// -> Almost works but also doesn't support wallpaper tinting.COMMENT
LOWApp/UI/Main/Tabs/ButtonTab/AddField.swift241 /// Animation curveCOMMENT
LOWApp/UI/Main/Tabs/ButtonTab/AddField_New.swift1//COMMENT
LOWApp/UI/Main/Tabs/ButtonTab/AddField_New.swift21COMMENT
LOWApp/UI/Main/Tabs/ButtonTab/AddField_New.swift41/// -> Too complicated (See 35742760e0bb0c126e16183f11f65532953822cb)COMMENT
LOWApp/UI/Main/Tabs/ButtonTab/AddField_New.swift61/// (found them by searching for 'background', maybe there are more)COMMENT
LOWApp/UI/Main/Tabs/ButtonTab/AddField_New.swift181 let transformAnimation = playAcceptAnimation ? bounceAnimation : animationCOMMENT
LOW…/UI/Main/Tabs/ButtonTab/RemapTable/RemapTableUtility.h1//COMMENT
LOW…/Main/Tabs/ButtonTab/RemapTable/RemapTableController.h1//COMMENT
LOW…/Main/Tabs/ButtonTab/RemapTable/RemapTableTranslator.h1//COMMENT
LOW…UI/Main/Tabs/ButtonTab/RemapTable/RemapTableCellView.m1//COMMENT
LOW…/Main/Tabs/ButtonTab/RemapTable/RemapTableController.m1//COMMENT
LOW…/Main/Tabs/ButtonTab/RemapTable/RemapTableController.m21#import "UIStrings.h"COMMENT
LOW…/Main/Tabs/ButtonTab/RemapTable/RemapTableController.m441// NSMutableArray *result = [NSMutableArray array];COMMENT
LOW…/UI/Main/Tabs/ButtonTab/RemapTable/RemapTableUtility.m1//COMMENT
LOW…/UI/Main/Tabs/ButtonTab/RemapTable/RemapTableUtility.m101 return groupedModelIndex - groupRowCtr;COMMENT
LOW…/UI/Main/Tabs/ButtonTab/RemapTable/RemapTableUtility.m121 ///COMMENT
LOWApp/UI/Main/Tabs/ButtonTab/RemapTable/MFScrollView.m1//COMMENT
LOWApp/UI/Main/Tabs/ButtonTab/RemapTable/MFScrollView.m21 COMMENT
LOWApp/UI/Main/Tabs/ButtonTab/RemapTable/MFScrollView.m41// NSBezierPath * clipPath = [NSBezierPath bezierPathWithRect:outerRect];COMMENT
LOWApp/UI/Main/Tabs/ButtonTab/RemapTable/RemapTableView.m1//COMMENT
726 more matches not shown…
AI Slop Vocabulary33 hits · 92 pts
SeverityFileLineSnippetContext
MEDIUMApp/UI/Unused/Overrides/OverridePanel.m339 [self loadTableViewDataModelFromConfig]; // At the time of writing: not necessary. Not sure if useful. Might make thCODE
MEDIUMApp/UI/UIExtensions/CoolNSTextField.swift167 /// -> I have a suspicion, that this is not the case on older OSs / other systems, based on what I read on SCOMMENT
MEDIUMApp/UI/Main/Tabs/TabControllerUtility.swift87 /// Before, I used `lessThanOrEqualToConstant:` instead of `equalToConstant:` to make things more robustCOMMENT
MEDIUMApp/UI/Main/Tabs/ButtonTab/AddField.swift91 /// -> Since this is what NSBox does natively (See above), it may be the most robust approach.COMMENT
MEDIUMApp/UI/Main/Tabs/ButtonTab/AddField_New.swift53/// -> Since this is what NSBox does natively (See above), it may be the most robust approach.COMMENT
MEDIUM…/Main/Tabs/ButtonTab/RemapTable/RemapTableController.m175 [self.tableView reloadDataForRowIndexes:[NSIndexSet indexSetWithIndex:row] columnIndexes:[NSIndexSet indexSetWitCODE
MEDIUMApp/Update/SparkleUpdaterController.m317 /// -> This edge case seems very unlikely now that I think about it, but there's always going to be someone COMMENT
MEDIUMApp/Update/SparkleUpdaterController.m357 /// It might be more robust and simple to find and kill any strange helpers *whenever* the app starts, but this shouCOMMENT
MEDIUMShared/Strings/MarkdownParser/MarkdownParser.m505 if (starti == -1 || endi == -1) return NSMakeRange(NSNotFound, 0); /// Not sure this `NSNotFound` error handlingCODE
MEDIUMShared/Locator/Locator.m133 /// ^ I thought this would be very robust, but this stuff fails after moving the app.COMMENT
MEDIUMShared/License/Retrieve/APIRequests.swift17 /// Essentially, we send a json dict to a URL, and get a json dict backCOMMENT
MEDIUMShared/Config/Config.m12/// - We're using our custom coolKeyPath API all over this class, instead of Apple's key-value-coding API (aka KVC) (SeeCOMMENT
MEDIUMShared/HelperServices/HelperServices.m154 /// Update: [Sep 2025] Apple did fix things in macOS 15.0 Sequoia! We're also unregistering strange COMMENT
MEDIUMShared/HelperServices/HelperServices.m203 /// - We could only do this only if strangeHelperIsRegisteredWithLaunchd, but users have been having some weCOMMENT
MEDIUMShared/HelperServices/HelperServices.m471 /// - From my testing this does the same as the `bootout` command, but it doesn't rely on a valid launchd.plist fileCOMMENT
MEDIUMShared/Animation/DynamicSystemAnimator.swift183 /// This feels weird and too slow. Definitely incorrectCOMMENT
MEDIUMShared/Devices/Device.m126 /// Could probably also just count the number elements instead of this. But this might be more robust.COMMENT
MEDIUMShared/Utility/MFDataClass.m514 /// - [Oct 2024] Immutable values can just return themselves instead of a copy and noone will notice. Could we deterCOMMENT
LOWShared/Utility/Unused/DerivedProperty.swift155/// Actually, this won't work with static properties, either, because keyPaths don't work for static properties 😑. At leCOMMENT
MEDIUMShared/Utility/MFCoding/MFCoding.m55/// So it's inconsistent and less robust compared to using `.raiseException`COMMENT
MEDIUMShared/Utility/MFCoding/MFCoding.m270 ((NSKeyedUnarchiver *)decoder).decodingFailurePolicy = NSDecodingFailurePolicyRaiseException; /// Use old-schoolCODE
MEDIUMShared/Utility/MFCoding/MFCoding.m334/// Using a dictionary archive might also be less robust than the alternatives, since I think the dict's key ordCOMMENT
MEDIUMShared/Utility/MFCoding/MFCoding.m335/// ... Yeah I think We should probably stick to the standard binary/xmlString formats for the archive - until wCOMMENT
MEDIUMHelper/UNIXSignals.m196 /// (Update 30.09.2024: Since we're only handling simple termination signals now (SIGTERM, SIGINT, SIGHUP), exitCOMMENT
MEDIUMHelper/Core/Modifiers/Modifiers.m182 /// 4. We could add an 'accessibilityAccessEnabled state to the SwitchMaster, and make it so that, when there's COMMENT
MEDIUMHelper/Core/Buttons/ClickCycle.swift19/// - Edit: IIRC we're just not implementing the dispatchQueue stuff properly because race conditions are incredibly rarCOMMENT
MEDIUMHelper/Core/Scroll/Scroll.m1011 /// [Jul 2025] Simulating the tap shouldn't usually be necessary for kMFAnimationCallbackPhaseEnd, sCOMMENT
MEDIUMHelper/Core/Touch/TouchAnimatorBase.swift202 /// Orrr we can also have self.isRunning() execute on self.queue. - we did that. Should be most robust sCOMMENT
MEDIUMHelper/Core/Config/ScrollConfig.swift628 /// Conclusion: You can use 0.001 as the 'defaultEpsilon'. it has no overhead and might makeCOMMENT
MEDIUMHelper/Utility/EventUtility.m46 /// - In `ButtonInputReceiver.m` I also discuss the idea of just filtering events based on attachedDevices –COMMENT
MEDIUMHelper/Utility/PointerFreeze.m141 /// Not sure why this happens. But adding a delay of 0.02 before hiding makes it look seamless.COMMENT
MEDIUMLocalization/Screenshots/AnnotationUtility.h20 __builtin_return_address(0) /// If this fails, `backtrace()` should be more robustCODE
MEDIUMLocalization/Screenshots/AnnotationUtility.m403 /// Not sure this is even slower than the main approach. (If not then this should be the main approach) Should be moCOMMENT
Example Usage Blocks14 hits · 21 pts
SeverityFileLineSnippetContext
LOWLocalizationScreenshotTaker/XCUIElement+Additions.h88/// Usage example:COMMENT
LOWShared/Extensions/NSImage+Additions.m145 /// Usage example:COMMENT
LOWShared/Utility/Links.m125 /// Usage example:COMMENT
LOWShared/Utility/Macros/SharedMacros.h68/// Usage example:COMMENT
LOWShared/Utility/Macros/SharedMacros.h76/// Usage example:COMMENT
LOWShared/Utility/Macros/SharedMacros.h119/// Example usage:COMMENT
LOWShared/Utility/Macros/SharedMacros.h146/// Example usage:COMMENT
LOWShared/Utility/Macros/SharedMacros.h198/// Example usage:COMMENT
LOWShared/Utility/Macros/SharedMacros.h304/// Example usage:COMMENT
LOWShared/Utility/Macros/SharedMacros.h412/// Usage example:COMMENT
LOWShared/Utility/Macros/SharedMacros.h456/// Example usage:COMMENT
LOWShared/Utility/Macros/SharedMacros.h519 /// Example usage:COMMENT
LOWShared/Utility/Macros/SharedMacros.h540 /// Example usage:COMMENT
LOWShared/Utility/Macros/MFDefer.h13/// Usage example:COMMENT
Slop Phrases11 hits · 18 pts
SeverityFileLineSnippetContext
LOWApp/UI/Main/Tabs/ButtonTab/ButtonTabController.swift314 /// - If you implement this don't forget to consider making this escape-dismissable, like most other sheetsCOMMENT
MEDIUM…/UI/Main/Tabs/ButtonTab/RemapTable/RemapTableUtility.m128 /// - Based on this, I think it does make sense to maybe extend the simple explanation from what wasCOMMENT
LOWApp/UI/Notifications/Toasts/LicenseToasts.swift74 /// We added this localizedStringKey on the master branch inside .strings files, while we alCOMMENT
LOWShared/License/License.m157 /// - All other properties should be checked - don't forget to update this when adding new properties!COMMENT
LOWShared/License/License.m199 if (info.class == MFLicenseTypeInfoGumroadBusinessV1.class) return NO; /// Don't forget to add definitions hereCODE
LOWShared/Extensions/NSImage+Additions.m35 /// The r, g, and b values are *premultiplied* with the alpha value. So if you want to change a, don't forget to alsCOMMENT
LOWShared/Utility/MFDataClass.m565 /// If you override this with an NSArray of propertyValues, don't forget to substitute nil values with `[NSNCOMMENT
LOWShared/Utility/Macros/ListOperations.h266/// (a): Stores the mapping result in newly allocated memory on the heap. (Use this for C types) (Don't forgCOMMENT
LOWShared/Utility/Macros/ListOperations.h305#define mapa(src, count, varname, transform...) ({ /** (a)llocates a new array for the mapped values. Don't forCOMMENT
LOWShared/Utility/MFCoding/NSCoderErrors.m145 /// - Wrap this in a failWithError() macro instead of calling this directly – so you don't forget to return after caCOMMENT
LOWShared/Utility/MFCoding/NSCoderErrors.m170 /// Wrap this in a failWithError() macro instead of calling this directly – so you don't forget to return after COMMENT
Hallucination Indicators1 hit · 10 pts
SeverityFileLineSnippetContext
CRITICAL…alizationScreenshotTaker/LocalizationScreenshots.swift53 var description: String { ScreenshotAndMetadata_description_from_key_value_pairs([("screenshot", screenshot), ("CODE
Verbosity Indicators5 hits · 8 pts
SeverityFileLineSnippetContext
LOWApp/UI/Main/Tabs/AboutTabController.swift118 /// Step 1: Set UI to cacheCOMMENT
LOWApp/UI/Main/Tabs/AboutTabController.swift133 /// Step 2: Get real values and update UICOMMENT
LOWHelper/AccessibilityCheck.m69 /// - We need to launch a new helper instance instead of just using the normal helper instance because `AXIsCOMMENT
LOWHelper/Core/Buttons/ButtonModifiers.m62 /// Do we need to check if the buttonMods actually changed?COMMENT
LOWHelper/Utility/PointerFreeze.m418 /// Since we call sync, we need to check if we're already on main to avoid deadlockCOMMENT
AI Response Leakage1 hit · 8 pts
SeverityFileLineSnippetContext
HIGHHelper/Core/Touch/GestureScrollSimulator.m97 /// Update: [Jul 2025] I've added an assert(false) here. It seems our algorithms don't produce those unwanteCOMMENT
Structural Annotation Overuse2 hits · 3 pts
SeverityFileLineSnippetContext
LOWApp/UI/Main/Tabs/AboutTabController.swift118 /// Step 1: Set UI to cacheCOMMENT
LOWApp/UI/Main/Tabs/AboutTabController.swift133 /// Step 2: Get real values and update UICOMMENT