Executive summary
bbohec/bangarang is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 32 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 20, is the weakest lens and counts most in the score. The best first step is rebalancing the test suite towards unit tests, worth about 7 points. Adding access checks comes next, worth about 6 points. Raising Production Readiness to 70 would lift the score to about 42.
Forty-nine known security holes in the packages the code depends on can be used by attackers. Four passwords or keys are open to anyone who can read the repository. Updating the vulnerable packages and replacing each exposed password or key would close both risks. Hashing passwords with a password-hashing function such as Argon2, bcrypt or PBKDF2 would fix the four places where passwords are scrambled with a fast general-purpose hash. The three uses of packages that aren't listed need adding to the project's list of dependencies.
The product code is 14,312 lines, about €13,000 to rebuild.
If Production Readiness rose from 20 to 70, the lowest score rated Strong, the score would rise from 32 to about 42.
New since the last survey: 8 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Access Controls · No authorization REDACTED
Fixed since the last survey: 200 findings
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High vulnerability: REDACTED REDACTED
- Dependency Vulnerabilities · High vulnerability: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Code Duplication · Duplicated block with local edits (5 matched lines × 2 locations) src/client/adapters/RestBangarangMembersInteractor.ts
- Test Coverage · No test reaches this file src/client/adapters/SvelteDeclaringClaimUserNotificationInteractor.ts
- Test Coverage · No test reaches this file src/client/adapters/SvelteRegisteringUserNotificationInteractor.ts
- Test Coverage · No test reaches this file src/client/adapters/SvelteRetrievingClaimUserNotificationInteractor.ts
- Test Coverage · No test reaches this file src/client/adapters/SvelteSigningInUserNotificationInteractor.ts
- Test Coverage · No test reaches this file src/client/components/AppBarComponents/Actions/NavigateToCurrentClaim.svelte
- Test Coverage · No test reaches this file src/client/components/Form/Fields/GenericSubmitField.svelte
- Test Coverage · No test reaches this file src/client/components/AppBarComponents/Actions/NavigateBackToMainMenu.svelte
- Test Coverage · No test reaches this file src/client/components/AppBarComponents/Actions/NavigateToBusinessModel.svelte
- Test Coverage · No test reaches this file src/client/components/AppBarComponents/Actions/NavigateToDeclareClaim.svelte
- Test Coverage · No test reaches this file src/client/components/AppBarComponents/Actions/NavigateToLeanCanvas.svelte
- Test Coverage · No test reaches this file src/client/components/AppBarComponents/Actions/NavigateToMainMenu.svelte
- Test Coverage · No test reaches this file src/client/components/AppBarComponents/Actions/NavigateToRegisterMenu.svelte
- Test Coverage · No test reaches this file src/client/components/AppBarComponents/Actions/NavigateToSignInMenu.svelte
- Test Coverage · No test reaches this file src/client/components/AppBarComponents/Notifications/GenericTaskNotification.svelte
- Test Coverage · No test reaches this file src/client/components/Lists/ValuePropositionDesignCanvasList.svelte
- Test Coverage · No test reaches this file src/client/components/Titles/MainSubTitle.svelte
- Test Coverage · No test reaches this file src/client/logic/claiming.ts
- Test Coverage · No test reaches this file src/client/components/AppBarComponents/Actions/GenericInteractiveAction.svelte
- Test Coverage · No test reaches this file src/client/components/Footers/SignInFooter.svelte
- Test Coverage · No test reaches this file src/client/components/Form/Fields/GenericTextAreaField.svelte
- Test Coverage · No test reaches this file src/client/components/Links/BackToMainMenuLink.svelte
- Test Coverage · No test reaches this file src/client/logic/retreiveClaimsByClaimSearchValue.ts
- Test Coverage · No test reaches this file src/client/logic/retrievingClaimById.ts
- Test Coverage · No test reaches this file src/client/logic/valueProposition/retreiveValuePropositionFromValuePropositionPageLink.ts
- Test Coverage · No test reaches this file src/client/components/AppBarComponents/Actions/ResetClaimSearch.svelte
- Test Coverage · No test reaches this file src/client/components/Mains/SignInMain.svelte
- Test Coverage · No test reaches this file src/client/components/Sections/RegisterSection.svelte
- Test Coverage · No test reaches this file src/client/views/ClaimView.svelte
- Test Coverage · No test reaches this file src/client/views/ValuePropositionView.svelte
- Test Coverage · No test reaches this file src/client.ts
- Test Coverage · No test reaches this file src/client/components/AppBarComponents/Actions/ClaimShare.svelte
- Test Coverage · No test reaches this file src/client/components/Cards/DemoPreviewCard.svelte
- Test Coverage · No test reaches this file src/client/components/Cards/SecurityUserCard.svelte
- Test Coverage · No test reaches this file src/client/components/Footers/SearchedClaimsFooter.svelte
- Test Coverage · No test reaches this file src/client/components/Form/Fields/GenericPasswordField.svelte
- Test Coverage · No test reaches this file src/client/components/Form/Fields/GenericTextField.svelte
- Test Coverage · No test reaches this file src/client/components/Mains/LeanCanvasMain.svelte
- Test Coverage · No test reaches this file src/client/components/Mains/SelectLanguageMain.svelte
- Test Coverage · No test reaches this file src/client/components/Sections/SignInSection.svelte
- Test Coverage · No test reaches this file src/client/components/Titles/HeaderTitle.svelte
- Test Coverage · No test reaches this file src/client/components/Cards/DescriptionCard.svelte
- Test Coverage · No test reaches this file src/client/components/Descriptions/BangarangDescription.svelte
- Test Coverage · No test reaches this file src/client/components/Footers/DeclareClaimFooter.svelte
- Test Coverage · No test reaches this file src/client/components/Footers/LeanCanvasFooter.svelte
- Test Coverage · No test reaches this file src/client/components/Footers/MainMenuFooter.svelte
- Test Coverage · No test reaches this file src/client/components/Footers/RegisterFooter.svelte
- Test Coverage · No test reaches this file src/client/components/Headers/SelectLanguageHeader.svelte
- Test Coverage · No test reaches this file src/client/components/Headers/ValuePropositionHeader.svelte
- Test Coverage · No test reaches this file src/client/components/Inputs/ClaimAsProposalRadioButton.svelte
- Test Coverage · No test reaches this file src/client/components/Mains/MainMenuMain.svelte
- Test Coverage · No test reaches this file src/client/components/Mains/ValuePropositionMain.svelte
- Test Coverage · No test reaches this file src/client/components/Titles/RegisterTitle.svelte
- Test Coverage · No test reaches this file src/client/components/Titles/WelcomeTitle.svelte
- Test Coverage · No test reaches this file src/client/stores/currentUserContract.ts
- Test Coverage · No test reaches this file src/client/views/BusinessModelView.svelte
- Test Coverage · No test reaches this file src/client/views/DeclareClaimView.svelte
- Test Coverage · No test reaches this file src/client/views/LandingPageView.svelte
- Test Coverage · No test reaches this file src/client/views/LeanCanvasView.svelte
- Test Coverage · No test reaches this file src/client/views/RegisterView.svelte
- Test Coverage · No test reaches this file src/client/views/SignInView.svelte
- Test Coverage · No test reaches this file src/client/components/AppBarComponents/Notifications/ClaimingInformation.svelte
- Test Coverage · No test reaches this file src/client/components/AppBarComponents/Notifications/DeclaringInformation.svelte
- Test Coverage · No test reaches this file src/client/components/AppBarComponents/Notifications/RegisteringInformation.svelte
- Test Coverage · No test reaches this file src/client/components/AppBarComponents/Notifications/SearchingClaimsInformation.svelte
- Test Coverage · No test reaches this file src/client/components/AppBarComponents/Notifications/SignInInformation.svelte
- Test Coverage · No test reaches this file src/client/components/Footers/BusinessModelFooter.svelte
- Test Coverage · No test reaches this file src/client/components/Footers/ValuePropositionFooter.svelte
- Test Coverage · No test reaches this file src/client/components/Headers/BusinessModelHeader.svelte
- Test Coverage · No test reaches this file src/client/components/Headers/DeclareClaimHeader.svelte
- Test Coverage · No test reaches this file src/client/components/Headers/LeanCanvasHeader.svelte
- Test Coverage · No test reaches this file src/client/components/Headers/SignInHeader.svelte
- Test Coverage · No test reaches this file src/client/stores/claimSearchStore.ts
- Test Coverage · No test reaches this file src/client/stores/claimingStore.ts
- Test Coverage · No test reaches this file src/client/stores/declaringClaimStore.ts
- Test Coverage · No test reaches this file src/client/stores/languageStore.ts
- Test Coverage · No test reaches this file src/client/stores/registeringStore.ts
- Test Coverage · No test reaches this file src/client/stores/retrievingClaimStore.ts
- Test Coverage · No test reaches this file src/client/stores/searchingClaimsStore.ts
- Test Coverage · No test reaches this file src/client/stores/signInStore.ts
- Test Coverage · No test reaches this file src/client/views/MainMenuView.svelte
- Test Coverage · No test reaches this file src/client/views/SearchClaimsView.svelte
- Test Coverage · No test reaches this file src/client/components/Headers/ClaimHeader.svelte
- Test Coverage · No test reaches this file src/client/components/Headers/RegisterHeader.svelte
- Test Coverage · No test reaches this file src/client/components/Mains/DeclareClaimMain.svelte
- Test Coverage · No test reaches this file src/client/components/Mains/RegisterMain.svelte
- Test Coverage · No test reaches this file src/client/components/Mains/SearchedClaimsMain.svelte
- Test Coverage · No test reaches this file src/client/stores/currentClaimIdStore.ts
- Test Coverage · No test reaches this file src/routes/LanguageSelect.svelte
- Test Coverage · No test reaches this file src/routes/index.svelte
- Test Coverage · No test reaches this file src/client/components/Icons/BackIcon.svelte
- Test Coverage · No test reaches this file src/client/components/Icons/ChevronRight.svelte
Rebuild cost: about €13,000 · Estimate
| Cost to rebuild | €4,400 to €22,000, for 74 to 235 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.7 at a score of 32. 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: 14,312 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: which parts of the code depend on which
| uses → | 1 client.adapters.GcpDatastoreInteractor | 2 client.adapters.RestInteractor | 3 client.port.ClaimChoice | 4 client.port.Command | 5 client.port.MemberClaim | 6 client.port.UserContact | 7 client.port.bangarangMemberCredential | 8 client.port.interactors.BangarangUserInterfaceInteractor | 9 client.port.interactors.ClaimingUserNotificationInteractorContract | 10 client.port.interactors.EmailInteractorContract | 11 client.port.interactors.PasswordInteractorContract | 12 client.port.interactors.RegisteringUserNotificationInteractorContract | 13 client.port.interactors.SearchingClaimsUserNotificationInteractorContract | 14 client.port.interactors.SigningInUserNotificationInteractorContract | 15 client.adapters.FakeBangarangUserInterfaceInteractor | 16 client.logic | 17 client.port.ClaimContract | 18 client.port.interactors.BangarangMembersInteractorContract | 19 client.adapters.FakeBangarangMembersInteractor | 20 client.adapters.GcpDatastoreBangarangMembersInteractor | 21 client.adapters.RestBangarangMembersInteractor | 22 client.port.interactors.BangarangClaimInteractorContract | 23 client.port.interactors.DeclaringClaimUserNotificationInteractorContract | 24 client.port.interactors.RetrievingClaimUserNotificationInteractorContract | 25 client.adapters | 26 client.adapters.FakeBangarangClaimInteractor | 27 client.adapters.GcpDatastoreBangarangClaimInteractor | 28 client.adapters.RestBangarangClaimInteractor | 29 client.businessLogic.entities.Claim | 30 client.port.BangarangAdaptersContract | 31 client.port.interactors | 32 server | 33 client.businessLogic.commands.claiming | 34 client.businessLogic.commands.declaringClaim | 35 client.businessLogic.commands.registering | 36 client.businessLogic.commands.retrievingClaimById | 37 client.businessLogic.commands.searchingClaims | 38 client.businessLogic.commands.signingIn | 39 client.businessLogic.entities.User | 40 client.businessLogic.entities.UserBuilder |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 client.adapters.GcpDatastoreInteractor | ||||||||||||||||||||||||||||||||||||||||
| 2 client.adapters.RestInteractor | ||||||||||||||||||||||||||||||||||||||||
| 3 client.port.ClaimChoice | ||||||||||||||||||||||||||||||||||||||||
| 4 client.port.Command | ||||||||||||||||||||||||||||||||||||||||
| 5 client.port.MemberClaim | ||||||||||||||||||||||||||||||||||||||||
| 6 client.port.UserContact | ||||||||||||||||||||||||||||||||||||||||
| 7 client.port.bangarangMemberCredential | ||||||||||||||||||||||||||||||||||||||||
| 8 client.port.interactors.BangarangUserInterfaceInteractor | ||||||||||||||||||||||||||||||||||||||||
| 9 client.port.interactors.ClaimingUserNotificationInteractorContract | ||||||||||||||||||||||||||||||||||||||||
| 10 client.port.interactors.EmailInteractorContract | ||||||||||||||||||||||||||||||||||||||||
| 11 client.port.interactors.PasswordInteractorContract | ||||||||||||||||||||||||||||||||||||||||
| 12 client.port.interactors.RegisteringUserNotificationInteractorContract | ||||||||||||||||||||||||||||||||||||||||
| 13 client.port.interactors.SearchingClaimsUserNotificationInteractorContract | ||||||||||||||||||||||||||||||||||||||||
| 14 client.port.interactors.SigningInUserNotificationInteractorContract | ||||||||||||||||||||||||||||||||||||||||
| 15 client.adapters.FakeBangarangUserInterfaceInteractor | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 client.logic | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 client.port.ClaimContract | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 client.port.interactors.BangarangMembersInteractorContract | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 client.adapters.FakeBangarangMembersInteractor | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 20 client.adapters.GcpDatastoreBangarangMembersInteractor | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 21 client.adapters.RestBangarangMembersInteractor | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 22 client.port.interactors.BangarangClaimInteractorContract | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 client.port.interactors.DeclaringClaimUserNotificationInteractorContract | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 client.port.interactors.RetrievingClaimUserNotificationInteractorContract | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 client.adapters | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 client.adapters.FakeBangarangClaimInteractor | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 client.adapters.GcpDatastoreBangarangClaimInteractor | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 client.adapters.RestBangarangClaimInteractor | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 client.businessLogic.entities.Claim | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 client.port.BangarangAdaptersContract | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||
| 31 client.port.interactors | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 32 server | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 client.businessLogic.commands.claiming | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 client.businessLogic.commands.declaringClaim | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 client.businessLogic.commands.registering | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 client.businessLogic.commands.retrievingClaimById | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 client.businessLogic.commands.searchingClaims | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 client.businessLogic.commands.signingIn | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 client.businessLogic.entities.User | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 client.businessLogic.entities.UserBuilder | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
15→8 client.adapters.FakeBangarangUserInterfaceInteractor uses client.port.interactors.BangarangUserInterfaceInteractor✕
- Connections
- 1 pair of types, where a type in client.adapters.FakeBangarangUserInterfaceInteractor uses a type in client.port.interactors.BangarangUserInterfaceInteractor.
- The types involved
src.client.adapters.FakeBangarangUserInterfaceInteractor.FakeBangarangUserInterfaceInteractor→src.client.port.interactors.BangarangUserInterfaceInteractor.BangarangUserInterfaceInteractorContract
- Direction
- client.adapters.FakeBangarangUserInterfaceInteractor uses client.port.interactors.BangarangUserInterfaceInteractor, so a change to client.port.interactors.BangarangUserInterfaceInteractor can break client.adapters.FakeBangarangUserInterfaceInteractor, while a change to client.adapters.FakeBangarangUserInterfaceInteractor can't break client.port.interactors.BangarangUserInterfaceInteractor.
- Position
- Below the diagonal: client.adapters.FakeBangarangUserInterfaceInteractor uses a module listed above it, which is the healthy direction.
16→3 client.logic uses client.port.ClaimChoice✕
- Connections
- 1 pair of types, where a type in client.logic uses a type in client.port.ClaimChoice.
- The types involved
src.client.logic.claiming→src.client.port.ClaimChoice.ClaimChoice
- Direction
- client.logic uses client.port.ClaimChoice, so a change to client.port.ClaimChoice can break client.logic, while a change to client.logic can't break client.port.ClaimChoice.
- Position
- Below the diagonal: client.logic uses a module listed above it, which is the healthy direction.
16→6 client.logic uses client.port.UserContact✕
- Connections
- 1 pair of types, where a type in client.logic uses a type in client.port.UserContact.
- The types involved
src.client.logic.registering→src.client.port.UserContact.UserContract
- Direction
- client.logic uses client.port.UserContact, so a change to client.port.UserContact can break client.logic, while a change to client.logic can't break client.port.UserContact.
- Position
- Below the diagonal: client.logic uses a module listed above it, which is the healthy direction.
17→3 client.port.ClaimContract uses client.port.ClaimChoice✕
- Connections
- 1 pair of types, where a type in client.port.ClaimContract uses a type in client.port.ClaimChoice.
- The types involved
src.client.port.ClaimContract.ClaimContractWithMemberPreviousClaimChoice→src.client.port.ClaimChoice.ClaimChoice
- Direction
- client.port.ClaimContract uses client.port.ClaimChoice, so a change to client.port.ClaimChoice can break client.port.ClaimContract, while a change to client.port.ClaimContract can't break client.port.ClaimChoice.
- Position
- Below the diagonal: client.port.ClaimContract uses a module listed above it, which is the healthy direction.
18→5 client.port.interactors.BangarangMembersInteractorContract uses client.port.MemberClaim✕
- Connections
- 1 pair of types, where a type in client.port.interactors.BangarangMembersInteractorContract uses a type in client.port.MemberClaim.
- The types involved
src.client.port.interactors.BangarangMembersInteractorContract.BangarangMembersInteractorContract→src.client.port.MemberClaim.MemberClaim
- Direction
- client.port.interactors.BangarangMembersInteractorContract uses client.port.MemberClaim, so a change to client.port.MemberClaim can break client.port.interactors.BangarangMembersInteractorContract, while a change to client.port.interactors.BangarangMembersInteractorContract can't break client.port.MemberClaim.
- Position
- Below the diagonal: client.port.interactors.BangarangMembersInteractorContract uses a module listed above it, which is the healthy direction.
18→6 client.port.interactors.BangarangMembersInteractorContract uses client.port.UserContact✕
- Connections
- 1 pair of types, where a type in client.port.interactors.BangarangMembersInteractorContract uses a type in client.port.UserContact.
- The types involved
src.client.port.interactors.BangarangMembersInteractorContract.BangarangMembersInteractorContract→src.client.port.UserContact.UserContract
- Direction
- client.port.interactors.BangarangMembersInteractorContract uses client.port.UserContact, so a change to client.port.UserContact can break client.port.interactors.BangarangMembersInteractorContract, while a change to client.port.interactors.BangarangMembersInteractorContract can't break client.port.UserContact.
- Position
- Below the diagonal: client.port.interactors.BangarangMembersInteractorContract uses a module listed above it, which is the healthy direction.
18→7 client.port.interactors.BangarangMembersInteractorContract uses client.port.bangarangMemberCredential✕
- Connections
- 1 pair of types, where a type in client.port.interactors.BangarangMembersInteractorContract uses a type in client.port.bangarangMemberCredential.
- The types involved
src.client.port.interactors.BangarangMembersInteractorContract.BangarangMembersInteractorContract→src.client.port.bangarangMemberCredential.Credentials
- Direction
- client.port.interactors.BangarangMembersInteractorContract uses client.port.bangarangMemberCredential, so a change to client.port.bangarangMemberCredential can break client.port.interactors.BangarangMembersInteractorContract, while a change to client.port.interactors.BangarangMembersInteractorContract can't break client.port.bangarangMemberCredential.
- Position
- Below the diagonal: client.port.interactors.BangarangMembersInteractorContract uses a module listed above it, which is the healthy direction.
19→5 client.adapters.FakeBangarangMembersInteractor uses client.port.MemberClaim✕
- Connections
- 1 pair of types, where a type in client.adapters.FakeBangarangMembersInteractor uses a type in client.port.MemberClaim.
- The types involved
src.client.adapters.FakeBangarangMembersInteractor.FakeBangarangMembersInteractor→src.client.port.MemberClaim.MemberClaim
- Direction
- client.adapters.FakeBangarangMembersInteractor uses client.port.MemberClaim, so a change to client.port.MemberClaim can break client.adapters.FakeBangarangMembersInteractor, while a change to client.adapters.FakeBangarangMembersInteractor can't break client.port.MemberClaim.
- Position
- Below the diagonal: client.adapters.FakeBangarangMembersInteractor uses a module listed above it, which is the healthy direction.
19→6 client.adapters.FakeBangarangMembersInteractor uses client.port.UserContact✕
- Connections
- 1 pair of types, where a type in client.adapters.FakeBangarangMembersInteractor uses a type in client.port.UserContact.
- The types involved
src.client.adapters.FakeBangarangMembersInteractor.FakeBangarangMembersInteractor→src.client.port.UserContact.UserContract
- Direction
- client.adapters.FakeBangarangMembersInteractor uses client.port.UserContact, so a change to client.port.UserContact can break client.adapters.FakeBangarangMembersInteractor, while a change to client.adapters.FakeBangarangMembersInteractor can't break client.port.UserContact.
- Position
- Below the diagonal: client.adapters.FakeBangarangMembersInteractor uses a module listed above it, which is the healthy direction.
19→7 client.adapters.FakeBangarangMembersInteractor uses client.port.bangarangMemberCredential✕
- Connections
- 1 pair of types, where a type in client.adapters.FakeBangarangMembersInteractor uses a type in client.port.bangarangMemberCredential.
- The types involved
src.client.adapters.FakeBangarangMembersInteractor.FakeBangarangMembersInteractor→src.client.port.bangarangMemberCredential.Credentials
- Direction
- client.adapters.FakeBangarangMembersInteractor uses client.port.bangarangMemberCredential, so a change to client.port.bangarangMemberCredential can break client.adapters.FakeBangarangMembersInteractor, while a change to client.adapters.FakeBangarangMembersInteractor can't break client.port.bangarangMemberCredential.
- Position
- Below the diagonal: client.adapters.FakeBangarangMembersInteractor uses a module listed above it, which is the healthy direction.
19→18 client.adapters.FakeBangarangMembersInteractor uses client.port.interactors.BangarangMembersInteractorContract✕
- Connections
- 1 pair of types, where a type in client.adapters.FakeBangarangMembersInteractor uses a type in client.port.interactors.BangarangMembersInteractorContract.
- The types involved
src.client.adapters.FakeBangarangMembersInteractor.FakeBangarangMembersInteractor→src.client.port.interactors.BangarangMembersInteractorContract.BangarangMembersInteractorContract
- Direction
- client.adapters.FakeBangarangMembersInteractor uses client.port.interactors.BangarangMembersInteractorContract, so a change to client.port.interactors.BangarangMembersInteractorContract can break client.adapters.FakeBangarangMembersInteractor, while a change to client.adapters.FakeBangarangMembersInteractor can't break client.port.interactors.BangarangMembersInteractorContract.
- Position
- Below the diagonal: client.adapters.FakeBangarangMembersInteractor uses a module listed above it, which is the healthy direction.
20→1 client.adapters.GcpDatastoreBangarangMembersInteractor uses client.adapters.GcpDatastoreInteractor✕
- Connections
- 1 pair of types, where a type in client.adapters.GcpDatastoreBangarangMembersInteractor uses a type in client.adapters.GcpDatastoreInteractor.
- The types involved
src.client.adapters.GcpDatastoreBangarangMembersInteractor.GcpDatastoreBangarangMembersInteractor→src.client.adapters.GcpDatastoreInteractor.GcpDatastoreInteractor
- Direction
- client.adapters.GcpDatastoreBangarangMembersInteractor uses client.adapters.GcpDatastoreInteractor, so a change to client.adapters.GcpDatastoreInteractor can break client.adapters.GcpDatastoreBangarangMembersInteractor, while a change to client.adapters.GcpDatastoreBangarangMembersInteractor can't break client.adapters.GcpDatastoreInteractor.
- Position
- Below the diagonal: client.adapters.GcpDatastoreBangarangMembersInteractor uses a module listed above it, which is the healthy direction.
20→5 client.adapters.GcpDatastoreBangarangMembersInteractor uses client.port.MemberClaim✕
- Connections
- 1 pair of types, where a type in client.adapters.GcpDatastoreBangarangMembersInteractor uses a type in client.port.MemberClaim.
- The types involved
src.client.adapters.GcpDatastoreBangarangMembersInteractor.GcpDatastoreBangarangMembersInteractor→src.client.port.MemberClaim.MemberClaim
- Direction
- client.adapters.GcpDatastoreBangarangMembersInteractor uses client.port.MemberClaim, so a change to client.port.MemberClaim can break client.adapters.GcpDatastoreBangarangMembersInteractor, while a change to client.adapters.GcpDatastoreBangarangMembersInteractor can't break client.port.MemberClaim.
- Position
- Below the diagonal: client.adapters.GcpDatastoreBangarangMembersInteractor uses a module listed above it, which is the healthy direction.
20→6 client.adapters.GcpDatastoreBangarangMembersInteractor uses client.port.UserContact✕
- Connections
- 1 pair of types, where a type in client.adapters.GcpDatastoreBangarangMembersInteractor uses a type in client.port.UserContact.
- The types involved
src.client.adapters.GcpDatastoreBangarangMembersInteractor.GcpDatastoreBangarangMembersInteractor→src.client.port.UserContact.UserContract
- Direction
- client.adapters.GcpDatastoreBangarangMembersInteractor uses client.port.UserContact, so a change to client.port.UserContact can break client.adapters.GcpDatastoreBangarangMembersInteractor, while a change to client.adapters.GcpDatastoreBangarangMembersInteractor can't break client.port.UserContact.
- Position
- Below the diagonal: client.adapters.GcpDatastoreBangarangMembersInteractor uses a module listed above it, which is the healthy direction.
20→7 client.adapters.GcpDatastoreBangarangMembersInteractor uses client.port.bangarangMemberCredential✕
- Connections
- 1 pair of types, where a type in client.adapters.GcpDatastoreBangarangMembersInteractor uses a type in client.port.bangarangMemberCredential.
- The types involved
src.client.adapters.GcpDatastoreBangarangMembersInteractor.GcpDatastoreBangarangMembersInteractor→src.client.port.bangarangMemberCredential.Credentials
- Direction
- client.adapters.GcpDatastoreBangarangMembersInteractor uses client.port.bangarangMemberCredential, so a change to client.port.bangarangMemberCredential can break client.adapters.GcpDatastoreBangarangMembersInteractor, while a change to client.adapters.GcpDatastoreBangarangMembersInteractor can't break client.port.bangarangMemberCredential.
- Position
- Below the diagonal: client.adapters.GcpDatastoreBangarangMembersInteractor uses a module listed above it, which is the healthy direction.
20→18 client.adapters.GcpDatastoreBangarangMembersInteractor uses client.port.interactors.BangarangMembersInteractorContract✕
- Connections
- 1 pair of types, where a type in client.adapters.GcpDatastoreBangarangMembersInteractor uses a type in client.port.interactors.BangarangMembersInteractorContract.
- The types involved
src.client.adapters.GcpDatastoreBangarangMembersInteractor.GcpDatastoreBangarangMembersInteractor→src.client.port.interactors.BangarangMembersInteractorContract.BangarangMembersInteractorContract
- Direction
- client.adapters.GcpDatastoreBangarangMembersInteractor uses client.port.interactors.BangarangMembersInteractorContract, so a change to client.port.interactors.BangarangMembersInteractorContract can break client.adapters.GcpDatastoreBangarangMembersInteractor, while a change to client.adapters.GcpDatastoreBangarangMembersInteractor can't break client.port.interactors.BangarangMembersInteractorContract.
- Position
- Below the diagonal: client.adapters.GcpDatastoreBangarangMembersInteractor uses a module listed above it, which is the healthy direction.
21→2 client.adapters.RestBangarangMembersInteractor uses client.adapters.RestInteractor✕
- Connections
- 1 pair of types, where a type in client.adapters.RestBangarangMembersInteractor uses a type in client.adapters.RestInteractor.
- The types involved
src.client.adapters.RestBangarangMembersInteractor.RestBangarangMembersInteractor→src.client.adapters.RestInteractor.RestInteractor
- Direction
- client.adapters.RestBangarangMembersInteractor uses client.adapters.RestInteractor, so a change to client.adapters.RestInteractor can break client.adapters.RestBangarangMembersInteractor, while a change to client.adapters.RestBangarangMembersInteractor can't break client.adapters.RestInteractor.
- Position
- Below the diagonal: client.adapters.RestBangarangMembersInteractor uses a module listed above it, which is the healthy direction.
21→5 client.adapters.RestBangarangMembersInteractor uses client.port.MemberClaim✕
- Connections
- 1 pair of types, where a type in client.adapters.RestBangarangMembersInteractor uses a type in client.port.MemberClaim.
- The types involved
src.client.adapters.RestBangarangMembersInteractor.RestBangarangMembersInteractor→src.client.port.MemberClaim.MemberClaim
- Direction
- client.adapters.RestBangarangMembersInteractor uses client.port.MemberClaim, so a change to client.port.MemberClaim can break client.adapters.RestBangarangMembersInteractor, while a change to client.adapters.RestBangarangMembersInteractor can't break client.port.MemberClaim.
- Position
- Below the diagonal: client.adapters.RestBangarangMembersInteractor uses a module listed above it, which is the healthy direction.
21→6 client.adapters.RestBangarangMembersInteractor uses client.port.UserContact✕
- Connections
- 1 pair of types, where a type in client.adapters.RestBangarangMembersInteractor uses a type in client.port.UserContact.
- The types involved
src.client.adapters.RestBangarangMembersInteractor.RestBangarangMembersInteractor→src.client.port.UserContact.UserContract
- Direction
- client.adapters.RestBangarangMembersInteractor uses client.port.UserContact, so a change to client.port.UserContact can break client.adapters.RestBangarangMembersInteractor, while a change to client.adapters.RestBangarangMembersInteractor can't break client.port.UserContact.
- Position
- Below the diagonal: client.adapters.RestBangarangMembersInteractor uses a module listed above it, which is the healthy direction.
21→7 client.adapters.RestBangarangMembersInteractor uses client.port.bangarangMemberCredential✕
- Connections
- 1 pair of types, where a type in client.adapters.RestBangarangMembersInteractor uses a type in client.port.bangarangMemberCredential.
- The types involved
src.client.adapters.RestBangarangMembersInteractor.RestBangarangMembersInteractor→src.client.port.bangarangMemberCredential.Credentials
- Direction
- client.adapters.RestBangarangMembersInteractor uses client.port.bangarangMemberCredential, so a change to client.port.bangarangMemberCredential can break client.adapters.RestBangarangMembersInteractor, while a change to client.adapters.RestBangarangMembersInteractor can't break client.port.bangarangMemberCredential.
- Position
- Below the diagonal: client.adapters.RestBangarangMembersInteractor uses a module listed above it, which is the healthy direction.
21→18 client.adapters.RestBangarangMembersInteractor uses client.port.interactors.BangarangMembersInteractorContract✕
- Connections
- 1 pair of types, where a type in client.adapters.RestBangarangMembersInteractor uses a type in client.port.interactors.BangarangMembersInteractorContract.
- The types involved
src.client.adapters.RestBangarangMembersInteractor.RestBangarangMembersInteractor→src.client.port.interactors.BangarangMembersInteractorContract.BangarangMembersInteractorContract
- Direction
- client.adapters.RestBangarangMembersInteractor uses client.port.interactors.BangarangMembersInteractorContract, so a change to client.port.interactors.BangarangMembersInteractorContract can break client.adapters.RestBangarangMembersInteractor, while a change to client.adapters.RestBangarangMembersInteractor can't break client.port.interactors.BangarangMembersInteractorContract.
- Position
- Below the diagonal: client.adapters.RestBangarangMembersInteractor uses a module listed above it, which is the healthy direction.
22→17 client.port.interactors.BangarangClaimInteractorContract uses client.port.ClaimContract✕
- Connections
- 1 pair of types, where a type in client.port.interactors.BangarangClaimInteractorContract uses a type in client.port.ClaimContract.
- The types involved
src.client.port.interactors.BangarangClaimInteractorContract.BangarangClaimInteractorContract→src.client.port.ClaimContract.ClaimContract
- Direction
- client.port.interactors.BangarangClaimInteractorContract uses client.port.ClaimContract, so a change to client.port.ClaimContract can break client.port.interactors.BangarangClaimInteractorContract, while a change to client.port.interactors.BangarangClaimInteractorContract can't break client.port.ClaimContract.
- Position
- Below the diagonal: client.port.interactors.BangarangClaimInteractorContract uses a module listed above it, which is the healthy direction.
23→17 client.port.interactors.DeclaringClaimUserNotificationInteractorContract uses client.port.ClaimContract✕
- Connections
- 1 pair of types, where a type in client.port.interactors.DeclaringClaimUserNotificationInteractorContract uses a type in client.port.ClaimContract.
- The types involved
src.client.port.interactors.DeclaringClaimUserNotificationInteractorContract.DeclaringClaimUserNotificationContract→src.client.port.ClaimContract.ClaimContract
- Direction
- client.port.interactors.DeclaringClaimUserNotificationInteractorContract uses client.port.ClaimContract, so a change to client.port.ClaimContract can break client.port.interactors.DeclaringClaimUserNotificationInteractorContract, while a change to client.port.interactors.DeclaringClaimUserNotificationInteractorContract can't break client.port.ClaimContract.
- Position
- Below the diagonal: client.port.interactors.DeclaringClaimUserNotificationInteractorContract uses a module listed above it, which is the healthy direction.
24→17 client.port.interactors.RetrievingClaimUserNotificationInteractorContract uses client.port.ClaimContract✕
- Connections
- 1 pair of types, where a type in client.port.interactors.RetrievingClaimUserNotificationInteractorContract uses a type in client.port.ClaimContract.
- The types involved
src.client.port.interactors.RetrievingClaimUserNotificationInteractorContract.RetrievingClaimUserNotificationContract→src.client.port.ClaimContract.ClaimContractWithMemberPreviousClaimChoice
- Direction
- client.port.interactors.RetrievingClaimUserNotificationInteractorContract uses client.port.ClaimContract, so a change to client.port.ClaimContract can break client.port.interactors.RetrievingClaimUserNotificationInteractorContract, while a change to client.port.interactors.RetrievingClaimUserNotificationInteractorContract can't break client.port.ClaimContract.
- Position
- Below the diagonal: client.port.interactors.RetrievingClaimUserNotificationInteractorContract uses a module listed above it, which is the healthy direction.
25→17 client.adapters uses client.port.ClaimContract✕
- Connections
- 1 pair of types, where a type in client.adapters uses a type in client.port.ClaimContract.
- The types involved
src.client.adapters.uiPrimaryAdapter→src.client.port.ClaimContract.ClaimContract
- Direction
- client.adapters uses client.port.ClaimContract, so a change to client.port.ClaimContract can break client.adapters, while a change to client.adapters can't break client.port.ClaimContract.
- Position
- Below the diagonal: client.adapters uses a module listed above it, which is the healthy direction.
25→20 client.adapters uses client.adapters.GcpDatastoreBangarangMembersInteractor✕
- Connections
- 1 pair of types, where a type in client.adapters uses a type in client.adapters.GcpDatastoreBangarangMembersInteractor.
- The types involved
src.client.adapters.GcpDatastoreBangarangMembersInteractor→src.client.adapters.GcpDatastoreBangarangMembersInteractor.Kind
- Direction
- client.adapters uses client.adapters.GcpDatastoreBangarangMembersInteractor, so a change to client.adapters.GcpDatastoreBangarangMembersInteractor can break client.adapters, while a change to client.adapters can't break client.adapters.GcpDatastoreBangarangMembersInteractor.
- Position
- Below the diagonal: client.adapters uses a module listed above it, which is the healthy direction.
26→17 client.adapters.FakeBangarangClaimInteractor uses client.port.ClaimContract✕
- Connections
- 1 pair of types, where a type in client.adapters.FakeBangarangClaimInteractor uses a type in client.port.ClaimContract.
- The types involved
src.client.adapters.FakeBangarangClaimInteractor.FakeBangarangClaimInteractor→src.client.port.ClaimContract.ClaimContract
- Direction
- client.adapters.FakeBangarangClaimInteractor uses client.port.ClaimContract, so a change to client.port.ClaimContract can break client.adapters.FakeBangarangClaimInteractor, while a change to client.adapters.FakeBangarangClaimInteractor can't break client.port.ClaimContract.
- Position
- Below the diagonal: client.adapters.FakeBangarangClaimInteractor uses a module listed above it, which is the healthy direction.
26→22 client.adapters.FakeBangarangClaimInteractor uses client.port.interactors.BangarangClaimInteractorContract✕
- Connections
- 1 pair of types, where a type in client.adapters.FakeBangarangClaimInteractor uses a type in client.port.interactors.BangarangClaimInteractorContract.
- The types involved
src.client.adapters.FakeBangarangClaimInteractor.FakeBangarangClaimInteractor→src.client.port.interactors.BangarangClaimInteractorContract.BangarangClaimInteractorContract
- Direction
- client.adapters.FakeBangarangClaimInteractor uses client.port.interactors.BangarangClaimInteractorContract, so a change to client.port.interactors.BangarangClaimInteractorContract can break client.adapters.FakeBangarangClaimInteractor, while a change to client.adapters.FakeBangarangClaimInteractor can't break client.port.interactors.BangarangClaimInteractorContract.
- Position
- Below the diagonal: client.adapters.FakeBangarangClaimInteractor uses a module listed above it, which is the healthy direction.
27→1 client.adapters.GcpDatastoreBangarangClaimInteractor uses client.adapters.GcpDatastoreInteractor✕
- Connections
- 1 pair of types, where a type in client.adapters.GcpDatastoreBangarangClaimInteractor uses a type in client.adapters.GcpDatastoreInteractor.
- The types involved
src.client.adapters.GcpDatastoreBangarangClaimInteractor.GcpDatastoreBangarangClaimInteractor→src.client.adapters.GcpDatastoreInteractor.GcpDatastoreInteractor
- Direction
- client.adapters.GcpDatastoreBangarangClaimInteractor uses client.adapters.GcpDatastoreInteractor, so a change to client.adapters.GcpDatastoreInteractor can break client.adapters.GcpDatastoreBangarangClaimInteractor, while a change to client.adapters.GcpDatastoreBangarangClaimInteractor can't break client.adapters.GcpDatastoreInteractor.
- Position
- Below the diagonal: client.adapters.GcpDatastoreBangarangClaimInteractor uses a module listed above it, which is the healthy direction.
27→17 client.adapters.GcpDatastoreBangarangClaimInteractor uses client.port.ClaimContract✕
- Connections
- 1 pair of types, where a type in client.adapters.GcpDatastoreBangarangClaimInteractor uses a type in client.port.ClaimContract.
- The types involved
src.client.adapters.GcpDatastoreBangarangClaimInteractor.GcpDatastoreBangarangClaimInteractor→src.client.port.ClaimContract.ClaimContract
- Direction
- client.adapters.GcpDatastoreBangarangClaimInteractor uses client.port.ClaimContract, so a change to client.port.ClaimContract can break client.adapters.GcpDatastoreBangarangClaimInteractor, while a change to client.adapters.GcpDatastoreBangarangClaimInteractor can't break client.port.ClaimContract.
- Position
- Below the diagonal: client.adapters.GcpDatastoreBangarangClaimInteractor uses a module listed above it, which is the healthy direction.
27→22 client.adapters.GcpDatastoreBangarangClaimInteractor uses client.port.interactors.BangarangClaimInteractorContract✕
- Connections
- 1 pair of types, where a type in client.adapters.GcpDatastoreBangarangClaimInteractor uses a type in client.port.interactors.BangarangClaimInteractorContract.
- The types involved
src.client.adapters.GcpDatastoreBangarangClaimInteractor.GcpDatastoreBangarangClaimInteractor→src.client.port.interactors.BangarangClaimInteractorContract.BangarangClaimInteractorContract
- Direction
- client.adapters.GcpDatastoreBangarangClaimInteractor uses client.port.interactors.BangarangClaimInteractorContract, so a change to client.port.interactors.BangarangClaimInteractorContract can break client.adapters.GcpDatastoreBangarangClaimInteractor, while a change to client.adapters.GcpDatastoreBangarangClaimInteractor can't break client.port.interactors.BangarangClaimInteractorContract.
- Position
- Below the diagonal: client.adapters.GcpDatastoreBangarangClaimInteractor uses a module listed above it, which is the healthy direction.
28→2 client.adapters.RestBangarangClaimInteractor uses client.adapters.RestInteractor✕
- Connections
- 1 pair of types, where a type in client.adapters.RestBangarangClaimInteractor uses a type in client.adapters.RestInteractor.
- The types involved
src.client.adapters.RestBangarangClaimInteractor.RestBangarangClaimInteractor→src.client.adapters.RestInteractor.RestInteractor
- Direction
- client.adapters.RestBangarangClaimInteractor uses client.adapters.RestInteractor, so a change to client.adapters.RestInteractor can break client.adapters.RestBangarangClaimInteractor, while a change to client.adapters.RestBangarangClaimInteractor can't break client.adapters.RestInteractor.
- Position
- Below the diagonal: client.adapters.RestBangarangClaimInteractor uses a module listed above it, which is the healthy direction.
28→17 client.adapters.RestBangarangClaimInteractor uses client.port.ClaimContract✕
- Connections
- 1 pair of types, where a type in client.adapters.RestBangarangClaimInteractor uses a type in client.port.ClaimContract.
- The types involved
src.client.adapters.RestBangarangClaimInteractor.RestBangarangClaimInteractor→src.client.port.ClaimContract.ClaimContract
- Direction
- client.adapters.RestBangarangClaimInteractor uses client.port.ClaimContract, so a change to client.port.ClaimContract can break client.adapters.RestBangarangClaimInteractor, while a change to client.adapters.RestBangarangClaimInteractor can't break client.port.ClaimContract.
- Position
- Below the diagonal: client.adapters.RestBangarangClaimInteractor uses a module listed above it, which is the healthy direction.
28→22 client.adapters.RestBangarangClaimInteractor uses client.port.interactors.BangarangClaimInteractorContract✕
- Connections
- 1 pair of types, where a type in client.adapters.RestBangarangClaimInteractor uses a type in client.port.interactors.BangarangClaimInteractorContract.
- The types involved
src.client.adapters.RestBangarangClaimInteractor.RestBangarangClaimInteractor→src.client.port.interactors.BangarangClaimInteractorContract.BangarangClaimInteractorContract
- Direction
- client.adapters.RestBangarangClaimInteractor uses client.port.interactors.BangarangClaimInteractorContract, so a change to client.port.interactors.BangarangClaimInteractorContract can break client.adapters.RestBangarangClaimInteractor, while a change to client.adapters.RestBangarangClaimInteractor can't break client.port.interactors.BangarangClaimInteractorContract.
- Position
- Below the diagonal: client.adapters.RestBangarangClaimInteractor uses a module listed above it, which is the healthy direction.
29→3 client.businessLogic.entities.Claim uses client.port.ClaimChoice✕
- Connections
- 1 pair of types, where a type in client.businessLogic.entities.Claim uses a type in client.port.ClaimChoice.
- The types involved
src.client.businessLogic.entities.Claim.Claim→src.client.port.ClaimChoice.ClaimChoice
- Direction
- client.businessLogic.entities.Claim uses client.port.ClaimChoice, so a change to client.port.ClaimChoice can break client.businessLogic.entities.Claim, while a change to client.businessLogic.entities.Claim can't break client.port.ClaimChoice.
- Position
- Below the diagonal: client.businessLogic.entities.Claim uses a module listed above it, which is the healthy direction.
29→17 client.businessLogic.entities.Claim uses client.port.ClaimContract✕
- Connections
- 1 pair of types, where a type in client.businessLogic.entities.Claim uses a type in client.port.ClaimContract.
- The types involved
src.client.businessLogic.entities.Claim.Claim→src.client.port.ClaimContract.ClaimContract
- Direction
- client.businessLogic.entities.Claim uses client.port.ClaimContract, so a change to client.port.ClaimContract can break client.businessLogic.entities.Claim, while a change to client.businessLogic.entities.Claim can't break client.port.ClaimContract.
- Position
- Below the diagonal: client.businessLogic.entities.Claim uses a module listed above it, which is the healthy direction.
29→18 client.businessLogic.entities.Claim uses client.port.interactors.BangarangMembersInteractorContract✕
- Connections
- 1 pair of types, where a type in client.businessLogic.entities.Claim uses a type in client.port.interactors.BangarangMembersInteractorContract.
- The types involved
src.client.businessLogic.entities.Claim.Claim→src.client.port.interactors.BangarangMembersInteractorContract.BangarangMembersInteractorContract
- Direction
- client.businessLogic.entities.Claim uses client.port.interactors.BangarangMembersInteractorContract, so a change to client.port.interactors.BangarangMembersInteractorContract can break client.businessLogic.entities.Claim, while a change to client.businessLogic.entities.Claim can't break client.port.interactors.BangarangMembersInteractorContract.
- Position
- Below the diagonal: client.businessLogic.entities.Claim uses a module listed above it, which is the healthy direction.
29→22 client.businessLogic.entities.Claim uses client.port.interactors.BangarangClaimInteractorContract✕
- Connections
- 1 pair of types, where a type in client.businessLogic.entities.Claim uses a type in client.port.interactors.BangarangClaimInteractorContract.
- The types involved
src.client.businessLogic.entities.Claim.Claim→src.client.port.interactors.BangarangClaimInteractorContract.BangarangClaimInteractorContract
- Direction
- client.businessLogic.entities.Claim uses client.port.interactors.BangarangClaimInteractorContract, so a change to client.port.interactors.BangarangClaimInteractorContract can break client.businessLogic.entities.Claim, while a change to client.businessLogic.entities.Claim can't break client.port.interactors.BangarangClaimInteractorContract.
- Position
- Below the diagonal: client.businessLogic.entities.Claim uses a module listed above it, which is the healthy direction.
30→8 client.port.BangarangAdaptersContract uses client.port.interactors.BangarangUserInterfaceInteractor✕
- Connections
- 1 pair of types, where a type in client.port.BangarangAdaptersContract uses a type in client.port.interactors.BangarangUserInterfaceInteractor.
- The types involved
src.client.port.BangarangAdaptersContract.BangarangAdaptersContract→src.client.port.interactors.BangarangUserInterfaceInteractor.BangarangUserInterfaceInteractorContract
- Direction
- client.port.BangarangAdaptersContract uses client.port.interactors.BangarangUserInterfaceInteractor, so a change to client.port.interactors.BangarangUserInterfaceInteractor can break client.port.BangarangAdaptersContract, while a change to client.port.BangarangAdaptersContract can't break client.port.interactors.BangarangUserInterfaceInteractor.
- Position
- Below the diagonal: client.port.BangarangAdaptersContract uses a module listed above it, which is the healthy direction.
30→9 client.port.BangarangAdaptersContract uses client.port.interactors.ClaimingUserNotificationInteractorContract✕
- Connections
- 1 pair of types, where a type in client.port.BangarangAdaptersContract uses a type in client.port.interactors.ClaimingUserNotificationInteractorContract.
- The types involved
src.client.port.BangarangAdaptersContract.BangarangAdaptersContract→src.client.port.interactors.ClaimingUserNotificationInteractorContract.ClaimingUserNotificationInteractorContract
- Direction
- client.port.BangarangAdaptersContract uses client.port.interactors.ClaimingUserNotificationInteractorContract, so a change to client.port.interactors.ClaimingUserNotificationInteractorContract can break client.port.BangarangAdaptersContract, while a change to client.port.BangarangAdaptersContract can't break client.port.interactors.ClaimingUserNotificationInteractorContract.
- Position
- Below the diagonal: client.port.BangarangAdaptersContract uses a module listed above it, which is the healthy direction.
30→10 client.port.BangarangAdaptersContract uses client.port.interactors.EmailInteractorContract✕
- Connections
- 1 pair of types, where a type in client.port.BangarangAdaptersContract uses a type in client.port.interactors.EmailInteractorContract.
- The types involved
src.client.port.BangarangAdaptersContract.BangarangAdaptersContract→src.client.port.interactors.EmailInteractorContract.EmailInteractorContract
- Direction
- client.port.BangarangAdaptersContract uses client.port.interactors.EmailInteractorContract, so a change to client.port.interactors.EmailInteractorContract can break client.port.BangarangAdaptersContract, while a change to client.port.BangarangAdaptersContract can't break client.port.interactors.EmailInteractorContract.
- Position
- Below the diagonal: client.port.BangarangAdaptersContract uses a module listed above it, which is the healthy direction.
30→11 client.port.BangarangAdaptersContract uses client.port.interactors.PasswordInteractorContract✕
- Connections
- 1 pair of types, where a type in client.port.BangarangAdaptersContract uses a type in client.port.interactors.PasswordInteractorContract.
- The types involved
src.client.port.BangarangAdaptersContract.BangarangAdaptersContract→src.client.port.interactors.PasswordInteractorContract.PasswordInteractorContract
- Direction
- client.port.BangarangAdaptersContract uses client.port.interactors.PasswordInteractorContract, so a change to client.port.interactors.PasswordInteractorContract can break client.port.BangarangAdaptersContract, while a change to client.port.BangarangAdaptersContract can't break client.port.interactors.PasswordInteractorContract.
- Position
- Below the diagonal: client.port.BangarangAdaptersContract uses a module listed above it, which is the healthy direction.
30→12 client.port.BangarangAdaptersContract uses client.port.interactors.RegisteringUserNotificationInteractorContract✕
- Connections
- 1 pair of types, where a type in client.port.BangarangAdaptersContract uses a type in client.port.interactors.RegisteringUserNotificationInteractorContract.
- The types involved
src.client.port.BangarangAdaptersContract.BangarangAdaptersContract→src.client.port.interactors.RegisteringUserNotificationInteractorContract.RegisteringUserNotificationInteractorContract
- Direction
- client.port.BangarangAdaptersContract uses client.port.interactors.RegisteringUserNotificationInteractorContract, so a change to client.port.interactors.RegisteringUserNotificationInteractorContract can break client.port.BangarangAdaptersContract, while a change to client.port.BangarangAdaptersContract can't break client.port.interactors.RegisteringUserNotificationInteractorContract.
- Position
- Below the diagonal: client.port.BangarangAdaptersContract uses a module listed above it, which is the healthy direction.
30→13 client.port.BangarangAdaptersContract uses client.port.interactors.SearchingClaimsUserNotificationInteractorContract✕
- Connections
- 1 pair of types, where a type in client.port.BangarangAdaptersContract uses a type in client.port.interactors.SearchingClaimsUserNotificationInteractorContract.
- The types involved
src.client.port.BangarangAdaptersContract.BangarangAdaptersContract→src.client.port.interactors.SearchingClaimsUserNotificationInteractorContract.SearchingClaimsUserNotificationInteractorContract
- Direction
- client.port.BangarangAdaptersContract uses client.port.interactors.SearchingClaimsUserNotificationInteractorContract, so a change to client.port.interactors.SearchingClaimsUserNotificationInteractorContract can break client.port.BangarangAdaptersContract, while a change to client.port.BangarangAdaptersContract can't break client.port.interactors.SearchingClaimsUserNotificationInteractorContract.
- Position
- Below the diagonal: client.port.BangarangAdaptersContract uses a module listed above it, which is the healthy direction.
30→14 client.port.BangarangAdaptersContract uses client.port.interactors.SigningInUserNotificationInteractorContract✕
- Connections
- 1 pair of types, where a type in client.port.BangarangAdaptersContract uses a type in client.port.interactors.SigningInUserNotificationInteractorContract.
- The types involved
src.client.port.BangarangAdaptersContract.BangarangAdaptersContract→src.client.port.interactors.SigningInUserNotificationInteractorContract.SigningInUserNotificationInteractorContract
- Direction
- client.port.BangarangAdaptersContract uses client.port.interactors.SigningInUserNotificationInteractorContract, so a change to client.port.interactors.SigningInUserNotificationInteractorContract can break client.port.BangarangAdaptersContract, while a change to client.port.BangarangAdaptersContract can't break client.port.interactors.SigningInUserNotificationInteractorContract.
- Position
- Below the diagonal: client.port.BangarangAdaptersContract uses a module listed above it, which is the healthy direction.
30→18 client.port.BangarangAdaptersContract uses client.port.interactors.BangarangMembersInteractorContract✕
- Connections
- 1 pair of types, where a type in client.port.BangarangAdaptersContract uses a type in client.port.interactors.BangarangMembersInteractorContract.
- The types involved
src.client.port.BangarangAdaptersContract.BangarangAdaptersContract→src.client.port.interactors.BangarangMembersInteractorContract.BangarangMembersInteractorContract
- Direction
- client.port.BangarangAdaptersContract uses client.port.interactors.BangarangMembersInteractorContract, so a change to client.port.interactors.BangarangMembersInteractorContract can break client.port.BangarangAdaptersContract, while a change to client.port.BangarangAdaptersContract can't break client.port.interactors.BangarangMembersInteractorContract.
- Position
- Below the diagonal: client.port.BangarangAdaptersContract uses a module listed above it, which is the healthy direction.
30→22 client.port.BangarangAdaptersContract uses client.port.interactors.BangarangClaimInteractorContract✕
- Connections
- 1 pair of types, where a type in client.port.BangarangAdaptersContract uses a type in client.port.interactors.BangarangClaimInteractorContract.
- The types involved
src.client.port.BangarangAdaptersContract.BangarangAdaptersContract→src.client.port.interactors.BangarangClaimInteractorContract.BangarangClaimInteractorContract
- Direction
- client.port.BangarangAdaptersContract uses client.port.interactors.BangarangClaimInteractorContract, so a change to client.port.interactors.BangarangClaimInteractorContract can break client.port.BangarangAdaptersContract, while a change to client.port.BangarangAdaptersContract can't break client.port.interactors.BangarangClaimInteractorContract.
- Position
- Below the diagonal: client.port.BangarangAdaptersContract uses a module listed above it, which is the healthy direction.
30→23 client.port.BangarangAdaptersContract uses client.port.interactors.DeclaringClaimUserNotificationInteractorContract✕
- Connections
- 1 pair of types, where a type in client.port.BangarangAdaptersContract uses a type in client.port.interactors.DeclaringClaimUserNotificationInteractorContract.
- The types involved
src.client.port.BangarangAdaptersContract.BangarangAdaptersContract→src.client.port.interactors.DeclaringClaimUserNotificationInteractorContract.DeclaringClaimUserNotificationInteractorContract
- Direction
- client.port.BangarangAdaptersContract uses client.port.interactors.DeclaringClaimUserNotificationInteractorContract, so a change to client.port.interactors.DeclaringClaimUserNotificationInteractorContract can break client.port.BangarangAdaptersContract, while a change to client.port.BangarangAdaptersContract can't break client.port.interactors.DeclaringClaimUserNotificationInteractorContract.
- Position
- Below the diagonal: client.port.BangarangAdaptersContract uses a module listed above it, which is the healthy direction.
30→24 client.port.BangarangAdaptersContract uses client.port.interactors.RetrievingClaimUserNotificationInteractorContract✕
- Connections
- 1 pair of types, where a type in client.port.BangarangAdaptersContract uses a type in client.port.interactors.RetrievingClaimUserNotificationInteractorContract.
- The types involved
src.client.port.BangarangAdaptersContract.BangarangAdaptersContract→src.client.port.interactors.RetrievingClaimUserNotificationInteractorContract.RetrievingClaimUserNotificationInteractorContract
- Direction
- client.port.BangarangAdaptersContract uses client.port.interactors.RetrievingClaimUserNotificationInteractorContract, so a change to client.port.interactors.RetrievingClaimUserNotificationInteractorContract can break client.port.BangarangAdaptersContract, while a change to client.port.BangarangAdaptersContract can't break client.port.interactors.RetrievingClaimUserNotificationInteractorContract.
- Position
- Below the diagonal: client.port.BangarangAdaptersContract uses a module listed above it, which is the healthy direction.
31→3 client.port.interactors uses client.port.ClaimChoice✕
- Connections
- 1 pair of types, where a type in client.port.interactors uses a type in client.port.ClaimChoice.
- The types involved
src.client.port.interactors.ClaimingUserNotificationInteractorContract→src.client.port.ClaimChoice.ClaimChoice
- Direction
- client.port.interactors uses client.port.ClaimChoice, so a change to client.port.ClaimChoice can break client.port.interactors, while a change to client.port.interactors can't break client.port.ClaimChoice.
- Position
- Below the diagonal: client.port.interactors uses a module listed above it, which is the healthy direction.
31→9 client.port.interactors uses client.port.interactors.ClaimingUserNotificationInteractorContract✕
- Connections
- 1 pair of types, where a type in client.port.interactors uses a type in client.port.interactors.ClaimingUserNotificationInteractorContract.
- The types involved
src.client.port.interactors.ClaimingUserNotificationInteractorContract→src.client.port.interactors.ClaimingUserNotificationInteractorContract.ClaimingUserNotificationContract
- Direction
- client.port.interactors uses client.port.interactors.ClaimingUserNotificationInteractorContract, so a change to client.port.interactors.ClaimingUserNotificationInteractorContract can break client.port.interactors, while a change to client.port.interactors can't break client.port.interactors.ClaimingUserNotificationInteractorContract.
- Position
- Below the diagonal: client.port.interactors uses a module listed above it, which is the healthy direction.
31→12 client.port.interactors uses client.port.interactors.RegisteringUserNotificationInteractorContract✕
- Connections
- 1 pair of types, where a type in client.port.interactors uses a type in client.port.interactors.RegisteringUserNotificationInteractorContract.
- The types involved
src.client.port.interactors.RegisteringUserNotificationInteractorContract→src.client.port.interactors.RegisteringUserNotificationInteractorContract.RegisteringUserNotificationContract
- Direction
- client.port.interactors uses client.port.interactors.RegisteringUserNotificationInteractorContract, so a change to client.port.interactors.RegisteringUserNotificationInteractorContract can break client.port.interactors, while a change to client.port.interactors can't break client.port.interactors.RegisteringUserNotificationInteractorContract.
- Position
- Below the diagonal: client.port.interactors uses a module listed above it, which is the healthy direction.
31→13 client.port.interactors uses client.port.interactors.SearchingClaimsUserNotificationInteractorContract✕
- Connections
- 1 pair of types, where a type in client.port.interactors uses a type in client.port.interactors.SearchingClaimsUserNotificationInteractorContract.
- The types involved
src.client.port.interactors.SearchingClaimsUserNotificationInteractorContract→src.client.port.interactors.SearchingClaimsUserNotificationInteractorContract.SearchingClaimsUserNotificationContract
- Direction
- client.port.interactors uses client.port.interactors.SearchingClaimsUserNotificationInteractorContract, so a change to client.port.interactors.SearchingClaimsUserNotificationInteractorContract can break client.port.interactors, while a change to client.port.interactors can't break client.port.interactors.SearchingClaimsUserNotificationInteractorContract.
- Position
- Below the diagonal: client.port.interactors uses a module listed above it, which is the healthy direction.
31→14 client.port.interactors uses client.port.interactors.SigningInUserNotificationInteractorContract✕
- Connections
- 1 pair of types, where a type in client.port.interactors uses a type in client.port.interactors.SigningInUserNotificationInteractorContract.
- The types involved
src.client.port.interactors.SigningInUserNotificationInteractorContract→src.client.port.interactors.SigningInUserNotificationInteractorContract.SigningInUserNotificationContract
- Direction
- client.port.interactors uses client.port.interactors.SigningInUserNotificationInteractorContract, so a change to client.port.interactors.SigningInUserNotificationInteractorContract can break client.port.interactors, while a change to client.port.interactors can't break client.port.interactors.SigningInUserNotificationInteractorContract.
- Position
- Below the diagonal: client.port.interactors uses a module listed above it, which is the healthy direction.
31→17 client.port.interactors uses client.port.ClaimContract✕
- Connections
- 2 pairs of types, where a type in client.port.interactors uses a type in client.port.ClaimContract.
- The types involved
src.client.port.interactors.DeclaringClaimUserNotificationInteractorContract→src.client.port.ClaimContract.ClaimContractsrc.client.port.interactors.RetrievingClaimUserNotificationInteractorContract→src.client.port.ClaimContract.ClaimContractWithMemberPreviousClaimChoice
- Direction
- client.port.interactors uses client.port.ClaimContract, so a change to client.port.ClaimContract can break client.port.interactors, while a change to client.port.interactors can't break client.port.ClaimContract.
- Position
- Below the diagonal: client.port.interactors uses a module listed above it, which is the healthy direction.
31→23 client.port.interactors uses client.port.interactors.DeclaringClaimUserNotificationInteractorContract✕
- Connections
- 1 pair of types, where a type in client.port.interactors uses a type in client.port.interactors.DeclaringClaimUserNotificationInteractorContract.
- The types involved
src.client.port.interactors.DeclaringClaimUserNotificationInteractorContract→src.client.port.interactors.DeclaringClaimUserNotificationInteractorContract.DeclaringClaimUserNotificationContract
- Direction
- client.port.interactors uses client.port.interactors.DeclaringClaimUserNotificationInteractorContract, so a change to client.port.interactors.DeclaringClaimUserNotificationInteractorContract can break client.port.interactors, while a change to client.port.interactors can't break client.port.interactors.DeclaringClaimUserNotificationInteractorContract.
- Position
- Below the diagonal: client.port.interactors uses a module listed above it, which is the healthy direction.
31→24 client.port.interactors uses client.port.interactors.RetrievingClaimUserNotificationInteractorContract✕
- Connections
- 1 pair of types, where a type in client.port.interactors uses a type in client.port.interactors.RetrievingClaimUserNotificationInteractorContract.
- The types involved
src.client.port.interactors.RetrievingClaimUserNotificationInteractorContract→src.client.port.interactors.RetrievingClaimUserNotificationInteractorContract.RetrievingClaimUserNotificationContract
- Direction
- client.port.interactors uses client.port.interactors.RetrievingClaimUserNotificationInteractorContract, so a change to client.port.interactors.RetrievingClaimUserNotificationInteractorContract can break client.port.interactors, while a change to client.port.interactors can't break client.port.interactors.RetrievingClaimUserNotificationInteractorContract.
- Position
- Below the diagonal: client.port.interactors uses a module listed above it, which is the healthy direction.
32→18 server uses client.port.interactors.BangarangMembersInteractorContract✕
- Connections
- 1 pair of types, where a type in server uses a type in client.port.interactors.BangarangMembersInteractorContract.
- The types involved
src.server.BangarangMembersInteractor→src.client.port.interactors.BangarangMembersInteractorContract.BangarangMembersInteractorContract
- Direction
- server uses client.port.interactors.BangarangMembersInteractorContract, so a change to client.port.interactors.BangarangMembersInteractorContract can break server, while a change to server can't break client.port.interactors.BangarangMembersInteractorContract.
- Position
- Below the diagonal: server uses a module listed above it, which is the healthy direction.
32→22 server uses client.port.interactors.BangarangClaimInteractorContract✕
- Connections
- 1 pair of types, where a type in server uses a type in client.port.interactors.BangarangClaimInteractorContract.
- The types involved
src.server.BangarangClaimInteractor→src.client.port.interactors.BangarangClaimInteractorContract.BangarangClaimInteractorContract
- Direction
- server uses client.port.interactors.BangarangClaimInteractorContract, so a change to client.port.interactors.BangarangClaimInteractorContract can break server, while a change to server can't break client.port.interactors.BangarangClaimInteractorContract.
- Position
- Below the diagonal: server uses a module listed above it, which is the healthy direction.
33→4 client.businessLogic.commands.claiming uses client.port.Command✕
- Connections
- 2 pairs of types, where a type in client.businessLogic.commands.claiming uses a type in client.port.Command.
- The types involved
src.client.businessLogic.commands.claiming.Claiming→src.client.port.Command.Commandsrc.client.businessLogic.commands.claiming.Claiming→src.client.port.Command.CommandName
- Direction
- client.businessLogic.commands.claiming uses client.port.Command, so a change to client.port.Command can break client.businessLogic.commands.claiming, while a change to client.businessLogic.commands.claiming can't break client.port.Command.
- Position
- Below the diagonal: client.businessLogic.commands.claiming uses a module listed above it, which is the healthy direction.
33→30 client.businessLogic.commands.claiming uses client.port.BangarangAdaptersContract✕
- Connections
- 1 pair of types, where a type in client.businessLogic.commands.claiming uses a type in client.port.BangarangAdaptersContract.
- The types involved
src.client.businessLogic.commands.claiming.Claiming→src.client.port.BangarangAdaptersContract.BangarangAdaptersContract
- Direction
- client.businessLogic.commands.claiming uses client.port.BangarangAdaptersContract, so a change to client.port.BangarangAdaptersContract can break client.businessLogic.commands.claiming, while a change to client.businessLogic.commands.claiming can't break client.port.BangarangAdaptersContract.
- Position
- Below the diagonal: client.businessLogic.commands.claiming uses a module listed above it, which is the healthy direction.
34→4 client.businessLogic.commands.declaringClaim uses client.port.Command✕
- Connections
- 2 pairs of types, where a type in client.businessLogic.commands.declaringClaim uses a type in client.port.Command.
- The types involved
src.client.businessLogic.commands.declaringClaim.DeclaringClaim→src.client.port.Command.Commandsrc.client.businessLogic.commands.declaringClaim.DeclaringClaim→src.client.port.Command.CommandName
- Direction
- client.businessLogic.commands.declaringClaim uses client.port.Command, so a change to client.port.Command can break client.businessLogic.commands.declaringClaim, while a change to client.businessLogic.commands.declaringClaim can't break client.port.Command.
- Position
- Below the diagonal: client.businessLogic.commands.declaringClaim uses a module listed above it, which is the healthy direction.
34→30 client.businessLogic.commands.declaringClaim uses client.port.BangarangAdaptersContract✕
- Connections
- 1 pair of types, where a type in client.businessLogic.commands.declaringClaim uses a type in client.port.BangarangAdaptersContract.
- The types involved
src.client.businessLogic.commands.declaringClaim.DeclaringClaim→src.client.port.BangarangAdaptersContract.BangarangAdaptersContract
- Direction
- client.businessLogic.commands.declaringClaim uses client.port.BangarangAdaptersContract, so a change to client.port.BangarangAdaptersContract can break client.businessLogic.commands.declaringClaim, while a change to client.businessLogic.commands.declaringClaim can't break client.port.BangarangAdaptersContract.
- Position
- Below the diagonal: client.businessLogic.commands.declaringClaim uses a module listed above it, which is the healthy direction.
35→4 client.businessLogic.commands.registering uses client.port.Command✕
- Connections
- 2 pairs of types, where a type in client.businessLogic.commands.registering uses a type in client.port.Command.
- The types involved
src.client.businessLogic.commands.registering.Registering→src.client.port.Command.Commandsrc.client.businessLogic.commands.registering.Registering→src.client.port.Command.CommandName
- Direction
- client.businessLogic.commands.registering uses client.port.Command, so a change to client.port.Command can break client.businessLogic.commands.registering, while a change to client.businessLogic.commands.registering can't break client.port.Command.
- Position
- Below the diagonal: client.businessLogic.commands.registering uses a module listed above it, which is the healthy direction.
35→30 client.businessLogic.commands.registering uses client.port.BangarangAdaptersContract✕
- Connections
- 1 pair of types, where a type in client.businessLogic.commands.registering uses a type in client.port.BangarangAdaptersContract.
- The types involved
src.client.businessLogic.commands.registering.Registering→src.client.port.BangarangAdaptersContract.BangarangAdaptersContract
- Direction
- client.businessLogic.commands.registering uses client.port.BangarangAdaptersContract, so a change to client.port.BangarangAdaptersContract can break client.businessLogic.commands.registering, while a change to client.businessLogic.commands.registering can't break client.port.BangarangAdaptersContract.
- Position
- Below the diagonal: client.businessLogic.commands.registering uses a module listed above it, which is the healthy direction.
36→4 client.businessLogic.commands.retrievingClaimById uses client.port.Command✕
- Connections
- 2 pairs of types, where a type in client.businessLogic.commands.retrievingClaimById uses a type in client.port.Command.
- The types involved
src.client.businessLogic.commands.retrievingClaimById.RetrievingClaimById→src.client.port.Command.Commandsrc.client.businessLogic.commands.retrievingClaimById.RetrievingClaimById→src.client.port.Command.CommandName
- Direction
- client.businessLogic.commands.retrievingClaimById uses client.port.Command, so a change to client.port.Command can break client.businessLogic.commands.retrievingClaimById, while a change to client.businessLogic.commands.retrievingClaimById can't break client.port.Command.
- Position
- Below the diagonal: client.businessLogic.commands.retrievingClaimById uses a module listed above it, which is the healthy direction.
36→30 client.businessLogic.commands.retrievingClaimById uses client.port.BangarangAdaptersContract✕
- Connections
- 1 pair of types, where a type in client.businessLogic.commands.retrievingClaimById uses a type in client.port.BangarangAdaptersContract.
- The types involved
src.client.businessLogic.commands.retrievingClaimById.RetrievingClaimById→src.client.port.BangarangAdaptersContract.BangarangAdaptersContract
- Direction
- client.businessLogic.commands.retrievingClaimById uses client.port.BangarangAdaptersContract, so a change to client.port.BangarangAdaptersContract can break client.businessLogic.commands.retrievingClaimById, while a change to client.businessLogic.commands.retrievingClaimById can't break client.port.BangarangAdaptersContract.
- Position
- Below the diagonal: client.businessLogic.commands.retrievingClaimById uses a module listed above it, which is the healthy direction.
37→4 client.businessLogic.commands.searchingClaims uses client.port.Command✕
- Connections
- 2 pairs of types, where a type in client.businessLogic.commands.searchingClaims uses a type in client.port.Command.
- The types involved
src.client.businessLogic.commands.searchingClaims.SearchingClaims→src.client.port.Command.Commandsrc.client.businessLogic.commands.searchingClaims.SearchingClaims→src.client.port.Command.CommandName
- Direction
- client.businessLogic.commands.searchingClaims uses client.port.Command, so a change to client.port.Command can break client.businessLogic.commands.searchingClaims, while a change to client.businessLogic.commands.searchingClaims can't break client.port.Command.
- Position
- Below the diagonal: client.businessLogic.commands.searchingClaims uses a module listed above it, which is the healthy direction.
37→30 client.businessLogic.commands.searchingClaims uses client.port.BangarangAdaptersContract✕
- Connections
- 1 pair of types, where a type in client.businessLogic.commands.searchingClaims uses a type in client.port.BangarangAdaptersContract.
- The types involved
src.client.businessLogic.commands.searchingClaims.SearchingClaims→src.client.port.BangarangAdaptersContract.BangarangAdaptersContract
- Direction
- client.businessLogic.commands.searchingClaims uses client.port.BangarangAdaptersContract, so a change to client.port.BangarangAdaptersContract can break client.businessLogic.commands.searchingClaims, while a change to client.businessLogic.commands.searchingClaims can't break client.port.BangarangAdaptersContract.
- Position
- Below the diagonal: client.businessLogic.commands.searchingClaims uses a module listed above it, which is the healthy direction.
38→4 client.businessLogic.commands.signingIn uses client.port.Command✕
- Connections
- 2 pairs of types, where a type in client.businessLogic.commands.signingIn uses a type in client.port.Command.
- The types involved
src.client.businessLogic.commands.signingIn.SigningIn→src.client.port.Command.Commandsrc.client.businessLogic.commands.signingIn.SigningIn→src.client.port.Command.CommandName
- Direction
- client.businessLogic.commands.signingIn uses client.port.Command, so a change to client.port.Command can break client.businessLogic.commands.signingIn, while a change to client.businessLogic.commands.signingIn can't break client.port.Command.
- Position
- Below the diagonal: client.businessLogic.commands.signingIn uses a module listed above it, which is the healthy direction.
38→30 client.businessLogic.commands.signingIn uses client.port.BangarangAdaptersContract✕
- Connections
- 1 pair of types, where a type in client.businessLogic.commands.signingIn uses a type in client.port.BangarangAdaptersContract.
- The types involved
src.client.businessLogic.commands.signingIn.SigningIn→src.client.port.BangarangAdaptersContract.BangarangAdaptersContract
- Direction
- client.businessLogic.commands.signingIn uses client.port.BangarangAdaptersContract, so a change to client.port.BangarangAdaptersContract can break client.businessLogic.commands.signingIn, while a change to client.businessLogic.commands.signingIn can't break client.port.BangarangAdaptersContract.
- Position
- Below the diagonal: client.businessLogic.commands.signingIn uses a module listed above it, which is the healthy direction.
39→3 client.businessLogic.entities.User uses client.port.ClaimChoice✕
- Connections
- 1 pair of types, where a type in client.businessLogic.entities.User uses a type in client.port.ClaimChoice.
- The types involved
src.client.businessLogic.entities.User.User→src.client.port.ClaimChoice.ClaimChoice
- Direction
- client.businessLogic.entities.User uses client.port.ClaimChoice, so a change to client.port.ClaimChoice can break client.businessLogic.entities.User, while a change to client.businessLogic.entities.User can't break client.port.ClaimChoice.
- Position
- Below the diagonal: client.businessLogic.entities.User uses a module listed above it, which is the healthy direction.
39→4 client.businessLogic.entities.User uses client.port.Command✕
- Connections
- 1 pair of types, where a type in client.businessLogic.entities.User uses a type in client.port.Command.
- The types involved
src.client.businessLogic.entities.User.User→src.client.port.Command.CommandName
- Direction
- client.businessLogic.entities.User uses client.port.Command, so a change to client.port.Command can break client.businessLogic.entities.User, while a change to client.businessLogic.entities.User can't break client.port.Command.
- Position
- Below the diagonal: client.businessLogic.entities.User uses a module listed above it, which is the healthy direction.
39→6 client.businessLogic.entities.User uses client.port.UserContact✕
- Connections
- 1 pair of types, where a type in client.businessLogic.entities.User uses a type in client.port.UserContact.
- The types involved
src.client.businessLogic.entities.User.User→src.client.port.UserContact.UserContract
- Direction
- client.businessLogic.entities.User uses client.port.UserContact, so a change to client.port.UserContact can break client.businessLogic.entities.User, while a change to client.businessLogic.entities.User can't break client.port.UserContact.
- Position
- Below the diagonal: client.businessLogic.entities.User uses a module listed above it, which is the healthy direction.
39→30 client.businessLogic.entities.User uses client.port.BangarangAdaptersContract✕
- Connections
- 1 pair of types, where a type in client.businessLogic.entities.User uses a type in client.port.BangarangAdaptersContract.
- The types involved
src.client.businessLogic.entities.User.User→src.client.port.BangarangAdaptersContract.BangarangAdaptersContract
- Direction
- client.businessLogic.entities.User uses client.port.BangarangAdaptersContract, so a change to client.port.BangarangAdaptersContract can break client.businessLogic.entities.User, while a change to client.businessLogic.entities.User can't break client.port.BangarangAdaptersContract.
- Position
- Below the diagonal: client.businessLogic.entities.User uses a module listed above it, which is the healthy direction.
40→8 client.businessLogic.entities.UserBuilder uses client.port.interactors.BangarangUserInterfaceInteractor✕
- Connections
- 1 pair of types, where a type in client.businessLogic.entities.UserBuilder uses a type in client.port.interactors.BangarangUserInterfaceInteractor.
- The types involved
src.client.businessLogic.entities.UserBuilder.UserBuilder→src.client.port.interactors.BangarangUserInterfaceInteractor.BangarangUserInterfaceInteractorContract
- Direction
- client.businessLogic.entities.UserBuilder uses client.port.interactors.BangarangUserInterfaceInteractor, so a change to client.port.interactors.BangarangUserInterfaceInteractor can break client.businessLogic.entities.UserBuilder, while a change to client.businessLogic.entities.UserBuilder can't break client.port.interactors.BangarangUserInterfaceInteractor.
- Position
- Below the diagonal: client.businessLogic.entities.UserBuilder uses a module listed above it, which is the healthy direction.
40→9 client.businessLogic.entities.UserBuilder uses client.port.interactors.ClaimingUserNotificationInteractorContract✕
- Connections
- 1 pair of types, where a type in client.businessLogic.entities.UserBuilder uses a type in client.port.interactors.ClaimingUserNotificationInteractorContract.
- The types involved
src.client.businessLogic.entities.UserBuilder.UserBuilder→src.client.port.interactors.ClaimingUserNotificationInteractorContract.ClaimingUserNotificationInteractorContract
- Direction
- client.businessLogic.entities.UserBuilder uses client.port.interactors.ClaimingUserNotificationInteractorContract, so a change to client.port.interactors.ClaimingUserNotificationInteractorContract can break client.businessLogic.entities.UserBuilder, while a change to client.businessLogic.entities.UserBuilder can't break client.port.interactors.ClaimingUserNotificationInteractorContract.
- Position
- Below the diagonal: client.businessLogic.entities.UserBuilder uses a module listed above it, which is the healthy direction.
40→12 client.businessLogic.entities.UserBuilder uses client.port.interactors.RegisteringUserNotificationInteractorContract✕
- Connections
- 1 pair of types, where a type in client.businessLogic.entities.UserBuilder uses a type in client.port.interactors.RegisteringUserNotificationInteractorContract.
- The types involved
src.client.businessLogic.entities.UserBuilder.UserBuilder→src.client.port.interactors.RegisteringUserNotificationInteractorContract.RegisteringUserNotificationInteractorContract
- Direction
- client.businessLogic.entities.UserBuilder uses client.port.interactors.RegisteringUserNotificationInteractorContract, so a change to client.port.interactors.RegisteringUserNotificationInteractorContract can break client.businessLogic.entities.UserBuilder, while a change to client.businessLogic.entities.UserBuilder can't break client.port.interactors.RegisteringUserNotificationInteractorContract.
- Position
- Below the diagonal: client.businessLogic.entities.UserBuilder uses a module listed above it, which is the healthy direction.
40→13 client.businessLogic.entities.UserBuilder uses client.port.interactors.SearchingClaimsUserNotificationInteractorContract✕
- Connections
- 1 pair of types, where a type in client.businessLogic.entities.UserBuilder uses a type in client.port.interactors.SearchingClaimsUserNotificationInteractorContract.
- The types involved
src.client.businessLogic.entities.UserBuilder.UserBuilder→src.client.port.interactors.SearchingClaimsUserNotificationInteractorContract.SearchingClaimsUserNotificationInteractorContract
- Direction
- client.businessLogic.entities.UserBuilder uses client.port.interactors.SearchingClaimsUserNotificationInteractorContract, so a change to client.port.interactors.SearchingClaimsUserNotificationInteractorContract can break client.businessLogic.entities.UserBuilder, while a change to client.businessLogic.entities.UserBuilder can't break client.port.interactors.SearchingClaimsUserNotificationInteractorContract.
- Position
- Below the diagonal: client.businessLogic.entities.UserBuilder uses a module listed above it, which is the healthy direction.
40→14 client.businessLogic.entities.UserBuilder uses client.port.interactors.SigningInUserNotificationInteractorContract✕
- Connections
- 1 pair of types, where a type in client.businessLogic.entities.UserBuilder uses a type in client.port.interactors.SigningInUserNotificationInteractorContract.
- The types involved
src.client.businessLogic.entities.UserBuilder.UserBuilder→src.client.port.interactors.SigningInUserNotificationInteractorContract.SigningInUserNotificationInteractorContract
- Direction
- client.businessLogic.entities.UserBuilder uses client.port.interactors.SigningInUserNotificationInteractorContract, so a change to client.port.interactors.SigningInUserNotificationInteractorContract can break client.businessLogic.entities.UserBuilder, while a change to client.businessLogic.entities.UserBuilder can't break client.port.interactors.SigningInUserNotificationInteractorContract.
- Position
- Below the diagonal: client.businessLogic.entities.UserBuilder uses a module listed above it, which is the healthy direction.
40→18 client.businessLogic.entities.UserBuilder uses client.port.interactors.BangarangMembersInteractorContract✕
- Connections
- 1 pair of types, where a type in client.businessLogic.entities.UserBuilder uses a type in client.port.interactors.BangarangMembersInteractorContract.
- The types involved
src.client.businessLogic.entities.UserBuilder.UserBuilder→src.client.port.interactors.BangarangMembersInteractorContract.BangarangMembersInteractorContract
- Direction
- client.businessLogic.entities.UserBuilder uses client.port.interactors.BangarangMembersInteractorContract, so a change to client.port.interactors.BangarangMembersInteractorContract can break client.businessLogic.entities.UserBuilder, while a change to client.businessLogic.entities.UserBuilder can't break client.port.interactors.BangarangMembersInteractorContract.
- Position
- Below the diagonal: client.businessLogic.entities.UserBuilder uses a module listed above it, which is the healthy direction.
40→22 client.businessLogic.entities.UserBuilder uses client.port.interactors.BangarangClaimInteractorContract✕
- Connections
- 1 pair of types, where a type in client.businessLogic.entities.UserBuilder uses a type in client.port.interactors.BangarangClaimInteractorContract.
- The types involved
src.client.businessLogic.entities.UserBuilder.UserBuilder→src.client.port.interactors.BangarangClaimInteractorContract.BangarangClaimInteractorContract
- Direction
- client.businessLogic.entities.UserBuilder uses client.port.interactors.BangarangClaimInteractorContract, so a change to client.port.interactors.BangarangClaimInteractorContract can break client.businessLogic.entities.UserBuilder, while a change to client.businessLogic.entities.UserBuilder can't break client.port.interactors.BangarangClaimInteractorContract.
- Position
- Below the diagonal: client.businessLogic.entities.UserBuilder uses a module listed above it, which is the healthy direction.
40→23 client.businessLogic.entities.UserBuilder uses client.port.interactors.DeclaringClaimUserNotificationInteractorContract✕
- Connections
- 1 pair of types, where a type in client.businessLogic.entities.UserBuilder uses a type in client.port.interactors.DeclaringClaimUserNotificationInteractorContract.
- The types involved
src.client.businessLogic.entities.UserBuilder.UserBuilder→src.client.port.interactors.DeclaringClaimUserNotificationInteractorContract.DeclaringClaimUserNotificationInteractorContract
- Direction
- client.businessLogic.entities.UserBuilder uses client.port.interactors.DeclaringClaimUserNotificationInteractorContract, so a change to client.port.interactors.DeclaringClaimUserNotificationInteractorContract can break client.businessLogic.entities.UserBuilder, while a change to client.businessLogic.entities.UserBuilder can't break client.port.interactors.DeclaringClaimUserNotificationInteractorContract.
- Position
- Below the diagonal: client.businessLogic.entities.UserBuilder uses a module listed above it, which is the healthy direction.
40→24 client.businessLogic.entities.UserBuilder uses client.port.interactors.RetrievingClaimUserNotificationInteractorContract✕
- Connections
- 1 pair of types, where a type in client.businessLogic.entities.UserBuilder uses a type in client.port.interactors.RetrievingClaimUserNotificationInteractorContract.
- The types involved
src.client.businessLogic.entities.UserBuilder.UserBuilder→src.client.port.interactors.RetrievingClaimUserNotificationInteractorContract.RetrievingClaimUserNotificationInteractorContract
- Direction
- client.businessLogic.entities.UserBuilder uses client.port.interactors.RetrievingClaimUserNotificationInteractorContract, so a change to client.port.interactors.RetrievingClaimUserNotificationInteractorContract can break client.businessLogic.entities.UserBuilder, while a change to client.businessLogic.entities.UserBuilder can't break client.port.interactors.RetrievingClaimUserNotificationInteractorContract.
- Position
- Below the diagonal: client.businessLogic.entities.UserBuilder uses a module listed above it, which is the healthy direction.
40→30 client.businessLogic.entities.UserBuilder uses client.port.BangarangAdaptersContract✕
- Connections
- 1 pair of types, where a type in client.businessLogic.entities.UserBuilder uses a type in client.port.BangarangAdaptersContract.
- The types involved
src.client.businessLogic.entities.UserBuilder.UserBuilder→src.client.port.BangarangAdaptersContract.BangarangAdaptersContract
- Direction
- client.businessLogic.entities.UserBuilder uses client.port.BangarangAdaptersContract, so a change to client.port.BangarangAdaptersContract can break client.businessLogic.entities.UserBuilder, while a change to client.businessLogic.entities.UserBuilder can't break client.port.BangarangAdaptersContract.
- Position
- Below the diagonal: client.businessLogic.entities.UserBuilder uses a module listed above it, which is the healthy direction.
40→39 client.businessLogic.entities.UserBuilder uses client.businessLogic.entities.User✕
- Connections
- 1 pair of types, where a type in client.businessLogic.entities.UserBuilder uses a type in client.businessLogic.entities.User.
- The types involved
src.client.businessLogic.entities.UserBuilder.UserBuilder→src.client.businessLogic.entities.User.User
- Direction
- client.businessLogic.entities.UserBuilder uses client.businessLogic.entities.User, so a change to client.businessLogic.entities.User can break client.businessLogic.entities.UserBuilder, while a change to client.businessLogic.entities.UserBuilder can't break client.businessLogic.entities.User.
- Position
- Below the diagonal: client.businessLogic.entities.UserBuilder 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 — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 70 | High / Critical |
| A07:2025 — Authentication Failures | 5 | High / Critical |
Roadmap
Top priorities: Resolve the 1 Inverted test pyramid finding(s) in Test Distribution; Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do; Store passwords with a salted, deliberately slow KDF — scrypt or PBKDF2 from node:crypto, or bcrypt/Argon2 — and compare with a constant-time check. A fast digest of a password, however it is encoded, is reversed by precomputed tables or GPU guessing. Start in `REDACTED:2115`.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Inverted test pyramid finding(s) in Test Distribution. | +7.2 pts | Low | Test Distribution |
| Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do. | +6.4 pts | Medium | Access Controls |
| Store passwords with a salted, deliberately slow KDF — scrypt or PBKDF2 from node:crypto, or bcrypt/Argon2 — and compare with a constant-time check. A fast digest of a password, however it is encoded, is reversed by precomputed tables or GPU guessing. Start in `REDACTED:2115`. | +5.8 pts | Medium | Web-Security Posture |
| Resolve the 4 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED. | +1.6 pts | Low | Secrets (history) |
| Adopt pino (or winston) and log at meaningful points in the services you run. | +3.0 pts | Medium | Observability |
| Resolve the 41 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (41). | +2.9 pts | Medium | Dependency Vulnerabilities |
| Resolve the 16 No assertions finding(s) in Test Quality — start with retrievingClaim.spec.ts (5), declaringClaim.spec.ts (4), signingIn.spec.ts (4). | +2.7 pts | Medium | Test Quality |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +2.7 pts | Medium | Keyboard semantics |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| src/tests/acceptance/retrievingClaim.spec.ts | 7.1 | Mixed | Test Quality: No assertions: When the user retrieve the claim with title '${expectedClaim.title}' |
| src/tests/acceptance/declaringClaim.spec.ts | 7.2 | Mixed | Test Quality: No assertions: When the user declare a new '${expectedClaim.type}' claim with title '${expectedClaim.title}'. |
| src/tests/acceptance/signingIn.spec.ts | 7.2 | Mixed | Test Quality: No assertions: When the user signin as '${expectedUser.username}' with password '${expectedUserPassword}' |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| src/tests/acceptance/claiming.spec.ts | 8.5 | Near-clean | Test Quality: No assertions: When the user claim '${scenario.userChoice}' on the claim with title '${scenario.expectedClaim.title}' |
| src/tests/acceptance/registering.spec.ts | 8.5 | Near-clean | Test Quality: No assertions: When the user register on Bangarang with the following parameters: | username | password | email | fullname | | ${scenario.userContract.username} | ${scenario.userPassword} | ${scenario.userContract.email} | ${scenario.userContract.fullname} | |
| src/tests/acceptance/searchingClaims.spec.ts | 8.5 | Near-clean | Test Quality: No assertions: When the user search claims with search criteria '${scenario.searchCriteria}' |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 71 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 71 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, 235 of 251 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D1 Cyclomatic Complexity — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.js, .svelte) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D2 Cognitive Complexity — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.js, .svelte) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's 1 package.json manifest(s) WERE read and their pinning discipline assessed; what went unanswered is the currency half, because answering it needs a lockfile resolved to CONCRETE versions and this repository's 1 committed lockfile(s) are in a format this engine does not resolve. The resolver reads pnpm-lock.yaml, REDACTED / npm-shrinkwrap.json at lockfileVersion 2 or 3, yarn.lock in both the classic and berry dialects, and bun's text bun.lock; what it cannot read is bun.lockb, a binary serialisation of bun's install graph with no published layout, and a lockfileVersion 1 REDACTED, which is a differently-shaped nested tree. So nothing here could be graded and registry.npmjs.org was never asked. This is OUR side and it is a COLLECTOR gap, not an environment fault: the remedy is to write the reader for the format this repository commits, and no change to the scan image or the egress allowlist can close it.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository declares package.json manifests but commits no lockfile this pass can resolve (npm, pnpm, yarn and bun each write a different one, and `bun.lockb` is a binary format with no published shape), so the set of packages it actually ships is not resolvable from the checkout: its declarations carry version RANGES, and grading whichever release happens to be newest today would be a verdict about a dependency graph this repository has not pinned. Commit the lock and this dimension grades its production dependencies against registry.npmjs.org. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 137 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The dev server kept running but no port it opened served a page in the time allowed. (rule: no-answer). The renderer reported: the dev server (`npm run dev`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "at Module._compile (node:internal/modules/cjs/loader:1562:14) / at Object..js (node:internal/modules/cjs/loader:1699:10) / at Module.load (node:internal/modules/cjs/loader:1313:32) / at Function._load (node:internal/modules/cjs/loader:1123:12) / at TracingChannel.traceSync (node:diagnostics_channel:322:14) / at wrapModuleLoad (node:internal/modules/cjs/loader:217:24) / at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:170:5) / at node:internal/main/run_main_module:36:49 / Node.js v22.13.0 / > Server crashed / ✔ service worker (616ms)" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "at Module._compile (node:internal/modules/cjs/loader:1562:14) / at Object..js (node:internal/modules/cjs/loader:1699:10) / at Module.load (node:internal/modules/cjs/loader:1313:32) / at Function._load (node:internal/modules/cjs/loader:1123:12) / at TracingChannel.traceSync (node:diagnostics_channel:322:14) / at wrapModuleLoad (node:internal/modules/cjs/loader:217:24) / at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:170:5) / at node:internal/main/run_main_module:36:49 / Node.js v22.13.0 / > Server crashed / ✔ service worker (616ms)" No runtime evidence was gathered.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 96 further occurrence(s) are not listed individually; the score already reflects all 136.
- R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 97 further occurrence(s) are not listed individually; the score already reflects all 137.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- 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.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
Dimensions
D6 · Cohesion (LCOM4)
0 of 10 classes have LCOM4 above 3.
D9 · Test Distribution
112 test methods: 0 unit, 24 integration, 88 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 112 `it`/`test` case(s) across 8 test file(s) declaring at least one; its tier split is read from package names and paths only.
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, 16 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 112 tests.
What to do
- Resolve the 16 No assertions finding(s) in Test Quality — start with retrievingClaim.spec.ts (5), declaringClaim.spec.ts (4), signingIn.spec.ts (4). — One of this dimension's main actionable groups (16 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.
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (mocha via `npm ci --ignore-scripts` in the repository root (217 tests)): measured (0 flaky).
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 3142 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 13 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 1 build units (npm) flagged as possibly oversized/incoherent.
D27 · Navigability
63 % of calls cross a namespace and 21 % go through an interface, but 97 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Improve Navigability — currently 8.8/10. — 63 % of calls cross a namespace and 21 % go through an interface, but 97 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
4 finding(s): 0 critical, 4 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 4 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 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)
semgrep found no security issues.
D30 · Dependency Vulnerabilities
70 finding(s): 5 critical, 44 high, 13 medium, 8 low.
What to do
- Resolve the 41 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (41). — One of this dimension's main actionable groups (41 issue-level).
- Resolve the 5 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 3 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
D34 · Knowledge Freshness
24 of 24 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/client/logic/messages.ts. Counted over 24 of the 187 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 23 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED, uiPrimaryAdapter.ts, valuePropositions.ts. — One of this dimension's main actionable groups (23 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Most significant orphaned file finding(s) in Knowledge Freshness — start with messages.ts. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
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 8 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
AC2 · Forms & labels
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. — src/client/components/SearchBars/ClaimSearchBar.svelte:25
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — src/template.html:2
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — src/template.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×2) — src/client/components/Cards/SearchedClaim.svelte:12, src/client/components/Links/BackToMainMenuLink.svelte:9
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC6 · Visual & motion safety
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (eslint-plugin-svelte (a11y rules are built in)) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 101 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — package.json:36
What to do
- Enforce accessibility in the toolchain: add eslint-plugin-svelte (a11y rules are built in), then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
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
AX6 · Interface segregation
C2 · Access Controls
- This repository serves requests — express() (REDACTED:61) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — REDACTED:61
What to do
- Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
GD1 · Unfinished & placeholder code
- A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in. (×4) — REDACTED:2573, REDACTED:2611, src/client/adapters/uiPrimaryAdapter.ts:92, …
What to do
- Finish or delete the functions that still throw "not implemented", and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
M1 · Documentation (README)
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
- A CI pipeline exists but no test-runner invocation (your stack's test command, or a test job) was found — changes may merge without the suite running.
- A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
- Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.
- Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
P2 · Observability
- No logging call was found in the 86 JavaScript/TypeScript production file(s) this check read across 1 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Adopt pino (or winston) and log at meaningful points in the services you run.
- Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 42 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.
- `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:26
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P7 · Outbound HTTP resilience
- `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×4) — __sapper__/build/client/shimport@2.0.4.js:1, REDACTED:9644, __sapper__/build/service-worker.js:82, …
- `axios(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — src/client/adapters/RestInteractor.ts:27
What to do
- Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- src/client/businessLogic/commands/registering.ts:8 · src/client/businessLogic/commands/signingIn.ts:10 — the two spans are one implementation copied and then locally edited — 234 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/client/businessLogic/commands/registering.ts:8
- REDACTED:212 · REDACTED:224 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:212
- REDACTED:105 · REDACTED:248 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:105
- src/client/logic/messages.ts:522 · src/client/logic/messages.ts:532 · src/client/logic/messages.ts:542 · src/client/logic/messages.ts:552 · +4 more site(s) not listed — all 8 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/client/logic/messages.ts:522
- REDACTED:137 · REDACTED:174 · REDACTED:188 · REDACTED:202 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:137
- REDACTED:185 · REDACTED:199 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:185
- src/client/adapters/GcpDatastoreBangarangClaimInteractor.ts:11 · REDACTED:19 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/client/adapters/GcpDatastoreBangarangClaimInteractor.ts:11
- src/client/logic/messages.ts:507 · src/client/logic/messages.ts:526 · src/client/logic/messages.ts:536 · src/client/logic/messages.ts:546 · +5 more site(s) not listed — all 9 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/client/logic/messages.ts:507
- REDACTED:163 · REDACTED:177 · REDACTED:191 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:163
- REDACTED:55 · REDACTED:61 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:55
- src/client/adapters/GcpDatastoreInteractor.ts:43 · src/client/adapters/GcpDatastoreInteractor.ts:65 · src/client/adapters/GcpDatastoreInteractor.ts:83 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/client/adapters/GcpDatastoreInteractor.ts:43
- REDACTED:70 · REDACTED:98 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:70
- REDACTED:239 · REDACTED:257 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:239
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
R3 · Large Files
- src/client/logic/messages.ts has 731 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/client/logic/messages.ts:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — src/client/logic/messages.ts:1, src/client/logic/valueProposition/valuePropositions.ts:1, REDACTED:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
- 46 outdated package(s); JS/npm CVEs scored in D30
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
- test ✓ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add eslint and `tsc --noEmit` as package.json scripts and run them in CI.
R7 · Dead Code
- Unreachable from the 1 application, 4 tooling and 8 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), but 34 in-repo import(s) from 34 other file(s) do name it (src/client/components/AppBarComponents/Actions/ClaimShare.svelte, src/client/components/AppBarComponents/Actions/NavigateBackToMainMenu.svelte, src/client/components/AppBarComponents/Actions/NavigateToBusinessModel.svelte and 31 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/client/logic/messages.ts
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (src/client/components/Mains/LandingPageMain.svelte, src/client/logic/messages.ts, src/client/logic/valueProposition/retreiveValuePropositionFromValuePropositionPageLink.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/client/logic/valueProposition/valuePropositions.ts
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), but 7 in-repo import(s) from 7 other file(s) do name it (src/client/logic/claiming.ts, src/client/logic/declaringNewClaim.ts, src/client/logic/registering.ts and 4 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/client/adapters/uiPrimaryAdapter.ts
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×9) — src/routes/[language]/claims/[claimId].svelte, src/routes/[language]/landingPages/[audience]/[landingPageId].svelte, src/routes/[language]/valuePropositions/[valuePropositionPageLink].svelte, …
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/client/adapters/uiPrimaryAdapter.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×6) — src/client/adapters/SvelteBangarangUserInterfaceInteractor.ts, src/client/adapters/SvelteSearchingClaimsUserNotificationInteractorContract.ts, src/client/adapters/SvelteClaimingUserNotificationInteractorContract.ts, …
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), but 10 in-repo import(s) from 10 other file(s) do name it (src/client/components/AppBarComponents/Actions/ClaimShare.svelte, src/client/components/AppBarComponents/Actions/NavigateBackToMainMenu.svelte, src/client/components/AppBarComponents/Actions/NavigateToBusinessModel.svelte and 7 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/client/components/Icons/heroicon.ts
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/client/views/BusinessModelView.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/client/components/Mains/BusinessModelMain.svelte
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/client/components/Footers/MainMenuFooter.svelte, src/client/components/Footers/SearchedClaimsFooter.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/client/components/SearchBars/ClaimSearchBar.svelte
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/client/views/ClaimView.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — src/client/components/Footers/ClaimFooter.svelte, src/client/components/Mains/ClaimMain.svelte
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/client/components/Form/NewClaimForm.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/client/logic/declaringNewClaim.ts
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/client/components/Sections/RegisterSection.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/client/components/Form/RegisterForm.svelte
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/client/components/Mains/DeclareClaimMain.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/client/components/Form/NewClaimForm.svelte
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/client/components/Sections/SignInSection.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/client/components/Form/SignInForm.svelte
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/routes/[language]/index.svelte, src/routes/index.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/routes/[language]/MainMenu.svelte
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (src/client/components/Headers/SelectLanguageHeader.svelte, src/client/components/Mains/LandingPageMain.svelte, src/client/components/Mains/LeanCanvasMain.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/client/components/Titles/MainTitle.svelte
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), but 7 in-repo import(s) from 7 other file(s) do name it (src/client/components/Headers/ValuePropositionHeader.svelte, src/client/components/Lists/ValuePropositionDesignCanvasList.svelte, src/client/components/Mains/ValuePropositionMain.svelte and 4 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/client/interfaces/ValuePropositionCanvasContract.ts
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/client/views/LandingPageView.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/client/components/Mains/LandingPageMain.svelte
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/routes/LanguageSelect.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/client/views/SelectLanguageView.svelte
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/client/components/Mains/ClaimMain.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/client/components/Buttons/ClaimButton.svelte
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/client/components/Mains/SearchedClaimsMain.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/client/components/Lists/SearchedClaims.svelte
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/client/components/Form/SignInForm.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/client/logic/signingIn.ts
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/client/components/Buttons/ClaimButton.svelte, src/client/components/Mains/LandingPageMain.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/client/components/Buttons/GenericButton.svelte
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/client/components/Lists/SearchedClaims.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/client/components/Cards/SearchedClaim.svelte
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/client/components/Cards/DescriptionCard.svelte, src/client/components/Mains/SelectLanguageMain.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/client/components/Links/Link.svelte
- no import path from any entry point (1 application, 4 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/client/components/Form/RegisterForm.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/client/logic/registering.ts
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×3) — src/client/logic/language.ts:3, REDACTED:5, src/service-worker.ts:1
- Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
S1 · Web-Security Posture
- `credentialOnDatabase.password === credentials.password` checks a password against the stored one in plaintext, so the store holds the password itself and whoever reads it holds every account. (×2) — REDACTED:2115, src/client/adapters/FakeBangarangMembersInteractor.ts:35
- `result.password === credentials.password` checks a password against the stored one in plaintext, so the store holds the password itself and whoever reads it holds every account. (×2) — REDACTED:10167, REDACTED:78
- `https://www.googletagmanager.com/gtag/js?id=G-SK0GKMDDJT` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. — src/template.html:30
- 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 `vercel.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.) — vercel.json:1
- `App$1.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — REDACTED:10588
- `App.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — REDACTED:278
What to do
- Store passwords with a salted, deliberately slow KDF — scrypt or PBKDF2 from node:crypto, or bcrypt/Argon2 — and compare with a constant-time check. A fast digest of a password, however it is encoded, is reversed by precomputed tables or GPU guessing. Start in `REDACTED:2115`.
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
- 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.
- Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 70% | Adequate — gated by R7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 90% | Exemplary | Solid. |
| Maturity | 68% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 20% | Critical — gated by D9, R4, R6, R8, P2, P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 24% | Critical — gated by C2, S1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 41% | Weak — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Not evidenced — 2 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 58 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run dev`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "at Module._compile (node:internal/modules/cjs/loader:1562:14) / at Object..js (node:internal/modules/cjs/loader:1699:10) / at Module.load (node:internal/modules/cjs/loader:1313:32) / at Function._load (node:internal/modules/cjs/loader:1123:12) / at TracingChannel.traceSync (node:diagnostics_channel:322:14) / at wrapModuleLoad (node:internal/modules/cjs/loader:217:24) / at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:170:5) / at node:internal/main/run_main_module:36:49 / Node.js v22.13.0 / > Server crashed / ✔ service worker (616ms)" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
- D1 Cyclomatic Complexity — cyclomatic complexity not measured — .js, .svelte exposed no member bodies
- D12 Dependency Hygiene — Dependency currency not established — no reader for this repository's lockfile format
- D14 License Compliance — npm licences not graded — this npm repository commits no lockfile this pass can resolve
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D2 Cognitive Complexity — cognitive complexity not measured — .js, .svelte exposed no member bodies
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; html not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- 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 — Too few judgeable comments (9 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D3 God Classes — Most of this repository's production source (.js, .svelte) was not read by god-class detection, so class size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's class size. 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) — 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.
- 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). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- 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.
- D4 Code Duplication — This repository's production source (.js, .svelte, .ts) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- 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.
- D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the repository root runs mocha but declares no coverage provider, so the suite can run and still produce no lcov — add `c8` (or `nyc`) as a devDependency so the suite can be wrapped for coverage. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- 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
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) 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 tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 64 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Password hashing without a KDF REDACTED:2115
- Password hashing without a KDF REDACTED:10167
- Password hashing without a KDF src/client/adapters/FakeBangarangMembersInteractor.ts:35
- Password hashing without a KDF REDACTED:78
- REDACTED
- REDACTED
- REDACTED
- <input> without a programmatic label src/client/components/SearchBars/ClaimSearchBar.svelte:25
- Document without a <title> src/template.html:2
- Click handler on a non-interactive <div> src/client/components/Cards/SearchedClaim.svelte:12
- Click handler on a non-interactive <p> src/client/components/Links/BackToMainMenuLink.svelte:9
- Unlisted import '@sapper/app' src/client/logic/language.ts:3
- Unlisted import '@sapper/server' REDACTED:5
- Unlisted import '@sapper/service-worker' src/service-worker.ts:1
Serious — 137 finding(s)
- No test reaches this file src/client/logic/messages.ts:1
- No test reaches this file src/client/logic/valueProposition/valuePropositions.ts:1
- No test reaches this file REDACTED:1
- No test reaches this file src/client/adapters/uiPrimaryAdapter.ts:1
- No test reaches this file src/client/adapters/GcpDatastoreBangarangClaimInteractor.ts:1
- No test reaches this file src/client/adapters/GcpDatastoreInteractor.ts:1
- No test reaches this file src/routes/[language]/claims/[claimId].svelte:1
- No test reaches this file REDACTED:1
- No test reaches this file src/client/logic/language.ts:1
- No test reaches this file src/client/adapters/SvelteBangarangUserInterfaceInteractor.ts:1
- No test reaches this file src/client/components/Icons/heroicon.ts:1
- No test reaches this file src/client/components/Mains/BusinessModelMain.svelte:1
- No test reaches this file src/client/components/SearchBars/ClaimSearchBar.svelte:1
- No test reaches this file src/routes/[language]/landingPages/[audience]/[landingPageId].svelte:1
- No test reaches this file src/client/components/Footers/ClaimFooter.svelte:1
- No test reaches this file src/client/logic/declaringNewClaim.ts:1
- No test reaches this file src/client/components/Form/RegisterForm.svelte:1
- No test reaches this file src/routes/[language]/valuePropositions/[valuePropositionPageLink].svelte:1
- No test reaches this file src/client/components/Form/NewClaimForm.svelte:1
- No test reaches this file src/client/components/Form/SignInForm.svelte:1
- No test reaches this file src/routes/[language]/MainMenu.svelte:1
- No test reaches this file src/client/components/Titles/MainTitle.svelte:1
- No test reaches this file src/routes/[language]/BusinessModel.svelte:1
- No test reaches this file src/routes/[language]/DeclareClaim.svelte:1
- No test reaches this file src/routes/[language]/LeanCanvas.svelte:1
- No assertions: When the user claim '${scenario.userChoice}' on the claim with title '${scenario.expectedClaim.title}' src/tests/acceptance/claiming.spec.ts:218
- No assertions: When the user declare a new '${expectedClaim.type}' claim with title '${expectedClaim.title}'. src/tests/acceptance/declaringClaim.spec.ts:34
- No assertions: When the user declare a new '${expectedClaim.type}' claim with title '${expectedClaim.title}'. src/tests/acceptance/declaringClaim.spec.ts:60
- No assertions: When the user declare a new '${upperCaseClaim.type}' claim with title '${upperCaseClaim.title}'. src/tests/acceptance/declaringClaim.spec.ts:86
- No assertions: When the user declare a new '${claimWithoutTitle.type}' claim with title '${claimWithoutTitle.title}'. src/tests/acceptance/declaringClaim.spec.ts:107
- No assertions: When the user register on Bangarang with the following parameters: | username | password | email | fullname | | ${scenario.userContract.username} | ${scenario.userPassword} | ${scenario.userContract.email} | ${scenario.userContract.fullname} | src/tests/acceptance/registering.spec.ts:107
- No assertions: When the user retrieve the claim with title '${expectedClaim.title}' src/tests/acceptance/retrievingClaim.spec.ts:71
- No assertions: When the user retrieve the claim with id '${expectedClaim.id}' src/tests/acceptance/retrievingClaim.spec.ts:100
- No assertions: When the user retrieve the claim with id '${expectedClaim.id}' src/tests/acceptance/retrievingClaim.spec.ts:129
- No assertions: When the user retrieve the claim with id '${expectedClaim.id}' src/tests/acceptance/retrievingClaim.spec.ts:159
- No assertions: When the user retrieve the claim with title '${expectedClaim.id}' src/tests/acceptance/retrievingClaim.spec.ts:185
- No assertions: When the user search claims with search criteria '${scenario.searchCriteria}' src/tests/acceptance/searchingClaims.spec.ts:258
- No assertions: When the user signin as '${expectedUser.username}' with password '${expectedUserPassword}' src/tests/acceptance/signingIn.spec.ts:38
- No assertions: When the user signin as '${expectedUser.username}' with password '${expectedUserPassword}' src/tests/acceptance/signingIn.spec.ts:71
- No assertions: When the user signin as '${expectedUser.username}' with password '${expectedUserPassword}' src/tests/acceptance/signingIn.spec.ts:95
- No assertions: When the user signin as '${expectedUser.username}' with password '${badPassword}' src/tests/acceptance/signingIn.spec.ts:122
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Dead file (~14 LoC) src/client/components/Titles/MainTitle.svelte
- Dead file (~14 LoC) src/client/interfaces/ValuePropositionCanvasContract.ts
- Dead file (~14 LoC) src/routes/[language]/BusinessModel.svelte
- Dead file (~14 LoC) src/routes/[language]/DeclareClaim.svelte
- Dead file (~14 LoC) src/routes/[language]/LeanCanvas.svelte
- Dead file (~14 LoC) src/routes/[language]/Register.svelte
- Dead file (~14 LoC) src/routes/[language]/SigningInMenu.svelte
- Dead file (~10 LoC) src/client/adapters/SvelteSearchingClaimsUserNotificationInteractorContract.ts
- Dead file (~10 LoC) src/client/components/Buttons/GenericButton.svelte
- Dead file (~10 LoC) src/client/components/Cards/SearchedClaim.svelte
- Dead file (~10 LoC) src/client/components/Links/Link.svelte
- Dead file (~10 LoC) src/client/logic/registering.ts
- Dead file (~10 LoC) src/routes/[language]/index.svelte
- Outbound HTTP without resilience __sapper__/build/client/shimport@2.0.4.js:1
- Outbound HTTP without resilience REDACTED:9644
- Outbound HTTP without resilience __sapper__/build/service-worker.js:82
- Outbound HTTP without resilience src/client/adapters/RestInteractor.ts:27
- Outbound HTTP without resilience src/service-worker.ts:43
- Dead file (~9 LoC) src/client/adapters/SvelteClaimingUserNotificationInteractorContract.ts
- Dead file (~9 LoC) src/client/adapters/SvelteDeclaringClaimUserNotificationInteractor.ts
- Dead file (~9 LoC) src/client/adapters/SvelteRegisteringUserNotificationInteractor.ts
- Dead file (~9 LoC) src/client/adapters/SvelteRetrievingClaimUserNotificationInteractor.ts
- Dead file (~23 LoC) src/client/components/Mains/BusinessModelMain.svelte
- Dead file (~23 LoC) src/client/components/SearchBars/ClaimSearchBar.svelte
- Dead file (~23 LoC) src/routes/[language]/landingPages/[audience]/[landingPageId].svelte
- Dead file (~11 LoC) src/client/components/Buttons/ClaimButton.svelte
- Dead file (~11 LoC) src/client/components/Lists/SearchedClaims.svelte
- Dead file (~11 LoC) src/client/logic/signingIn.ts
- Duplicated block (5 lines × 2 locations) REDACTED:70
- Duplicated block (5 lines × 2 locations) REDACTED:239
- Dead file (~25 LoC) src/client/adapters/SvelteBangarangUserInterfaceInteractor.ts
- Dead file (~25 LoC) src/client/components/Icons/heroicon.ts
- Dead file (~18 LoC) src/client/components/Form/RegisterForm.svelte
- Dead file (~18 LoC) src/routes/[language]/valuePropositions/[valuePropositionPageLink].svelte
- Dead file (~17 LoC) src/client/components/Form/NewClaimForm.svelte
- Dead file (~17 LoC) src/client/components/Form/SignInForm.svelte
- Dead file (~12 LoC) src/client/components/Mains/ClaimMain.svelte
- Dead file (~12 LoC) src/client/views/SelectLanguageView.svelte
- Page without a main landmark src/template.html:2
- Accessibility enforcement below the top rung package.json:36
- No authorization REDACTED:61
- Coverage not measured — JavaScript/TypeScript suite
- No structured logging
- Duplicated block with local edits (34 matched lines × 2 locations) src/client/businessLogic/commands/registering.ts:8
- Duplicated block (12 lines × 2 locations) REDACTED:212
- Duplicated block (11 lines × 2 locations) REDACTED:105
- Duplicated block (10 lines × 8 locations) src/client/logic/messages.ts:522
- Duplicated block (9 lines × 4 locations) REDACTED:137
- Duplicated block (9 lines × 2 locations) REDACTED:185
- Duplicated block (7 lines × 2 locations) src/client/adapters/GcpDatastoreBangarangClaimInteractor.ts:11
- Duplicated block (7 lines × 9 locations) src/client/logic/messages.ts:507
- Duplicated block (7 lines × 3 locations) REDACTED:163
- Duplicated block (6 lines × 2 locations) REDACTED:55
- Duplicated block (5 lines × 3 locations) src/client/adapters/GcpDatastoreInteractor.ts:43
- src/client/logic/messages.ts: 731 lines of code src/client/logic/messages.ts:1
- Dependency Freshness
- No lint or typecheck script
- Dead file (~732 LoC) src/client/logic/messages.ts
- Dead file (~290 LoC) src/client/logic/valueProposition/valuePropositions.ts
- Dead file (~158 LoC) src/client/adapters/uiPrimaryAdapter.ts
- Dead file (~95 LoC) src/routes/[language]/claims/[claimId].svelte
- Dead file (~20 LoC) src/client/components/Footers/ClaimFooter.svelte
- Dead file (~19 LoC) src/client/logic/declaringNewClaim.ts
- Dead file (~16 LoC) src/routes/[language]/MainMenu.svelte
- Dead file (~13 LoC) src/client/components/Mains/LandingPageMain.svelte
- Unused dependency 'svelte-check'
- Unused dependency 'tslib'
- Third-party script without Subresource Integrity src/template.html:30
Minor — 50 finding(s)
- Orphaned file REDACTED:1
- Orphaned file src/client/adapters/uiPrimaryAdapter.ts:1
- Orphaned file src/client/logic/valueProposition/valuePropositions.ts:1
- Orphaned file src/client/adapters/GcpDatastoreBangarangClaimInteractor.ts:1
- Orphaned file src/client/businessLogic/entities/UserBuilder.ts:1
- Orphaned file src/routes/[language]/claims/[claimId].svelte:1
- Orphaned file src/client/adapters/GcpDatastoreInteractor.ts:1
- Orphaned file REDACTED:1
- Orphaned file src/client/adapters/FakeBangarangMembersInteractor.ts:1
- Orphaned file rollup.config.js:1
- Orphaned file src/client/businessLogic/commands/searchingClaims.ts:1
- Orphaned file src/client/businessLogic/commands/claiming.ts:1
- Orphaned file src/client/businessLogic/entities/User.ts:1
- Orphaned file src/client/businessLogic/commands/declaringClaim.ts:1
- Orphaned file src/client/adapters/RestBangarangMembersInteractor.ts:1
- Orphaned file src/client/adapters/FakeBangarangClaimInteractor.ts:1
- Orphaned file src/client/components/Icons/heroicon.ts:1
- Orphaned file src/client/businessLogic/commands/registering.ts:1
- Orphaned file src/client/businessLogic/commands/signingIn.ts:1
- Orphaned file src/client/businessLogic/commands/retrievingClaimById.ts:1
- Orphaned file src/service-worker.ts:1
- Orphaned file src/client/components/Footers/ClaimFooter.svelte:1
- Orphaned file src/client/components/Form/RegisterForm.svelte:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Placeholder literal left in code REDACTED:2573
- Placeholder literal left in code REDACTED:2611
- Placeholder literal left in code src/client/adapters/uiPrimaryAdapter.ts:92
- Placeholder literal left in code src/client/adapters/uiPrimaryAdapter.ts:126
- No app-layer HTTPS enforcement detected REDACTED:10588
- No app-layer HTTPS enforcement detected REDACTED:278
- No ADRs found
- REDACTED
- Dormant codebase
- Most significant orphaned file src/client/logic/messages.ts:1
- REDACTED
- Inverted test pyramid
- No ADRs
- CI test execution not evidenced
- CI build step not evidenced
- No SAST
- No dependency-update automation package.json:26
- No release approval gate
- No security response headers detected vercel.json:1
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-cf09eb6d4b0b4c278f19d405c3bbf20b/history.json --exit-code 0 --source . | 7 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-cf09eb6d4b0b4c278f19d405c3bbf20b/tree.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 70 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |