Executive summary
xtool-org/xtool falls short of our standard for production because we found no automated security scanning of the code, its secrets or its dependencies. It scores 65 out of 100 and is rated Adequate, and all 16 of its critical findings are security problems in the build pipeline and in its servers and containers.
Production Readiness, at 55, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 5 points. Adding automated security scanning would lift Production Readiness itself, worth about 7 points. Raising Production Readiness to 70 would lift the score to about 70.
Thirteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two pipeline steps run downloads nobody checks, and one setting leaves the servers or containers unsafe. Pinning each tool to an exact version, checking each download against a checksum and correcting the unsafe settings would close these risks.
The product code is 11,828 lines, about €15,000 to rebuild.
If Production Readiness rose from 55 to 70, the lowest score rated Strong, the score would rise from 65 to about 70.
New since the last survey: 18 findings
- Cognitive Complexity · FileDescriptor.writeAllWaiting (cognitive 22) Sources/XUtils/System+Utils.swift
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) Sources/XToolSupport/DSCommands/DSCertificatesCommand.swift
- Code Duplication · Edited copy of a member (28 corresponding lines) Sources/XToolSupport/DevCommand.swift
- Code Duplication · Edited copy of a member (8 corresponding lines) Sources/XUtils/DataChannel.swift
- Code Duplication · Edited copy of a member (8 corresponding lines) Sources/XKit/HTTPClientProtocol/AsyncHTTPClient+HTTP.swift
- Code Duplication · Edited copy of a member (12 corresponding lines) Sources/XKit/GrandSlam/Operations/GrandSlamTwoFactorAuthenticateOperation.swift
- Code Duplication · Edited copy of a member (6 corresponding lines) Sources/XKit/GrandSlam/Requests/Concrete/GrandSlamTrustedDeviceRequest.swift
- Code Duplication · Edited copy of a member (9 corresponding lines) Documentation/xtool.docc/First-app-code/edit-2.swift
- Code Duplication · Duplicated block (11–12 lines × 4) Sources/XToolSupport/DSCommands/DSCertificatesCommand.swift
- Code Duplication · Duplicated block (10–11 lines × 2) Sources/XToolSupport/DevCommand.swift
- Code Duplication · Duplicated block (7 lines × 2) Sources/XKit/DeveloperServices/Certificates/DeveloperServicesFetchCertificateOperation.swift
- Code Duplication · Duplicated block (5 lines × 2) Sources/XcodeProjects/XcodeProject.swift
- Test Quality · No assertions: newlinePreservesRemainderAfterPartialRead Tests/XToolTests/DataChannelTests.swift
- Churn × Complexity Hotspots · Hotspot: Sources/XToolSupport/DSCommands/DSCertificatesCommand.swift Sources/XToolSupport/DSCommands/DSCertificatesCommand.swift
- Churn × Complexity Hotspots · Hotspot: Sources/XToolSupport/DSCommands/DSProfilesCommand.swift Sources/XToolSupport/DSCommands/DSProfilesCommand.swift
- Explicit Debt · TodoComment Sources/XCLIUtils/Console.swift
- Dependency Vulnerabilities · REDACTED
- Change Coupling · Change-coupling hub: GrandSlamClient.swift → AsyncHTTPClient+HTTP.swift, HTTPClientProtocol.swift, URLSession+HTTP.swift Sources/XKit/GrandSlam/GrandSlamClient.swift
Fixed since the last survey: 16 findings
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) Sources/XToolSupport/DSCommands/DSCertificatesCommand.swift
- Code Duplication · Duplicated block (20–24 lines × 2) Sources/XToolSupport/DSCommands/DSCertificatesCommand.swift
- Code Duplication · Duplicated block (19–23 lines × 2) Sources/XToolSupport/DSCommands/DSDevicesCommand.swift
- Code Duplication · Duplicated block (15–17 lines × 3) Sources/XToolSupport/DSCommands/DSDevicesCommand.swift
- Code Duplication · Duplicated block (13 lines × 3) Sources/XToolSupport/DSCommands/DSCertificatesCommand.swift
- Code Duplication · Duplicated block (10–13 lines × 2) Sources/XToolSupport/DSCommands/DSCertificatesCommand.swift
- Code Duplication · Duplicated block (9–11 lines × 3) Sources/XToolSupport/DSCommands/DSCertificatesCommand.swift
- Code Duplication · Duplicated block (10–11 lines × 2) Sources/XToolSupport/DevCommand.swift
- Code Duplication · Duplicated block (9 lines × 4) Sources/XToolSupport/DSCommands/DSCertificatesCommand.swift
- Code Duplication · Duplicated block (7–8 lines × 2) Sources/XToolSupport/XToolInstallerDelegate.swift
- Code Duplication · Duplicated block (7 lines × 3) Sources/XToolSupport/DSCommands/DSCertificatesCommand.swift
- Code Duplication · Duplicated block (7 lines × 2) Sources/XKit/DeveloperServices/Certificates/DeveloperServicesFetchCertificateOperation.swift
- Explicit Debt · TodoComment Sources/XToolSupport/Console.swift
- Explicit Debt · TodoComment Sources/XKit/Signer/SignerImpl.swift
- Explicit Debt · FixmeComment Sources/XKit/DeveloperServices/App IDs/Entitlements/DeveloperServicesCapability.swift
- Documentation (README) · README may be stale
Rebuild cost: about €15,000 · Estimate
| Cost to rebuild | €5,000 to €25,000, for 84 to 267 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.9 at a score of 65. 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,828 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 Sources.DeveloperAPI | 2 xtool | 3 XUtils | 4 XKit | 5 XCLIUtils | 6 DeveloperAPI | 7 PackLib | 8 XcodeProjects | 9 XToolSupport | 10 repository |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 Sources.DeveloperAPI | ||||||||||
| 2 xtool | ||||||||||
| 3 XUtils | 1 | 5 | ||||||||
| 4 XKit | 63 | 118 | 9 | |||||||
| 5 XCLIUtils | 5 | 8 | ||||||||
| 6 DeveloperAPI | 3 | 2 | 89 | |||||||
| 7 PackLib | 10 | 2 | 22 | |||||||
| 8 XcodeProjects | 4 | 5 | ||||||||
| 9 XToolSupport | 5 | 10 | 30 | 2 | ||||||
| 10 repository | 1 | 1 |
3→4 XUtils uses XKit part of a loop✕
- Connections
- 1 pair of types, where a type in XUtils uses a type in XKit.
- The types involved
XUtils.DispatchInput→XKit.Task
- Direction
- XUtils uses XKit, so a change to XKit can break XUtils, while a change to XUtils can't break XKit.
- 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.
3→5 XUtils uses XCLIUtils part of a loop✕
- Connections
- 5 pairs of types, where a type in XUtils uses a type in XCLIUtils.
- The types involved
XUtils.CommandOutput→XCLIUtils.StringXUtils.Data→XCLIUtils.StringXUtils.Foundation+Utils.swift→XCLIUtils.StringXUtils.Stream→XCLIUtils.StringXUtils.TemporaryDirectory→XCLIUtils.String
- Direction
- XUtils uses XCLIUtils, so a change to XCLIUtils can break XUtils, while a change to XUtils can't break XCLIUtils.
- 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.
4→3 XKit uses XUtils✕
- Connections
- 63 pairs of types, where a type in XKit uses a type in XUtils. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
XKit.ADIDataProvider→XUtils.DataXKit.AppInstaller→XUtils.URLXKit.AppTokens→XUtils.DataXKit.AutoSigner→XUtils.URLXKit.Certificate→XUtils.DataXKit.Certificate→XUtils.URLXKit.Client→XUtils.URLXKit.ClientDelegate→XUtils.DataXKit.DDILoc→XUtils.URLXKit.DDIMounter→XUtils.DataXKit.Decoder→XUtils.DataXKit.DeveloperAPIASCAuthMiddleware→XUtils.URLXKit.DeveloperAPIXcodeAuthMiddleware→XUtils.URLXKit.DeveloperServicesAPIVersion→XUtils.DataXKit.DeveloperServicesAPIVersion→XUtils.URLXKit.DeveloperServicesAPIVersionLegacy→XUtils.DataXKit.DeveloperServicesAPIVersionLegacy→XUtils.URLXKit.DeveloperServicesAddAppOperation→XUtils.URLXKit.DeveloperServicesProvisioningOperation→XUtils.URLXKit.DirectoryStorage→XUtils.DataXKit.DirectoryStorage→XUtils.URLXKit.GrandSlamAppTokensRequest→XUtils.DataXKit.GrandSlamAuthCompleteRequest→XUtils.DataXKit.GrandSlamAuthInitRequest→XUtils.DataXKit.GrandSlamDataDecoder→XUtils.Data
- Direction
- XKit uses XUtils, so a change to XUtils can break XKit, while a change to XKit can't break XUtils.
- Position
- Below the diagonal: XKit uses a module listed above it, which is the healthy direction.
4→5 XKit uses XCLIUtils part of a loop✕
- Connections
- 118 pairs of types, where a type in XKit uses a type in XCLIUtils. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
XKit.ADIDataProvider→XCLIUtils.StringXKit.APSEnvironmentEntitlement→XCLIUtils.StringXKit.ASCJWTGenerator→XCLIUtils.StringXKit.ASCKey→XCLIUtils.StringXKit.AnisetteData→XCLIUtils.StringXKit.AnisetteDataProvider→XCLIUtils.StringXKit.AppGroupEntitlement→XCLIUtils.StringXKit.AppInstaller→XCLIUtils.StringXKit.AppTokenKey→XCLIUtils.StringXKit.AppTokens→XCLIUtils.StringXKit.AppleSignInEntitlement→XCLIUtils.StringXKit.ApplicationIdentifierEntitlement→XCLIUtils.StringXKit.AssociatedDomainsEntitlement→XCLIUtils.StringXKit.AutoSigner→XCLIUtils.StringXKit.CSR→XCLIUtils.StringXKit.Certificate→XCLIUtils.StringXKit.ClientDelegate→XCLIUtils.StringXKit.ClientDevice→XCLIUtils.StringXKit.ClientInfoWithUserAgent→XCLIUtils.StringXKit.CodingKeys→XCLIUtils.StringXKit.Command→XCLIUtils.StringXKit.Connection→XCLIUtils.StringXKit.ConnectionDescriptor→XCLIUtils.StringXKit.ConnectionKey→XCLIUtils.StringXKit.ConnectionValue→XCLIUtils.String
- Direction
- XKit uses XCLIUtils, so a change to XCLIUtils can break XKit, while a change to XKit can't break XCLIUtils.
- 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.
4→6 XKit uses DeveloperAPI part of a loop✕
- Connections
- 9 pairs of types, where a type in XKit uses a type in DeveloperAPI.
- The types involved
XKit.ClientDevice→DeveloperAPI.DeviceXKit.Connection→DeveloperAPI.DeviceXKit.ConnectionValue→DeveloperAPI.DeviceXKit.DeveloperServicesAddAppOperation→DeveloperAPI.BundleIdXKit.DeveloperServicesAssignAppGroupsOperation→DeveloperAPI.BundleIdXKit.DeveloperServicesCapability→DeveloperAPI.CapabilitySettingXKit.DeveloperServicesCapability→DeveloperAPI.CapabilityTypeXKit.HeartbeatHandler→DeveloperAPI.DeviceXKit.SigningContext→DeveloperAPI.DeveloperAPIClient
- Direction
- XKit uses DeveloperAPI, so a change to DeveloperAPI can break XKit, while a change to XKit can't break DeveloperAPI.
- 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.
5→3 XCLIUtils uses XUtils✕
- Connections
- 5 pairs of types, where a type in XCLIUtils uses a type in XUtils.
- The types involved
XCLIUtils.CommandInput→XUtils.DataXCLIUtils.CommandInput→XUtils.DataChannelXCLIUtils.CommandInput→XUtils.LimitXCLIUtils.DependencyValues→XUtils.CommandOutputXCLIUtils.DependencyValues→XUtils.URL
- Direction
- XCLIUtils uses XUtils, so a change to XUtils can break XCLIUtils, while a change to XCLIUtils can't break XUtils.
- Position
- Below the diagonal: XCLIUtils uses a module listed above it, which is the healthy direction.
5→4 XCLIUtils uses XKit✕
- Connections
- 8 pairs of types, where a type in XCLIUtils uses a type in XKit.
- The types involved
XCLIUtils.DependencyValues→XKit.AnisetteDataProviderXCLIUtils.DependencyValues→XKit.HTTPClientProtocolXCLIUtils.DependencyValues→XKit.KeyValueStorageXCLIUtils.DependencyValues→XKit.RawADIProviderXCLIUtils.DependencyValues→XKit.SignerXCLIUtils.DependencyValues→XKit.SigningInfoManagerXCLIUtils.DependencyValues→XKit.ZIPCompressorXCLIUtils.State→XKit.Task
- Direction
- XCLIUtils uses XKit, so a change to XKit can break XCLIUtils, while a change to XCLIUtils can't break XKit.
- Position
- Below the diagonal: XCLIUtils uses a module listed above it, which is the healthy direction.
6→3 DeveloperAPI uses XUtils✕
- Connections
- 3 pairs of types, where a type in DeveloperAPI uses a type in XUtils.
- The types involved
DeveloperAPI.DeveloperAPIClient→XUtils.URLDeveloperAPI.Server1→XUtils.URLDeveloperAPI.Servers→XUtils.URL
- Direction
- DeveloperAPI uses XUtils, so a change to XUtils can break DeveloperAPI, while a change to DeveloperAPI can't break XUtils.
- Position
- Below the diagonal: DeveloperAPI uses a module listed above it, which is the healthy direction.
6→4 DeveloperAPI uses XKit✕
- Connections
- 2 pairs of types, where a type in DeveloperAPI uses a type in XKit.
- The types involved
DeveloperAPI.DeveloperAPIClient→XKit.DeveloperAPIAuthDataDeveloperAPI.DeveloperAPIClient→XKit.URLQueryItem
- Direction
- DeveloperAPI uses XKit, so a change to XKit can break DeveloperAPI, while a change to DeveloperAPI can't break XKit.
- Position
- Below the diagonal: DeveloperAPI uses a module listed above it, which is the healthy direction.
6→5 DeveloperAPI uses XCLIUtils✕
- Connections
- 89 pairs of types, where a type in DeveloperAPI uses a type in XCLIUtils. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
DeveloperAPI.AcceptableContentType→XCLIUtils.StringDeveloperAPI.AllowedInstancesPayload→XCLIUtils.StringDeveloperAPI.App→XCLIUtils.StringDeveloperAPI.AttributesPayload→XCLIUtils.StringDeveloperAPI.BundleId→XCLIUtils.StringDeveloperAPI.BundleIdCapabilitiesCreateInstance→XCLIUtils.StringDeveloperAPI.BundleIdCapabilitiesDeleteInstance→XCLIUtils.StringDeveloperAPI.BundleIdCapabilitiesUpdateInstance→XCLIUtils.StringDeveloperAPI.BundleIdCapability→XCLIUtils.StringDeveloperAPI.BundleIdPlatform→XCLIUtils.StringDeveloperAPI.BundleIdsAppGetToOneRelated→XCLIUtils.StringDeveloperAPI.BundleIdsAppGetToOneRelationship→XCLIUtils.StringDeveloperAPI.BundleIdsBundleIdCapabilitiesGetToManyRelated→XCLIUtils.StringDeveloperAPI.BundleIdsBundleIdCapabilitiesGetToManyRelationship→XCLIUtils.StringDeveloperAPI.BundleIdsCreateInstance→XCLIUtils.StringDeveloperAPI.BundleIdsDeleteInstance→XCLIUtils.StringDeveloperAPI.BundleIdsGetCollection→XCLIUtils.StringDeveloperAPI.BundleIdsGetInstance→XCLIUtils.StringDeveloperAPI.BundleIdsProfilesGetToManyRelated→XCLIUtils.StringDeveloperAPI.BundleIdsProfilesGetToManyRelationship→XCLIUtils.StringDeveloperAPI.BundleIdsUpdateInstance→XCLIUtils.StringDeveloperAPI.CapabilityOption→XCLIUtils.StringDeveloperAPI.CapabilitySetting→XCLIUtils.StringDeveloperAPI.CapabilityType→XCLIUtils.StringDeveloperAPI.Case2Payload→XCLIUtils.String
- Direction
- DeveloperAPI uses XCLIUtils, so a change to XCLIUtils can break DeveloperAPI, while a change to DeveloperAPI can't break XCLIUtils.
- Position
- Below the diagonal: DeveloperAPI uses a module listed above it, which is the healthy direction.
7→3 PackLib uses XUtils✕
- Connections
- 10 pairs of types, where a type in PackLib uses a type in XUtils.
- The types involved
PackLib.BuildSettings→XUtils.FilePathPackLib.Cache→XUtils.URLPackLib.DarwinSDK→XUtils.URLPackLib.PackSchema→XUtils.URLPackLib.Packer→XUtils.URLPackLib.Planner→XUtils.DataPackLib.Product→XUtils.URLPackLib.TemporaryBundle→XUtils.URLPackLib.ToolRegistry→XUtils.URLPackLib.XcodePacker→XUtils.URL
- Direction
- PackLib uses XUtils, so a change to XUtils can break PackLib, while a change to PackLib can't break XUtils.
- Position
- Below the diagonal: PackLib uses a module listed above it, which is the healthy direction.
7→4 PackLib uses XKit✕
- Connections
- 2 pairs of types, where a type in PackLib uses a type in XKit.
- The types involved
PackLib.BuildSettings→XKit.TaskPackLib.SwiftVersion→XKit.Task
- Direction
- PackLib uses XKit, so a change to XKit can break PackLib, while a change to PackLib can't break XKit.
- Position
- Below the diagonal: PackLib uses a module listed above it, which is the healthy direction.
7→5 PackLib uses XCLIUtils✕
- Connections
- 22 pairs of types, where a type in PackLib uses a type in XCLIUtils.
- The types involved
PackLib.BuildConfiguration→XCLIUtils.StringPackLib.BuildSettings→XCLIUtils.StringPackLib.BuildSystem→XCLIUtils.StringPackLib.Cache→XCLIUtils.StringPackLib.CodingKeys→XCLIUtils.StringPackLib.DarwinSDK→XCLIUtils.StringPackLib.Errors→XCLIUtils.StringPackLib.Extension→XCLIUtils.StringPackLib.IDSpecifier→XCLIUtils.StringPackLib.PackSchemaBase→XCLIUtils.StringPackLib.PackageDependency→XCLIUtils.StringPackLib.PackageDump→XCLIUtils.StringPackLib.PackageGraph→XCLIUtils.StringPackLib.Packer→XCLIUtils.StringPackLib.Planner→XCLIUtils.StringPackLib.Platform→XCLIUtils.StringPackLib.Product→XCLIUtils.StringPackLib.ProductType→XCLIUtils.StringPackLib.StringError→XCLIUtils.StringPackLib.SwiftVersion→XCLIUtils.StringPackLib.Target→XCLIUtils.StringPackLib.ToolRegistry→XCLIUtils.String
- Direction
- PackLib uses XCLIUtils, so a change to XCLIUtils can break PackLib, while a change to PackLib can't break XCLIUtils.
- Position
- Below the diagonal: PackLib uses a module listed above it, which is the healthy direction.
8→3 XcodeProjects uses XUtils✕
- Connections
- 4 pairs of types, where a type in XcodeProjects uses a type in XUtils.
- The types involved
XcodeProjects.Project→XUtils.DataXcodeProjects.XcodeProject→XUtils.URLXcodeProjects.XcodeWorkspace→XUtils.DataXcodeProjects.XcodeWorkspace→XUtils.URL
- Direction
- XcodeProjects uses XUtils, so a change to XUtils can break XcodeProjects, while a change to XcodeProjects can't break XUtils.
- Position
- Below the diagonal: XcodeProjects uses a module listed above it, which is the healthy direction.
8→5 XcodeProjects uses XCLIUtils✕
- Connections
- 5 pairs of types, where a type in XcodeProjects uses a type in XCLIUtils.
- The types involved
XcodeProjects.Base→XCLIUtils.StringXcodeProjects.Group→XCLIUtils.StringXcodeProjects.Location→XCLIUtils.StringXcodeProjects.Project→XCLIUtils.StringXcodeProjects.XcodeProject→XCLIUtils.String
- Direction
- XcodeProjects uses XCLIUtils, so a change to XCLIUtils can break XcodeProjects, while a change to XcodeProjects can't break XCLIUtils.
- Position
- Below the diagonal: XcodeProjects uses a module listed above it, which is the healthy direction.
9→3 XToolSupport uses XUtils✕
- Connections
- 5 pairs of types, where a type in XToolSupport uses a type in XUtils.
- The types involved
XToolSupport.LSPConfig→XUtils.URLXToolSupport.PackOperation→XUtils.URLXToolSupport.SDKBuilder→XUtils.URLXToolSupport.SimInstallOperation→XUtils.URLXToolSupport.XToolInstallerDelegate→XUtils.CommandOutput
- Direction
- XToolSupport uses XUtils, so a change to XUtils can break XToolSupport, while a change to XToolSupport can't break XUtils.
- Position
- Below the diagonal: XToolSupport uses a module listed above it, which is the healthy direction.
9→4 XToolSupport uses XKit✕
- Connections
- 10 pairs of types, where a type in XToolSupport uses a type in XKit.
- The types involved
XToolSupport.AuthToken→XKit.DeveloperAPIAuthDataXToolSupport.AuthToken→XKit.KeyValueStorageXToolSupport.ConnectionOptions→XKit.ClientDeviceXToolSupport.ConnectionOptions→XKit.SearchModeXToolSupport.DevicesCommand→XKit.SearchModeXToolSupport.WithoutSearchMode→XKit.ClientDeviceXToolSupport.WithoutSearchMode→XKit.SearchModeXToolSupport.XToolAuthDelegate→XKit.TwoFactorAuthDelegateXToolSupport.XToolInstallerDelegate→XKit.IntegratedInstallerDelegateXToolSupport.XToolInstallerDelegate→XKit.Message
- Direction
- XToolSupport uses XKit, so a change to XKit can break XToolSupport, while a change to XToolSupport can't break XKit.
- Position
- Below the diagonal: XToolSupport uses a module listed above it, which is the healthy direction.
9→5 XToolSupport uses XCLIUtils✕
- Connections
- 30 pairs of types, where a type in XToolSupport uses a type in XCLIUtils. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
XToolSupport.AppStoreConnect→XCLIUtils.StringXToolSupport.Arch→XCLIUtils.StringXToolSupport.ArchSelection→XCLIUtils.StringXToolSupport.AuthLoginCommand→XCLIUtils.StringXToolSupport.AuthMode→XCLIUtils.StringXToolSupport.AuthOperation→XCLIUtils.StringXToolSupport.AuthToken→XCLIUtils.StringXToolSupport.DevBSPCommand→XCLIUtils.StringXToolSupport.DevBuildCommand→XCLIUtils.StringXToolSupport.DevRunCommand→XCLIUtils.StringXToolSupport.DevSDKBuildCommand→XCLIUtils.StringXToolSupport.DevSDKInstallCommand→XCLIUtils.StringXToolSupport.Input→XCLIUtils.StringXToolSupport.InstallCommand→XCLIUtils.StringXToolSupport.InstallSDKOperation→XCLIUtils.StringXToolSupport.LaunchCommand→XCLIUtils.StringXToolSupport.NewCommand→XCLIUtils.StringXToolSupport.PackOperation→XCLIUtils.StringXToolSupport.ParsableCommand→XCLIUtils.StringXToolSupport.SDKBuilder→XCLIUtils.StringXToolSupport.SDKDefinition→XCLIUtils.StringXToolSupport.SimInstallOperation→XCLIUtils.StringXToolSupport.Triple→XCLIUtils.StringXToolSupport.UninstallCommand→XCLIUtils.StringXToolSupport.WithoutSearchMode→XCLIUtils.String
- Direction
- XToolSupport uses XCLIUtils, so a change to XCLIUtils can break XToolSupport, while a change to XToolSupport can't break XCLIUtils.
- Position
- Below the diagonal: XToolSupport uses a module listed above it, which is the healthy direction.
9→7 XToolSupport uses PackLib✕
- Connections
- 2 pairs of types, where a type in XToolSupport uses a type in PackLib.
- The types involved
XToolSupport.BuildOptions→PackLib.BuildConfigurationXToolSupport.LSPConfig→PackLib.PackSchema
- Direction
- XToolSupport uses PackLib, so a change to PackLib can break XToolSupport, while a change to XToolSupport can't break PackLib.
- Position
- Below the diagonal: XToolSupport uses a module listed above it, which is the healthy direction.
10→5 repository uses XCLIUtils✕
- Connections
- 1 pair of types, where a type in repository uses a type in XCLIUtils.
- The types involved
repository.ContentView→XCLIUtils.String
- Direction
- repository uses XCLIUtils, so a change to XCLIUtils can break repository, while a change to repository can't break XCLIUtils.
- Position
- Below the diagonal: repository uses a module listed above it, which is the healthy direction.
10→6 repository uses DeveloperAPI✕
- Connections
- 1 pair of types, where a type in repository uses a type in DeveloperAPI.
- The types involved
repository.XToolMacUI→DeveloperAPI.App
- Direction
- repository uses DeveloperAPI, so a change to DeveloperAPI can break repository, while a change to repository can't break DeveloperAPI.
- Position
- Below the diagonal: repository 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 — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 15 | High / Critical |
| A02:2025 — Security Misconfiguration | 15 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 11 | Medium |
Roadmap
Top priorities: 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; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Package.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 No ADRs found finding(s) in ADR Quality — start with Package.swift. | +4.7 pts | Low | ADR Quality |
| 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. | +7.2 pts | Medium | Security & performance tooling |
| 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. | +4.6 pts | Medium | Architecture documentation |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +3.5 pts | Medium | Release Hygiene |
| Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production. | +3.1 pts | Medium | Observability |
| Resolve the 1 No assertions finding(s) in Test Quality — start with DataChannelTests.swift. | +1.1 pts | Low | Test Quality |
| Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +0.4 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). | +0.4 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| Sources/XToolSupport/SDKBuilder.swift | 6.0 | Mixed | Explicit Debt: TodoComment |
| Sources/XToolSupport/DevCommand.swift | 6.0 | Mixed | Explicit Debt: TodoComment |
| Sources/PackLib/Planner.swift | 6.7 | Mixed | Explicit Debt: TodoComment |
| Sources/XKit/GrandSlam/Operations/GrandSlamTwoFactorAuthenticateOperation.swift | 6.7 | Mixed | Explicit Debt: TodoComment |
| Sources/XToolSupport/DSCommands/DSCertificatesCommand.swift | 7.2 | Mixed | Cyclomatic Complexity: DSCertificatesListCommand.run (cyclomatic 16) |
| Sources/XKit/Integration/IntegratedInstaller.swift | 7.3 | Mixed | Explicit Debt: TodoComment |
| Package.swift | 7.7 | Mixed | Explicit Debt: TodoComment |
| Sources/XToolSupport/DSCommands/DSProfilesCommand.swift | 7.8 | Mixed | Cyclomatic Complexity: DSProfilesListCommand.run (cyclomatic 16) |
| Sources/PackLib/XcodePacker.swift | 7.8 | Mixed | Cognitive Complexity: XcodePacker.createProject (cognitive 25) |
| Sources/XKit/DeveloperServices/App IDs/DeveloperServicesAddAppOperation.swift | 7.8 | Mixed | Cognitive Complexity: DeveloperServicesAddAppOperation.addApp (cognitive 20) |
| Sources/XKit/DeveloperServices/OpenAPI/DeveloperServices+OpenAPI.swift | 7.8 | Mixed | Cognitive Complexity: DeveloperAPIXcodeAuthMiddleware.intercept (cognitive 19) |
| REDACTED | 7.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| Examples/DemoTCA/Package.swift | 8.2 | Near-clean | Explicit Debt: TodoComment |
| Sources/xtool/XTool.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 45 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 45 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, 90 of 112 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 · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — 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. Coverage NOT MEASURED: the Swift half could not be measured — the Swift suite in . produced no coverage export. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- 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 source is present (.swift) and this repository declares a SwiftPM test suite (xtool), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — 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 repository declares a Swift Package.swift/Package.resolved, but the licence verdict published here was taken over its gem dependencies. Nothing was read about its SwiftPM dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- 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. Single-maintainer repository — bus factor is not applicable (20 contributor(s) across 447 commit(s) sampled, automation and bot accounts excluded). One of them holds 95% of the history; the other 19 hold 0.3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- 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.
- D32 Data Compliance (PII/GDPR) — 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. `Examples/DemoResources/Sources/DemoResources/App.swift`, `Examples/ExampleSupport/Sources/ExampleDynamicLibrary/ExampleDynamicLibrary.swift`, `Sources/PackLib/BuildSettings.swift`, `Sources/PackLib/DarwinSDK.swift`, `Sources/PackLib/Stdlib+Utils.swift`, … (+35 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — 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 Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is swift-dependencies, whose lifetimes are not modelled 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.
- AX6 Interface segregation — 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing 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.
- 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 DockerCompose (docker-compose.yml). compose up failed (exit 1 — a container did not start, exited, or never became healthy) — services.xtool-test: container name "xtool" is already in use by service {}"; runtime evidence skipped.
- 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.
- 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.
- P5 DR & Backup — 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. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- 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.
- X27 Collection changed while being enumerated — 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 Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's C, Swift (Foundation mutable collections) 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.
- 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.
- X5 Nullable reference types — 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 MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's C, Swift 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.
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 Secret Scanning: Secret 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").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- 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.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- 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.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- 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
3 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SDKBuilder.installDeveloper at 23.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with SDKBuilder.installDeveloper (cyclomatic 23), DSCertificatesListCommand.run (cyclomatic 16), DSProfilesListCommand.run (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 3 together lifts Cyclomatic Complexity from 9.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
11 method(s) exceeded the cognitive complexity threshold of 15; the worst was DSProfilesListCommand.run at 37.
What to do
- Bring the 11 bodies over 15 down to 15 or less in Cognitive Complexity — start with DSProfilesListCommand.run (cognitive 37), SDKBuilder.installDeveloper (cognitive 36), DSCertificatesListCommand.run (cognitive 31). — 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 11 together lifts Cognitive Complexity from 8.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
4 god class(es) detected.
What to do
- Resolve the 2 MethodTooLong finding(s) in God Classes — start with XcodePacker.swift, SDKBuilder.swift. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with SDKBuilder.swift. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with SDKBuilder.swift. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
5 duplicated block group(s) detected. 1.8 % of the production lines (217 of 11,828) are in a reported copy. A further 7 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 2 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with DataChannel.swift, AsyncHTTPClient+HTTP.swift. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with DSCertificatesCommand.swift. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (28 corresponding lines) finding(s) in Code Duplication — start with DevCommand.swift. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
9 production modules (SwiftPM), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 6 of the 9 (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).
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
0 of 20 classes have LCOM4 above 3.
D10 · Test Quality
0 skipped, 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 61 tests.
What to do
- Resolve the 1 No assertions finding(s) in Test Quality — start with DataChannelTests.swift. — One of this dimension's main actionable groups (1 warning-level).
D12 · Dependency Hygiene
9 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 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 105 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 105 gem(s) a consumer installs — this repository's runtime declarations closed transitively over its committed REDACTED. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. 1 of them publish no licence on rubygems.org; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's gem dependencies and nothing else. The repository also declares a Swift Package.swift/Package.resolved, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: Sources/XToolSupport/SDKBuilder.swift (10×23=230); Sources/XToolSupport/DSCommands/DSCertificatesCommand.swift (2×16=32); Sources/XToolSupport/DSCommands/DSProfilesCommand.swift (2×16=32) Repeated repair below the complexity floor: Sources/XKit/GrandSlam/Anisette/DeviceInfo.swift (3 of 5 changes were fixes)
What to do
- Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with SDKBuilder.swift, DSCertificatesCommand.swift, DSProfilesCommand.swift. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with DeviceInfo.swift. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
13 deducted task-comment markers across 11828 LoC (0.1/KLoC) → score 9.8. 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 13 TodoComment finding(s) in Explicit Debt — start with Package.swift (2), DevCommand.swift (2), SDKBuilder.swift (2). — One of this dimension's main actionable groups (13 warning-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Package.swift. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 2 build units (Bundler, SwiftPM) 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
2 % of calls cross a namespace and 20 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
15 finding(s): 0 critical, 15 high, 0 medium, 0 low. 13 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. semgrep hit a parse error in 6 file(s) — `Documentation/xtool.docc/First-app-code/build-3.sh` (lines 7–17), `Documentation/xtool.docc/First-app-code/rerun-5a.sh` (lines 7–17), `Documentation/xtool.docc/First-app-code/rerun-5b.sh` (lines 7–17), `Documentation/xtool.docc/First-app-code/rerun-6.sh` (lines 7–17), `Documentation/xtool.docc/First-app-code/template-4a.sh` (line 25), … (+1 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 12 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 (12 issue-level, 0 of them charged here).
- 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
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
What to do
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
15 finding(s): 0 critical, 1 high, 12 medium, 2 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 12 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (12). — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 62 of the 137 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: GrandSlamClient.swift↔HTTPClientProtocol.swift 60%; GrandSlamClient.swift↔AsyncHTTPClient+HTTP.swift 50%; GrandSlamClient.swift↔URLSession+HTTP.swift 50%
What to do
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with GrandSlamClient.swift. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- 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 — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 2 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
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
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `macOS`.
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 4 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. — REDACTED:5
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.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
- `sleep` is async and calls sleep — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs. — Sources/XKit/Utilities/Task+Utils.swift:2
What to do
- Swift: await instead of blocking — `try await Task.sleep(for:)` for Thread.sleep/sleep, a checked continuation instead of a DispatchSemaphore or DispatchGroup wait, the async Process and URLSession APIs; never park a thread waiting on a Task — the cooperative pool cannot guarantee it progress.
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
X28 · Index access outside its own emptiness guard
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/XUtils/TemporaryDirectory.swift:148
- `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/XToolSupport/XToolInstallerDelegate.swift:89
What to do
- Swallowed exception (empty catch)
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 80% | Strong | Solid. |
| Architecture | 90% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 64% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 55% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 78% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 85% | Strong | Strongest area. |
Not evidenced — 2 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.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 70 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 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
- 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 — not assessed — interface segregation is computed over a type surface 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
- 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 — compose up failed (exit 1 — a container did not start, exited, or never became healthy) — services.xtool-test: container name "xtool" is already in use by service {}"; runtime evidence skipped 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.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D11 Test Reliability — Test reliability not included — the .swift suite was found but not re-run
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- 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.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
- 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
- D32 Data Compliance (PII/GDPR) — 40 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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.
- 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 — Swift suite
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- 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.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 1% of this repository's production lines — swift (11,828 lines), c (106 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 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
- 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- X5 Nullable reference types — 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 — 16 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 72 finding(s)
- TodoComment Package.swift:79
- TodoComment Examples/DemoTCA/Package.swift:21
- TodoComment Sources/xtool/XTool.swift:11
- TodoComment Sources/XToolSupport/DevCommand.swift:31
- TodoComment Sources/XToolSupport/DevCommand.swift:302
- TodoComment Sources/XToolSupport/ProcessZIPCompressor.swift:9
- TodoComment Sources/XToolSupport/SDKBuilder.swift:103
- TodoComment Sources/XToolSupport/SDKBuilder.swift:801
- TodoComment Sources/XKit/Integration/IntegratedInstaller.swift:235
- TodoComment Sources/XKit/Integration/IntegratedInstaller.swift:319
- TodoComment Sources/XKit/GrandSlam/Operations/GrandSlamTwoFactorAuthenticateOperation.swift:29
- TodoComment Sources/XCLIUtils/Console.swift:37
- TodoComment Sources/PackLib/Planner.swift:76
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Hotspot: Sources/XToolSupport/SDKBuilder.swift Sources/XToolSupport/SDKBuilder.swift:479
- Hotspot: Sources/XToolSupport/DSCommands/DSCertificatesCommand.swift Sources/XToolSupport/DSCommands/DSCertificatesCommand.swift:25
- Hotspot: Sources/XToolSupport/DSCommands/DSProfilesCommand.swift Sources/XToolSupport/DSCommands/DSProfilesCommand.swift:27
- REDACTED
- REDACTED
- REDACTED
- MethodTooLong: XcodePacker.createProject Sources/PackLib/XcodePacker.swift:12
- MethodTooLong: SDKBuilder.installDeveloper Sources/XToolSupport/SDKBuilder.swift:479
- Edited copy of a member (8 corresponding lines) Sources/XUtils/DataChannel.swift:57
- Edited copy of a member (8 corresponding lines) Sources/XKit/HTTPClientProtocol/AsyncHTTPClient+HTTP.swift:89
- Off the main sequence: XcodeProjects
- Off the main sequence: XUtils
- SDKBuilder.installDeveloper (cyclomatic 23) Sources/XToolSupport/SDKBuilder.swift:479
- DSCertificatesListCommand.run (cyclomatic 16) Sources/XToolSupport/DSCommands/DSCertificatesCommand.swift:25
- DSProfilesListCommand.run (cyclomatic 16) Sources/XToolSupport/DSCommands/DSProfilesCommand.swift:27
- No assertions: newlinePreservesRemainderAfterPartialRead Tests/XToolTests/DataChannelTests.swift:39
- Repeated repair: Sources/XKit/GrandSlam/Anisette/DeviceInfo.swift Sources/XKit/GrandSlam/Anisette/DeviceInfo.swift:15
- DSProfilesListCommand.run (cognitive 37) Sources/XToolSupport/DSCommands/DSProfilesCommand.swift:27
- SDKBuilder.installDeveloper (cognitive 36) Sources/XToolSupport/SDKBuilder.swift:479
- DSCertificatesListCommand.run (cognitive 31) Sources/XToolSupport/DSCommands/DSCertificatesCommand.swift:25
- XcodePacker.createProject (cognitive 25) Sources/PackLib/XcodePacker.swift:12
- Planner.product (cognitive 24) Sources/PackLib/Planner.swift:118
- FileDescriptor.writeAllWaiting (cognitive 22) Sources/XUtils/System+Utils.swift:32
- DeveloperServicesAddAppOperation.addApp (cognitive 20) Sources/XKit/DeveloperServices/App IDs/DeveloperServicesAddAppOperation.swift:166
- DeveloperAPIXcodeAuthMiddleware.intercept (cognitive 19) Sources/XKit/DeveloperServices/OpenAPI/DeveloperServices+OpenAPI.swift:119
- DeveloperServicesAddAppOperation.upsertApp (cognitive 18) Sources/XKit/DeveloperServices/App IDs/DeveloperServicesAddAppOperation.swift:48
- TemporaryDirectoryRoot.pruneOrphans (cognitive 18) Sources/XUtils/TemporaryDirectory.swift:123
- DSDevicesListCommand.run (cognitive 17) Sources/XToolSupport/DSCommands/DSDevicesCommand.swift:24
- ClassTooLong: SDKBuilder Sources/XToolSupport/SDKBuilder.swift:10
- FileTooLong: XToolSupport/SDKBuilder.swift Sources/XToolSupport/SDKBuilder.swift
- REDACTED
- Change-coupling hub: GrandSlamClient.swift → AsyncHTTPClient+HTTP.swift, HTTPClientProtocol.swift, URLSession+HTTP.swift Sources/XKit/GrandSlam/GrandSlamClient.swift
- REDACTED
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) Sources/XToolSupport/DSCommands/DSCertificatesCommand.swift:25
- Edited copy of a member (28 corresponding lines) Sources/XToolSupport/DevCommand.swift:241
- Edited copy of a member (12 corresponding lines) Sources/XKit/GrandSlam/Operations/GrandSlamTwoFactorAuthenticateOperation.swift:28
- Edited copy of a member (6 corresponding lines) Sources/XKit/GrandSlam/Requests/Concrete/GrandSlamTrustedDeviceRequest.swift:50
- Edited copy of a member (9 corresponding lines) Documentation/xtool.docc/First-app-code/edit-2.swift:4
- Duplicated block (11–12 lines × 4) Sources/XToolSupport/DSCommands/DSCertificatesCommand.swift:31
- Duplicated block (12 lines × 2) Sources/XKit/DeveloperServices/OpenAPI/DeveloperServices+OpenAPI.swift:119
- Duplicated block (10–11 lines × 2) Sources/XToolSupport/DevCommand.swift:251
- Duplicated block (7 lines × 2) Sources/XKit/DeveloperServices/Certificates/DeveloperServicesFetchCertificateOperation.swift:39
- Duplicated block (5 lines × 2) Sources/XcodeProjects/XcodeProject.swift:79
- Sync-over-async blocking Sources/XKit/Utilities/Task+Utils.swift:2
- Swallowed exception (empty catch) Sources/XUtils/TemporaryDirectory.swift:148
- Swallowed exception (caught, then discarded) Sources/XToolSupport/XToolInstallerDelegate.swift:89
Minor — 15 finding(s)
- REDACTED
- REDACTED
- No ADRs found Package.swift:47
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No SAST REDACTED:5
- No changelog
- No security response headers detected netlify.toml:1
Minor — 9 finding(s)
- Outdated: async-http-client
- Outdated: swift-certificates
- Outdated: swift-collections
- Outdated: swift-crypto
- Outdated: swift-dependencies
- Outdated: swift-openapi-generator
- Outdated: swift-openapi-runtime
- Outdated: swift-system
- Outdated: xcodeproj
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-8086f55e38bf4d0299514f84a68a0e6d/history.json --exit-code 0 --source . | 0 | 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-8086f55e38bf4d0299514f84a68a0e6d/tree.json --exit-code 0 --source . | 0 | 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 --exclude Sources/DeveloperAPI/Generated . | 15 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 1 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 15 | artifacts/raw/trivy-config.json |
| 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. semgrep could not parse 40 file(s) — `Examples/DemoResources/Sources/DemoResources/App.swift`, `Examples/ExampleSupport/Sources/ExampleDynamicLibrary/ExampleDynamicLibrary.swift`, `Sources/PackLib/BuildSettings.swift`, `Sources/PackLib/DarwinSDK.swift`, `Sources/PackLib/Stdlib+Utils.swift`, … (+35 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |