Repository Analysis

hamed-elfayome/Claude-Usage-Tracker

Native macOS menu bar app for tracking Claude AI usage limits in real-time. Built with Swift/SwiftUI.

2.5 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of hamed-elfayome/Claude-Usage-Tracker, a Swift project with 3,032 GitHub stars. SynthScan v2.0 examined 41,191 lines of code across 157 source files, recording 60 pattern matches distributed across 7 syntactic categories. The overall adjusted score of 2.5 places this repository in the Likely human-written 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).

2.5
Adjusted Score
2.5
Raw Score
100%
Time Factor
2026-07-12
Last Push
3.0K
Stars
Swift
Language
41.2K
Lines of Code
157
Files
60
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

Longitudinal tracking requires multiple scan runs. Once this repository is re-scanned after new commits land, this chart will visualise how the synthetic code signal evolves over time — enabling you to detect whether AI authorship is growing, stabilising, or being actively corrected by human engineers.

No multi-scan history yet — run the scanner again to build trend data.

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 53

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 60 distinct pattern matches across 7 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.

Verbosity Indicators13 hits · 25 pts
SeverityFileLineSnippetContext
LOWClaude Usage/MenuBar/StatusBarUIManager.swift136 // Step 1: Remove items that are no longer neededCOMMENT
LOWClaude Usage/MenuBar/StatusBarUIManager.swift151 // Step 2: Add items that are newCOMMENT
LOWClaude Usage/MenuBar/StatusBarUIManager.swift176 // Step 3: Items that already exist don't need recreation, just keep themCOMMENT
LOWClaude Usage/MenuBar/StatusBarUIManager.swift355 // Step 1: Remove items that are no longer neededCOMMENT
LOWClaude Usage/MenuBar/StatusBarUIManager.swift370 // Step 2: Add items that are newCOMMENT
LOWClaude Usage/Shared/Utilities/SessionKeyValidator.swift104 // Step 1: Trim whitespaceCOMMENT
LOWClaude Usage/Shared/Utilities/SessionKeyValidator.swift107 // Step 2: Check if emptyCOMMENT
LOWClaude Usage/Shared/Utilities/SessionKeyValidator.swift112 // Step 3: Check for internal whitespaceCOMMENT
LOWClaude Usage/Shared/Utilities/SessionKeyValidator.swift117 // Step 4: Check length constraintsCOMMENT
LOWClaude Usage/Shared/Utilities/SessionKeyValidator.swift132 // Step 5: Check prefixCOMMENT
LOWClaude Usage/Shared/Utilities/SessionKeyValidator.swift137 // Step 6: Security checks (strict mode) - CHECK BEFORE character validationCOMMENT
LOWClaude Usage/Shared/Utilities/SessionKeyValidator.swift143 // Step 7: Validate character setCOMMENT
LOWClaude Usage/Shared/Utilities/SessionKeyValidator.swift155 // Step 8: Format validationCOMMENT
Structural Annotation Overuse13 hits · 25 pts
SeverityFileLineSnippetContext
LOWClaude Usage/MenuBar/StatusBarUIManager.swift136 // Step 1: Remove items that are no longer neededCOMMENT
LOWClaude Usage/MenuBar/StatusBarUIManager.swift151 // Step 2: Add items that are newCOMMENT
LOWClaude Usage/MenuBar/StatusBarUIManager.swift176 // Step 3: Items that already exist don't need recreation, just keep themCOMMENT
LOWClaude Usage/MenuBar/StatusBarUIManager.swift355 // Step 1: Remove items that are no longer neededCOMMENT
LOWClaude Usage/MenuBar/StatusBarUIManager.swift370 // Step 2: Add items that are newCOMMENT
LOWClaude Usage/Shared/Utilities/SessionKeyValidator.swift104 // Step 1: Trim whitespaceCOMMENT
LOWClaude Usage/Shared/Utilities/SessionKeyValidator.swift107 // Step 2: Check if emptyCOMMENT
LOWClaude Usage/Shared/Utilities/SessionKeyValidator.swift112 // Step 3: Check for internal whitespaceCOMMENT
LOWClaude Usage/Shared/Utilities/SessionKeyValidator.swift117 // Step 4: Check length constraintsCOMMENT
LOWClaude Usage/Shared/Utilities/SessionKeyValidator.swift132 // Step 5: Check prefixCOMMENT
LOWClaude Usage/Shared/Utilities/SessionKeyValidator.swift137 // Step 6: Security checks (strict mode) - CHECK BEFORE character validationCOMMENT
LOWClaude Usage/Shared/Utilities/SessionKeyValidator.swift143 // Step 7: Validate character setCOMMENT
LOWClaude Usage/Shared/Utilities/SessionKeyValidator.swift155 // Step 8: Format validationCOMMENT
Decorative Section Separators6 hits · 22 pts
SeverityFileLineSnippetContext
MEDIUMClaude Usage/Views/FeedbackPromptView.swift12// ─────────────────────────────────────────────────────────────────────COMMENT
MEDIUMClaude Usage/Views/FeedbackPromptView.swift14// ─────────────────────────────────────────────────────────────────────COMMENT
MEDIUMClaude Usage/Views/FeedbackPromptView.swift24// ─────────────────────────────────────────────────────────────────────COMMENT
MEDIUMClaude Usage/Views/Settings/App/MobileAppView.swift12// ─────────────────────────────────────────────────────────────────────COMMENT
MEDIUMClaude Usage/Views/Settings/App/MobileAppView.swift14// ─────────────────────────────────────────────────────────────────────COMMENT
MEDIUMClaude Usage/Views/Settings/App/MobileAppView.swift28// ─────────────────────────────────────────────────────────────────────COMMENT
Over-Commented Block21 hits · 21 pts
SeverityFileLineSnippetContext
LOWClaude Usage/MenuBar/MenuBarIconRenderer.swift721 fullText.draw(at: NSPoint(x: 2, y: textY), withAttributes: attributes)COMMENT
LOWClaude Usage/Shared/Models/Profile.swift21 var apiSessionKeyExpiry: Date?COMMENT
LOW…aude Usage/Shared/Models/StatuslineElementColors.swift1//COMMENT
LOWClaude Usage/Shared/Utilities/PaceStatus.swift1//COMMENT
LOW…age/Shared/Protocols/NotificationServiceProtocol.swift1//COMMENT
LOW…aude Usage/Shared/Services/ClaudeCodeSyncService.swift281 /// Resolves the correct keychain service name for Claude Code credentials.COMMENT
LOW…aude Usage/Shared/Services/ClaudeCodeSyncService.swift441 serviceName: serviceName,COMMENT
LOW…aude Usage/Shared/Services/ClaudeCodeSyncService.swift501 return String(hex.prefix(length))COMMENT
LOW…aude Usage/Shared/Services/ClaudeCodeSyncService.swift981 throw ClaudeCodeError.refreshFailed(status: -1, body: "No HTTP response")COMMENT
LOW…de Usage/Shared/Services/NotchHUD/HookHTTPParser.swift1//COMMENT
LOW…sage/Shared/Services/NotchHUD/NotchHookInstaller.swift1//COMMENT
LOW…e Usage/Shared/Services/NotchHUD/NotchHookServer.swift1//COMMENT
LOWClaude Usage/Views/FeedbackPromptView.swift1//COMMENT
LOW…ude Usage/Views/Settings/DesignSystem/Typography.swift1//COMMENT
LOW…Usage/Views/Settings/DesignSystem/SettingsColors.swift1//COMMENT
LOWClaude Usage/Views/Settings/DesignSystem/Spacing.swift1//COMMENT
LOW…Views/Settings/DesignSystem/SettingsDesignSystem.swift1//COMMENT
LOWClaude Usage/Views/Settings/App/MobileAppView.swift1//COMMENT
LOW.github/workflows/codeql.yml1# For most projects, this workflow file will not need changing; you simply needCOMMENT
LOW.github/workflows/codeql.yml41 - language: swiftCOMMENT
LOW.github/workflows/codeql.yml61 # Initializes the CodeQL tools for scanning.COMMENT
Redundant / Tautological Comments3 hits · 4 pts
SeverityFileLineSnippetContext
LOWscripts/validate_localizations.sh18# Check if en.lproj existsCOMMENT
LOW.github/workflows/release.yml243 # Check if we got contentCOMMENT
LOW.github/workflows/generate-appcast.yml178 # Check if there are changes to commitCOMMENT
Slop Phrases1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUM.github/workflows/codeql.yml49 # If you are analyzing a compiled language, you can modify the 'build-mode' for that language to customize howCOMMENT
Fake / Example Data3 hits · 2 pts
SeverityFileLineSnippetContext
LOWClaude UsageTests/ClaudeUsageTests.swift253 emailAddress: "user@example.com",STRING
LOWClaude UsageTests/ClaudeUsageTests.swift263 emailAddress: "user@example.com",STRING
LOWClaude UsageTests/ClaudeUsageTests.swift273 emailAddress: "user@example.com",STRING