AI Slop Code Risk Monitor

pointfreeco/swift-composable-architecture

SlopCodeMonitor badge for pointfreeco/swift-composable-architecture Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

A library for building applications in a consistent and understandable way, with composition, testing, and ergonomics in mind.

2.9 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for pointfreeco/swift-composable-architecture, a Swift project with 15,001 GitHub stars. SynthScan examined 96,682 lines of code across 929 source files, recording 192 pattern matches distributed across 5 syntactic categories. The legacy adjusted pattern signal is 2.9 (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.9
Adjusted Signal
2.9
Raw Pattern Score
100%
Time Factor
2026-10-27
Last Push
15.0K
Stars
Swift
Language
96.7K
Lines of Code
929
Files
192
Pattern Hits
2026-10-31
Scan Date
0.03
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 7.4/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.8/100 · LOW

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

Agent Over-Engineering Ratio 5.9/100 · LOW

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

PR Review Velocity Impact 15.2/100 · LOW

Which changes need focused human review? 192 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 1HIGH 23MEDIUM 1LOW 167

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 192 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 Block161 hits · 148 pts
SeverityFileLineSnippetContext
LOWTests/ComposableArchitectureTests/StoreTests.swift1121 // initialState: InvalidatedStoreScopeParentFeature.State(COMMENT
LOW…hitectureTests/Reducers/PresentationReducerTests.swift2621 // alert: AlertState { TextState("Oops!") }COMMENT
LOWSources/ComposableArchitecture/Reducer.swift1/// A protocol that describes how to evolve the current state of an application to the next state,COMMENT
LOWSources/ComposableArchitecture/Reducer.swift41 /// from top to bottom, and usually involves some reducer operations for integrating, such asCOMMENT
LOWSources/ComposableArchitecture/Reducer.swift121/// }COMMENT
LOWSources/ComposableArchitecture/Effect.swift21 init(operation: Operation) {COMMENT
LOWSources/ComposableArchitecture/Effect.swift41// MARK: - Creating EffectsCOMMENT
LOWSources/ComposableArchitecture/Effect.swift61 /// Then you could attach to it in a `run` effect by using `for await` and sending each action ofCOMMENT
LOWSources/ComposableArchitecture/Effect.swift81 /// - priority: Priority of the underlying task. If `nil`, the priority will come fromCOMMENT
LOWSources/ComposableArchitecture/Effect.swift141 /// > child-parent communication, where a child may want to emit a "delegate" action for a parentCOMMENT
LOWSources/ComposableArchitecture/Effect.swift161/// for await event in self.events {COMMENT
LOWSources/ComposableArchitecture/TestStore.swift1@_spi(Internals) import CasePathsCOMMENT
LOWSources/ComposableArchitecture/TestStore.swift21/// By default, ``TestStore`` requires you to exhaustively prove how your feature evolves fromCOMMENT
LOWSources/ComposableArchitecture/TestStore.swift41///COMMENT
LOWSources/ComposableArchitecture/TestStore.swift61/// var body: some Reducer<State, Action> {COMMENT
LOWSources/ComposableArchitecture/TestStore.swift81/// struct CounterTests {COMMENT
LOWSources/ComposableArchitecture/TestStore.swift101/// mutable value of the state before the action was sent, and it is our job to mutate the value toCOMMENT
LOWSources/ComposableArchitecture/TestStore.swift121/// >COMMENT
LOWSources/ComposableArchitecture/TestStore.swift141/// @Dependency(\.continuousClock) var clockCOMMENT
LOWSources/ComposableArchitecture/TestStore.swift161/// // Do error handling here.COMMENT
LOWSources/ComposableArchitecture/TestStore.swift181///COMMENT
LOWSources/ComposableArchitecture/TestStore.swift201/// ```COMMENT
LOWSources/ComposableArchitecture/TestStore.swift221/// a test failure:COMMENT
LOWSources/ComposableArchitecture/TestStore.swift241/// }COMMENT
LOWSources/ComposableArchitecture/TestStore.swift261///COMMENT
LOWSources/ComposableArchitecture/TestStore.swift281/// each assertion detailing the changes that were not asserted against. This allows you to see whatCOMMENT
LOWSources/ComposableArchitecture/TestStore.swift301/// In order to test such a complex flow we must test the integration of multiple features, whichCOMMENT
LOWSources/ComposableArchitecture/TestStore.swift321/// await store.receive(\.login.loginResponse.success) {COMMENT
LOWSources/ComposableArchitecture/TestStore.swift341///COMMENT
LOWSources/ComposableArchitecture/TestStore.swift361/// await store.send(\.login.submitButtonTapped)COMMENT
LOWSources/ComposableArchitecture/TestStore.swift381/// store.exhaustivity = .off(showSkippedAssertions: true) // ⬅️COMMENT
LOWSources/ComposableArchitecture/TestStore.swift401/// > )COMMENT
LOWSources/ComposableArchitecture/TestStore.swift421///COMMENT
LOWSources/ComposableArchitecture/TestStore.swift441 /// let store = TestStore(/* ... */) {COMMENT
LOWSources/ComposableArchitecture/TestStore.swift501 let reducer: TestReducer<State, Action>COMMENT
LOWSources/ComposableArchitecture/TestStore.swift781 ) async rethrows -> R {COMMENT
LOWSources/ComposableArchitecture/TestStore.swift801/// ```COMMENT
LOWSources/ComposableArchitecture/TestStore.swift821 /// analytics event in an effect when an action is sent, you can assert on that behaviorCOMMENT
LOWSources/ComposableArchitecture/TestStore.swift841 ///COMMENT
LOWSources/ComposableArchitecture/TestStore.swift861 /// let store = TestStore(/* ... */)COMMENT
LOWSources/ComposableArchitecture/TestStore.swift981 }COMMENT
LOWSources/ComposableArchitecture/TestStore.swift1001 /// await store.finish()COMMENT
LOWSources/ComposableArchitecture/TestStore.swift1261COMMENT
LOWSources/ComposableArchitecture/TestStore.swift1281 /// To change the amount of time this method waits for an action, pass an explicit `timeout`COMMENT
LOWSources/ComposableArchitecture/TestStore.swift1441 fileID: fileID,COMMENT
LOWSources/ComposableArchitecture/TestStore.swift1461 /// store.count = 42COMMENT
LOWSources/ComposableArchitecture/TestStore.swift1561 /// ```swiftCOMMENT
LOWSources/ComposableArchitecture/TestStore.swift1661 ///COMMENT
LOWSources/ComposableArchitecture/TestStore.swift1921 /// …can be simplified to:COMMENT
LOWSources/ComposableArchitecture/TestStore.swift1961 /// This method is similar to ``send(_:assert:fileID:file:line:column:)-8f2pl``, except it allowsCOMMENT
LOWSources/ComposableArchitecture/TestStore.swift2021 /// // Assert on how state changedCOMMENT
LOWSources/ComposableArchitecture/TestStore.swift2101 /// Cancels any currently in-flight effects.COMMENT
LOWSources/ComposableArchitecture/TestStore.swift2221}COMMENT
LOWSources/ComposableArchitecture/TestStore.swift2241/// await mainQueue.advance(by: .seconds(1))COMMENT
LOWSources/ComposableArchitecture/TestStore.swift2261 /// Cancels the underlying task and waits for it to finish.COMMENT
LOWSources/ComposableArchitecture/TestStore.swift2461 }COMMENT
LOWSources/ComposableArchitecture/TestStore.swift2481COMMENT
LOWSources/ComposableArchitecture/Store.swift1import CombineCOMMENT
LOWSources/ComposableArchitecture/Store.swift21/// }COMMENT
LOWSources/ComposableArchitecture/Store.swift41/// Button("Tap") {COMMENT
101 more matches not shown…
Cross-File Repetition23 hits · 115 pts
SeverityFileLineSnippetContext
HIGH…omposableArchitectureTests/TestStoreFailureTests.swift0an effect returned for this action is still running. it must complete before the end of \ the test. to fix, inspect any STRING
HIGH…ableArchitectureTests/Reducers/StackReducerTests.swift0an effect returned for this action is still running. it must complete before the end of \ the test. to fix, inspect any STRING
HIGH…hitectureTests/Reducers/PresentationReducerTests.swift0an effect returned for this action is still running. it must complete before the end of \ the test. to fix, inspect any STRING
HIGHSources/ComposableArchitecture/TestStore.swift0an effect returned for this action is still running. it must complete before the end of \ the test. to fix, inspect any STRING
HIGH…leArchitectureTests/Reducers/ForEachReducerTests.swift0a "foreach" at "\(self.fileid):\(self.line)" received an action for a missing element. action: \(debugcaseoutput(action)STRING
HIGH…ableArchitectureTests/Reducers/StackReducerTests.swift0a "foreach" at "\(self.fileid):\(self.line)" received an action for a missing element. action: \(debugcaseoutput(action)STRING
HIGH…osableArchitecture/Reducer/Reducers/StackReducer.swift0a "foreach" at "\(self.fileid):\(self.line)" received an action for a missing element. action: \(debugcaseoutput(action)STRING
HIGH…ableArchitecture/Reducer/Reducers/ForEachReducer.swift0a "foreach" at "\(self.fileid):\(self.line)" received an action for a missing element. action: \(debugcaseoutput(action)STRING
HIGH…es/SwiftUICaseStudies/02-SharedState-FileStorage.swift0this tab shows the count from the previous tab, and it is capable of resetting the count \ back to 0. this shows that itSTRING
HIGH…udies/SwiftUICaseStudies/02-SharedState-InMemory.swift0this tab shows the count from the previous tab, and it is capable of resetting the count \ back to 0. this shows that itSTRING
HIGH…s/SwiftUICaseStudies/02-SharedState-UserDefaults.swift0this tab shows the count from the previous tab, and it is capable of resetting the count \ back to 0. this shows that itSTRING
HIGH…ecognition/SpeechRecognition/SpeechClient/Client.swift0lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor \ incididunt ut labore et dolore magna alSTRING
HIGH…es/SyncUps/SyncUps/Dependencies/SpeechRecognizer.swift0lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor \ incididunt ut labore et dolore magna alSTRING
HIGHExamples/SyncUps/SyncUps/Models.swift0lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor \ incididunt ut labore et dolore magna alSTRING
HIGHExamples/Integration/IntegrationUITests/EnumTests.swift0basicsview.body basicsview.body viewstoreof<basicsview.feature>.deinit viewstoreof<basicsview.feature>.deinit viewstoreoSTRING
HIGH…IntegrationUITests/iOS 16+17/NewOldSiblingsTests.swift0basicsview.body basicsview.body viewstoreof<basicsview.feature>.deinit viewstoreof<basicsview.feature>.deinit viewstoreoSTRING
HIGH…tegration/IntegrationUITests/iOS 16/SiblingTests.swift0basicsview.body basicsview.body viewstoreof<basicsview.feature>.deinit viewstoreof<basicsview.feature>.deinit viewstoreoSTRING
HIGH…ntegration/IntegrationUITests/iOS 16/BasicsTests.swift0basicsview.body basicsview.body viewstoreof<basicsview.feature>.deinit viewstoreof<basicsview.feature>.deinit viewstoreoSTRING
HIGH…egration/IntegrationUITests/iOS 16/OptionalTests.swift0basicsview.body basicsview.body viewstoreof<basicsview.feature>.deinit viewstoreof<basicsview.feature>.deinit viewstoreoSTRING
HIGH…on/IntegrationUITests/iOS 16/IdentifiedListTests.swift0basicsview.body basicsview.body viewstoreof<basicsview.feature>.deinit viewstoreof<basicsview.feature>.deinit viewstoreoSTRING
HIGH…/Integration/IntegrationUITests/iOS 16/EnumTests.swift0basicsview.body basicsview.body viewstoreof<basicsview.feature>.deinit viewstoreof<basicsview.feature>.deinit viewstoreoSTRING
HIGH…ration/IntegrationUITests/iOS 16/NavigationTests.swift0basicsview.body basicsview.body viewstoreof<basicsview.feature>.deinit viewstoreof<basicsview.feature>.deinit viewstoreoSTRING
HIGH…tion/IntegrationUITests/iOS 16/PresentationTests.swift0basicsview.body basicsview.body viewstoreof<basicsview.feature>.deinit viewstoreof<basicsview.feature>.deinit viewstoreoSTRING
Hallucination Indicators1 hit · 10 pts
SeverityFileLineSnippetContext
CRITICAL…ntegrationUITests/Legacy/LegacyPresentationTests.swift412 self.app.navigationBars.buttons.element.tap()CODE
Fake / Example Data6 hits · 6 pts
SeverityFileLineSnippetContext
LOW…ecognition/SpeechRecognition/SpeechClient/Client.swift34 Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor \CODE
LOW…ecognition/SpeechRecognition/SpeechClient/Client.swift34 Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor \CODE
LOWExamples/SyncUps/SyncUps/Models.swift81 Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor \CODE
LOWExamples/SyncUps/SyncUps/Models.swift81 Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor \CODE
LOW…es/SyncUps/SyncUps/Dependencies/SpeechRecognizer.swift43 Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor \CODE
LOW…es/SyncUps/SyncUps/Dependencies/SpeechRecognizer.swift43 Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor \CODE
Decorative Section Separators1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMSources/ComposableArchitecture/Macros.swift193/// //┬─────────COMMENT