Executive summary
firebase/FirebaseUI-iOS falls short of our standard for production, in part because we found no logging, tracing or health checks in the code. It scores 56 out of 100 and is rated Adequate, and 16 of its 29 critical findings are security problems.
Production Readiness, at 37, is the weakest lens and counts most in the score. The best first step is rebalancing the test suite towards unit tests, worth about 17 points. Making the tests check their results comes next, worth about 5 points. Raising Production Readiness to 70 would lift the score to about 70.
Thirteen pipeline steps install packages that can change without warning. Three passwords or keys are open to anyone who can read the repository. Pinning what the pipeline installs and replacing each exposed password or key would close both risks. The 13 tests that check nothing need to check the result they produce.
The product code is 10,657 lines, about €13,000 to rebuild.
If Production Readiness rose from 37 to 70, the lowest score rated Strong, the score would rise from 56 to about 70.
New since the last survey: 8 findings
- God Classes · MethodTooLong: MFAEnrolmentView.smsEnrollmentContent FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/MFAEnrolmentView.swift
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/MFAEnrolmentView.swift
- Code Duplication · Duplicated block (7 lines × 2) FirebaseSwiftUI/FirebaseAuthUIComponents/Sources/Components/AuthTextField.swift
- Churn × Complexity Hotspots · Hotspot: FirebaseSwiftUI/FirebaseAuthUIComponents/Sources/Components/AuthTextField.swift FirebaseSwiftUI/FirebaseAuthUIComponents/Sources/Components/AuthTextField.swift
- Churn × Complexity Hotspots · Repeated repair: FirebaseSwiftUI/FirebaseAuthUIComponents/Sources/Theme/AuthTypography.swift FirebaseSwiftUI/FirebaseAuthUIComponents/Sources/Theme/AuthTypography.swift
- Churn × Complexity Hotspots · Repeated repair: FirebaseSwiftUI/FirebaseAuthUIComponents/Sources/Components/VerificationCodeInputField.swift FirebaseSwiftUI/FirebaseAuthUIComponents/Sources/Components/VerificationCodeInputField.swift
- Change Coupling · Change coupling: EmailAuthView.swift ↔ EnterVerificationCodeView.swift FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/EmailAuthView.swift
- Documentation (README) · README may be stale
Fixed since the last survey: 2 findings
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/MFAEnrolmentView.swift
- Code Duplication · Duplicated block (11 lines × 2) FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/MFAEnrolmentView.swift
Rebuild cost: about €13,000 · Estimate
| Cost to rebuild | €4,500 to €22,000, for 74 to 236 hours of work, under 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.8 at a score of 56. 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: 10,657 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 FirebaseSwiftUI~FirebaseAuthSwiftUI | 2 FirebaseSwiftUI~FirebaseAuthSwiftUI~Auth | 3 FirebaseSwiftUI~FirebaseAuthSwiftUI~Utils | 4 FirebaseSwiftUI~FirebaseAuthUIComponents | 5 FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions | 6 FirebaseSwiftUI~FirebaseAuthUIComponents~Validation | 7 repository | 8 FirebaseSwiftUI~FirebaseAuthUIComponents~Theme | 9 FirebaseSwiftUI~FirebaseFacebookSwiftUI~Services | 10 FirebaseSwiftUI~FirebaseGoogleSwiftUI~Services | 11 FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services | 12 FirebaseSwiftUI~FirebaseTwitterSwiftUI~Services | 13 FirebaseSwiftUI~FirebaseAuthUIComponents~Components | 14 FirebaseSwiftUI~FirebaseAuthSwiftUI~Views | 15 FirebaseSwiftUI~FirebaseAuthSwiftUI~Services | 16 FirebaseSwiftUI~FirebaseFacebookSwiftUI~Views | 17 FirebaseSwiftUI~FirebaseGoogleSwiftUI~Views | 18 FirebaseSwiftUI~FirebaseOAuthSwiftUI~Views | 19 FirebaseSwiftUI~FirebasePhoneAuthSwiftUI~Views | 20 FirebaseSwiftUI~FirebaseTwitterSwiftUI~Views | 21 FirebaseSwiftUI~FirebaseAppleSwiftUI~Services | 22 FirebaseSwiftUI~FirebasePhoneAuthSwiftUI~Services | 23 FirebaseSwiftUI~FirebaseAppleSwiftUI~Views |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 FirebaseSwiftUI~FirebaseAuthSwiftUI | |||||||||||||||||||||||
| 2 FirebaseSwiftUI~FirebaseAuthSwiftUI~Auth | |||||||||||||||||||||||
| 3 FirebaseSwiftUI~FirebaseAuthSwiftUI~Utils | |||||||||||||||||||||||
| 4 FirebaseSwiftUI~FirebaseAuthUIComponents | |||||||||||||||||||||||
| 5 FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions | |||||||||||||||||||||||
| 6 FirebaseSwiftUI~FirebaseAuthUIComponents~Validation | |||||||||||||||||||||||
| 7 repository | |||||||||||||||||||||||
| 8 FirebaseSwiftUI~FirebaseAuthUIComponents~Theme | 2 | 2 | |||||||||||||||||||||
| 9 FirebaseSwiftUI~FirebaseFacebookSwiftUI~Services | 3 | ||||||||||||||||||||||
| 10 FirebaseSwiftUI~FirebaseGoogleSwiftUI~Services | 3 | ||||||||||||||||||||||
| 11 FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services | 1 | 3 | |||||||||||||||||||||
| 12 FirebaseSwiftUI~FirebaseTwitterSwiftUI~Services | 3 | ||||||||||||||||||||||
| 13 FirebaseSwiftUI~FirebaseAuthUIComponents~Components | 2 | 2 | 1 | 5 | |||||||||||||||||||
| 14 FirebaseSwiftUI~FirebaseAuthSwiftUI~Views | 2 | 5 | 2 | 5 | 2 | 2 | |||||||||||||||||
| 15 FirebaseSwiftUI~FirebaseAuthSwiftUI~Services | 3 | 3 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | ||||||||||||||
| 16 FirebaseSwiftUI~FirebaseFacebookSwiftUI~Views | 1 | 1 | |||||||||||||||||||||
| 17 FirebaseSwiftUI~FirebaseGoogleSwiftUI~Views | 1 | 1 | |||||||||||||||||||||
| 18 FirebaseSwiftUI~FirebaseOAuthSwiftUI~Views | 1 | 1 | |||||||||||||||||||||
| 19 FirebaseSwiftUI~FirebasePhoneAuthSwiftUI~Views | 1 | ||||||||||||||||||||||
| 20 FirebaseSwiftUI~FirebaseTwitterSwiftUI~Views | 1 | 1 | |||||||||||||||||||||
| 21 FirebaseSwiftUI~FirebaseAppleSwiftUI~Services | 3 | ||||||||||||||||||||||
| 22 FirebaseSwiftUI~FirebasePhoneAuthSwiftUI~Services | 3 | ||||||||||||||||||||||
| 23 FirebaseSwiftUI~FirebaseAppleSwiftUI~Views | 1 | 1 |
8→5 FirebaseSwiftUI~FirebaseAuthUIComponents~Theme uses FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions✕
- Connections
- 2 pairs of types, where a type in FirebaseSwiftUI~FirebaseAuthUIComponents~Theme uses a type in FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions.
- The types involved
FirebaseSwiftUI~FirebaseAuthUIComponents~Theme.AuthTextFieldStyle→FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions.ColorFirebaseSwiftUI~FirebaseAuthUIComponents~Theme.ProviderStyle→FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions.Color
- Direction
- FirebaseSwiftUI~FirebaseAuthUIComponents~Theme uses FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions, so a change to FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions can break FirebaseSwiftUI~FirebaseAuthUIComponents~Theme, while a change to FirebaseSwiftUI~FirebaseAuthUIComponents~Theme can't break FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseAuthUIComponents~Theme uses a module listed above it, which is the healthy direction.
8→14 FirebaseSwiftUI~FirebaseAuthUIComponents~Theme uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Views part of a loop✕
- Connections
- 2 pairs of types, where a type in FirebaseSwiftUI~FirebaseAuthUIComponents~Theme uses a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.
- The types involved
FirebaseSwiftUI~FirebaseAuthUIComponents~Theme.AuthCustomFontModifier→FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.ViewFirebaseSwiftUI~FirebaseAuthUIComponents~Theme.AuthFontModifier→FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.View
- Direction
- FirebaseSwiftUI~FirebaseAuthUIComponents~Theme uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Views, so a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Views can break FirebaseSwiftUI~FirebaseAuthUIComponents~Theme, while a change to FirebaseSwiftUI~FirebaseAuthUIComponents~Theme can't break FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→15 FirebaseSwiftUI~FirebaseFacebookSwiftUI~Services uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Services part of a loop✕
- Connections
- 3 pairs of types, where a type in FirebaseSwiftUI~FirebaseFacebookSwiftUI~Services uses a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.
- The types involved
FirebaseSwiftUI~FirebaseFacebookSwiftUI~Services.FacebookProviderAuthUI→FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthProviderSwiftFirebaseSwiftUI~FirebaseFacebookSwiftUI~Services.FacebookProviderAuthUI→FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthProviderUIFirebaseSwiftUI~FirebaseFacebookSwiftUI~Services.FacebookProviderSwift→FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.CredentialAuthProviderSwift
- Direction
- FirebaseSwiftUI~FirebaseFacebookSwiftUI~Services uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Services, so a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Services can break FirebaseSwiftUI~FirebaseFacebookSwiftUI~Services, while a change to FirebaseSwiftUI~FirebaseFacebookSwiftUI~Services can't break FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.
- 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.
10→15 FirebaseSwiftUI~FirebaseGoogleSwiftUI~Services uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Services part of a loop✕
- Connections
- 3 pairs of types, where a type in FirebaseSwiftUI~FirebaseGoogleSwiftUI~Services uses a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.
- The types involved
FirebaseSwiftUI~FirebaseGoogleSwiftUI~Services.GoogleProviderAuthUI→FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthProviderSwiftFirebaseSwiftUI~FirebaseGoogleSwiftUI~Services.GoogleProviderAuthUI→FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthProviderUIFirebaseSwiftUI~FirebaseGoogleSwiftUI~Services.GoogleProviderSwift→FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.CredentialAuthProviderSwift
- Direction
- FirebaseSwiftUI~FirebaseGoogleSwiftUI~Services uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Services, so a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Services can break FirebaseSwiftUI~FirebaseGoogleSwiftUI~Services, while a change to FirebaseSwiftUI~FirebaseGoogleSwiftUI~Services can't break FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.
- 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.
11→5 FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services uses FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions✕
- Connections
- 1 pair of types, where a type in FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services uses a type in FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions.
- The types involved
FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services.OAuthProviderSwift→FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions.Color
- Direction
- FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services uses FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions, so a change to FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions can break FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services, while a change to FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services can't break FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services uses a module listed above it, which is the healthy direction.
11→15 FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Services part of a loop✕
- Connections
- 3 pairs of types, where a type in FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services uses a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.
- The types involved
FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services.OAuthProviderAuthUI→FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthProviderSwiftFirebaseSwiftUI~FirebaseOAuthSwiftUI~Services.OAuthProviderAuthUI→FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthProviderUIFirebaseSwiftUI~FirebaseOAuthSwiftUI~Services.OAuthProviderSwift→FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.CredentialAuthProviderSwift
- Direction
- FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Services, so a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Services can break FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services, while a change to FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services can't break FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→15 FirebaseSwiftUI~FirebaseTwitterSwiftUI~Services uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Services part of a loop✕
- Connections
- 3 pairs of types, where a type in FirebaseSwiftUI~FirebaseTwitterSwiftUI~Services uses a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.
- The types involved
FirebaseSwiftUI~FirebaseTwitterSwiftUI~Services.TwitterProviderAuthUI→FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthProviderSwiftFirebaseSwiftUI~FirebaseTwitterSwiftUI~Services.TwitterProviderAuthUI→FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthProviderUIFirebaseSwiftUI~FirebaseTwitterSwiftUI~Services.TwitterProviderSwift→FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.CredentialAuthProviderSwift
- Direction
- FirebaseSwiftUI~FirebaseTwitterSwiftUI~Services uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Services, so a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Services can break FirebaseSwiftUI~FirebaseTwitterSwiftUI~Services, while a change to FirebaseSwiftUI~FirebaseTwitterSwiftUI~Services can't break FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.
- 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.
13→5 FirebaseSwiftUI~FirebaseAuthUIComponents~Components uses FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions✕
- Connections
- 2 pairs of types, where a type in FirebaseSwiftUI~FirebaseAuthUIComponents~Components uses a type in FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions.
- The types involved
FirebaseSwiftUI~FirebaseAuthUIComponents~Components.AuthProviderButton→FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions.ColorFirebaseSwiftUI~FirebaseAuthUIComponents~Components.SingleDigitField→FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions.Color
- Direction
- FirebaseSwiftUI~FirebaseAuthUIComponents~Components uses FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions, so a change to FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions can break FirebaseSwiftUI~FirebaseAuthUIComponents~Components, while a change to FirebaseSwiftUI~FirebaseAuthUIComponents~Components can't break FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseAuthUIComponents~Components uses a module listed above it, which is the healthy direction.
13→6 FirebaseSwiftUI~FirebaseAuthUIComponents~Components uses FirebaseSwiftUI~FirebaseAuthUIComponents~Validation✕
- Connections
- 2 pairs of types, where a type in FirebaseSwiftUI~FirebaseAuthUIComponents~Components uses a type in FirebaseSwiftUI~FirebaseAuthUIComponents~Validation.
- The types involved
FirebaseSwiftUI~FirebaseAuthUIComponents~Components.AuthTextField→FirebaseSwiftUI~FirebaseAuthUIComponents~Validation.FormValidatorFirebaseSwiftUI~FirebaseAuthUIComponents~Components.VerificationCodeInputField→FirebaseSwiftUI~FirebaseAuthUIComponents~Validation.FormValidator
- Direction
- FirebaseSwiftUI~FirebaseAuthUIComponents~Components uses FirebaseSwiftUI~FirebaseAuthUIComponents~Validation, so a change to FirebaseSwiftUI~FirebaseAuthUIComponents~Validation can break FirebaseSwiftUI~FirebaseAuthUIComponents~Components, while a change to FirebaseSwiftUI~FirebaseAuthUIComponents~Components can't break FirebaseSwiftUI~FirebaseAuthUIComponents~Validation.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseAuthUIComponents~Components uses a module listed above it, which is the healthy direction.
13→8 FirebaseSwiftUI~FirebaseAuthUIComponents~Components uses FirebaseSwiftUI~FirebaseAuthUIComponents~Theme✕
- Connections
- 1 pair of types, where a type in FirebaseSwiftUI~FirebaseAuthUIComponents~Components uses a type in FirebaseSwiftUI~FirebaseAuthUIComponents~Theme.
- The types involved
FirebaseSwiftUI~FirebaseAuthUIComponents~Components.AuthProviderButton→FirebaseSwiftUI~FirebaseAuthUIComponents~Theme.ProviderStyle
- Direction
- FirebaseSwiftUI~FirebaseAuthUIComponents~Components uses FirebaseSwiftUI~FirebaseAuthUIComponents~Theme, so a change to FirebaseSwiftUI~FirebaseAuthUIComponents~Theme can break FirebaseSwiftUI~FirebaseAuthUIComponents~Components, while a change to FirebaseSwiftUI~FirebaseAuthUIComponents~Components can't break FirebaseSwiftUI~FirebaseAuthUIComponents~Theme.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseAuthUIComponents~Components uses a module listed above it, which is the healthy direction.
13→14 FirebaseSwiftUI~FirebaseAuthUIComponents~Components uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Views part of a loop✕
- Connections
- 5 pairs of types, where a type in FirebaseSwiftUI~FirebaseAuthUIComponents~Components uses a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.
- The types involved
FirebaseSwiftUI~FirebaseAuthUIComponents~Components.AuthProviderButton→FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.ViewFirebaseSwiftUI~FirebaseAuthUIComponents~Components.AuthTextField→FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.ViewFirebaseSwiftUI~FirebaseAuthUIComponents~Components.CountrySelector→FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.ViewFirebaseSwiftUI~FirebaseAuthUIComponents~Components.SingleDigitField→FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.ViewFirebaseSwiftUI~FirebaseAuthUIComponents~Components.VerificationCodeInputField→FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.View
- Direction
- FirebaseSwiftUI~FirebaseAuthUIComponents~Components uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Views, so a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Views can break FirebaseSwiftUI~FirebaseAuthUIComponents~Components, while a change to FirebaseSwiftUI~FirebaseAuthUIComponents~Components can't break FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.
- 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.
14→1 FirebaseSwiftUI~FirebaseAuthSwiftUI~Views uses FirebaseSwiftUI~FirebaseAuthSwiftUI✕
- Connections
- 2 pairs of types, where a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Views uses a type in FirebaseSwiftUI~FirebaseAuthSwiftUI.
- The types involved
FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.AccountConflictModifier→FirebaseSwiftUI~FirebaseAuthSwiftUI.AccountConflictContextFirebaseSwiftUI~FirebaseAuthSwiftUI~Views.ReauthenticationCoordinator→FirebaseSwiftUI~FirebaseAuthSwiftUI.ReauthenticationType
- Direction
- FirebaseSwiftUI~FirebaseAuthSwiftUI~Views uses FirebaseSwiftUI~FirebaseAuthSwiftUI, so a change to FirebaseSwiftUI~FirebaseAuthSwiftUI can break FirebaseSwiftUI~FirebaseAuthSwiftUI~Views, while a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Views can't break FirebaseSwiftUI~FirebaseAuthSwiftUI.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseAuthSwiftUI~Views uses a module listed above it, which is the healthy direction.
14→2 FirebaseSwiftUI~FirebaseAuthSwiftUI~Views uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Auth✕
- Connections
- 5 pairs of types, where a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Views uses a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Auth.
- The types involved
FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.MFAEnrolmentView→FirebaseSwiftUI~FirebaseAuthSwiftUI~Auth.EnrollmentSessionFirebaseSwiftUI~FirebaseAuthSwiftUI~Views.MFAEnrolmentView→FirebaseSwiftUI~FirebaseAuthSwiftUI~Auth.SecondFactorTypeFirebaseSwiftUI~FirebaseAuthSwiftUI~Views.MFAHandlerModifier→FirebaseSwiftUI~FirebaseAuthSwiftUI~Auth.MFARequiredFirebaseSwiftUI~FirebaseAuthSwiftUI~Views.MFAResolutionView→FirebaseSwiftUI~FirebaseAuthSwiftUI~Auth.MFAHintFirebaseSwiftUI~FirebaseAuthSwiftUI~Views.MFAResolutionView→FirebaseSwiftUI~FirebaseAuthSwiftUI~Auth.MFARequired
- Direction
- FirebaseSwiftUI~FirebaseAuthSwiftUI~Views uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Auth, so a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Auth can break FirebaseSwiftUI~FirebaseAuthSwiftUI~Views, while a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Views can't break FirebaseSwiftUI~FirebaseAuthSwiftUI~Auth.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseAuthSwiftUI~Views uses a module listed above it, which is the healthy direction.
14→5 FirebaseSwiftUI~FirebaseAuthSwiftUI~Views uses FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions✕
- Connections
- 2 pairs of types, where a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Views uses a type in FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions.
- The types involved
FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.AuthCTAButtonStyle→FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions.ColorFirebaseSwiftUI~FirebaseAuthSwiftUI~Views.CTATintModifier→FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions.Color
- Direction
- FirebaseSwiftUI~FirebaseAuthSwiftUI~Views uses FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions, so a change to FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions can break FirebaseSwiftUI~FirebaseAuthSwiftUI~Views, while a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Views can't break FirebaseSwiftUI~FirebaseAuthUIComponents~Extensions.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseAuthSwiftUI~Views uses a module listed above it, which is the healthy direction.
14→8 FirebaseSwiftUI~FirebaseAuthSwiftUI~Views uses FirebaseSwiftUI~FirebaseAuthUIComponents~Theme✕
- Connections
- 5 pairs of types, where a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Views uses a type in FirebaseSwiftUI~FirebaseAuthUIComponents~Theme.
- The types involved
FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.EnvironmentValues→FirebaseSwiftUI~FirebaseAuthUIComponents~Theme.AuthTextFieldStyleFirebaseSwiftUI~FirebaseAuthSwiftUI~Views.EnvironmentValues→FirebaseSwiftUI~FirebaseAuthUIComponents~Theme.AuthTypographyFirebaseSwiftUI~FirebaseAuthSwiftUI~Views.View→FirebaseSwiftUI~FirebaseAuthUIComponents~Theme.AuthTextFieldStyleFirebaseSwiftUI~FirebaseAuthSwiftUI~Views.View→FirebaseSwiftUI~FirebaseAuthUIComponents~Theme.AuthTypographyFirebaseSwiftUI~FirebaseAuthSwiftUI~Views.View→FirebaseSwiftUI~FirebaseAuthUIComponents~Theme.TextStyle
- Direction
- FirebaseSwiftUI~FirebaseAuthSwiftUI~Views uses FirebaseSwiftUI~FirebaseAuthUIComponents~Theme, so a change to FirebaseSwiftUI~FirebaseAuthUIComponents~Theme can break FirebaseSwiftUI~FirebaseAuthSwiftUI~Views, while a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Views can't break FirebaseSwiftUI~FirebaseAuthUIComponents~Theme.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseAuthSwiftUI~Views uses a module listed above it, which is the healthy direction.
14→13 FirebaseSwiftUI~FirebaseAuthSwiftUI~Views uses FirebaseSwiftUI~FirebaseAuthUIComponents~Components✕
- Connections
- 2 pairs of types, where a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Views uses a type in FirebaseSwiftUI~FirebaseAuthUIComponents~Components.
- The types involved
FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.EnterPhoneNumberView→FirebaseSwiftUI~FirebaseAuthUIComponents~Components.CountryDataFirebaseSwiftUI~FirebaseAuthSwiftUI~Views.MFAEnrolmentView→FirebaseSwiftUI~FirebaseAuthUIComponents~Components.CountryData
- Direction
- FirebaseSwiftUI~FirebaseAuthSwiftUI~Views uses FirebaseSwiftUI~FirebaseAuthUIComponents~Components, so a change to FirebaseSwiftUI~FirebaseAuthUIComponents~Components can break FirebaseSwiftUI~FirebaseAuthSwiftUI~Views, while a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Views can't break FirebaseSwiftUI~FirebaseAuthUIComponents~Components.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseAuthSwiftUI~Views uses a module listed above it, which is the healthy direction.
14→15 FirebaseSwiftUI~FirebaseAuthSwiftUI~Views uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Services part of a loop✕
- Connections
- 2 pairs of types, where a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Views uses a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.
- The types involved
FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.DefaultAuthPickerDestination→FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthViewFirebaseSwiftUI~FirebaseAuthSwiftUI~Views.ReauthenticationHelpers.swift→FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthService
- Direction
- FirebaseSwiftUI~FirebaseAuthSwiftUI~Views uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Services, so a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Services can break FirebaseSwiftUI~FirebaseAuthSwiftUI~Views, while a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Views can't break FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→1 FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses FirebaseSwiftUI~FirebaseAuthSwiftUI✕
- Connections
- 3 pairs of types, where a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses a type in FirebaseSwiftUI~FirebaseAuthSwiftUI.
- The types involved
FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthService→FirebaseSwiftUI~FirebaseAuthSwiftUI.AccountConflictContextFirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthService→FirebaseSwiftUI~FirebaseAuthSwiftUI.AccountConflictTypeFirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthService→FirebaseSwiftUI~FirebaseAuthSwiftUI.OAuthReauthContext
- Direction
- FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses FirebaseSwiftUI~FirebaseAuthSwiftUI, so a change to FirebaseSwiftUI~FirebaseAuthSwiftUI can break FirebaseSwiftUI~FirebaseAuthSwiftUI~Services, while a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Services can't break FirebaseSwiftUI~FirebaseAuthSwiftUI.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses a module listed above it, which is the healthy direction.
15→2 FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Auth✕
- Connections
- 3 pairs of types, where a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Auth.
- The types involved
FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthService→FirebaseSwiftUI~FirebaseAuthSwiftUI~Auth.EnrollmentSessionFirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthService→FirebaseSwiftUI~FirebaseAuthSwiftUI~Auth.MFAHintFirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthService→FirebaseSwiftUI~FirebaseAuthSwiftUI~Auth.SecondFactorType
- Direction
- FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Auth, so a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Auth can break FirebaseSwiftUI~FirebaseAuthSwiftUI~Services, while a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Services can't break FirebaseSwiftUI~FirebaseAuthSwiftUI~Auth.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses a module listed above it, which is the healthy direction.
15→3 FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Utils✕
- Connections
- 1 pair of types, where a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Utils.
- The types involved
FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthService→FirebaseSwiftUI~FirebaseAuthSwiftUI~Utils.StringUtils
- Direction
- FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Utils, so a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Utils can break FirebaseSwiftUI~FirebaseAuthSwiftUI~Services, while a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Services can't break FirebaseSwiftUI~FirebaseAuthSwiftUI~Utils.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses a module listed above it, which is the healthy direction.
15→9 FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses FirebaseSwiftUI~FirebaseFacebookSwiftUI~Services✕
- Connections
- 1 pair of types, where a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses a type in FirebaseSwiftUI~FirebaseFacebookSwiftUI~Services.
- The types involved
FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthService→FirebaseSwiftUI~FirebaseFacebookSwiftUI~Services.FacebookProviderSwift
- Direction
- FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses FirebaseSwiftUI~FirebaseFacebookSwiftUI~Services, so a change to FirebaseSwiftUI~FirebaseFacebookSwiftUI~Services can break FirebaseSwiftUI~FirebaseAuthSwiftUI~Services, while a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Services can't break FirebaseSwiftUI~FirebaseFacebookSwiftUI~Services.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses a module listed above it, which is the healthy direction.
15→10 FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses FirebaseSwiftUI~FirebaseGoogleSwiftUI~Services✕
- Connections
- 1 pair of types, where a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses a type in FirebaseSwiftUI~FirebaseGoogleSwiftUI~Services.
- The types involved
FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthService→FirebaseSwiftUI~FirebaseGoogleSwiftUI~Services.GoogleProviderSwift
- Direction
- FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses FirebaseSwiftUI~FirebaseGoogleSwiftUI~Services, so a change to FirebaseSwiftUI~FirebaseGoogleSwiftUI~Services can break FirebaseSwiftUI~FirebaseAuthSwiftUI~Services, while a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Services can't break FirebaseSwiftUI~FirebaseGoogleSwiftUI~Services.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses a module listed above it, which is the healthy direction.
15→11 FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services✕
- Connections
- 1 pair of types, where a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses a type in FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services.
- The types involved
FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthService→FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services.OAuthProviderSwift
- Direction
- FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services, so a change to FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services can break FirebaseSwiftUI~FirebaseAuthSwiftUI~Services, while a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Services can't break FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses a module listed above it, which is the healthy direction.
15→12 FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses FirebaseSwiftUI~FirebaseTwitterSwiftUI~Services✕
- Connections
- 1 pair of types, where a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses a type in FirebaseSwiftUI~FirebaseTwitterSwiftUI~Services.
- The types involved
FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthService→FirebaseSwiftUI~FirebaseTwitterSwiftUI~Services.TwitterProviderSwift
- Direction
- FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses FirebaseSwiftUI~FirebaseTwitterSwiftUI~Services, so a change to FirebaseSwiftUI~FirebaseTwitterSwiftUI~Services can break FirebaseSwiftUI~FirebaseAuthSwiftUI~Services, while a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Services can't break FirebaseSwiftUI~FirebaseTwitterSwiftUI~Services.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses a module listed above it, which is the healthy direction.
15→14 FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Views✕
- Connections
- 2 pairs of types, where a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.
- The types involved
FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthService→FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.MultiFactorInfoFirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthService→FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.View
- Direction
- FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Views, so a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Views can break FirebaseSwiftUI~FirebaseAuthSwiftUI~Services, while a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Services can't break FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses a module listed above it, which is the healthy direction.
15→21 FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses FirebaseSwiftUI~FirebaseAppleSwiftUI~Services part of a loop✕
- Connections
- 1 pair of types, where a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses a type in FirebaseSwiftUI~FirebaseAppleSwiftUI~Services.
- The types involved
FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthService→FirebaseSwiftUI~FirebaseAppleSwiftUI~Services.AppleProviderSwift
- Direction
- FirebaseSwiftUI~FirebaseAuthSwiftUI~Services uses FirebaseSwiftUI~FirebaseAppleSwiftUI~Services, so a change to FirebaseSwiftUI~FirebaseAppleSwiftUI~Services can break FirebaseSwiftUI~FirebaseAuthSwiftUI~Services, while a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Services can't break FirebaseSwiftUI~FirebaseAppleSwiftUI~Services.
- 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.
16→9 FirebaseSwiftUI~FirebaseFacebookSwiftUI~Views uses FirebaseSwiftUI~FirebaseFacebookSwiftUI~Services✕
- Connections
- 1 pair of types, where a type in FirebaseSwiftUI~FirebaseFacebookSwiftUI~Views uses a type in FirebaseSwiftUI~FirebaseFacebookSwiftUI~Services.
- The types involved
FirebaseSwiftUI~FirebaseFacebookSwiftUI~Views.SignInWithFacebookButton→FirebaseSwiftUI~FirebaseFacebookSwiftUI~Services.FacebookProviderSwift
- Direction
- FirebaseSwiftUI~FirebaseFacebookSwiftUI~Views uses FirebaseSwiftUI~FirebaseFacebookSwiftUI~Services, so a change to FirebaseSwiftUI~FirebaseFacebookSwiftUI~Services can break FirebaseSwiftUI~FirebaseFacebookSwiftUI~Views, while a change to FirebaseSwiftUI~FirebaseFacebookSwiftUI~Views can't break FirebaseSwiftUI~FirebaseFacebookSwiftUI~Services.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseFacebookSwiftUI~Views uses a module listed above it, which is the healthy direction.
16→14 FirebaseSwiftUI~FirebaseFacebookSwiftUI~Views uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Views✕
- Connections
- 1 pair of types, where a type in FirebaseSwiftUI~FirebaseFacebookSwiftUI~Views uses a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.
- The types involved
FirebaseSwiftUI~FirebaseFacebookSwiftUI~Views.SignInWithFacebookButton→FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.View
- Direction
- FirebaseSwiftUI~FirebaseFacebookSwiftUI~Views uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Views, so a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Views can break FirebaseSwiftUI~FirebaseFacebookSwiftUI~Views, while a change to FirebaseSwiftUI~FirebaseFacebookSwiftUI~Views can't break FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseFacebookSwiftUI~Views uses a module listed above it, which is the healthy direction.
17→10 FirebaseSwiftUI~FirebaseGoogleSwiftUI~Views uses FirebaseSwiftUI~FirebaseGoogleSwiftUI~Services✕
- Connections
- 1 pair of types, where a type in FirebaseSwiftUI~FirebaseGoogleSwiftUI~Views uses a type in FirebaseSwiftUI~FirebaseGoogleSwiftUI~Services.
- The types involved
FirebaseSwiftUI~FirebaseGoogleSwiftUI~Views.SignInWithGoogleButton→FirebaseSwiftUI~FirebaseGoogleSwiftUI~Services.GoogleProviderSwift
- Direction
- FirebaseSwiftUI~FirebaseGoogleSwiftUI~Views uses FirebaseSwiftUI~FirebaseGoogleSwiftUI~Services, so a change to FirebaseSwiftUI~FirebaseGoogleSwiftUI~Services can break FirebaseSwiftUI~FirebaseGoogleSwiftUI~Views, while a change to FirebaseSwiftUI~FirebaseGoogleSwiftUI~Views can't break FirebaseSwiftUI~FirebaseGoogleSwiftUI~Services.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseGoogleSwiftUI~Views uses a module listed above it, which is the healthy direction.
17→14 FirebaseSwiftUI~FirebaseGoogleSwiftUI~Views uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Views✕
- Connections
- 1 pair of types, where a type in FirebaseSwiftUI~FirebaseGoogleSwiftUI~Views uses a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.
- The types involved
FirebaseSwiftUI~FirebaseGoogleSwiftUI~Views.SignInWithGoogleButton→FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.View
- Direction
- FirebaseSwiftUI~FirebaseGoogleSwiftUI~Views uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Views, so a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Views can break FirebaseSwiftUI~FirebaseGoogleSwiftUI~Views, while a change to FirebaseSwiftUI~FirebaseGoogleSwiftUI~Views can't break FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseGoogleSwiftUI~Views uses a module listed above it, which is the healthy direction.
18→11 FirebaseSwiftUI~FirebaseOAuthSwiftUI~Views uses FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services✕
- Connections
- 1 pair of types, where a type in FirebaseSwiftUI~FirebaseOAuthSwiftUI~Views uses a type in FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services.
- The types involved
FirebaseSwiftUI~FirebaseOAuthSwiftUI~Views.GenericOAuthButton→FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services.OAuthProviderSwift
- Direction
- FirebaseSwiftUI~FirebaseOAuthSwiftUI~Views uses FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services, so a change to FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services can break FirebaseSwiftUI~FirebaseOAuthSwiftUI~Views, while a change to FirebaseSwiftUI~FirebaseOAuthSwiftUI~Views can't break FirebaseSwiftUI~FirebaseOAuthSwiftUI~Services.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseOAuthSwiftUI~Views uses a module listed above it, which is the healthy direction.
18→14 FirebaseSwiftUI~FirebaseOAuthSwiftUI~Views uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Views✕
- Connections
- 1 pair of types, where a type in FirebaseSwiftUI~FirebaseOAuthSwiftUI~Views uses a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.
- The types involved
FirebaseSwiftUI~FirebaseOAuthSwiftUI~Views.GenericOAuthButton→FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.View
- Direction
- FirebaseSwiftUI~FirebaseOAuthSwiftUI~Views uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Views, so a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Views can break FirebaseSwiftUI~FirebaseOAuthSwiftUI~Views, while a change to FirebaseSwiftUI~FirebaseOAuthSwiftUI~Views can't break FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseOAuthSwiftUI~Views uses a module listed above it, which is the healthy direction.
19→14 FirebaseSwiftUI~FirebasePhoneAuthSwiftUI~Views uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Views✕
- Connections
- 1 pair of types, where a type in FirebaseSwiftUI~FirebasePhoneAuthSwiftUI~Views uses a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.
- The types involved
FirebaseSwiftUI~FirebasePhoneAuthSwiftUI~Views.PhoneAuthButtonView→FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.View
- Direction
- FirebaseSwiftUI~FirebasePhoneAuthSwiftUI~Views uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Views, so a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Views can break FirebaseSwiftUI~FirebasePhoneAuthSwiftUI~Views, while a change to FirebaseSwiftUI~FirebasePhoneAuthSwiftUI~Views can't break FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebasePhoneAuthSwiftUI~Views uses a module listed above it, which is the healthy direction.
20→12 FirebaseSwiftUI~FirebaseTwitterSwiftUI~Views uses FirebaseSwiftUI~FirebaseTwitterSwiftUI~Services✕
- Connections
- 1 pair of types, where a type in FirebaseSwiftUI~FirebaseTwitterSwiftUI~Views uses a type in FirebaseSwiftUI~FirebaseTwitterSwiftUI~Services.
- The types involved
FirebaseSwiftUI~FirebaseTwitterSwiftUI~Views.SignInWithTwitterButton→FirebaseSwiftUI~FirebaseTwitterSwiftUI~Services.TwitterProviderSwift
- Direction
- FirebaseSwiftUI~FirebaseTwitterSwiftUI~Views uses FirebaseSwiftUI~FirebaseTwitterSwiftUI~Services, so a change to FirebaseSwiftUI~FirebaseTwitterSwiftUI~Services can break FirebaseSwiftUI~FirebaseTwitterSwiftUI~Views, while a change to FirebaseSwiftUI~FirebaseTwitterSwiftUI~Views can't break FirebaseSwiftUI~FirebaseTwitterSwiftUI~Services.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseTwitterSwiftUI~Views uses a module listed above it, which is the healthy direction.
20→14 FirebaseSwiftUI~FirebaseTwitterSwiftUI~Views uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Views✕
- Connections
- 1 pair of types, where a type in FirebaseSwiftUI~FirebaseTwitterSwiftUI~Views uses a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.
- The types involved
FirebaseSwiftUI~FirebaseTwitterSwiftUI~Views.SignInWithTwitterButton→FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.View
- Direction
- FirebaseSwiftUI~FirebaseTwitterSwiftUI~Views uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Views, so a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Views can break FirebaseSwiftUI~FirebaseTwitterSwiftUI~Views, while a change to FirebaseSwiftUI~FirebaseTwitterSwiftUI~Views can't break FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseTwitterSwiftUI~Views uses a module listed above it, which is the healthy direction.
21→15 FirebaseSwiftUI~FirebaseAppleSwiftUI~Services uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Services✕
- Connections
- 3 pairs of types, where a type in FirebaseSwiftUI~FirebaseAppleSwiftUI~Services uses a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.
- The types involved
FirebaseSwiftUI~FirebaseAppleSwiftUI~Services.AppleProviderAuthUI→FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthProviderSwiftFirebaseSwiftUI~FirebaseAppleSwiftUI~Services.AppleProviderAuthUI→FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthProviderUIFirebaseSwiftUI~FirebaseAppleSwiftUI~Services.AppleProviderSwift→FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.CredentialAuthProviderSwift
- Direction
- FirebaseSwiftUI~FirebaseAppleSwiftUI~Services uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Services, so a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Services can break FirebaseSwiftUI~FirebaseAppleSwiftUI~Services, while a change to FirebaseSwiftUI~FirebaseAppleSwiftUI~Services can't break FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseAppleSwiftUI~Services uses a module listed above it, which is the healthy direction.
22→15 FirebaseSwiftUI~FirebasePhoneAuthSwiftUI~Services uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Services✕
- Connections
- 3 pairs of types, where a type in FirebaseSwiftUI~FirebasePhoneAuthSwiftUI~Services uses a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.
- The types involved
FirebaseSwiftUI~FirebasePhoneAuthSwiftUI~Services.PhoneAuthProviderAuthUI→FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthProviderSwiftFirebaseSwiftUI~FirebasePhoneAuthSwiftUI~Services.PhoneAuthProviderAuthUI→FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthProviderUIFirebaseSwiftUI~FirebasePhoneAuthSwiftUI~Services.PhoneProviderSwift→FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.AuthProviderSwift
- Direction
- FirebaseSwiftUI~FirebasePhoneAuthSwiftUI~Services uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Services, so a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Services can break FirebaseSwiftUI~FirebasePhoneAuthSwiftUI~Services, while a change to FirebaseSwiftUI~FirebasePhoneAuthSwiftUI~Services can't break FirebaseSwiftUI~FirebaseAuthSwiftUI~Services.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebasePhoneAuthSwiftUI~Services uses a module listed above it, which is the healthy direction.
23→14 FirebaseSwiftUI~FirebaseAppleSwiftUI~Views uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Views✕
- Connections
- 1 pair of types, where a type in FirebaseSwiftUI~FirebaseAppleSwiftUI~Views uses a type in FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.
- The types involved
FirebaseSwiftUI~FirebaseAppleSwiftUI~Views.SignInWithAppleButton→FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.View
- Direction
- FirebaseSwiftUI~FirebaseAppleSwiftUI~Views uses FirebaseSwiftUI~FirebaseAuthSwiftUI~Views, so a change to FirebaseSwiftUI~FirebaseAuthSwiftUI~Views can break FirebaseSwiftUI~FirebaseAppleSwiftUI~Views, while a change to FirebaseSwiftUI~FirebaseAppleSwiftUI~Views can't break FirebaseSwiftUI~FirebaseAuthSwiftUI~Views.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseAppleSwiftUI~Views uses a module listed above it, which is the healthy direction.
23→21 FirebaseSwiftUI~FirebaseAppleSwiftUI~Views uses FirebaseSwiftUI~FirebaseAppleSwiftUI~Services✕
- Connections
- 1 pair of types, where a type in FirebaseSwiftUI~FirebaseAppleSwiftUI~Views uses a type in FirebaseSwiftUI~FirebaseAppleSwiftUI~Services.
- The types involved
FirebaseSwiftUI~FirebaseAppleSwiftUI~Views.SignInWithAppleButton→FirebaseSwiftUI~FirebaseAppleSwiftUI~Services.AppleProviderSwift
- Direction
- FirebaseSwiftUI~FirebaseAppleSwiftUI~Views uses FirebaseSwiftUI~FirebaseAppleSwiftUI~Services, so a change to FirebaseSwiftUI~FirebaseAppleSwiftUI~Services can break FirebaseSwiftUI~FirebaseAppleSwiftUI~Views, while a change to FirebaseSwiftUI~FirebaseAppleSwiftUI~Views can't break FirebaseSwiftUI~FirebaseAppleSwiftUI~Services.
- Position
- Below the diagonal: FirebaseSwiftUI~FirebaseAppleSwiftUI~Views 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 |
| A07:2025 — Authentication Failures | 4 | High / Critical |
Roadmap
Begin by fixing the inverted test pyramid in Test Distribution and addressing the seven commented-out assertions and six non-verifying tests in the specified Firebase test files. Simultaneously, implement diagnostic logging via os.Logger for all subsystems, prioritizing error paths that currently provide no visibility. Finally, document significant design decisions in a structured ADR format to establish a clear record of architectural choices and their consequences.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Inverted test pyramid finding(s) in Test Distribution. | +16.6 pts | Low | Test Distribution |
| Resolve the 7 Assertions commented out finding(s) in Test Quality — start with FirebaseAppleSwiftUITests.swift, FirebaseAuthSwiftUITests.swift, FirebaseFacebookSwiftUITests.swift. | +5.4 pts | Low | Test Quality |
| Resolve the 6 Test project verifies nothing finding(s) in Test Quality — start with FirebaseAppleSwiftUITests.swift, FirebaseFacebookSwiftUITests.swift, FirebaseGoogleSwiftUITests.swift. | +4.6 pts | Low | Test Quality |
| Write a diagnostic trail the user can hand back with a bug report: log through `os.Logger` (one per subsystem), which the unified log keeps and a sysdiagnose carries to you. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +7.4 pts | Medium | Observability |
| 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.2 pts | Medium | Architecture documentation |
| 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. | +3.6 pts | Medium | Security & performance tooling |
| Resolve the 2 No assertions finding(s) in Test Quality — start with MFAEnrolmentUITests.swift (2). | +1.5 pts | Low | Test Quality |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +1.5 pts | Low | Bus Factor |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/EmailAuthView.swift | 5.5 | Mixed | God Classes: MethodTooLong: EmailAuthView.body |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| FirebaseSwiftUI/FirebaseAppleSwiftUI/Sources/Views/SignInWithAppleButton.swift | 5.9 | Mixed | Code Duplication: Members sharing a duplicated core (5 members, 50+ identical tokens) |
| FirebaseSwiftUI/FirebaseAppleSwiftUI/Tests/FirebaseAppleSwiftUITests/FirebaseAppleSwiftUITests.swift | 7.0 | Mixed | Test Quality: Assertions commented out: example |
| FirebaseSwiftUI/FirebaseFacebookSwiftUI/Tests/FirebaseFacebookSwiftUITests/FirebaseFacebookSwiftUITests.swift | 7.0 | Mixed | Test Quality: Assertions commented out: example |
| FirebaseSwiftUI/FirebaseGoogleSwiftUI/Tests/FirebaseGoogleSwiftUITests/FirebaseGoogleSwiftUITests.swift | 7.0 | Mixed | Test Quality: Assertions commented out: example |
| FirebaseSwiftUI/FirebaseOAuthSwiftUI/Tests/FirebaseOAuthSwiftUITests/FirebaseOAuthSwiftUITests.swift | 7.0 | Mixed | Test Quality: Assertions commented out: example |
| FirebaseSwiftUI/FirebasePhoneAuthSwiftUI/Tests/FirebasePhoneAuthSwiftUITests/FirebasePhoneAuthSwiftUITests.swift | 7.0 | Mixed | Test Quality: Assertions commented out: example |
| FirebaseSwiftUI/FirebaseTwitterSwiftUI/Tests/FirebaseTwitterSwiftUITests/FirebaseTwitterSwiftUITests.swift | 7.0 | Mixed | Test Quality: Assertions commented out: example |
| FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/MFAEnrolmentView.swift | 7.0 | Mixed | God Classes: MethodTooLong: MFAEnrolmentView.totpEnrollmentContent |
| FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Services/AuthService.swift | 7.2 | Mixed | Cognitive Complexity: AuthService.handleSignInLink (cognitive 37) |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| FirebaseSwiftUI/FirebaseAuthUIComponents/Sources/Components/AuthTextField.swift | 7.4 | Mixed | Cyclomatic Complexity: AuthTextField.body (cyclomatic 16) |
| FirebaseSwiftUI/FirebaseAuthUIComponents/Sources/Components/VerificationCodeInputField.swift | 7.8 | Mixed | Code Duplication: Duplicated block (23 lines × 2) |
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
Watchdog 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. 42 of 42 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 42 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, 80 of 95 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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 |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D4 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. The 17 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .m (5,387 lines, 34% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
- D8 Code Coverage — not measured this run — Watchdog 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 — a coverage step in CI (`-enableCodeCoverage YES`) shows coverage is measured in your own CI. Commit the lcov/Cobertura report it produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog 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 (FirebaseUI), but it was not re-run: no test result was produced. 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 — Watchdog measured this, but not all of it. What it 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.
- D21 Naming Consistency — not measured this run — Watchdog 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. D21's deterministic naming 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. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog 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 — Watchdog 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 the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D26 Project Cohesion — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. Project size and spread are measured over build units whose source a code model reads. This repository's .m source is a material share of its production lines and was read by none, so the score is a verdict about the units that were read. Not a finding that the unread source is cohesive — it is unmeasured.
- D27 Navigability — not measured this run — Watchdog 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog 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. `FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/AuthPickerView.swift`, `FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/EmailAuthView.swift`, `FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/EmailLinkReauthView.swift`, `FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/EmailLinkView.swift`, `FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/EmailReauthView.swift`, … (+16 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.
- AX6 Interface segregation — not measured this run — Watchdog 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.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog 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. Subject: a native UI project (samples/swiftui/FirebaseSwiftUISample/FirebaseSwiftUISample.xcodeproj/project.pbxproj). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C1 Data Protection — not measured this run — Watchdog 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 — Watchdog 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — Watchdog 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 retention 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 retention controls.
- C5 Data-Subject Rights — not measured this run — Watchdog 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 data-subject rights 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 data-subject rights controls.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog 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 no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Swift, c, objectivec 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 — Watchdog 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 no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Swift, c, objectivec 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 — Watchdog measured this, but not all of it. What it 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.
- P8 Schema migrations — not measured this run — Watchdog 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 EF Core usage in C# and the schema tooling its file scan recognises only, and no .NET project was loaded, and this repository's language is not one the scan models, 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.
- X1 Async correctness — not measured this run — Watchdog 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, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, 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.
- X12 Unreachable branch — not measured this run — Watchdog 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, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
- X13 Undrained process stream — not measured this run — Watchdog 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, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
- X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog 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, Scala, PHP, Ruby, Python, Go, Rust and Dart source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Ruby, Python, Go, Rust or Dart was found in this repository, 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.
- X16 Unfloored truncation loop — not measured this run — Watchdog 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, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog 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, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
- X18 Disposal-pattern correctness — not measured this run — Watchdog 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, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, 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.
- X19 Unrestored process-global state — not measured this run — Watchdog 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, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, 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.
- X2 Cancellation propagation — not measured this run — Watchdog 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 JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python or Rust was found in this repository, 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.
- X22 Contradicted release guard — not measured this run — Watchdog 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, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's C, Objective-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.
- X23 Unguarded diagnostic materialisation — not measured this run — Watchdog 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, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, 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.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog 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, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, 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.
- X25 Inert configuration knob — not measured this run — Watchdog 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, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, 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 — Watchdog 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 Objective-C 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.
- X29 Per-element action decided by a fixed element — not measured this run — Watchdog 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, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
- X30 Support guard that admits what it rejects — not measured this run — Watchdog 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 Scala, JavaScript/TypeScript, Java, Kotlin, Python, PHP, Go, Rust, Dart and Ruby source only, and no C# was loaded and no Scala, JavaScript, TypeScript, Java, Kotlin, Python, PHP, Go, Rust, Dart or Ruby was found in this repository, 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 — Watchdog 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 no JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala or Rust was found in this repository, 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 — Watchdog 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, Objectivec, 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
Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- 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.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- 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.
- 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.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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 Dockerfile (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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- 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
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was AuthTextField.body at 16. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being AuthServiceError.errorDescription at 18 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/AuthServiceError.swift (AuthServiceError.errorDescription at 18). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with AuthTextField.body (cyclomatic 16). — Refactoring it lifts Cyclomatic Complexity from 9.9 to about 10.0/10.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
3 method(s) exceeded the cognitive complexity threshold of 15; the worst was AuthService.handleSignInLink at 37.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cognitive Complexity — start with AuthService.handleSignInLink (cognitive 37), AuthTextField.body (cognitive 22), AuthService.completeEnrollment (cognitive 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 Cognitive Complexity from 8.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
5 god class(es) detected.
What to do
- Resolve the 3 MethodTooLong finding(s) in God Classes — start with MFAEnrolmentView.swift (2), EmailAuthView.swift. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with AuthService.swift. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with AuthService.swift. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
17 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 3 of the 19 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population. Measured on part of this repository only: .m (34% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.
What to do
- Resolve the 2 Duplicated block (13–15 lines × 3) finding(s) in Code Duplication — start with MFAEnrolmentView.swift (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with MFAResolutionView.swift, ChatViewController.swift. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Members sharing a duplicated core (5 members, 50+ identical tokens) finding(s) in Code Duplication — start with SignInWithAppleButton.swift. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
12 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 8 of the 12 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
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).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
1 of 13 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with StorageViewController.swift. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
48 test methods: 7 unit, 0 integration, 0 BDD, 41 e2e.
What to do
- Resolve the 1 Inverted test pyramid finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
D10 · Test Quality
0 skipped, 9 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 48 tests.
What to do
- Resolve the 7 Assertions commented out finding(s) in Test Quality — start with FirebaseAppleSwiftUITests.swift, FirebaseAuthSwiftUITests.swift, FirebaseFacebookSwiftUITests.swift. — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 6 Test project verifies nothing finding(s) in Test Quality — start with FirebaseAppleSwiftUITests.swift, FirebaseFacebookSwiftUITests.swift, FirebaseGoogleSwiftUITests.swift. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 2 No assertions finding(s) in Test Quality — start with MFAEnrolmentUITests.swift (2). — One of this dimension's main actionable groups (2 warning-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D12 · Dependency Hygiene
2 outdated direct SwiftPM dependencies, 0 pinning defect(s). SwiftPM has no package registry: a dependency is a repository URL and its releases are that repository's semver tags, so currency is answered by listing tags rather than by querying an index. Only a newer tag on the SAME MAJOR is reported — a `from:` requirement admits everything below the next major and nothing above it, so a major crossing needs a Package.swift edit rather than an update, and naming the update as its remedy would be wrong. Whether any dependency is DEPRECATED or ABANDONED is not graded and cannot be: a repository publishes no such marker, and there is no registry that could carry one. Known CVEs in this dependency graph are D30's question.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 44 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 44 gem(s) a consumer installs — this repository's runtime declarations closed transitively over its committed Gemfile.lock. 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: FirebaseSwiftUI/FirebaseAuthUIComponents/Sources/Components/AuthTextField.swift (4×16=64) Repeated repair below the complexity floor: FirebaseSwiftUI/FirebaseAuthUIComponents/Sources/Theme/AuthTypography.swift (3 of 4 changes were fixes); FirebaseSwiftUI/FirebaseAuthUIComponents/Sources/Components/VerificationCodeInputField.swift (3 of 4 changes were fixes)
What to do
- Resolve the 2 Repeated repair finding(s) in Churn × Complexity Hotspots — start with AuthTypography.swift, VerificationCodeInputField.swift. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with AuthTextField.swift. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
15 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Services/AuthService.swift. Counted over 43 of the 70 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
1 deducted task-comment markers across 10657 LoC (0.0/KLoC) → score 10.0. 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 1 TodoComment finding(s) in Explicit Debt — start with MFAResolutionUITests.swift. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D26 · Project Cohesion
1 of 2 build units (Bundler, Xcode) flagged as possibly oversized/incoherent. This repository's .m source was read by no build unit, so this covers part of the tree, not all of it.
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).
D28 · Secrets (history)
3 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
15 finding(s): 0 critical, 13 high, 2 medium, 0 low.
What to do
- Resolve the 13 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (13 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 43 of the 70 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: SignInWithAppleButton.swift↔SignInWithTwitterButton.swift 83%; SignInWithAppleButton.swift↔SignInWithGoogleButton.swift 83%; SignInWithAppleButton.swift↔GenericOAuthButton.swift 75%
What to do
- Resolve the 6 Change coupling finding(s) in Change Coupling — start with SignInWithFacebookButton.swift (2), EmailAuthView.swift (2), SignInWithGoogleButton.swift. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 2 Change-coupling hub finding(s) in Change Coupling — start with SignInWithAppleButton.swift, GenericOAuthButton.swift. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with AppleProviderAuthUI.swift. — One of this dimension's main actionable groups (1 warning-level).
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 3 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
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
M1 · Documentation (README)
- 34 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
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.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Review the README against recent changes; refresh the parts that drifted.
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.
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.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
- 71/99 types (72%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Swift: leave it `internal` (the default) instead of `public`) so internals can change without breaking consumers.
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: log through `os.Logger` (one per subsystem), which the unified log keeps and a sysdiagnose carries to you. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
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 28493 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:14
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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
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 `firebase.json` 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.) — e2eTest/FirebaseSwiftUIExample/FirebaseSwiftUIExample/firebase.json: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.
X14 · Bypassable address classification
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. — FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/UpdatePasswordView.swift:55
- `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. — FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Services/AuthService.swift:1174
What to do
- Swallowed exception (empty catch)
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 82% | Strong | Solid. |
| Architecture | 87% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 63% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 37% | Weak — gated by D9, P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 78% | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention 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 retention 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.
- C5 Data-Subject Rights — Not assessed: these data-subject rights 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 data-subject rights 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.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- 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.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Swift imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- 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.
- 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
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .swift suite was found but not re-run
- 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.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# only; Swift not measured.
- 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# and Visual Basic comments only — this repository's production source is .swift, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.swift), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 21 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release).
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- 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
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Swift source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — 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
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `swift test --enable-code-coverage` (SwiftPM) or `xcodebuild test -scheme <YourScheme> -enableCodeCoverage YES` (an .xcodeproj/.xcworkspace suite), then `xcrun llvm-cov export -format=lcov`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- 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 applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Swift code has 10,272 production line(s), 1 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- X1 Async correctness — 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
- X12 Unreachable branch — 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
- X13 Undrained process stream — 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
- X15 Unvalidated length from an untrusted reader — 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
- X16 Unfloored truncation loop — 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
- X17 Uncapped recursion over a caller-supplied document — 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
- X18 Disposal-pattern correctness — 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
- X19 Unrestored process-global state — 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
- 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: this check looks for a pattern guard or `case` label that increments, decrements or assigns while the switch is deciding whether it matches, and in this repository's languages none can. In C a `case` label must be a constant expression, and a switch has no guards, so no label can change state. In Objective-C a `case` label must be a constant expression, and a switch has no guards, so no label can change state. Swift has no `++` or `--`, and an assignment yields `()`, which cannot be an operand of `&&`, `||` or `?:` nor the Bool a `case … where` clause needs. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — 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
- X23 Unguarded diagnostic materialisation — 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
- X24 Document value interpolated into markup unescaped — 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
- X25 Inert configuration knob — 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
- 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 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
- X30 Support guard that admits what it rejects — 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
- 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 — 29 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Assertions commented out: example FirebaseSwiftUI/FirebaseAppleSwiftUI/Tests/FirebaseAppleSwiftUITests/FirebaseAppleSwiftUITests.swift:18
- Assertions commented out: example FirebaseSwiftUI/FirebaseAuthSwiftUI/Tests/FirebaseAuthSwiftUITests/FirebaseAuthSwiftUITests.swift:18
- Assertions commented out: example FirebaseSwiftUI/FirebaseFacebookSwiftUI/Tests/FirebaseFacebookSwiftUITests/FirebaseFacebookSwiftUITests.swift:18
- Assertions commented out: example FirebaseSwiftUI/FirebaseGoogleSwiftUI/Tests/FirebaseGoogleSwiftUITests/FirebaseGoogleSwiftUITests.swift:18
- Assertions commented out: example FirebaseSwiftUI/FirebaseOAuthSwiftUI/Tests/FirebaseOAuthSwiftUITests/FirebaseOAuthSwiftUITests.swift:18
- Assertions commented out: example FirebaseSwiftUI/FirebasePhoneAuthSwiftUI/Tests/FirebasePhoneAuthSwiftUITests/FirebasePhoneAuthSwiftUITests.swift:18
- Assertions commented out: example FirebaseSwiftUI/FirebaseTwitterSwiftUI/Tests/FirebaseTwitterSwiftUITests/FirebaseTwitterSwiftUITests.swift:18
- Test project verifies nothing: FirebaseAppleSwiftUITests FirebaseSwiftUI/FirebaseAppleSwiftUI/Tests/FirebaseAppleSwiftUITests/FirebaseAppleSwiftUITests.swift:18
- Test project verifies nothing: FirebaseFacebookSwiftUITests FirebaseSwiftUI/FirebaseFacebookSwiftUI/Tests/FirebaseFacebookSwiftUITests/FirebaseFacebookSwiftUITests.swift:18
- Test project verifies nothing: FirebaseGoogleSwiftUITests FirebaseSwiftUI/FirebaseGoogleSwiftUI/Tests/FirebaseGoogleSwiftUITests/FirebaseGoogleSwiftUITests.swift:18
- Test project verifies nothing: FirebaseOAuthSwiftUITests FirebaseSwiftUI/FirebaseOAuthSwiftUI/Tests/FirebaseOAuthSwiftUITests/FirebaseOAuthSwiftUITests.swift:18
- Test project verifies nothing: FirebasePhoneAuthSwiftUITests FirebaseSwiftUI/FirebasePhoneAuthSwiftUI/Tests/FirebasePhoneAuthSwiftUITests/FirebasePhoneAuthSwiftUITests.swift:18
- Test project verifies nothing: FirebaseTwitterSwiftUITests FirebaseSwiftUI/FirebaseTwitterSwiftUI/Tests/FirebaseTwitterSwiftUITests/FirebaseTwitterSwiftUITests.swift:18
- REDACTED
- REDACTED
- REDACTED
Serious — 53 finding(s)
- Change coupling: SignInWithGoogleButton.swift ↔ SignInWithTwitterButton.swift FirebaseSwiftUI/FirebaseGoogleSwiftUI/Sources/Views/SignInWithGoogleButton.swift:1
- Change coupling: SignInWithFacebookButton.swift ↔ SignInWithTwitterButton.swift FirebaseSwiftUI/FirebaseFacebookSwiftUI/Sources/Views/SignInWithFacebookButton.swift:1
- Change coupling: EmailAuthView.swift ↔ EmailLinkView.swift FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/EmailAuthView.swift:1
- Change coupling: EmailLinkView.swift ↔ PasswordRecoveryView.swift FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/EmailLinkView.swift:1
- Change coupling: SignInWithFacebookButton.swift ↔ SignInWithGoogleButton.swift FirebaseSwiftUI/FirebaseFacebookSwiftUI/Sources/Views/SignInWithFacebookButton.swift:1
- Change coupling: EmailAuthView.swift ↔ EnterVerificationCodeView.swift FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/EmailAuthView.swift:1
- MethodTooLong: EmailAuthView.body FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/EmailAuthView.swift:107
- MethodTooLong: MFAEnrolmentView.totpEnrollmentContent FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/MFAEnrolmentView.swift:506
- MethodTooLong: MFAEnrolmentView.smsEnrollmentContent FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/MFAEnrolmentView.swift:370
- No assertions: testMFAManagementButtonExistsAndIsTappable e2eTest/FirebaseSwiftUIExample/FirebaseSwiftUIExampleUITests/MFAEnrolmentUITests.swift:46
- No assertions: testErrorMessageDisplay e2eTest/FirebaseSwiftUIExample/FirebaseSwiftUIExampleUITests/MFAEnrolmentUITests.swift:348
- Repeated repair: FirebaseSwiftUI/FirebaseAuthUIComponents/Sources/Theme/AuthTypography.swift FirebaseSwiftUI/FirebaseAuthUIComponents/Sources/Theme/AuthTypography.swift:123
- Repeated repair: FirebaseSwiftUI/FirebaseAuthUIComponents/Sources/Components/VerificationCodeInputField.swift FirebaseSwiftUI/FirebaseAuthUIComponents/Sources/Components/VerificationCodeInputField.swift:57
- REDACTED
- REDACTED
- Change-coupling hub: SignInWithAppleButton.swift → EmailAuthView.swift, SignInWithFacebookButton.swift, SignInWithGoogleButton.swift, GenericOAuthButton.swift, SignInWithTwitterButton.swift FirebaseSwiftUI/FirebaseAppleSwiftUI/Sources/Views/SignInWithAppleButton.swift
- Change-coupling hub: GenericOAuthButton.swift → EmailAuthView.swift, SignInWithFacebookButton.swift, SignInWithGoogleButton.swift, SignInWithTwitterButton.swift FirebaseSwiftUI/FirebaseOAuthSwiftUI/Sources/Views/GenericOAuthButton.swift
- Duplicated block (13–15 lines × 3) FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/MFAEnrolmentView.swift:227
- Duplicated block (13–15 lines × 3) FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/MFAEnrolmentView.swift:321
- Duplicated block (12 lines × 2) FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/MFAResolutionView.swift:362
- Duplicated block (12 lines × 2) samples/swift/FirebaseUI-demo-swift/Samples/Chat/ChatViewController.swift:159
- Off the main sequence: FirebaseAuthUIComponents
- Off the main sequence: FirebaseAuthSwiftUI
- AuthTextField.body (cyclomatic 16) FirebaseSwiftUI/FirebaseAuthUIComponents/Sources/Components/AuthTextField.swift:76
- Hotspot: FirebaseSwiftUI/FirebaseAuthUIComponents/Sources/Components/AuthTextField.swift FirebaseSwiftUI/FirebaseAuthUIComponents/Sources/Components/AuthTextField.swift:76
- TodoComment e2eTest/FirebaseSwiftUIExample/FirebaseSwiftUIExampleUITests/MFAResolutionUITests.swift:114
- AuthService.handleSignInLink (cognitive 37) FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Services/AuthService.swift:477
- AuthTextField.body (cognitive 22) FirebaseSwiftUI/FirebaseAuthUIComponents/Sources/Components/AuthTextField.swift:76
- AuthService.completeEnrollment (cognitive 16) FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Services/AuthService.swift:773
- TooManyMethods: AuthService FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Services/AuthService.swift:137
- FileTooLong: Services/AuthService.swift FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Services/AuthService.swift
- Change coupling clique: AppleProviderAuthUI.swift, FacebookProviderAuthUI.swift, GoogleProviderAuthUI.swift, OAuthProviderSwift.swift, PhoneAuthProviderAuthUI.swift, TwitterProviderAuthUI.swift FirebaseSwiftUI/FirebaseAppleSwiftUI/Sources/Services/AppleProviderAuthUI.swift
- Members sharing a duplicated core (5 members, 50+ identical tokens) FirebaseSwiftUI/FirebaseAppleSwiftUI/Sources/Views/SignInWithAppleButton.swift:33
- Members sharing a duplicated core (4 members, 50+ identical tokens) FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/MFAEnrolmentView.swift:302
- Duplicated block (25 lines × 2) FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/MFAEnrolmentView.swift:463
- Duplicated block (23 lines × 3) FirebaseSwiftUI/FirebaseAppleSwiftUI/Sources/Views/SignInWithAppleButton.swift:38
- Duplicated block (23 lines × 2) FirebaseSwiftUI/FirebaseAuthUIComponents/Sources/Components/VerificationCodeInputField.swift:524
- Duplicated block (18 lines × 4) FirebaseSwiftUI/FirebaseAppleSwiftUI/Sources/Views/SignInWithAppleButton.swift:44
- Duplicated block (17 lines × 2) FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/EmailReauthView.swift:39
- Duplicated block (14 lines × 3) FirebaseSwiftUI/FirebaseAuthUIComponents/Sources/Components/VerificationCodeInputField.swift:522
- Duplicated block (14 lines × 2) FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/MFAEnrolmentView.swift:306
- Duplicated block (13 lines × 2) FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/EmailAuthView.swift:62
- Duplicated block (9 lines × 3) FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/MFAEnrolmentView.swift:445
- Duplicated block (7 lines × 2) FirebaseSwiftUI/FirebaseAuthUIComponents/Sources/Components/AuthTextField.swift:164
- Duplicated block (6 lines × 3) FirebaseSwiftUI/FirebaseAppleSwiftUI/Sources/Services/AuthService+Apple.swift:25
- Duplicated block (17–19 lines × 3) samples/swiftui/FirebaseSwiftUISample/FirebaseSwiftUISample/Application/ContentView.swift:77
- Duplicated block (15 lines × 2) samples/swift/FirebaseUI-demo-swift/Samples/Chat/ChatViewController.swift:143
- Low cohesion: StorageViewController (LCOM4 4) samples/swift/FirebaseUI-demo-swift/Samples/StorageViewController.swift:21
- README may be stale
- Coverage collected but not gated
- No structured logging
- Swallowed exception (empty catch) FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/UpdatePasswordView.swift:55
- Swallowed exception (caught, then discarded) FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Services/AuthService.swift:1174
Minor — 11 finding(s)
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Projects may be oversized for their cohesion
- REDACTED
- Inverted test pyramid
- No ADRs
- Large public API surface
- No SAST REDACTED:14
- No changelog
- No security response headers detected e2eTest/FirebaseSwiftUIExample/FirebaseSwiftUIExample/firebase.json:1
- Duplicated predicate FirebaseSwiftUI/FirebaseAuthUIComponents/Sources/Components/AuthTextField.swift:159
Minor — 2 finding(s)
- Outdated: firebase-ios-sdk
- Outdated: googlesignin-ios
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8dd3aaa99b3d498c8fdca55759e83edd/history.json --exit-code 0 --source . | 4 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8dd3aaa99b3d498c8fdca55759e83edd/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/watchdog-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 . | 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 . | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 21 file(s) — `FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/AuthPickerView.swift`, `FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/EmailAuthView.swift`, `FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/EmailLinkReauthView.swift`, `FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/EmailLinkView.swift`, `FirebaseSwiftUI/FirebaseAuthSwiftUI/Sources/Views/EmailReauthView.swift`, … (+16 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | 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 |