Mac Mouse Fix - Make Your $10 Mouse Better Than an Apple Trackpad!
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).
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.
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.
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.
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.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | XCStringsDummyApp/AppDelegate.h | 1 | // | COMMENT |
| LOW | XCStringsDummyApp/main.m | 1 | // | COMMENT |
| LOW | App/AppDelegate.h | 1 | // | COMMENT |
| LOW | App/AppState.h | 1 | // | COMMENT |
| LOW | App/AppDelegate.m | 1 | // | COMMENT |
| LOW | App/AppDelegate.m | 161 | COMMENT | |
| LOW | App/AppState.m | 1 | // | COMMENT |
| LOW | App/UI/Unused/Overrides/OverridePanel.m | 21 | #import "OverridePanel.h" | COMMENT |
| LOW | App/UI/UIExtensions/NSBox+Additions.m | 1 | // | COMMENT |
| LOW | App/UI/UIExtensions/NSColor+Additions.m | 1 | // | COMMENT |
| LOW | App/UI/UIExtensions/NSBox+Additions.h | 1 | // | COMMENT |
| LOW | App/UI/UIExtensions/CoolNSTextField.swift | 81 | configureForAttributedString() | COMMENT |
| LOW | App/UI/UIExtensions/NSTextField+Additions.m | 1 | // | COMMENT |
| LOW | App/UI/UIExtensions/NSTextField+Additions.m | 21 | // NSLigatureAttributeName: NSNull.null, | COMMENT |
| LOW | App/UI/UIExtensions/NSTextField+Additions.m | 61 | NSFontAttributeName: self.font, | COMMENT |
| LOW | App/UI/LicenseSheet/LicenseSheetController.swift | 81 | /// Server validation | COMMENT |
| LOW | App/UI/LicenseSheet/LicenseSheetController.swift | 101 | /// Determine if this is a licenseKey *activation* or just a *check* | COMMENT |
| LOW | App/UI/LicenseSheet/LicenseSheetController.swift | 281 | /// Define errors | COMMENT |
| LOW | App/UI/Main/TabViewController.swift | 1 | // | COMMENT |
| LOW | App/UI/Main/TabViewController.swift | 21 | /// - Update: [Sep 2025] You can actually easily define the views in code while still using a Storyboard | COMMENT |
| LOW | App/UI/Main/TabViewController.swift | 281 | /// | COMMENT |
| LOW | App/UI/Main/TabViewController.swift | 521 | /// Zoom out | COMMENT |
| LOW | App/UI/Main/ResizingTabWindow.swift | 161 | /// Get position delta | COMMENT |
| LOW | App/UI/Main/ResizingTabWindow.swift | 181 | /// Get animation duration for position delta | COMMENT |
| LOW | App/UI/Main/Tabs/GeneralTabController.swift | 101 | /// Due to this, the instructions on the `enable-timeout-toast` and the `is-strange-help | COMMENT |
| LOW | App/UI/Main/Tabs/GeneralTabController.swift | 241 | /// Notes: | COMMENT |
| LOW | App/UI/Main/Tabs/GeneralTabController.swift | 261 | // guard let window = MainAppState.shared.window else { return } | COMMENT |
| LOW | App/UI/Main/Tabs/AboutTabController.swift | 101 | /// The manager swaps out the trialSection and stuff, so always access the trialSection through the manager! | COMMENT |
| LOW | App/UI/Main/Tabs/ScrollTabController.swift | 121 | /// Notes: | COMMENT |
| LOW | App/UI/Main/Tabs/ScrollTabController.swift | 181 | /// Create explicit width constraints, that match the natural width of the preciseSection | COMMENT |
| LOW | App/UI/Main/Tabs/TabControllerUtility.swift | 1 | // | COMMENT |
| LOW | App/UI/Main/Tabs/TabControllerUtility.swift | 21 | /// Problem: But that means localizers need to 'design' the tab width – but without being able to see what t | COMMENT |
| LOW | App/UI/Main/Tabs/ButtonTab/ButtonTabController.swift | 1 | // | COMMENT |
| LOW | App/UI/Main/Tabs/ButtonTab/ButtonTabController.swift | 261 | do { | COMMENT |
| LOW | App/UI/Main/Tabs/ButtonTab/ButtonTabController.swift | 301 | /// Notes: | COMMENT |
| LOW | App/UI/Main/Tabs/ButtonTab/ButtonTabController.swift | 501 | COMMENT | |
| LOW | App/UI/Main/Tabs/ButtonTab/AddField.swift | 1 | // | COMMENT |
| LOW | App/UI/Main/Tabs/ButtonTab/AddField.swift | 21 | /// Storage | COMMENT |
| LOW | App/UI/Main/Tabs/ButtonTab/AddField.swift | 61 | } | COMMENT |
| LOW | App/UI/Main/Tabs/ButtonTab/AddField.swift | 81 | /// -> Almost works but also doesn't support wallpaper tinting. | COMMENT |
| LOW | App/UI/Main/Tabs/ButtonTab/AddField.swift | 241 | /// Animation curve | COMMENT |
| LOW | App/UI/Main/Tabs/ButtonTab/AddField_New.swift | 1 | // | COMMENT |
| LOW | App/UI/Main/Tabs/ButtonTab/AddField_New.swift | 21 | COMMENT | |
| LOW | App/UI/Main/Tabs/ButtonTab/AddField_New.swift | 41 | /// -> Too complicated (See 35742760e0bb0c126e16183f11f65532953822cb) | COMMENT |
| LOW | App/UI/Main/Tabs/ButtonTab/AddField_New.swift | 61 | /// (found them by searching for 'background', maybe there are more) | COMMENT |
| LOW | App/UI/Main/Tabs/ButtonTab/AddField_New.swift | 181 | let transformAnimation = playAcceptAnimation ? bounceAnimation : animation | COMMENT |
| LOW | …/UI/Main/Tabs/ButtonTab/RemapTable/RemapTableUtility.h | 1 | // | COMMENT |
| LOW | …/Main/Tabs/ButtonTab/RemapTable/RemapTableController.h | 1 | // | COMMENT |
| LOW | …/Main/Tabs/ButtonTab/RemapTable/RemapTableTranslator.h | 1 | // | COMMENT |
| LOW | …UI/Main/Tabs/ButtonTab/RemapTable/RemapTableCellView.m | 1 | // | COMMENT |
| LOW | …/Main/Tabs/ButtonTab/RemapTable/RemapTableController.m | 1 | // | COMMENT |
| LOW | …/Main/Tabs/ButtonTab/RemapTable/RemapTableController.m | 21 | #import "UIStrings.h" | COMMENT |
| LOW | …/Main/Tabs/ButtonTab/RemapTable/RemapTableController.m | 441 | // NSMutableArray *result = [NSMutableArray array]; | COMMENT |
| LOW | …/UI/Main/Tabs/ButtonTab/RemapTable/RemapTableUtility.m | 1 | // | COMMENT |
| LOW | …/UI/Main/Tabs/ButtonTab/RemapTable/RemapTableUtility.m | 101 | return groupedModelIndex - groupRowCtr; | COMMENT |
| LOW | …/UI/Main/Tabs/ButtonTab/RemapTable/RemapTableUtility.m | 121 | /// | COMMENT |
| LOW | App/UI/Main/Tabs/ButtonTab/RemapTable/MFScrollView.m | 1 | // | COMMENT |
| LOW | App/UI/Main/Tabs/ButtonTab/RemapTable/MFScrollView.m | 21 | COMMENT | |
| LOW | App/UI/Main/Tabs/ButtonTab/RemapTable/MFScrollView.m | 41 | // NSBezierPath * clipPath = [NSBezierPath bezierPathWithRect:outerRect]; | COMMENT |
| LOW | App/UI/Main/Tabs/ButtonTab/RemapTable/RemapTableView.m | 1 | // | COMMENT |
| 726 more matches not shown… | ||||
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | App/UI/Unused/Overrides/OverridePanel.m | 339 | [self loadTableViewDataModelFromConfig]; // At the time of writing: not necessary. Not sure if useful. Might make th | CODE |
| MEDIUM | App/UI/UIExtensions/CoolNSTextField.swift | 167 | /// -> I have a suspicion, that this is not the case on older OSs / other systems, based on what I read on S | COMMENT |
| MEDIUM | App/UI/Main/Tabs/TabControllerUtility.swift | 87 | /// Before, I used `lessThanOrEqualToConstant:` instead of `equalToConstant:` to make things more robust | COMMENT |
| MEDIUM | App/UI/Main/Tabs/ButtonTab/AddField.swift | 91 | /// -> Since this is what NSBox does natively (See above), it may be the most robust approach. | COMMENT |
| MEDIUM | App/UI/Main/Tabs/ButtonTab/AddField_New.swift | 53 | /// -> Since this is what NSBox does natively (See above), it may be the most robust approach. | COMMENT |
| MEDIUM | …/Main/Tabs/ButtonTab/RemapTable/RemapTableController.m | 175 | [self.tableView reloadDataForRowIndexes:[NSIndexSet indexSetWithIndex:row] columnIndexes:[NSIndexSet indexSetWit | CODE |
| MEDIUM | App/Update/SparkleUpdaterController.m | 317 | /// -> This edge case seems very unlikely now that I think about it, but there's always going to be someone | COMMENT |
| MEDIUM | App/Update/SparkleUpdaterController.m | 357 | /// It might be more robust and simple to find and kill any strange helpers *whenever* the app starts, but this shou | COMMENT |
| MEDIUM | Shared/Strings/MarkdownParser/MarkdownParser.m | 505 | if (starti == -1 || endi == -1) return NSMakeRange(NSNotFound, 0); /// Not sure this `NSNotFound` error handling | CODE |
| MEDIUM | Shared/Locator/Locator.m | 133 | /// ^ I thought this would be very robust, but this stuff fails after moving the app. | COMMENT |
| MEDIUM | Shared/License/Retrieve/APIRequests.swift | 17 | /// Essentially, we send a json dict to a URL, and get a json dict back | COMMENT |
| MEDIUM | Shared/Config/Config.m | 12 | /// - We're using our custom coolKeyPath API all over this class, instead of Apple's key-value-coding API (aka KVC) (See | COMMENT |
| MEDIUM | Shared/HelperServices/HelperServices.m | 154 | /// Update: [Sep 2025] Apple did fix things in macOS 15.0 Sequoia! We're also unregistering strange | COMMENT |
| MEDIUM | Shared/HelperServices/HelperServices.m | 203 | /// - We could only do this only if strangeHelperIsRegisteredWithLaunchd, but users have been having some we | COMMENT |
| MEDIUM | Shared/HelperServices/HelperServices.m | 471 | /// - From my testing this does the same as the `bootout` command, but it doesn't rely on a valid launchd.plist file | COMMENT |
| MEDIUM | Shared/Animation/DynamicSystemAnimator.swift | 183 | /// This feels weird and too slow. Definitely incorrect | COMMENT |
| MEDIUM | Shared/Devices/Device.m | 126 | /// Could probably also just count the number elements instead of this. But this might be more robust. | COMMENT |
| MEDIUM | Shared/Utility/MFDataClass.m | 514 | /// - [Oct 2024] Immutable values can just return themselves instead of a copy and noone will notice. Could we deter | COMMENT |
| LOW | Shared/Utility/Unused/DerivedProperty.swift | 155 | /// Actually, this won't work with static properties, either, because keyPaths don't work for static properties 😑. At le | COMMENT |
| MEDIUM | Shared/Utility/MFCoding/MFCoding.m | 55 | /// So it's inconsistent and less robust compared to using `.raiseException` | COMMENT |
| MEDIUM | Shared/Utility/MFCoding/MFCoding.m | 270 | ((NSKeyedUnarchiver *)decoder).decodingFailurePolicy = NSDecodingFailurePolicyRaiseException; /// Use old-school | CODE |
| MEDIUM | Shared/Utility/MFCoding/MFCoding.m | 334 | /// Using a dictionary archive might also be less robust than the alternatives, since I think the dict's key ord | COMMENT |
| MEDIUM | Shared/Utility/MFCoding/MFCoding.m | 335 | /// ... Yeah I think We should probably stick to the standard binary/xmlString formats for the archive - until w | COMMENT |
| MEDIUM | Helper/UNIXSignals.m | 196 | /// (Update 30.09.2024: Since we're only handling simple termination signals now (SIGTERM, SIGINT, SIGHUP), exit | COMMENT |
| MEDIUM | Helper/Core/Modifiers/Modifiers.m | 182 | /// 4. We could add an 'accessibilityAccessEnabled state to the SwitchMaster, and make it so that, when there's | COMMENT |
| MEDIUM | Helper/Core/Buttons/ClickCycle.swift | 19 | /// - Edit: IIRC we're just not implementing the dispatchQueue stuff properly because race conditions are incredibly rar | COMMENT |
| MEDIUM | Helper/Core/Scroll/Scroll.m | 1011 | /// [Jul 2025] Simulating the tap shouldn't usually be necessary for kMFAnimationCallbackPhaseEnd, s | COMMENT |
| MEDIUM | Helper/Core/Touch/TouchAnimatorBase.swift | 202 | /// Orrr we can also have self.isRunning() execute on self.queue. - we did that. Should be most robust s | COMMENT |
| MEDIUM | Helper/Core/Config/ScrollConfig.swift | 628 | /// Conclusion: You can use 0.001 as the 'defaultEpsilon'. it has no overhead and might make | COMMENT |
| MEDIUM | Helper/Utility/EventUtility.m | 46 | /// - In `ButtonInputReceiver.m` I also discuss the idea of just filtering events based on attachedDevices – | COMMENT |
| MEDIUM | Helper/Utility/PointerFreeze.m | 141 | /// Not sure why this happens. But adding a delay of 0.02 before hiding makes it look seamless. | COMMENT |
| MEDIUM | Localization/Screenshots/AnnotationUtility.h | 20 | __builtin_return_address(0) /// If this fails, `backtrace()` should be more robust | CODE |
| MEDIUM | Localization/Screenshots/AnnotationUtility.m | 403 | /// Not sure this is even slower than the main approach. (If not then this should be the main approach) Should be mo | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | LocalizationScreenshotTaker/XCUIElement+Additions.h | 88 | /// Usage example: | COMMENT |
| LOW | Shared/Extensions/NSImage+Additions.m | 145 | /// Usage example: | COMMENT |
| LOW | Shared/Utility/Links.m | 125 | /// Usage example: | COMMENT |
| LOW | Shared/Utility/Macros/SharedMacros.h | 68 | /// Usage example: | COMMENT |
| LOW | Shared/Utility/Macros/SharedMacros.h | 76 | /// Usage example: | COMMENT |
| LOW | Shared/Utility/Macros/SharedMacros.h | 119 | /// Example usage: | COMMENT |
| LOW | Shared/Utility/Macros/SharedMacros.h | 146 | /// Example usage: | COMMENT |
| LOW | Shared/Utility/Macros/SharedMacros.h | 198 | /// Example usage: | COMMENT |
| LOW | Shared/Utility/Macros/SharedMacros.h | 304 | /// Example usage: | COMMENT |
| LOW | Shared/Utility/Macros/SharedMacros.h | 412 | /// Usage example: | COMMENT |
| LOW | Shared/Utility/Macros/SharedMacros.h | 456 | /// Example usage: | COMMENT |
| LOW | Shared/Utility/Macros/SharedMacros.h | 519 | /// Example usage: | COMMENT |
| LOW | Shared/Utility/Macros/SharedMacros.h | 540 | /// Example usage: | COMMENT |
| LOW | Shared/Utility/Macros/MFDefer.h | 13 | /// Usage example: | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | App/UI/Main/Tabs/ButtonTab/ButtonTabController.swift | 314 | /// - If you implement this don't forget to consider making this escape-dismissable, like most other sheets | COMMENT |
| MEDIUM | …/UI/Main/Tabs/ButtonTab/RemapTable/RemapTableUtility.m | 128 | /// - Based on this, I think it does make sense to maybe extend the simple explanation from what was | COMMENT |
| LOW | App/UI/Notifications/Toasts/LicenseToasts.swift | 74 | /// We added this localizedStringKey on the master branch inside .strings files, while we al | COMMENT |
| LOW | Shared/License/License.m | 157 | /// - All other properties should be checked - don't forget to update this when adding new properties! | COMMENT |
| LOW | Shared/License/License.m | 199 | if (info.class == MFLicenseTypeInfoGumroadBusinessV1.class) return NO; /// Don't forget to add definitions here | CODE |
| LOW | Shared/Extensions/NSImage+Additions.m | 35 | /// The r, g, and b values are *premultiplied* with the alpha value. So if you want to change a, don't forget to als | COMMENT |
| LOW | Shared/Utility/MFDataClass.m | 565 | /// If you override this with an NSArray of propertyValues, don't forget to substitute nil values with `[NSN | COMMENT |
| LOW | Shared/Utility/Macros/ListOperations.h | 266 | /// (a): Stores the mapping result in newly allocated memory on the heap. (Use this for C types) (Don't forg | COMMENT |
| LOW | Shared/Utility/Macros/ListOperations.h | 305 | #define mapa(src, count, varname, transform...) ({ /** (a)llocates a new array for the mapped values. Don't for | COMMENT |
| LOW | Shared/Utility/MFCoding/NSCoderErrors.m | 145 | /// - Wrap this in a failWithError() macro instead of calling this directly – so you don't forget to return after ca | COMMENT |
| LOW | Shared/Utility/MFCoding/NSCoderErrors.m | 170 | /// Wrap this in a failWithError() macro instead of calling this directly – so you don't forget to return after | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| CRITICAL | …alizationScreenshotTaker/LocalizationScreenshots.swift | 53 | var description: String { ScreenshotAndMetadata_description_from_key_value_pairs([("screenshot", screenshot), (" | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | App/UI/Main/Tabs/AboutTabController.swift | 118 | /// Step 1: Set UI to cache | COMMENT |
| LOW | App/UI/Main/Tabs/AboutTabController.swift | 133 | /// Step 2: Get real values and update UI | COMMENT |
| LOW | Helper/AccessibilityCheck.m | 69 | /// - We need to launch a new helper instance instead of just using the normal helper instance because `AXIs | COMMENT |
| LOW | Helper/Core/Buttons/ButtonModifiers.m | 62 | /// Do we need to check if the buttonMods actually changed? | COMMENT |
| LOW | Helper/Utility/PointerFreeze.m | 418 | /// Since we call sync, we need to check if we're already on main to avoid deadlock | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| HIGH | Helper/Core/Touch/GestureScrollSimulator.m | 97 | /// Update: [Jul 2025] I've added an assert(false) here. It seems our algorithms don't produce those unwante | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | App/UI/Main/Tabs/AboutTabController.swift | 118 | /// Step 1: Set UI to cache | COMMENT |
| LOW | App/UI/Main/Tabs/AboutTabController.swift | 133 | /// Step 2: Get real values and update UI | COMMENT |