Executive summary
apollographql/apollo-ios is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because 50 files are no longer known to anyone active in the project. It scores 51 out of 100, which the At risk rating leaves unchanged.
Maturity, at 30, is the weakest lens and counts most in the score. The best first step is improving the documentation, worth about 18 points. Having someone learn and document the 50 files no active contributor knows comes next, worth about 17 points. Raising Maturity to 70 would lift the score to about 66.
Ten known security holes in the packages the code depends on can be used by attackers. Six passwords or keys are open to anyone who can read the repository, and one pipeline tool is referenced by a changeable name, so the build pipeline can be tampered with. Updating the vulnerable packages, replacing each exposed password or key and pinning the tool to an exact version would close these risks. Moving the business rules into the object that owns the data would take care of the business object that only holds data.
The product code is 11,397 lines, about €20,000 to rebuild.
If Maturity rose from 30 to 70, the lowest score rated Strong, the score would rise from 51 to about 66.
New since the last survey: 23 findings
- Code Duplication · Edited copy of a member (43 corresponding lines) Sources/Apollo/Decoding.swift
- Code Duplication · Edited copy of a member (33 corresponding lines) Sources/Apollo/RequestBodyCreator.swift
- Code Duplication · Edited copy of a member (16 corresponding lines) Sources/ApolloCodegenLib/ApolloSchemaDownloader.swift
- Code Duplication · Edited copy of a member (20 corresponding lines) Sources/Apollo/MaxRetryInterceptor.swift
- Code Duplication · Edited copy of a member (13 corresponding lines) Sources/Apollo/RequestChainNetworkTransport.swift
- Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) Sources/Apollo/ApolloStore.swift
- Code Duplication · Edited copy of a member (11 corresponding lines) Sources/Apollo/Collection+Helpers.swift
- Code Duplication · Edited copy of a member (14 corresponding lines) Sources/Apollo/RequestChainNetworkTransport.swift
- Code Duplication · Edited copy of a member (11 corresponding lines) Sources/Apollo/DefaultInterceptorProvider.swift
- Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) Sources/Apollo/GraphQLResultAccumulator.swift
- Code Duplication · Edited copy of a member (12 corresponding lines) Sources/Apollo/RequestChain.swift
- Code Duplication · Edited copy of a member (11 corresponding lines) Sources/Apollo/MultipartFormData.swift
- Code Duplication · Edited copy of a member (11 corresponding lines) Sources/Apollo/GraphQLFile.swift
- Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) Sources/Apollo/GraphQLSelectionSet.swift
- Code Duplication · Edited copy of a member (3 corresponding lines) Sources/Apollo/GraphQLResponseGenerator.swift
- Code Duplication · Duplicated block (11 lines × 2) Sources/Apollo/GraphQLSelectionSet.swift
- Code Duplication · Duplicated block (8 lines × 2) Sources/Apollo/GraphQLSelectionSet.swift
- Code Duplication · Duplicated block (7 lines × 2) Sources/Apollo/GraphQLSelectionSet.swift
- Code Duplication · Edited copy of a member (10 corresponding lines) Sources/ApolloTestSupport/XCTAssertHelpers.swift
- Code Duplication · Edited copy of a member (3 corresponding lines) Sources/ApolloTestSupport/XCTAssertHelpers.swift
- Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) Sources/ApolloCodegenTestSupport/CodegenTestHelper.swift
- Code Duplication · Edited copy of a member (7 corresponding lines) Sources/ApolloTestSupport/AsyncResultObserver.swift
- Code Duplication · Edited copy of a member (4 corresponding lines) Sources/ApolloTestSupport/SQLiteTestCacheProvider.swift
Fixed since the last survey: 3 findings
- Code Duplication · Duplicated block (8 lines × 2) Sources/Apollo/GraphQLSelectionSet.swift
- Code Duplication · Duplicated block (7 lines × 2) Sources/Apollo/GraphQLSelectionSet.swift
- Secrets (history) · High secret: WD-SECRET-0005 docs/package-lock.json
Rebuild cost: about €20,000 · Estimate
| Cost to rebuild | €6,800 to €34,000, for 113 to 357 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 51. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 11,397 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 (global) | 2 SimpleUploadServer | 3 Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.values | 4 Sources.ApolloCodegenLib.Frontend.JavaScript.src.utilities | 5 Sources.ApolloCodegenLib.Frontend.JavaScript.src.utilities.graphql | 6 SwiftScripts~SchemaDownload | 7 ApolloAPI | 8 ApolloUtils | 9 Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler | 10 Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.ir | 11 ApolloWebSocket | 12 Sources.ApolloCodegenLib.Frontend.JavaScript | 13 Sources.ApolloCodegenLib.Frontend.JavaScript.src | 14 ApolloCodegenLib | 15 Apollo | 16 ApolloSQLite | 17 GitHubAPI | 18 StarWarsAPI | 19 SubscriptionAPI | 20 SwiftScripts~Codegen | 21 SwiftScripts~DocumentationGenerator | 22 UploadAPI |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||
| 2 SimpleUploadServer | ||||||||||||||||||||||
| 3 Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.values | ||||||||||||||||||||||
| 4 Sources.ApolloCodegenLib.Frontend.JavaScript.src.utilities | ||||||||||||||||||||||
| 5 Sources.ApolloCodegenLib.Frontend.JavaScript.src.utilities.graphql | ||||||||||||||||||||||
| 6 SwiftScripts~SchemaDownload | ||||||||||||||||||||||
| 7 ApolloAPI | 12 | |||||||||||||||||||||
| 8 ApolloUtils | 5 | |||||||||||||||||||||
| 9 Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler | 1 | |||||||||||||||||||||
| 10 Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.ir | 2 | |||||||||||||||||||||
| 11 ApolloWebSocket | 2 | 63 | ||||||||||||||||||||
| 12 Sources.ApolloCodegenLib.Frontend.JavaScript | 1 | |||||||||||||||||||||
| 13 Sources.ApolloCodegenLib.Frontend.JavaScript.src | 1 | |||||||||||||||||||||
| 14 ApolloCodegenLib | 4 | 76 | ||||||||||||||||||||
| 15 Apollo | 2 | 4 | 5 | 13 | ||||||||||||||||||
| 16 ApolloSQLite | 11 | |||||||||||||||||||||
| 17 GitHubAPI | 1 | 38 | ||||||||||||||||||||
| 18 StarWarsAPI | 192 | |||||||||||||||||||||
| 19 SubscriptionAPI | 6 | |||||||||||||||||||||
| 20 SwiftScripts~Codegen | 1 | 4 | ||||||||||||||||||||
| 21 SwiftScripts~DocumentationGenerator | 1 | |||||||||||||||||||||
| 22 UploadAPI | 18 |
7→15 ApolloAPI uses Apollo part of a loop✕
- Connections
- 12 pairs of types, where a type in ApolloAPI uses a type in Apollo.
- The types involved
ApolloAPI.BooleanCondition→Apollo.BoolApolloAPI.BooleanCondition→Apollo.StringApolloAPI.Field→Apollo.StringApolloAPI.GraphQLEnum→Apollo.BoolApolloAPI.GraphQLEnum→Apollo.RawRepresentableApolloAPI.GraphQLEnum→Apollo.StringApolloAPI.GraphQLEnum.swift→Apollo.BoolApolloAPI.GraphQLOptional→Apollo.BoolApolloAPI.SchemaObjectType→Apollo.BoolApolloAPI.SchemaTypeEnum→Apollo.RawRepresentableApolloAPI.SelectionSet→Apollo.StringApolloAPI.SelectionSet.swift→Apollo.Bool
- Direction
- ApolloAPI uses Apollo, so a change to Apollo can break ApolloAPI, while a change to ApolloAPI can't break Apollo.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→15 ApolloUtils uses Apollo part of a loop✕
- Connections
- 5 pairs of types, where a type in ApolloUtils uses a type in Apollo.
- The types involved
ApolloUtils.ApolloExtension→Apollo.BoolApolloUtils.ApolloExtension→Apollo.DispatchQueueApolloUtils.ApolloExtension→Apollo.IntApolloUtils.ApolloExtension→Apollo.StringApolloUtils.ApolloExtension→Apollo.URL
- Direction
- ApolloUtils uses Apollo, so a change to Apollo can break ApolloUtils, while a change to ApolloUtils can't break Apollo.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→3 Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler uses Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.values✕
- Connections
- 1 pair of types, where a type in Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler uses a type in Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.values.
- The types involved
Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.values→Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.values.GraphQLValue
- Direction
- Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler uses Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.values, so a change to Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.values can break Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler, while a change to Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler can't break Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.values.
- Position
- Below the diagonal: Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler uses a module listed above it, which is the healthy direction.
10→3 Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.ir uses Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.values✕
- Connections
- 2 pairs of types, where a type in Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.ir uses a type in Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.values.
- The types involved
Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.ir.Argument→Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.values.GraphQLValueSources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.ir.VariableDefinition→Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.values.GraphQLValue
- Direction
- Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.ir uses Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.values, so a change to Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.values can break Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.ir, while a change to Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.ir can't break Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.values.
- Position
- Below the diagonal: Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.ir uses a module listed above it, which is the healthy direction.
11→8 ApolloWebSocket uses ApolloUtils✕
- Connections
- 2 pairs of types, where a type in ApolloWebSocket uses a type in ApolloUtils.
- The types involved
ApolloWebSocket.ApolloSequencedOperationMessageIdCreator→ApolloUtils.AtomicApolloWebSocket.WebSocketTransport→ApolloUtils.Atomic
- Direction
- ApolloWebSocket uses ApolloUtils, so a change to ApolloUtils can break ApolloWebSocket, while a change to ApolloWebSocket can't break ApolloUtils.
- Position
- Below the diagonal: ApolloWebSocket uses a module listed above it, which is the healthy direction.
11→15 ApolloWebSocket uses Apollo part of a loop✕
- Connections
- 63 pairs of types, where a type in ApolloWebSocket uses a type in Apollo. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
ApolloWebSocket.ApolloSequencedOperationMessageIdCreator→Apollo.IntApolloWebSocket.ApolloSequencedOperationMessageIdCreator→Apollo.StringApolloWebSocket.CompressionState→Apollo.BoolApolloWebSocket.CompressionState→Apollo.IntApolloWebSocket.Compressor→Apollo.BoolApolloWebSocket.Compressor→Apollo.IntApolloWebSocket.Constants→Apollo.IntApolloWebSocket.Constants→Apollo.StringApolloWebSocket.Decompressor→Apollo.BoolApolloWebSocket.Decompressor→Apollo.IntApolloWebSocket.ErrorKind→Apollo.StringApolloWebSocket.FoundationStream→Apollo.BoolApolloWebSocket.FoundationStream→Apollo.DispatchQueueApolloWebSocket.FoundationStream→Apollo.IntApolloWebSocket.FoundationStream→Apollo.URLApolloWebSocket.Notifications→Apollo.StringApolloWebSocket.OperationMessage→Apollo.StringApolloWebSocket.OperationMessageIdCreator→Apollo.StringApolloWebSocket.ParseHandler→Apollo.StringApolloWebSocket.SSLClientCertificate→Apollo.StringApolloWebSocket.SSLClientCertificate→Apollo.URLApolloWebSocket.SSLClientCertificateError→Apollo.StringApolloWebSocket.SSLSecurity→Apollo.BoolApolloWebSocket.SSLSecurity→Apollo.StringApolloWebSocket.SSLSettings→Apollo.Bool
- Direction
- ApolloWebSocket uses Apollo, so a change to Apollo can break ApolloWebSocket, while a change to ApolloWebSocket can't break Apollo.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→9 Sources.ApolloCodegenLib.Frontend.JavaScript uses Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler✕
- Connections
- 1 pair of types, where a type in Sources.ApolloCodegenLib.Frontend.JavaScript uses a type in Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.
- The types involved
Sources.ApolloCodegenLib.Frontend.JavaScript.index→Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.CompilationResult
- Direction
- Sources.ApolloCodegenLib.Frontend.JavaScript uses Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler, so a change to Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler can break Sources.ApolloCodegenLib.Frontend.JavaScript, while a change to Sources.ApolloCodegenLib.Frontend.JavaScript can't break Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.
- Position
- Below the diagonal: Sources.ApolloCodegenLib.Frontend.JavaScript uses a module listed above it, which is the healthy direction.
13→9 Sources.ApolloCodegenLib.Frontend.JavaScript.src uses Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler✕
- Connections
- 1 pair of types, where a type in Sources.ApolloCodegenLib.Frontend.JavaScript.src uses a type in Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.
- The types involved
Sources.ApolloCodegenLib.Frontend.JavaScript.src.index→Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.CompilationResult
- Direction
- Sources.ApolloCodegenLib.Frontend.JavaScript.src uses Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler, so a change to Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler can break Sources.ApolloCodegenLib.Frontend.JavaScript.src, while a change to Sources.ApolloCodegenLib.Frontend.JavaScript.src can't break Sources.ApolloCodegenLib.Frontend.JavaScript.src.compiler.
- Position
- Below the diagonal: Sources.ApolloCodegenLib.Frontend.JavaScript.src uses a module listed above it, which is the healthy direction.
14→11 ApolloCodegenLib uses ApolloWebSocket✕
- Connections
- 4 pairs of types, where a type in ApolloCodegenLib uses a type in ApolloWebSocket.
- The types involved
ApolloCodegenLib.ApolloSchemaDownloader→ApolloWebSocket.URLRequestApolloCodegenLib.NetworkSession→ApolloWebSocket.URLRequestApolloCodegenLib.URLDownloader→ApolloWebSocket.URLRequestApolloCodegenLib.URLSession→ApolloWebSocket.URLRequest
- Direction
- ApolloCodegenLib uses ApolloWebSocket, so a change to ApolloWebSocket can break ApolloCodegenLib, while a change to ApolloCodegenLib can't break ApolloWebSocket.
- Position
- Below the diagonal: ApolloCodegenLib uses a module listed above it, which is the healthy direction.
14→15 ApolloCodegenLib uses Apollo part of a loop✕
- Connections
- 76 pairs of types, where a type in ApolloCodegenLib uses a type in Apollo. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
ApolloCodegenLib.ASTNode→Apollo.StringApolloCodegenLib.AccessModifier→Apollo.StringApolloCodegenLib.ApolloCLI→Apollo.DoubleApolloCodegenLib.ApolloCLI→Apollo.StringApolloCodegenLib.ApolloCLI→Apollo.URLApolloCodegenLib.ApolloCodegen→Apollo.StringApolloCodegenLib.ApolloCodegen→Apollo.URLApolloCodegenLib.ApolloCodegenFrontend→Apollo.StringApolloCodegenLib.ApolloCodegenFrontend→Apollo.URLApolloCodegenLib.ApolloCodegenOptions→Apollo.BoolApolloCodegenLib.ApolloCodegenOptions→Apollo.DoubleApolloCodegenLib.ApolloCodegenOptions→Apollo.StringApolloCodegenLib.ApolloCodegenOptions→Apollo.URLApolloCodegenLib.ApolloFilePathHelper→Apollo.URLApolloCodegenLib.ApolloRegistrySettings→Apollo.StringApolloCodegenLib.ApolloSchemaDownloadConfiguration→Apollo.DoubleApolloCodegenLib.ApolloSchemaDownloadConfiguration→Apollo.StringApolloCodegenLib.ApolloSchemaDownloadConfiguration→Apollo.URLApolloCodegenLib.ApolloSchemaDownloader→Apollo.BoolApolloCodegenLib.ApolloSchemaDownloader→Apollo.StringApolloCodegenLib.ApolloSchemaDownloader→Apollo.URLApolloCodegenLib.ApolloURLError→Apollo.StringApolloCodegenLib.Argument→Apollo.StringApolloCodegenLib.BashError→Apollo.StringApolloCodegenLib.Basher→Apollo.String
- Direction
- ApolloCodegenLib uses Apollo, so a change to Apollo can break ApolloCodegenLib, while a change to ApolloCodegenLib can't break Apollo.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→7 Apollo uses ApolloAPI✕
- Connections
- 2 pairs of types, where a type in Apollo uses a type in ApolloAPI.
- The types involved
Apollo.FieldArguments→ApolloAPI.InputValueApollo.GraphQLSelectionSet.swift→ApolloAPI.InputValue
- Direction
- Apollo uses ApolloAPI, so a change to ApolloAPI can break Apollo, while a change to Apollo can't break ApolloAPI.
- Position
- Below the diagonal: Apollo uses a module listed above it, which is the healthy direction.
15→8 Apollo uses ApolloUtils✕
- Connections
- 4 pairs of types, where a type in Apollo uses a type in ApolloUtils.
- The types involved
Apollo.GraphQLQueryWatcher→ApolloUtils.AtomicApollo.NetworkFetchInterceptor→ApolloUtils.AtomicApollo.RequestChain→ApolloUtils.AtomicApollo.URLSessionClient→ApolloUtils.Atomic
- Direction
- Apollo uses ApolloUtils, so a change to ApolloUtils can break Apollo, while a change to Apollo can't break ApolloUtils.
- Position
- Below the diagonal: Apollo uses a module listed above it, which is the healthy direction.
15→11 Apollo uses ApolloWebSocket✕
- Connections
- 5 pairs of types, where a type in Apollo uses a type in ApolloWebSocket.
- The types involved
Apollo.HTTPRequest→ApolloWebSocket.URLRequestApollo.JSONRequest→ApolloWebSocket.URLRequestApollo.NetworkTransport→ApolloWebSocket.URLRequestApollo.URLSessionClient→ApolloWebSocket.URLRequestApollo.UploadRequest→ApolloWebSocket.URLRequest
- Direction
- Apollo uses ApolloWebSocket, so a change to ApolloWebSocket can break Apollo, while a change to Apollo can't break ApolloWebSocket.
- Position
- Below the diagonal: Apollo uses a module listed above it, which is the healthy direction.
15→14 Apollo uses ApolloCodegenLib✕
- Connections
- 13 pairs of types, where a type in Apollo uses a type in ApolloCodegenLib.
- The types involved
Apollo.Array→ApolloCodegenLib.JSValueApollo.Array→ApolloCodegenLib.JavaScriptBridgeApollo.Bool→ApolloCodegenLib.JSValueApollo.Bool→ApolloCodegenLib.JavaScriptBridgeApollo.Dictionary→ApolloCodegenLib.JSValueApollo.Dictionary→ApolloCodegenLib.JavaScriptBridgeApollo.Int→ApolloCodegenLib.JSValueApollo.Int→ApolloCodegenLib.JavaScriptBridgeApollo.Optional→ApolloCodegenLib.JSValueApollo.Optional→ApolloCodegenLib.JavaScriptBridgeApollo.String→ApolloCodegenLib.JSValueApollo.String→ApolloCodegenLib.JavaScriptBridgeApollo.URLSessionClient→ApolloCodegenLib.URLSession
- Direction
- Apollo uses ApolloCodegenLib, so a change to ApolloCodegenLib can break Apollo, while a change to Apollo can't break ApolloCodegenLib.
- Position
- Below the diagonal: Apollo uses a module listed above it, which is the healthy direction.
16→15 ApolloSQLite uses Apollo✕
- Connections
- 11 pairs of types, where a type in ApolloSQLite uses a type in Apollo.
- The types involved
ApolloSQLite.DatabaseRow→Apollo.StringApolloSQLite.SQLiteDatabase→Apollo.BoolApolloSQLite.SQLiteDatabase→Apollo.StringApolloSQLite.SQLiteDatabase→Apollo.URLApolloSQLite.SQLiteDotSwiftDatabase→Apollo.BoolApolloSQLite.SQLiteDotSwiftDatabase→Apollo.StringApolloSQLite.SQLiteDotSwiftDatabase→Apollo.URLApolloSQLite.SQLiteNormalizedCache→Apollo.BoolApolloSQLite.SQLiteNormalizedCache→Apollo.RecordApolloSQLite.SQLiteNormalizedCache→Apollo.RecordSetApolloSQLite.SQLiteNormalizedCache→Apollo.URL
- Direction
- ApolloSQLite uses Apollo, so a change to Apollo can break ApolloSQLite, while a change to ApolloSQLite can't break Apollo.
- Position
- Below the diagonal: ApolloSQLite uses a module listed above it, which is the healthy direction.
17→11 GitHubAPI uses ApolloWebSocket✕
- Connections
- 1 pair of types, where a type in GitHubAPI uses a type in ApolloWebSocket.
- The types involved
GitHubAPI.Data→ApolloWebSocket.UnsafeBufferPointer
- Direction
- GitHubAPI uses ApolloWebSocket, so a change to ApolloWebSocket can break GitHubAPI, while a change to GitHubAPI can't break ApolloWebSocket.
- Position
- Below the diagonal: GitHubAPI uses a module listed above it, which is the healthy direction.
17→15 GitHubAPI uses Apollo✕
- Connections
- 38 pairs of types, where a type in GitHubAPI uses a type in Apollo. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
GitHubAPI.AsIssue→Apollo.BoolGitHubAPI.AsIssue→Apollo.GraphQLSelectionGitHubAPI.AsIssue→Apollo.GraphQLSelectionSetGitHubAPI.AsIssue→Apollo.StringGitHubAPI.AsUser→Apollo.GraphQLSelectionGitHubAPI.AsUser→Apollo.GraphQLSelectionSetGitHubAPI.AsUser→Apollo.StringGitHubAPI.Author→Apollo.GraphQLSelectionGitHubAPI.Author→Apollo.GraphQLSelectionSetGitHubAPI.Author→Apollo.StringGitHubAPI.AuthorDetails→Apollo.GraphQLFragmentGitHubAPI.AuthorDetails→Apollo.GraphQLSelectionGitHubAPI.AuthorDetails→Apollo.StringGitHubAPI.Comment→Apollo.GraphQLSelectionGitHubAPI.Comment→Apollo.GraphQLSelectionSetGitHubAPI.Comment→Apollo.StringGitHubAPI.Data→Apollo.GraphQLSelectionGitHubAPI.Data→Apollo.GraphQLSelectionSetGitHubAPI.Data→Apollo.StringGitHubAPI.Issue→Apollo.GraphQLSelectionGitHubAPI.Issue→Apollo.GraphQLSelectionSetGitHubAPI.Issue→Apollo.StringGitHubAPI.IssueOrPullRequest→Apollo.BoolGitHubAPI.IssueOrPullRequest→Apollo.GraphQLSelectionGitHubAPI.IssueOrPullRequest→Apollo.GraphQLSelectionSet
- Direction
- GitHubAPI uses Apollo, so a change to Apollo can break GitHubAPI, while a change to GitHubAPI can't break Apollo.
- Position
- Below the diagonal: GitHubAPI uses a module listed above it, which is the healthy direction.
18→15 StarWarsAPI uses Apollo✕
- Connections
- 192 pairs of types, where a type in StarWarsAPI uses a type in Apollo. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
StarWarsAPI.AsDroid→Apollo.GraphQLSelectionStarWarsAPI.AsDroid→Apollo.GraphQLSelectionSetStarWarsAPI.AsDroid→Apollo.StringStarWarsAPI.AsHuman→Apollo.DoubleStarWarsAPI.AsHuman→Apollo.GraphQLSelectionStarWarsAPI.AsHuman→Apollo.GraphQLSelectionSetStarWarsAPI.AsHuman→Apollo.StringStarWarsAPI.AsStarship→Apollo.GraphQLSelectionStarWarsAPI.AsStarship→Apollo.GraphQLSelectionSetStarWarsAPI.AsStarship→Apollo.StringStarWarsAPI.CharacterAppearsIn→Apollo.GraphQLFragmentStarWarsAPI.CharacterAppearsIn→Apollo.GraphQLSelectionStarWarsAPI.CharacterAppearsIn→Apollo.StringStarWarsAPI.CharacterName→Apollo.GraphQLFragmentStarWarsAPI.CharacterName→Apollo.GraphQLSelectionStarWarsAPI.CharacterName→Apollo.StringStarWarsAPI.CharacterNameAndAppearsIn→Apollo.GraphQLFragmentStarWarsAPI.CharacterNameAndAppearsIn→Apollo.GraphQLSelectionStarWarsAPI.CharacterNameAndAppearsIn→Apollo.StringStarWarsAPI.CharacterNameAndAppearsInWithNestedFragments→Apollo.GraphQLFragmentStarWarsAPI.CharacterNameAndAppearsInWithNestedFragments→Apollo.GraphQLSelectionStarWarsAPI.CharacterNameAndAppearsInWithNestedFragments→Apollo.StringStarWarsAPI.CharacterNameAndDroidAppearsIn→Apollo.GraphQLFragmentStarWarsAPI.CharacterNameAndDroidAppearsIn→Apollo.GraphQLSelectionStarWarsAPI.CharacterNameAndDroidAppearsIn→Apollo.String
- Direction
- StarWarsAPI uses Apollo, so a change to Apollo can break StarWarsAPI, while a change to StarWarsAPI can't break Apollo.
- Position
- Below the diagonal: StarWarsAPI uses a module listed above it, which is the healthy direction.
19→15 SubscriptionAPI uses Apollo✕
- Connections
- 6 pairs of types, where a type in SubscriptionAPI uses a type in Apollo.
- The types involved
SubscriptionAPI.Data→Apollo.GraphQLSelectionSubscriptionAPI.Data→Apollo.GraphQLSelectionSetSubscriptionAPI.Data→Apollo.IntSubscriptionAPI.Data→Apollo.StringSubscriptionAPI.IncrementingSubscription→Apollo.GraphQLSubscriptionSubscriptionAPI.IncrementingSubscription→Apollo.String
- Direction
- SubscriptionAPI uses Apollo, so a change to Apollo can break SubscriptionAPI, while a change to SubscriptionAPI can't break Apollo.
- Position
- Below the diagonal: SubscriptionAPI uses a module listed above it, which is the healthy direction.
20→14 SwiftScripts~Codegen uses ApolloCodegenLib✕
- Connections
- 1 pair of types, where a type in SwiftScripts~Codegen uses a type in ApolloCodegenLib.
- The types involved
SwiftScripts~Codegen.Target→ApolloCodegenLib.ApolloCodegenOptions
- Direction
- SwiftScripts~Codegen uses ApolloCodegenLib, so a change to ApolloCodegenLib can break SwiftScripts~Codegen, while a change to SwiftScripts~Codegen can't break ApolloCodegenLib.
- Position
- Below the diagonal: SwiftScripts~Codegen uses a module listed above it, which is the healthy direction.
20→15 SwiftScripts~Codegen uses Apollo✕
- Connections
- 4 pairs of types, where a type in SwiftScripts~Codegen uses a type in Apollo.
- The types involved
SwiftScripts~Codegen.ArgumentError→Apollo.StringSwiftScripts~Codegen.Codegen→Apollo.StringSwiftScripts~Codegen.Target→Apollo.StringSwiftScripts~Codegen.Target→Apollo.URL
- Direction
- SwiftScripts~Codegen uses Apollo, so a change to Apollo can break SwiftScripts~Codegen, while a change to SwiftScripts~Codegen can't break Apollo.
- Position
- Below the diagonal: SwiftScripts~Codegen uses a module listed above it, which is the healthy direction.
21→15 SwiftScripts~DocumentationGenerator uses Apollo✕
- Connections
- 1 pair of types, where a type in SwiftScripts~DocumentationGenerator uses a type in Apollo.
- The types involved
SwiftScripts~DocumentationGenerator.Target→Apollo.String
- Direction
- SwiftScripts~DocumentationGenerator uses Apollo, so a change to Apollo can break SwiftScripts~DocumentationGenerator, while a change to SwiftScripts~DocumentationGenerator can't break Apollo.
- Position
- Below the diagonal: SwiftScripts~DocumentationGenerator uses a module listed above it, which is the healthy direction.
22→15 UploadAPI uses Apollo✕
- Connections
- 18 pairs of types, where a type in UploadAPI uses a type in Apollo.
- The types involved
UploadAPI.Data→Apollo.GraphQLSelectionUploadAPI.Data→Apollo.GraphQLSelectionSetUploadAPI.Data→Apollo.StringUploadAPI.MultipleParameterUpload→Apollo.GraphQLSelectionUploadAPI.MultipleParameterUpload→Apollo.GraphQLSelectionSetUploadAPI.MultipleParameterUpload→Apollo.StringUploadAPI.MultipleUpload→Apollo.GraphQLSelectionUploadAPI.MultipleUpload→Apollo.GraphQLSelectionSetUploadAPI.MultipleUpload→Apollo.StringUploadAPI.SingleUpload→Apollo.GraphQLSelectionUploadAPI.SingleUpload→Apollo.GraphQLSelectionSetUploadAPI.SingleUpload→Apollo.StringUploadAPI.UploadMultipleFilesToDifferentParametersMutation→Apollo.GraphQLMutationUploadAPI.UploadMultipleFilesToDifferentParametersMutation→Apollo.StringUploadAPI.UploadMultipleFilesToTheSameParameterMutation→Apollo.GraphQLMutationUploadAPI.UploadMultipleFilesToTheSameParameterMutation→Apollo.StringUploadAPI.UploadOneFileMutation→Apollo.GraphQLMutationUploadAPI.UploadOneFileMutation→Apollo.String
- Direction
- UploadAPI uses Apollo, so a change to Apollo can break UploadAPI, while a change to UploadAPI can't break Apollo.
- Position
- Below the diagonal: UploadAPI uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 22 | High / Critical |
| A07:2025 — Authentication Failures | 7 | High / Critical |
| A05:2025 — Injection | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md; Resolve the 50 Orphaned file finding(s) in Knowledge Freshness — start with GraphQLExecutor.swift, ApolloStore.swift, JavaScriptBridge.swift; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +18.1 pts | Low | Documentation Quality |
| Resolve the 50 Orphaned file finding(s) in Knowledge Freshness — start with GraphQLExecutor.swift, ApolloStore.swift, JavaScriptBridge.swift. | +16.6 pts | Medium | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +9.3 pts | Medium | Architecture documentation |
| Reconcile the README with reality: docs/source/api/Apollo/README.md links to `protocols/ApolloClientProtocol/`, but `docs/source/api/Apollo/protocols/ApolloClientProtocol` does not exist; docs/source/api/Apollo/README.md links to `protocols/ApolloErrorInterceptor/`, but `docs/source/api/Apollo/protocols/ApolloErrorInterceptor` does not exist; docs/source/api/Apollo/README.md links to `protocols/ApolloInterceptor/`, but `docs/source/api/Apollo/protocols/ApolloInterceptor` does not exist; docs/source/api/Apollo/README.md links to `protocols/Cancellable/`, but `docs/source/api/Apollo/protocols/Cancellable` does not exist; docs/source/api/Apollo/README.md links to `protocols/GraphQLFragment/`, but `docs/source/api/Apollo/protocols/GraphQLFragment` does not exist. | +9.3 pts | Medium | Documentation accuracy |
| Resolve the 6 REDACTED finding(s) in Secrets (history) — start with REDACTED (4), REDACTED (2). | +1.7 pts | Low | Secrets (history) |
| Resolve the 8 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8). | +1.4 pts | Low | Dependency Vulnerabilities |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.0 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.0 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| Sources/ApolloCodegenTestSupport/CodegenTestHelper.swift | 6.7 | Mixed | Explicit Debt: TodoComment |
| Tests/ApolloTests/ResponsePathTests.swift | 7.1 | Mixed | Test Quality: No assertions: test__initializer__givenArray_shouldRespectKeyCasing |
| Sources/Apollo/GraphQLSelectionSet.swift | 7.2 | Mixed | Code Duplication: Edited copies of one member (3 members, 3+ corresponding lines) |
| Tests/ApolloServerIntegrationTests/StarWarsSubscriptionTests.swift | 7.2 | Mixed | Test Quality: No assertions: testConcurrentSubscribing |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| Tests/ApolloTests/Cache/FetchQueryTests.swift | 7.3 | Mixed | Explicit Debt: TodoComment |
| Sources/ApolloCodegenLib/Frontend/JavaScript/src/compiler/index.ts | 7.4 | Mixed | Cyclomatic Complexity: index.compileToIR (cyclomatic 27) |
| Sources/ApolloWebSocket/WebSocketTransport.swift | 7.4 | Mixed | Cyclomatic Complexity: WebSocketTransport.processMessage (cyclomatic 16) |
| Sources/Apollo/Decoding.swift | 7.4 | Mixed | Cognitive Complexity: Decoding.swift.collectFields (cognitive 18) |
| Sources/Apollo/GraphQLExecutor.swift | 7.8 | Mixed | Cognitive Complexity: GraphQLExecutor.collectFields (cognitive 18) |
| Sources/Apollo/RequestChainNetworkTransport.swift | 7.8 | Mixed | Code Duplication: Edited copy of a member (13 corresponding lines) |
| Sources/ApolloTestSupport/XCTAssertHelpers.swift | 7.8 | Mixed | Code Duplication: Edited copy of a member (10 corresponding lines) |
| Tests/ApolloCodegenTests/CLIExtractorTests.swift | 7.8 | Mixed | Test Quality: No assertions: testValidatingSHASUMWithMatchingWorks |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| Tests/ApolloTests/FragmentConstructionAndConversionTests.swift | 8.2 | Near-clean | Explicit Debt: TodoComment |
| Sources/ApolloCodegenLib/Frontend/CompilationResult.swift | 8.2 | Near-clean | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 52 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 52 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 187 of 210 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not scored — the JavaScript/TypeScript suite (jest via `npm install --ignore-scripts` (no lockfile) in Sources/ApolloCodegenLib/Frontend/JavaScript/ (0 tests)) ran but surfaced no test cases to the runner, so flakiness couldn't be exercised.
- D14 License Compliance — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 51 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 47 of the 141 production source files in this repository: 90 are under the ~2,400-byte size floor this dimension measures over, and the remaining 4 have no attributable history left to measure.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'SQLite' is imported (Sources/ApolloSQLite/SQLiteDotSwiftDatabase.swift:5), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'SQLite' is imported (Sources/ApolloSQLite/SQLiteDotSwiftDatabase.swift:5), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Swift, c is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Swift, c is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 77 further occurrence(s) are not listed individually; the score already reflects all 117.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was index.compileToIR at 27.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with index.compileToIR (cyclomatic 27), WebSocketTransport.processMessage (cyclomatic 16). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
6 method(s) exceeded the cognitive complexity threshold of 15; the worst was index.compileToIR::compileSelection at 21.
What to do
- Bring the 6 bodies over 15 down to 15 or less in Cognitive Complexity — start with index.compileToIR::compileSelection (cognitive 21), WebSocketTransport.processMessage (cognitive 20), GraphQLExecutor.collectFields (cognitive 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cognitive Complexity from 9.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 FunctionTooLong finding(s) in God Classes — start with index.ts. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
5 duplicated block group(s) detected. 4.8 % of the production lines (552 of 11,397) are in a reported copy. A further 20 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 5 of the 25 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 4 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with Collection+Helpers.swift, DefaultInterceptorProvider.swift, MultipartFormData.swift. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 Edited copies of one member (3 members, 3+ corresponding lines) finding(s) in Code Duplication — start with GraphQLResultAccumulator.swift, GraphQLSelectionSet.swift. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (3 corresponding lines) finding(s) in Code Duplication — start with GraphQLResponseGenerator.swift, XCTAssertHelpers.swift. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
12 production modules (npm+SwiftPM+Xcode), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a workspace's implicit (product-name) dependency is not visible there; 0 module(s) off the main sequence, with abstractness counted on 7 of the 12 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
3 of 36 classes have LCOM4 above 3.
What to do
- Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with URLSessionClient.swift, GraphQLResultNormalizer.swift, MockWebSocket.swift. — One of this dimension's main actionable groups (3 warning-level).
D10 · Test Quality
1 skipped, 13 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 469 tests.
What to do
- Resolve the 13 No assertions finding(s) in Test Quality — start with ResponsePathTests.swift (5), StarWarsSubscriptionTests.swift (4), CLIExtractorTests.swift (2). — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 1 Skipped test finding(s) in Test Quality — start with SchemaRegistryApolloSchemaDownloaderTests.swift. — One of this dimension's main actionable groups (1 warning-level).
D12 · Dependency Hygiene
5 outdated direct SwiftPM dependencies, 0 pinning defect(s). SwiftPM has no package registry: a dependency is a repository URL and its releases are that repository's semver tags, so currency is answered by listing tags rather than by querying an index. Only a newer tag on the SAME MAJOR is reported — a `from:` requirement admits everything below the next major and nothing above it, so a major crossing needs a Package.swift edit rather than an update, and naming the update as its remedy would be wrong. Whether any dependency is DEPRECATED or ABANDONED is not graded and cannot be: a repository publishes no such marker, and there is no registry that could carry one. Known CVEs in this dependency graph are D30's question.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
7 deducted task-comment markers across 11397 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 7 TodoComment finding(s) in Explicit Debt — start with FetchQueryTests.swift (2), FragmentConstructionAndConversionTests.swift, CodegenTestHelper.swift. — One of this dimension's main actionable groups (7 warning-level).
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 299 document(s) read across 3 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 4 build units (SwiftPM, npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
9 % of calls cross a namespace and 7 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
6 finding(s): 0 critical, 6 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 6 REDACTED finding(s) in Secrets (history) — start with REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
2 finding(s): 0 critical, 1 high, 1 medium, 0 low. 1 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- No action in Static Analysis (SAST) — all 1 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (1 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
18 finding(s): 2 critical, 8 high, 5 medium, 3 low.
What to do
- Resolve the 8 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8). — One of this dimension's main actionable groups (8 issue-level).
- Resolve the 5 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D34 · Knowledge Freshness
51 of 51 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Sources/ApolloWebSocket/WebSocketTransport.swift. Counted over 51 of the 141 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 50 Orphaned file finding(s) in Knowledge Freshness — start with GraphQLExecutor.swift, ApolloStore.swift, JavaScriptBridge.swift. — One of this dimension's main actionable groups (50 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Most significant orphaned file finding(s) in Knowledge Freshness — start with WebSocketTransport.swift. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
DM4 · Rich vs anemic domain model
- `String` is a data-only reference entity whose behaviour is DELEGATED to a foreign utility (static methods that take it as their first parameter and hold its logic) — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants rather than being driven from outside. — Sources/Apollo/JSONStandardTypeConversions.swift:3
What to do
- Move delegated behaviour onto the domain entity (or make it a value object); keep invariants inside the type.
DM5 · Encapsulated state
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
- docs/source/api/Apollo/README.md links to `protocols/ApolloClientProtocol/`, but `docs/source/api/Apollo/protocols/ApolloClientProtocol` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:5
- docs/source/api/Apollo/README.md links to `protocols/ApolloErrorInterceptor/`, but `docs/source/api/Apollo/protocols/ApolloErrorInterceptor` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:6
- docs/source/api/Apollo/README.md links to `protocols/ApolloInterceptor/`, but `docs/source/api/Apollo/protocols/ApolloInterceptor` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:7
- docs/source/api/Apollo/README.md links to `protocols/Cancellable/`, but `docs/source/api/Apollo/protocols/Cancellable` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:8
- docs/source/api/Apollo/README.md links to `protocols/GraphQLFragment/`, but `docs/source/api/Apollo/protocols/GraphQLFragment` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:9
- docs/source/api/Apollo/README.md links to `protocols/GraphQLMapConvertible/`, but `docs/source/api/Apollo/protocols/GraphQLMapConvertible` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:10
- docs/source/api/Apollo/README.md links to `protocols/GraphQLMutation/`, but `docs/source/api/Apollo/protocols/GraphQLMutation` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:11
- docs/source/api/Apollo/README.md links to `protocols/GraphQLOperation/`, but `docs/source/api/Apollo/protocols/GraphQLOperation` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:12
- docs/source/api/Apollo/README.md links to `protocols/GraphQLQuery/`, but `docs/source/api/Apollo/protocols/GraphQLQuery` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:13
- docs/source/api/Apollo/README.md links to `protocols/GraphQLSelection/`, but `docs/source/api/Apollo/protocols/GraphQLSelection` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:14
- docs/source/api/Apollo/README.md links to `protocols/GraphQLSelectionSet/`, but `docs/source/api/Apollo/protocols/GraphQLSelectionSet` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:15
- docs/source/api/Apollo/README.md links to `protocols/GraphQLSubscription/`, but `docs/source/api/Apollo/protocols/GraphQLSubscription` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:16
- docs/source/api/Apollo/README.md links to `protocols/JSONDecodable/`, but `docs/source/api/Apollo/protocols/JSONDecodable` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:18
- docs/source/api/Apollo/README.md links to `protocols/JSONEncodable/`, but `docs/source/api/Apollo/protocols/JSONEncodable` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:19
- docs/source/api/Apollo/README.md links to `protocols/NetworkTransport/`, but `docs/source/api/Apollo/protocols/NetworkTransport` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:20
- docs/source/api/Apollo/README.md links to `protocols/NormalizedCache/`, but `docs/source/api/Apollo/protocols/NormalizedCache` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:21
- docs/source/api/Apollo/README.md links to `protocols/RequestBodyCreator/`, but `docs/source/api/Apollo/protocols/RequestBodyCreator` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:22
- docs/source/api/Apollo/README.md links to `protocols/UploadingNetworkTransport/`, but `docs/source/api/Apollo/protocols/UploadingNetworkTransport` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:23
- docs/source/api/Apollo/README.md links to `structs/ApolloRequestBodyCreator/`, but `docs/source/api/Apollo/structs/ApolloRequestBodyCreator` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:27
- docs/source/api/Apollo/README.md links to `structs/AutomaticPersistedQueryInterceptor/`, but `docs/source/api/Apollo/structs/AutomaticPersistedQueryInterceptor` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:28
- docs/source/api/Apollo/README.md links to `structs/CacheReadInterceptor/`, but `docs/source/api/Apollo/structs/CacheReadInterceptor` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:29
- docs/source/api/Apollo/README.md links to `structs/CacheReference/`, but `docs/source/api/Apollo/structs/CacheReference` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:30
- docs/source/api/Apollo/README.md links to `structs/CacheWriteInterceptor/`, but `docs/source/api/Apollo/structs/CacheWriteInterceptor` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:31
- docs/source/api/Apollo/README.md links to `structs/FieldArguments/`, but `docs/source/api/Apollo/structs/FieldArguments` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:32
- docs/source/api/Apollo/README.md links to `structs/GraphQLBooleanCondition/`, but `docs/source/api/Apollo/structs/GraphQLBooleanCondition` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/Apollo/README.md:33
- docs/source/api/ApolloAPI/README.md links to `protocols/AnySelectionSet/`, but `docs/source/api/ApolloAPI/protocols/AnySelectionSet` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/ApolloAPI/README.md:5
- docs/source/api/ApolloAPI/README.md links to `protocols/Fragment/`, but `docs/source/api/ApolloAPI/protocols/Fragment` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/ApolloAPI/README.md:6
- docs/source/api/ApolloAPI/README.md links to `protocols/GraphQLSchema/`, but `docs/source/api/ApolloAPI/protocols/GraphQLSchema` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/ApolloAPI/README.md:7
- docs/source/api/ApolloAPI/README.md links to `protocols/HasFragments/`, but `docs/source/api/ApolloAPI/protocols/HasFragments` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/ApolloAPI/README.md:8
- docs/source/api/ApolloAPI/README.md links to `protocols/ResponseObject/`, but `docs/source/api/ApolloAPI/protocols/ResponseObject` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/ApolloAPI/README.md:9
- docs/source/api/ApolloAPI/README.md links to `protocols/ScalarType/`, but `docs/source/api/ApolloAPI/protocols/ScalarType` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/ApolloAPI/README.md:10
- docs/source/api/ApolloAPI/README.md links to `protocols/SchemaObjectType/`, but `docs/source/api/ApolloAPI/protocols/SchemaObjectType` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/ApolloAPI/README.md:11
- docs/source/api/ApolloAPI/README.md links to `protocols/SchemaTypeEnum/`, but `docs/source/api/ApolloAPI/protocols/SchemaTypeEnum` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/ApolloAPI/README.md:12
- docs/source/api/ApolloAPI/README.md links to `protocols/SchemaUnion/`, but `docs/source/api/ApolloAPI/protocols/SchemaUnion` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/ApolloAPI/README.md:13
- docs/source/api/ApolloAPI/README.md links to `protocols/SelectionSet/`, but `docs/source/api/ApolloAPI/protocols/SelectionSet` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/ApolloAPI/README.md:14
- docs/source/api/ApolloAPI/README.md links to `structs/Field.Arguments/`, but `docs/source/api/ApolloAPI/structs/Field.Arguments` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/ApolloAPI/README.md:18
- docs/source/api/ApolloAPI/README.md links to `structs/ResponseDict/`, but `docs/source/api/ApolloAPI/structs/ResponseDict` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/ApolloAPI/README.md:19
- docs/source/api/ApolloAPI/README.md links to `structs/Selection.BooleanCondition/`, but `docs/source/api/ApolloAPI/structs/Selection.BooleanCondition` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/ApolloAPI/README.md:20
- docs/source/api/ApolloAPI/README.md links to `structs/Selection.Field/`, but `docs/source/api/ApolloAPI/structs/Selection.Field` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/ApolloAPI/README.md:21
- docs/source/api/ApolloAPI/README.md links to `structs/Selection.FragmentSpread/`, but `docs/source/api/ApolloAPI/structs/Selection.FragmentSpread` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/source/api/ApolloAPI/README.md:22
What to do
- Reconcile the README with reality: docs/source/api/Apollo/README.md links to `protocols/ApolloClientProtocol/`, but `docs/source/api/Apollo/protocols/ApolloClientProtocol` does not exist; docs/source/api/Apollo/README.md links to `protocols/ApolloErrorInterceptor/`, but `docs/source/api/Apollo/protocols/ApolloErrorInterceptor` does not exist; docs/source/api/Apollo/README.md links to `protocols/ApolloInterceptor/`, but `docs/source/api/Apollo/protocols/ApolloInterceptor` does not exist; docs/source/api/Apollo/README.md links to `protocols/Cancellable/`, but `docs/source/api/Apollo/protocols/Cancellable` does not exist; docs/source/api/Apollo/README.md links to `protocols/GraphQLFragment/`, but `docs/source/api/Apollo/protocols/GraphQLFragment` does not exist.
P1 · CI/CD gates
- A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
- Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
P10 · Library API & versioning
P2 · Observability
- Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `SimpleUploadServer`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add a health-check endpoint (a /health route on your Vapor/Hummingbird router) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
R2 · Cyclomatic Complexity
- compileSelection has cyclomatic complexity 15 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Sources/ApolloCodegenLib/Frontend/JavaScript/src/compiler/index.ts:189
- getFieldDef has cyclomatic complexity 11 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Sources/ApolloCodegenLib/Frontend/JavaScript/src/utilities/graphql.ts:101
R3 · Large Files
R5 · Dependency Freshness
R6 · Tooling
- test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add `tsc --noEmit` as package.json scripts and run them in CI.
R7 · Dead Code
- Nothing ultimately consumes this binding: its only referrer is the re-export in Sources/ApolloCodegenLib/Frontend/JavaScript/src/utilities/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in Sources/ApolloCodegenLib/Frontend/JavaScript/src/utilities/index.ts in the same commit, or the barrel will import a name that no longer exists. (×4) — Sources/ApolloCodegenLib/Frontend/JavaScript/src/utilities/graphql.ts:45, Sources/ApolloCodegenLib/Frontend/JavaScript/src/utilities/graphql.ts:49, Sources/ApolloCodegenLib/Frontend/JavaScript/src/utilities/graphql.ts:62, …
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Declared in Sources/ApolloCodegenLib/Frontend/JavaScript/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `netlify.toml` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — netlify.toml:1
What to do
- Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X26 · Unsynchronised callback handoff
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — Sources/ApolloWebSocket/DefaultImplementation/WebSocket.swift:1024
- `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — Sources/Apollo/GraphQLGETTransformer.swift:44
What to do
- Swallowed exception (empty catch)
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 83% | Strong | Solid. |
| Architecture | 96% | Exemplary | Solid. |
| Maturity | 30% | Weak — gated by D34, M2, M4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 63% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 60% | Checked 4 of 10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 86% | Strong | Solid. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: this repository stores data through 'SQLite' (Sources/ApolloSQLite/SQLiteDotSwiftDatabase.swift:5) but declares no persisted model this check reads (SwiftData @Model, Core Data, Realm, GRDB and Fluent types, GRDB and SQLite.swift columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'SQLite' (Sources/ApolloSQLite/SQLiteDotSwiftDatabase.swift:5) but declares no persisted model this check reads (SwiftData @Model, Core Data NSManagedObject, Realm Object, GRDB record and Fluent Model properties, GRDB and SQLite.swift columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL files). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 78 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Swift imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — no exported interface declares behaviour
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D11 Test Reliability — No tests discovered
- D14 License Compliance — Package licences not graded — dependencies declared to CocoaPods
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (4795 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Swift surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .swift source were not judged.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in Sources/ApolloCodegenLib/Frontend/JavaScript/ ran and not one test passed (No tests found, exiting with code 1), so the coverage would describe the failed run, not the code; the Swift half could not be measured — the Swift suite in . produced no coverage export. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
- DM1 Aggregate boundaries — not scored for Swift: the sidecar flattens array/collection types (a child COLLECTION = legitimate membership vs a single embedded aggregate is indistinguishable), and aggregate-vs-value-object classification cannot be told apart in source (every struct-holding-struct reads alike) — reported as guidance rather than measured
- DM2 Strongly-typed ids — no in-repo typed-id idiom — primitive-obsession recorded as advisory DM8, DM2 not gated
- DM3 Integration-event coupling — not scored for Swift: a cross-SwiftPM-target domain leak cannot be told apart in source from a legitimate shared-kernel/contracts module, and most repositories ship a single module — reported as guidance rather than measured
- DM6 Domain ↔ infrastructure boundary — this Swift package maps no type to a persistence framework and declares no domain-model type carrying a method of its own, so DM6's domain↔infrastructure boundary read has no population to be taken over
- DM7 Repository granularity — not scored for Swift: 'a repository per CHILD entity' needs the aggregate-root structure, which is not source-resolvable — reported as guidance rather than measured
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Swift source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `Benchmark("…")` in a file importing package-benchmark, or package-benchmark in Package.swift, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — 1 test file(s) reach none of 8 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
- X1 Async correctness — X1 reached only 7% of this repository's production lines — swift (9,099 lines), c (62 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — X12 reached only 7% of this repository's production lines — swift (9,099 lines), c (62 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X21 Side-effecting pattern guard — X21 reached only 7% of this repository's production lines — swift (9,099 lines), c (62 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Swift's `Array`, `Dictionary` and `Set` are values: `for x in items` walks the copy taken when the loop starts, so a body that adds to or removes from `items` changes a different value, nothing is invalidated, and every original element is still visited. This repository's Swift names no Foundation mutable collection (`NSMutableArray` and kin), the one kind a Swift loop can walk by reference. Not a gap in the analyzer and not a finding about your code.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — X30 reached only 7% of this repository's production lines — swift (9,099 lines), c (62 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 19 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Test suite declares a test script but contains no test files: Sources/ApolloCodegenLib/Frontend/JavaScript/
- REDACTED
- Anemic domain model: String Sources/Apollo/JSONStandardTypeConversions.swift:3
Serious — 74 finding(s)
- No assertions: testValidatingSHASUMWithMatchingWorks Tests/ApolloCodegenTests/CLIExtractorTests.swift:76
- No assertions: testFolderExistsButMissingSHASUMFileReExtractionWorks Tests/ApolloCodegenTests/CLIExtractorTests.swift:146
- No assertions: testConcurrentSubscribing Tests/ApolloServerIntegrationTests/StarWarsSubscriptionTests.swift:311
- No assertions: testConcurrentSubscriptionCancellations Tests/ApolloServerIntegrationTests/StarWarsSubscriptionTests.swift:350
- No assertions: testConcurrentSubscriptionAndConnectionClose Tests/ApolloServerIntegrationTests/StarWarsSubscriptionTests.swift:384
- No assertions: testConcurrentConnectAndCloseConnection Tests/ApolloServerIntegrationTests/StarWarsSubscriptionTests.swift:411
- No assertions: testCancellingTaskThroughClientDoesNotCallCompletion Tests/ApolloServerIntegrationTests/URLSessionClientTests.swift:163
- No assertions: test__initializer__givenArray_shouldRespectKeyCasing Tests/ApolloTests/ResponsePathTests.swift:7
- No assertions: test__joined__givenArray_shouldReturnJoinedKeysInOrder Tests/ApolloTests/ResponsePathTests.swift:13
- No assertions: test__joined__whenAppendKey_shouldIncludeAppendedKeyLast Tests/ApolloTests/ResponsePathTests.swift:19
- No assertions: test__joined__whenAddKey_shouldIncludeAddedKeyLast Tests/ApolloTests/ResponsePathTests.swift:26
- No assertions: test__description__givenArray_shouldEqualJoined Tests/ApolloTests/ResponsePathTests.swift:33
- No assertions: testLocalMissingSubscription Tests/ApolloTests/WebSocket/WebSocketTests.swift:80
- TodoComment Tests/ApolloTests/FragmentConstructionAndConversionTests.swift:396
- TodoComment Tests/ApolloTests/Cache/FetchQueryTests.swift:237
- TodoComment Tests/ApolloTests/Cache/FetchQueryTests.swift:274
- TodoComment Sources/ApolloCodegenTestSupport/CodegenTestHelper.swift:37
- TodoComment Sources/ApolloCodegenLib/Frontend/CompilationResult.swift:27
- TodoComment Sources/ApolloCodegenLib/Frontend/JavaScriptBridge.swift:113
- TodoComment Sources/ApolloAPI/CodegenV1/SelectionSet.swift:52
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (11 corresponding lines) Sources/Apollo/Collection+Helpers.swift:6
- Edited copy of a member (11 corresponding lines) Sources/Apollo/DefaultInterceptorProvider.swift:30
- Edited copy of a member (11 corresponding lines) Sources/Apollo/MultipartFormData.swift:55
- Edited copy of a member (11 corresponding lines) Sources/Apollo/GraphQLFile.swift:36
- Low cohesion: URLSessionClient (LCOM4 13) Sources/Apollo/URLSessionClient.swift:14
- Low cohesion: GraphQLResultNormalizer (LCOM4 5) Sources/Apollo/GraphQLResultNormalizer.swift:3
- Low cohesion: MockWebSocket (LCOM4 4) Sources/ApolloTestSupport/MockWebSocket.swift:4
- Edited copies of one member (3 members, 3+ corresponding lines) Sources/Apollo/GraphQLResultAccumulator.swift:85
- Edited copies of one member (3 members, 3+ corresponding lines) Sources/Apollo/GraphQLSelectionSet.swift:79
- Edited copy of a member (3 corresponding lines) Sources/Apollo/GraphQLResponseGenerator.swift:16
- Edited copy of a member (3 corresponding lines) Sources/ApolloTestSupport/XCTAssertHelpers.swift:48
- Duplicated block (11 lines × 2) Sources/Apollo/Decoding.swift:64
- Duplicated block (11 lines × 2) Sources/Apollo/GraphQLSelectionSet.swift:52
- index.compileToIR (cyclomatic 27) Sources/ApolloCodegenLib/Frontend/JavaScript/src/compiler/index.ts:39
- WebSocketTransport.processMessage (cyclomatic 16) Sources/ApolloWebSocket/WebSocketTransport.swift:135
- Skipped test: testDownloadingSchema_fromSchemaRegistry_shouldOutputSDL Tests/ApolloServerIntegrationTests/SchemaRegistryApolloSchemaDownloaderTests.swift:8
- index.compileToIR::compileSelection (cognitive 21) Sources/ApolloCodegenLib/Frontend/JavaScript/src/compiler/index.ts:189
- WebSocketTransport.processMessage (cognitive 20) Sources/ApolloWebSocket/WebSocketTransport.swift:135
- GraphQLExecutor.collectFields (cognitive 18) Sources/Apollo/GraphQLExecutor.swift:177
- GraphQLExecutor.complete (cognitive 18) Sources/Apollo/GraphQLExecutor.swift:270
- Decoding.swift.collectFields (cognitive 18) Sources/Apollo/Decoding.swift:41
- WebSocketTransport.send (cognitive 16) Sources/ApolloWebSocket/WebSocketTransport.swift:388
- REDACTED
- FunctionTooLong: index.compileToIR Sources/ApolloCodegenLib/Frontend/JavaScript/src/compiler/index.ts:39
- REDACTED
- Edited copy of a member (43 corresponding lines) Sources/Apollo/Decoding.swift:41
- Edited copy of a member (33 corresponding lines) Sources/Apollo/RequestBodyCreator.swift:25
- Edited copy of a member (16 corresponding lines) Sources/ApolloCodegenLib/ApolloSchemaDownloader.swift:96
- Edited copy of a member (20 corresponding lines) Sources/Apollo/MaxRetryInterceptor.swift:27
- Edited copy of a member (13 corresponding lines) Sources/Apollo/RequestChainNetworkTransport.swift:85
- Edited copies of one member (3 members, 15+ corresponding lines) Sources/Apollo/ApolloStore.swift:76
- Edited copy of a member (14 corresponding lines) Sources/Apollo/RequestChainNetworkTransport.swift:63
- Edited copy of a member (12 corresponding lines) Sources/Apollo/RequestChain.swift:134
- Duplicated block (5 lines × 3) SwiftScripts/Sources/Codegen/Target.swift:47
- Duplicated block (8 lines × 2) Sources/Apollo/GraphQLSelectionSet.swift:98
- Duplicated block (7 lines × 2) Sources/Apollo/GraphQLSelectionSet.swift:125
- Edited copy of a member (10 corresponding lines) Sources/ApolloTestSupport/XCTAssertHelpers.swift:52
- Edited copies of one member (3 members, 11+ corresponding lines) Sources/ApolloCodegenTestSupport/CodegenTestHelper.swift:108
- Edited copy of a member (7 corresponding lines) Sources/ApolloTestSupport/AsyncResultObserver.swift:17
- Edited copy of a member (4 corresponding lines) Sources/ApolloTestSupport/SQLiteTestCacheProvider.swift:17
- Coverage not measured — JavaScript/TypeScript and Swift suite
- Complex function compileSelection (cyclomatic 15, cognitive 21) Sources/ApolloCodegenLib/Frontend/JavaScript/src/compiler/index.ts:189
- Complex function getFieldDef (cyclomatic 11, cognitive 9) Sources/ApolloCodegenLib/Frontend/JavaScript/src/utilities/graphql.ts:101
- No typecheck script
- Unused dependency 'common-tags'
- Unused dependency 'tslib'
- JavaScript dependencies are not locked Sources/ApolloCodegenLib/Frontend/JavaScript/package.json:15
- Swallowed exception (empty catch) Sources/ApolloWebSocket/DefaultImplementation/WebSocket.swift:1024
- Swallowed exception (caught, then discarded) Sources/Apollo/GraphQLGETTransformer.swift:44
Minor — 112 finding(s)
- Orphaned file Sources/Apollo/GraphQLExecutor.swift:1
- Orphaned file Sources/Apollo/ApolloStore.swift:1
- Orphaned file Sources/ApolloCodegenLib/Frontend/JavaScriptBridge.swift:1
- Orphaned file Sources/ApolloCodegenLib/ApolloSchemaDownloader.swift:1
- Orphaned file Sources/Apollo/URLSessionClient.swift:1
- Orphaned file Sources/ApolloCodegenLib/ApolloCodegenOptions.swift:1
- Orphaned file Sources/ApolloCodegenLib/Frontend/JavaScript/src/compiler/index.ts:1
- Orphaned file Sources/Apollo/Decoding.swift:1
- Orphaned file Sources/Apollo/RequestChain.swift:1
- Orphaned file Sources/ApolloTestSupport/XCTAssertHelpers.swift:1
- Orphaned file Sources/ApolloCodegenLib/CLIExtractor.swift:1
- Orphaned file Sources/Apollo/ApolloClient.swift:1
- Orphaned file Sources/Apollo/RequestChainNetworkTransport.swift:1
- Orphaned file Sources/Apollo/GraphQLResultAccumulator.swift:1
- Orphaned file Sources/Apollo/ApolloClientProtocol.swift:1
- Orphaned file Sources/Apollo/MultipartFormData.swift:1
- Orphaned file Sources/Apollo/UploadRequest.swift:1
- Orphaned file Sources/Apollo/JSONRequest.swift:1
- Orphaned file Sources/ApolloSQLite/SQLiteNormalizedCache.swift:1
- Orphaned file Sources/ApolloCodegenTestSupport/CodegenTestHelper.swift:1
- Orphaned file Sources/ApolloCodegenLib/Frontend/ApolloCodegenFrontend.swift:1
- Orphaned file Sources/Apollo/HTTPRequest.swift:1
- Orphaned file Sources/ApolloCodegenLib/ApolloSchemaDownloadConfiguration.swift:1
- Orphaned file Sources/ApolloTestSupport/MockGraphQLServer.swift:1
- Orphaned file Sources/ApolloCodegenLib/Frontend/CompilationResult.swift:1
- README/code drift docs/source/api/Apollo/README.md:5
- README/code drift docs/source/api/Apollo/README.md:6
- README/code drift docs/source/api/Apollo/README.md:7
- README/code drift docs/source/api/Apollo/README.md:8
- README/code drift docs/source/api/Apollo/README.md:9
- README/code drift docs/source/api/Apollo/README.md:10
- README/code drift docs/source/api/Apollo/README.md:11
- README/code drift docs/source/api/Apollo/README.md:12
- README/code drift docs/source/api/Apollo/README.md:13
- README/code drift docs/source/api/Apollo/README.md:14
- README/code drift docs/source/api/Apollo/README.md:15
- README/code drift docs/source/api/Apollo/README.md:16
- README/code drift docs/source/api/Apollo/README.md:18
- README/code drift docs/source/api/Apollo/README.md:19
- README/code drift docs/source/api/Apollo/README.md:20
- README/code drift docs/source/api/Apollo/README.md:21
- README/code drift docs/source/api/Apollo/README.md:22
- README/code drift docs/source/api/Apollo/README.md:23
- README/code drift docs/source/api/Apollo/README.md:27
- README/code drift docs/source/api/Apollo/README.md:28
- README/code drift docs/source/api/Apollo/README.md:29
- README/code drift docs/source/api/Apollo/README.md:30
- README/code drift docs/source/api/Apollo/README.md:31
- README/code drift docs/source/api/Apollo/README.md:32
- README/code drift docs/source/api/Apollo/README.md:33
- REDACTED
- REDACTED
- REDACTED
- Documentation: no build, run or usage example README.md:1
- Projects may be oversized for their cohesion
- REDACTED
- Dormant codebase
- Most significant orphaned file Sources/ApolloWebSocket/WebSocketTransport.swift:1
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- CI build step not evidenced
- Logging is not universal
- No SAST
- No release approval gate
- Unused export 'sourceAt' Sources/ApolloCodegenLib/Frontend/JavaScript/src/utilities/graphql.ts:45
- Unused export 'filePathForNode' Sources/ApolloCodegenLib/Frontend/JavaScript/src/utilities/graphql.ts:49
- Unused export 'withTypenameFieldAddedWhereNeeded' Sources/ApolloCodegenLib/Frontend/JavaScript/src/utilities/graphql.ts:62
- Unused export 'isObject' Sources/ApolloCodegenLib/Frontend/JavaScript/src/utilities/predicates.ts:7
- No security response headers detected netlify.toml:1
Minor — 5 finding(s)
- Outdated: cwlcatchexception
- Outdated: cwlpreconditiontesting
- Outdated: sqlite.swift
- Outdated: sqlite.swift
- Outdated: swift-argument-parser
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9bd96bce5372453bbdea65bc9bb1d485/history.json --exit-code 0 --source . | 9 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9bd96bce5372453bbdea65bc9bb1d485/tree.json --exit-code 0 --source . | 3 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 2 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 18 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |