Home / hamed-elfayome / Claude-Usage-Tracker
AI Slop Code Risk Monitor

hamed-elfayome/Claude-Usage-Tracker

SlopCodeMonitor badge for hamed-elfayome/Claude-Usage-Tracker Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

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

2.8 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for hamed-elfayome/Claude-Usage-Tracker, a Swift project with 3,723 GitHub stars. SynthScan examined 44,787 lines of code across 176 source files, recording 75 pattern matches distributed across 8 syntactic categories. The legacy adjusted pattern signal is 2.8 (Low pattern signal); it is not an authorship estimate.

Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.

2.8
Adjusted Signal
2.8
Raw Pattern Score
100%
Time Factor
2026-08-31
Last Push
3.7K
Stars
Swift
Language
44.8K
Lines of Code
176
Files
75
Pattern Hits
2026-10-31
Scan Date
0.01
HC Hit Rate

Risk Review · Payload v1

Use each vector to guide manual verification of the underlying findings.

Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.

Cognitive Ownership Risk 10.5/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 66 finding(s).

Hallucinated Dependency & Supply Chain Risk 0.2/100 · LOW

Are imports declared and package/API names verified? 3 finding(s).

Agent Over-Engineering Ratio 2.5/100 · LOW

Are wrappers, guards, and repeated structures necessary? 6 finding(s).

PR Review Velocity Impact 10.0/100 · LOW

Which changes need focused human review? 75 finding(s).

What These Metrics Mean

Adjusted Signal
Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score
Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor
A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits
Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate
High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files
Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 0HIGH 1MEDIUM 7LOW 67

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 75 distinct pattern matches across 8 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. 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 configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Over-Commented Block35 hits · 35 pts
SeverityFileLineSnippetContext
LOWClaude Usage/Shared/Models/ProviderDescriptor.swift1//COMMENT
LOWClaude Usage/Shared/Models/ProviderDescriptor.swift41/// hide/no-op the feature (never throw).COMMENT
LOWClaude Usage/Shared/Models/Profile.swift1//COMMENT
LOWClaude Usage/Shared/Models/Profile.swift41 /// which is what Claude Code rotates during normal use. Lets users with multipleCOMMENT
LOW…aude Usage/Shared/Models/StatuslineElementColors.swift1//COMMENT
LOW…sage/Shared/Extensions/NSWindow+FullScreenSpaces.swift1//COMMENT
LOWClaude Usage/Shared/Utilities/PaceStatus.swift1//COMMENT
LOW…age/Shared/Protocols/NotificationServiceProtocol.swift1//COMMENT
LOW…aude Usage/Shared/Protocols/UsageProviderService.swift1//COMMENT
LOW…ude Usage/Shared/Services/SupportReminderService.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/TerminalLauncherService.swift1//COMMENT
LOW…de Usage/Shared/Services/TerminalLauncherService.swift21/// so the FIRST launcher session needs a one-time `/login`; after that the appCOMMENT
LOWClaude Usage/Shared/Services/KeychainService.swift261 func deleteAllProfileSecrets(profileId: UUID) {COMMENT
LOWClaude Usage/Shared/Services/KeychainService.swift281 // check the data-protection store first and fall through to the file-basedCOMMENT
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
LOW…Usage/Shared/Services/Providers/ProviderRegistry.swift1//COMMENT
LOW…/Shared/Services/Providers/Codex/CodexAPIService.swift1//COMMENT
LOW…Shared/Services/Providers/Codex/CodexAuthService.swift1//COMMENT
LOW…d/Services/Providers/Codex/CodexAPIService+Types.swift1//COMMENT
LOW…vices/Providers/Anthropic/AnthropicUsageProvider.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
Verbosity Indicators13 hits · 25 pts
SeverityFileLineSnippetContext
LOWClaude Usage/MenuBar/StatusBarUIManager.swift133 // Step 1: Remove items that are no longer neededCOMMENT
LOWClaude Usage/MenuBar/StatusBarUIManager.swift148 // Step 2: Add items that are newCOMMENT
LOWClaude Usage/MenuBar/StatusBarUIManager.swift173 // Step 3: Items that already exist don't need recreation, just keep themCOMMENT
LOWClaude Usage/MenuBar/StatusBarUIManager.swift286 // Step 1: Remove items that are no longer neededCOMMENT
LOWClaude Usage/MenuBar/StatusBarUIManager.swift301 // Step 2: Add items that are newCOMMENT
LOW⚡Claude Usage/Shared/Utilities/SessionKeyValidator.swift104 // Step 1: Trim whitespaceCOMMENT
LOW⚡Claude Usage/Shared/Utilities/SessionKeyValidator.swift107 // Step 2: Check if emptyCOMMENT
LOW⚡Claude Usage/Shared/Utilities/SessionKeyValidator.swift112 // Step 3: Check for internal whitespaceCOMMENT
LOW⚡Claude Usage/Shared/Utilities/SessionKeyValidator.swift117 // Step 4: Check length constraintsCOMMENT
LOW⚡Claude Usage/Shared/Utilities/SessionKeyValidator.swift132 // Step 5: Check prefixCOMMENT
LOW⚡Claude Usage/Shared/Utilities/SessionKeyValidator.swift137 // Step 6: Security checks (strict mode) - CHECK BEFORE character validationCOMMENT
LOW⚡Claude 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.swift133 // Step 1: Remove items that are no longer neededCOMMENT
LOWClaude Usage/MenuBar/StatusBarUIManager.swift148 // Step 2: Add items that are newCOMMENT
LOWClaude Usage/MenuBar/StatusBarUIManager.swift173 // Step 3: Items that already exist don't need recreation, just keep themCOMMENT
LOWClaude Usage/MenuBar/StatusBarUIManager.swift286 // Step 1: Remove items that are no longer neededCOMMENT
LOWClaude Usage/MenuBar/StatusBarUIManager.swift301 // Step 2: Add items that are newCOMMENT
LOW⚡Claude Usage/Shared/Utilities/SessionKeyValidator.swift104 // Step 1: Trim whitespaceCOMMENT
LOW⚡Claude Usage/Shared/Utilities/SessionKeyValidator.swift107 // Step 2: Check if emptyCOMMENT
LOW⚡Claude Usage/Shared/Utilities/SessionKeyValidator.swift112 // Step 3: Check for internal whitespaceCOMMENT
LOW⚡Claude Usage/Shared/Utilities/SessionKeyValidator.swift117 // Step 4: Check length constraintsCOMMENT
LOW⚡Claude Usage/Shared/Utilities/SessionKeyValidator.swift132 // Step 5: Check prefixCOMMENT
LOW⚡Claude Usage/Shared/Utilities/SessionKeyValidator.swift137 // Step 6: Security checks (strict mode) - CHECK BEFORE character validationCOMMENT
LOW⚡Claude 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
MEDIUM⚡Claude Usage/Views/FeedbackPromptView.swift12// ─────────────────────────────────────────────────────────────────────COMMENT
MEDIUM⚡Claude Usage/Views/FeedbackPromptView.swift14// ─────────────────────────────────────────────────────────────────────COMMENT
MEDIUM⚡Claude 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
Synthetic Comment Markers1 hit · 8 pts
SeverityFileLineSnippetContext
HIGH…de Usage/Shared/Services/TerminalLauncherService.swift123 # Generated by Claude Usage for profile "\(profile.name)".COMMENT
Redundant / Tautological Comments3 hits · 4 pts
SeverityFileLineSnippetContext
LOWscripts/validate_localizations.sh18# Check if en.lproj existsCOMMENT
LOW.github/workflows/release.yml244 # 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
LOW⚡Claude UsageTests/ClaudeUsageTests.swift253 emailAddress: "user@example.com",STRING
LOW⚡Claude UsageTests/ClaudeUsageTests.swift263 emailAddress: "user@example.com",STRING
LOW⚡Claude UsageTests/ClaudeUsageTests.swift273 emailAddress: "user@example.com",STRING