Home / swiftbar / SwiftBar
AI Slop Code Risk Monitor

swiftbar/SwiftBar

SlopCodeMonitor badge for swiftbar/SwiftBar Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

Powerful macOS menu bar customization tool

1.2 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for swiftbar/SwiftBar, a Swift project with 4,741 GitHub stars. SynthScan examined 20,368 lines of code across 84 source files, recording 24 pattern matches distributed across 5 syntactic categories. The legacy adjusted pattern signal is 1.2 (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.

1.2
Adjusted Signal
1.2
Raw Pattern Score
100%
Time Factor
2026-09-29
Last Push
4.7K
Stars
Swift
Language
20.4K
Lines of Code
84
Files
24
Pattern Hits
2026-10-31
Scan Date
0.00
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 5.5/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

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

Agent Over-Engineering Ratio 0.5/100 · LOW

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

PR Review Velocity Impact 6.6/100 · LOW

Which changes need focused human review? 24 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 0MEDIUM 2LOW 22

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 24 distinct pattern matches across 5 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 Block14 hits · 14 pts
SeverityFileLineSnippetContext
LOWSwiftBar/AppDelegate.swift161 // `delegate.pluginManager` have a usable instance, then bail out beforeCOMMENT
LOWSwiftBar/UI/Plugin Repository/PluginEntryView.swift241// dependencies: "iTunes Lite applescript",COMMENT
LOWSwiftBar/MenuBar/MenuBarItem.swift941 /// changed or a child switched between fold and submenu modes, at any depth.COMMENT
LOWSwiftBar/MenuBar/MenuBarItem.swift1121COMMENT
LOWSwiftBar/MenuBar/MenuBarItem.swift1921 ) -> BarItemClickRoute {COMMENT
LOWSwiftBar/MenuBar/MenuDiff.swift21/// A wrapper that gives MenuItemNode a shape-based identity for CollectionDifference.COMMENT
LOWSwiftBar/Utility/PluginUtilities.swift121 /// Runs the retry chain without occupying an invoke-queue slot duringCOMMENT
LOWSwiftBarTests/RunScriptTests.swift101 #expect(recorder.recordedWriteError() == nil)COMMENT
LOWSwiftBarTests/SwiftBarTests.swift701 let appleScript = buildTerminalAppleScript(command: "echo hello", terminal: .iTerm)COMMENT
LOWSwiftBarTests/SwiftBarTests.swift1681 #expect(metadata.environment.count == 1)COMMENT
LOWSwiftBarTests/SwiftBarTests.swift1921 @Test func testVariableParsing_MultipleVariables() throws {COMMENT
LOWSwiftBarTests/SwiftBarTests.swift2081 let script = """COMMENT
LOWSwiftBarTests/SwiftBarTests.swift4101 #expect(tree.count == 4)COMMENT
LOWSwiftBarTests/SwiftBarTests.swift4921 item.menu(item.statusBarMenu, willHighlight: highlightedItem)COMMENT
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMSwiftBar/Utility/LaunchAtLogin.swift261 // live against the BTM database), but this keeps the removal robustCOMMENT
Verbosity Indicators4 hits · 3 pts
SeverityFileLineSnippetContext
LOW⚡SwiftBarTests/SwiftBarTests.swift2090 // Step 1: Parse metadataSTRING
LOW⚡SwiftBarTests/SwiftBarTests.swift2100 // Step 2: Simulate user values from .vars.jsonSTRING
LOW⚡SwiftBarTests/SwiftBarTests.swift2108 // Step 3: Build environment (should use user values)STRING
LOW⚡SwiftBarTests/SwiftBarTests.swift2111 // Step 4: Verify user values override defaultsSTRING
Structural Annotation Overuse4 hits · 3 pts
SeverityFileLineSnippetContext
LOW⚡SwiftBarTests/SwiftBarTests.swift2090 // Step 1: Parse metadataSTRING
LOW⚡SwiftBarTests/SwiftBarTests.swift2100 // Step 2: Simulate user values from .vars.jsonSTRING
LOW⚡SwiftBarTests/SwiftBarTests.swift2108 // Step 3: Build environment (should use user values)STRING
LOW⚡SwiftBarTests/SwiftBarTests.swift2111 // Step 4: Verify user values override defaultsSTRING
Excessive Try-Catch Wrapping1 hit · 2 pts
SeverityFileLineSnippetContext
MEDIUMSwiftBar/Plugin/PluginMetadata.swift216 print("Error parsing variable tags: \(error)")CODE