Executive summary
nblockchain/geewallet falls short of our standard for production, in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 52 out of 100 and is rated Adequate, and 32 of its 38 critical findings are security problems.
Production Readiness, at 45, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 5 points. Adding automated security scanning would lift Production Readiness itself, also worth about 5. Raising Production Readiness to 70 would lift the score to about 56.
Twenty-eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two passwords or keys in the code's history and one in the code are open to anyone who can read the repository, and one pipeline step installs packages that can change without warning. Replacing each exposed password or key, pinning each tool to an exact version and pinning what the pipeline installs would close these risks. The six sets of compiler warnings switched off in projects need turning back on in the build file.
The product code is 11,768 lines, about €13,000 to rebuild.
If Production Readiness rose from 45 to 70, the lowest score rated Strong, the score would rise from 52 to about 56.
New since the last survey: 4 findings
- Code Duplication · Edited copies of one member (3 members, 24+ corresponding lines) src/GWallet.Backend/Properties/AssemblyInfo.fs
- Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) src/GWallet.Frontend.XF.Gtk/Properties/AssemblyInfo.fs
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/GWallet.Backend.Tests/GWallet.Backend.Tests.fsproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/GWallet.Frontend.ConsoleApp/GWallet.Frontend.ConsoleApp.fsproj
Fixed since the last survey: 2 findings
- REDACTED Scanning · Leaked secret: private-key-store REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/GWallet.Frontend.ConsoleApp/GWallet.Frontend.ConsoleApp.fsproj
Rebuild cost: about €13,000 · Estimate
| Cost to rebuild | €4,300 to €21,000, for 71 to 226 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Low, 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 52. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 11,768 lines of product code |
| Comment lines | The estimate prices 11,717 lines. Comment lines count towards the size of 11,768 lines but aren't priced as work. |
| 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 — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Backend | 2 Backend.FSharpUtil | 3 Backend.FSharpUtil.ReflectionlessPrint | 4 Backend.FSharpUtil.UwpHacks | 5 Backend.Networking | 6 Backend.Shuffler | 7 Backend.VersionHelper | 8 Backend.WarpKey | 9 Frontend.ConsoleApp.Program | 10 Frontend.XF.Controls | 11 Frontend.XamForms.UWP | 12 Backend.Account | 13 Backend.BlockExplorer | 14 Backend.Caching | 15 Backend.Config | 16 Backend.Ether | 17 Backend.Ether.TokenManager | 18 Backend.Ether.Web3ServerSeedList | 19 Backend.FiatValueEstimation | 20 Backend.Formatting | 21 Backend.Infrastructure | 22 Backend.Marshalling | 23 Backend.ServerManager | 24 Backend.ServerRegistry | 25 Backend.UtxoCoin | 26 Frontend.Console | 27 Frontend.Console.Presentation | 28 Frontend.Console.Program | 29 Backend.Ether.Account | 30 Backend.Ether.Server | 31 Backend.UtxoCoin.Account | 32 Backend.UtxoCoin.ElectrumClient | 33 Backend.UtxoCoin.ElectrumServerSeedList | 34 Backend.UtxoCoin.Server | 35 Frontend.Console.UserInteraction | 36 Frontend.XF.FrontendHelpers | 37 Frontend.XF | 38 Frontend.XF.DummyPageConstructorHelper | 39 Frontend.XF.Initialization |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Backend | |||||||||||||||||||||||||||||||||||||||
| 2 Backend.FSharpUtil | |||||||||||||||||||||||||||||||||||||||
| 3 Backend.FSharpUtil.ReflectionlessPrint | |||||||||||||||||||||||||||||||||||||||
| 4 Backend.FSharpUtil.UwpHacks | |||||||||||||||||||||||||||||||||||||||
| 5 Backend.Networking | |||||||||||||||||||||||||||||||||||||||
| 6 Backend.Shuffler | |||||||||||||||||||||||||||||||||||||||
| 7 Backend.VersionHelper | |||||||||||||||||||||||||||||||||||||||
| 8 Backend.WarpKey | |||||||||||||||||||||||||||||||||||||||
| 9 Frontend.ConsoleApp.Program | |||||||||||||||||||||||||||||||||||||||
| 10 Frontend.XF.Controls | |||||||||||||||||||||||||||||||||||||||
| 11 Frontend.XamForms.UWP | |||||||||||||||||||||||||||||||||||||||
| 12 Backend.Account | 18 | ||||||||||||||||||||||||||||||||||||||
| 13 Backend.BlockExplorer | 2 | ||||||||||||||||||||||||||||||||||||||
| 14 Backend.Caching | 9 | ||||||||||||||||||||||||||||||||||||||
| 15 Backend.Config | 7 | ||||||||||||||||||||||||||||||||||||||
| 16 Backend.Ether | 9 | ||||||||||||||||||||||||||||||||||||||
| 17 Backend.Ether.TokenManager | 3 | ||||||||||||||||||||||||||||||||||||||
| 18 Backend.Ether.Web3ServerSeedList | 2 | ||||||||||||||||||||||||||||||||||||||
| 19 Backend.FiatValueEstimation | 2 | ||||||||||||||||||||||||||||||||||||||
| 20 Backend.Formatting | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 Backend.Infrastructure | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 Backend.Marshalling | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 Backend.ServerManager | 5 | ||||||||||||||||||||||||||||||||||||||
| 24 Backend.ServerRegistry | 2 | ||||||||||||||||||||||||||||||||||||||
| 25 Backend.UtxoCoin | 18 | ||||||||||||||||||||||||||||||||||||||
| 26 Frontend.Console | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 Frontend.Console.Presentation | 3 | ||||||||||||||||||||||||||||||||||||||
| 28 Frontend.Console.Program | 7 | ||||||||||||||||||||||||||||||||||||||
| 29 Backend.Ether.Account | 13 | 2 | |||||||||||||||||||||||||||||||||||||
| 30 Backend.Ether.Server | 10 | 3 | |||||||||||||||||||||||||||||||||||||
| 31 Backend.UtxoCoin.Account | 12 | 7 | |||||||||||||||||||||||||||||||||||||
| 32 Backend.UtxoCoin.ElectrumClient | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 33 Backend.UtxoCoin.ElectrumServerSeedList | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 Backend.UtxoCoin.Server | 9 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 Frontend.Console.UserInteraction | 5 | 2 | |||||||||||||||||||||||||||||||||||||
| 36 Frontend.XF.FrontendHelpers | 5 | 1 | 4 | ||||||||||||||||||||||||||||||||||||
| 37 Frontend.XF | 17 | 6 | |||||||||||||||||||||||||||||||||||||
| 38 Frontend.XF.DummyPageConstructorHelper | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 Frontend.XF.Initialization | 1 |
12→1 Backend.Account uses Backend✕
- Connections
- 18 pairs of types, where a type in Backend.Account uses a type in Backend.
- The types involved
GWallet.Backend.Account.Account→GWallet.Backend.AccountKindGWallet.Backend.Account.Account→GWallet.Backend.ArchivedAccountGWallet.Backend.Account.Account→GWallet.Backend.ConceptAccountGWallet.Backend.Account.Account→GWallet.Backend.CurrencyGWallet.Backend.Account.Account→GWallet.Backend.CustomCancelSourceGWallet.Backend.Account.Account→GWallet.Backend.FileRepresentationGWallet.Backend.Account.Account→GWallet.Backend.IAccountGWallet.Backend.Account.Account→GWallet.Backend.IBlockchainFeeInfoGWallet.Backend.Account.Account→GWallet.Backend.ITransactionDetailsGWallet.Backend.Account.Account→GWallet.Backend.ImportedTransaction`1GWallet.Backend.Account.Account→GWallet.Backend.NormalAccountGWallet.Backend.Account.Account→GWallet.Backend.ReadOnlyAccountGWallet.Backend.Account.Account→GWallet.Backend.ServerSelectionModeGWallet.Backend.Account.Account→GWallet.Backend.SignedTransaction`1GWallet.Backend.Account.Account→GWallet.Backend.TransferAmountGWallet.Backend.Account.Account→GWallet.Backend.UnsignedTransactionProposalGWallet.Backend.Account.Account→GWallet.Backend.UnsignedTransaction`1GWallet.Backend.Account.Account→GWallet.Backend.WatchWalletInfo
- Direction
- Backend.Account uses Backend, so a change to Backend can break Backend.Account, while a change to Backend.Account can't break Backend.
- Position
- Below the diagonal: Backend.Account uses a module listed above it, which is the healthy direction.
13→1 Backend.BlockExplorer uses Backend✕
- Connections
- 2 pairs of types, where a type in Backend.BlockExplorer uses a type in Backend.
- The types involved
GWallet.Backend.BlockExplorer.BlockExplorer→GWallet.Backend.CurrencyGWallet.Backend.BlockExplorer.BlockExplorer→GWallet.Backend.IAccount
- Direction
- Backend.BlockExplorer uses Backend, so a change to Backend can break Backend.BlockExplorer, while a change to Backend.BlockExplorer can't break Backend.
- Position
- Below the diagonal: Backend.BlockExplorer uses a module listed above it, which is the healthy direction.
14→1 Backend.Caching uses Backend✕
- Connections
- 9 pairs of types, where a type in Backend.Caching uses a type in Backend.
- The types involved
GWallet.Backend.Caching.Caching→GWallet.Backend.CacheFilesGWallet.Backend.Caching.Caching→GWallet.Backend.CurrencyGWallet.Backend.Caching.MainCache→GWallet.Backend.CacheFilesGWallet.Backend.Caching.MainCache→GWallet.Backend.CachedNetworkDataGWallet.Backend.Caching.MainCache→GWallet.Backend.CurrencyGWallet.Backend.Caching.MainCache→GWallet.Backend.DietCacheGWallet.Backend.Caching.MainCache→GWallet.Backend.HistoryFactGWallet.Backend.Caching.MainCache→GWallet.Backend.NotFresh`1GWallet.Backend.Caching.MainCache→GWallet.Backend.ServerDetails
- Direction
- Backend.Caching uses Backend, so a change to Backend can break Backend.Caching, while a change to Backend.Caching can't break Backend.
- Position
- Below the diagonal: Backend.Caching uses a module listed above it, which is the healthy direction.
15→1 Backend.Config uses Backend✕
- Connections
- 7 pairs of types, where a type in Backend.Config uses a type in Backend.
- The types involved
GWallet.Backend.Config.Config→GWallet.Backend.AccountKindGWallet.Backend.Config.Config→GWallet.Backend.BaseAccountGWallet.Backend.Config.Config→GWallet.Backend.ConceptAccountGWallet.Backend.Config.Config→GWallet.Backend.CurrencyGWallet.Backend.Config.Config→GWallet.Backend.FileRepresentationGWallet.Backend.Config.Config→GWallet.Backend.NormalAccountGWallet.Backend.Config.Config→GWallet.Backend.ReadOnlyAccount
- Direction
- Backend.Config uses Backend, so a change to Backend can break Backend.Config, while a change to Backend.Config can't break Backend.
- Position
- Below the diagonal: Backend.Config uses a module listed above it, which is the healthy direction.
16→1 Backend.Ether uses Backend✕
- Connections
- 9 pairs of types, where a type in Backend.Ether uses a type in Backend.
- The types involved
GWallet.Backend.Ether.AbnormalNullValueInJsonResponseException→GWallet.Backend.CommunicationUnsuccessfulExceptionGWallet.Backend.Ether.MinerFee→GWallet.Backend.CurrencyGWallet.Backend.Ether.ServerCannotBeResolvedException→GWallet.Backend.CommunicationUnsuccessfulExceptionGWallet.Backend.Ether.ServerChannelNegotiationException→GWallet.Backend.CloudFlareErrorGWallet.Backend.Ether.ServerChannelNegotiationException→GWallet.Backend.CommunicationUnsuccessfulExceptionGWallet.Backend.Ether.ServerRestrictiveException→GWallet.Backend.CommunicationUnsuccessfulExceptionGWallet.Backend.Ether.ServerUnavailableException→GWallet.Backend.CommunicationUnsuccessfulExceptionGWallet.Backend.Ether.TransactionMetadata→GWallet.Backend.CurrencyGWallet.Backend.Ether.TransactionMetadata→GWallet.Backend.IBlockchainFeeInfo
- Direction
- Backend.Ether uses Backend, so a change to Backend can break Backend.Ether, while a change to Backend.Ether can't break Backend.
- Position
- Below the diagonal: Backend.Ether uses a module listed above it, which is the healthy direction.
17→1 Backend.Ether.TokenManager uses Backend✕
- Connections
- 3 pairs of types, where a type in Backend.Ether.TokenManager uses a type in Backend.
- The types involved
GWallet.Backend.Ether.TokenManager.OfflineTokenServiceWrapper→GWallet.Backend.CurrencyGWallet.Backend.Ether.TokenManager.TokenManager→GWallet.Backend.CurrencyGWallet.Backend.Ether.TokenManager.TokenServiceWrapper→GWallet.Backend.Currency
- Direction
- Backend.Ether.TokenManager uses Backend, so a change to Backend can break Backend.Ether.TokenManager, while a change to Backend.Ether.TokenManager can't break Backend.
- Position
- Below the diagonal: Backend.Ether.TokenManager uses a module listed above it, which is the healthy direction.
18→1 Backend.Ether.Web3ServerSeedList uses Backend✕
- Connections
- 2 pairs of types, where a type in Backend.Ether.Web3ServerSeedList uses a type in Backend.
- The types involved
GWallet.Backend.Ether.Web3ServerSeedList.Web3ServerSeedList→GWallet.Backend.CurrencyGWallet.Backend.Ether.Web3ServerSeedList.Web3ServerSeedList→GWallet.Backend.ServerDetails
- Direction
- Backend.Ether.Web3ServerSeedList uses Backend, so a change to Backend can break Backend.Ether.Web3ServerSeedList, while a change to Backend.Ether.Web3ServerSeedList can't break Backend.
- Position
- Below the diagonal: Backend.Ether.Web3ServerSeedList uses a module listed above it, which is the healthy direction.
19→1 Backend.FiatValueEstimation uses Backend✕
- Connections
- 2 pairs of types, where a type in Backend.FiatValueEstimation uses a type in Backend.
- The types involved
GWallet.Backend.FiatValueEstimation.FiatValueEstimation→GWallet.Backend.CurrencyGWallet.Backend.FiatValueEstimation.FiatValueEstimation→GWallet.Backend.MaybeCached`1
- Direction
- Backend.FiatValueEstimation uses Backend, so a change to Backend can break Backend.FiatValueEstimation, while a change to Backend.FiatValueEstimation can't break Backend.
- Position
- Below the diagonal: Backend.FiatValueEstimation uses a module listed above it, which is the healthy direction.
20→1 Backend.Formatting uses Backend✕
- Connections
- 1 pair of types, where a type in Backend.Formatting uses a type in Backend.
- The types involved
GWallet.Backend.Formatting.Formatting→GWallet.Backend.CurrencyType
- Direction
- Backend.Formatting uses Backend, so a change to Backend can break Backend.Formatting, while a change to Backend.Formatting can't break Backend.
- Position
- Below the diagonal: Backend.Formatting uses a module listed above it, which is the healthy direction.
21→1 Backend.Infrastructure uses Backend✕
- Connections
- 1 pair of types, where a type in Backend.Infrastructure uses a type in Backend.
- The types involved
GWallet.Backend.Infrastructure.Infrastructure→GWallet.Backend.MarshalledException
- Direction
- Backend.Infrastructure uses Backend, so a change to Backend can break Backend.Infrastructure, while a change to Backend.Infrastructure can't break Backend.
- Position
- Below the diagonal: Backend.Infrastructure uses a module listed above it, which is the healthy direction.
22→1 Backend.Marshalling uses Backend✕
- Connections
- 1 pair of types, where a type in Backend.Marshalling uses a type in Backend.
- The types involved
GWallet.Backend.Marshalling.Marshalling→GWallet.Backend.MarshallingWrapper`1
- Direction
- Backend.Marshalling uses Backend, so a change to Backend can break Backend.Marshalling, while a change to Backend.Marshalling can't break Backend.
- Position
- Below the diagonal: Backend.Marshalling uses a module listed above it, which is the healthy direction.
23→1 Backend.ServerManager uses Backend✕
- Connections
- 5 pairs of types, where a type in Backend.ServerManager uses a type in Backend.
- The types involved
GWallet.Backend.ServerManager.ServerManager→GWallet.Backend.CommunicationUnsuccessfulExceptionGWallet.Backend.ServerManager.ServerManager→GWallet.Backend.CurrencyGWallet.Backend.ServerManager.ServerManager→GWallet.Backend.FaultTolerantParallelClientSettings`1GWallet.Backend.ServerManager.ServerManager→GWallet.Backend.FaultTolerantParallelClient`2GWallet.Backend.ServerManager.ServerManager→GWallet.Backend.ServerDetails
- Direction
- Backend.ServerManager uses Backend, so a change to Backend can break Backend.ServerManager, while a change to Backend.ServerManager can't break Backend.
- Position
- Below the diagonal: Backend.ServerManager uses a module listed above it, which is the healthy direction.
24→1 Backend.ServerRegistry uses Backend✕
- Connections
- 2 pairs of types, where a type in Backend.ServerRegistry uses a type in Backend.
- The types involved
GWallet.Backend.ServerRegistry.ServerRegistry→GWallet.Backend.CurrencyGWallet.Backend.ServerRegistry.ServerRegistry→GWallet.Backend.ServerDetails
- Direction
- Backend.ServerRegistry uses Backend, so a change to Backend can break Backend.ServerRegistry, while a change to Backend.ServerRegistry can't break Backend.
- Position
- Below the diagonal: Backend.ServerRegistry uses a module listed above it, which is the healthy direction.
25→1 Backend.UtxoCoin uses Backend✕
- Connections
- 18 pairs of types, where a type in Backend.UtxoCoin uses a type in Backend.
- The types involved
GWallet.Backend.UtxoCoin.ArchivedUtxoAccount→GWallet.Backend.ArchivedAccountGWallet.Backend.UtxoCoin.ArchivedUtxoAccount→GWallet.Backend.CurrencyGWallet.Backend.UtxoCoin.ArchivedUtxoAccount→GWallet.Backend.FileRepresentationGWallet.Backend.UtxoCoin.ElectrumServerReturningErrorInJsonResponseException→GWallet.Backend.CommunicationUnsuccessfulExceptionGWallet.Backend.UtxoCoin.ElectrumServerReturningImproperJsonResponseException→GWallet.Backend.ServerMisconfiguredExceptionGWallet.Backend.UtxoCoin.IUtxoAccount→GWallet.Backend.IAccountGWallet.Backend.UtxoCoin.IncompatibleServerException→GWallet.Backend.CommunicationUnsuccessfulExceptionGWallet.Backend.UtxoCoin.MinerFee→GWallet.Backend.CurrencyGWallet.Backend.UtxoCoin.NormalUtxoAccount→GWallet.Backend.CurrencyGWallet.Backend.UtxoCoin.NormalUtxoAccount→GWallet.Backend.FileRepresentationGWallet.Backend.UtxoCoin.NormalUtxoAccount→GWallet.Backend.NormalAccountGWallet.Backend.UtxoCoin.QuerySettings`1→GWallet.Backend.ServerSelectionModeGWallet.Backend.UtxoCoin.ReadOnlyUtxoAccount→GWallet.Backend.CurrencyGWallet.Backend.UtxoCoin.ReadOnlyUtxoAccount→GWallet.Backend.FileRepresentationGWallet.Backend.UtxoCoin.ReadOnlyUtxoAccount→GWallet.Backend.ReadOnlyAccountGWallet.Backend.UtxoCoin.StratumClient→GWallet.Backend.JsonRpcTcpClientGWallet.Backend.UtxoCoin.TransactionMetadata→GWallet.Backend.CurrencyGWallet.Backend.UtxoCoin.TransactionMetadata→GWallet.Backend.IBlockchainFeeInfo
- Direction
- Backend.UtxoCoin uses Backend, so a change to Backend can break Backend.UtxoCoin, while a change to Backend.UtxoCoin can't break Backend.
- Position
- Below the diagonal: Backend.UtxoCoin uses a module listed above it, which is the healthy direction.
26→1 Frontend.Console uses Backend✕
- Connections
- 1 pair of types, where a type in Frontend.Console uses a type in Backend.
- The types involved
GWallet.Frontend.Console.WhichAccount→GWallet.Backend.IAccount
- Direction
- Frontend.Console uses Backend, so a change to Backend can break Frontend.Console, while a change to Frontend.Console can't break Backend.
- Position
- Below the diagonal: Frontend.Console uses a module listed above it, which is the healthy direction.
27→1 Frontend.Console.Presentation uses Backend✕
- Connections
- 3 pairs of types, where a type in Frontend.Console.Presentation uses a type in Backend.
- The types involved
GWallet.Frontend.Console.Presentation.Presentation→GWallet.Backend.CurrencyGWallet.Frontend.Console.Presentation.Presentation→GWallet.Backend.IBlockchainFeeInfoGWallet.Frontend.Console.Presentation.Presentation→GWallet.Backend.ITransactionDetails
- Direction
- Frontend.Console.Presentation uses Backend, so a change to Backend can break Frontend.Console.Presentation, while a change to Frontend.Console.Presentation can't break Backend.
- Position
- Below the diagonal: Frontend.Console.Presentation uses a module listed above it, which is the healthy direction.
28→1 Frontend.Console.Program uses Backend✕
- Connections
- 7 pairs of types, where a type in Frontend.Console.Program uses a type in Backend.
- The types involved
GWallet.Frontend.Console.Program.Program→GWallet.Backend.CurrencyGWallet.Frontend.Console.Program.Program→GWallet.Backend.IAccountGWallet.Frontend.Console.Program.Program→GWallet.Backend.IBlockchainFeeInfoGWallet.Frontend.Console.Program.Program→GWallet.Backend.NormalAccountGWallet.Frontend.Console.Program.Program→GWallet.Backend.SignedTransaction`1GWallet.Frontend.Console.Program.Program→GWallet.Backend.TransferAmountGWallet.Frontend.Console.Program.Program→GWallet.Backend.UnsignedTransaction`1
- Direction
- Frontend.Console.Program uses Backend, so a change to Backend can break Frontend.Console.Program, while a change to Frontend.Console.Program can't break Backend.
- Position
- Below the diagonal: Frontend.Console.Program uses a module listed above it, which is the healthy direction.
29→1 Backend.Ether.Account uses Backend✕
- Connections
- 13 pairs of types, where a type in Backend.Ether.Account uses a type in Backend.
- The types involved
GWallet.Backend.Ether.Account.Account→GWallet.Backend.AccountKindGWallet.Backend.Ether.Account.Account→GWallet.Backend.ArchivedAccountGWallet.Backend.Ether.Account.Account→GWallet.Backend.CurrencyGWallet.Backend.Ether.Account.Account→GWallet.Backend.CustomCancelSourceGWallet.Backend.Ether.Account.Account→GWallet.Backend.FileRepresentationGWallet.Backend.Ether.Account.Account→GWallet.Backend.IAccountGWallet.Backend.Ether.Account.Account→GWallet.Backend.ITransactionDetailsGWallet.Backend.Ether.Account.Account→GWallet.Backend.NormalAccountGWallet.Backend.Ether.Account.Account→GWallet.Backend.ReadOnlyAccountGWallet.Backend.Ether.Account.Account→GWallet.Backend.ServerSelectionModeGWallet.Backend.Ether.Account.Account→GWallet.Backend.SignedTransaction`1GWallet.Backend.Ether.Account.Account→GWallet.Backend.TransferAmountGWallet.Backend.Ether.Account.Account→GWallet.Backend.UnsignedTransactionProposal
- Direction
- Backend.Ether.Account uses Backend, so a change to Backend can break Backend.Ether.Account, while a change to Backend.Ether.Account can't break Backend.
- Position
- Below the diagonal: Backend.Ether.Account uses a module listed above it, which is the healthy direction.
29→16 Backend.Ether.Account uses Backend.Ether✕
- Connections
- 2 pairs of types, where a type in Backend.Ether.Account uses a type in Backend.Ether.
- The types involved
GWallet.Backend.Ether.Account.Account→GWallet.Backend.Ether.BalanceTypeGWallet.Backend.Ether.Account.Account→GWallet.Backend.Ether.TransactionMetadata
- Direction
- Backend.Ether.Account uses Backend.Ether, so a change to Backend.Ether can break Backend.Ether.Account, while a change to Backend.Ether.Account can't break Backend.Ether.
- Position
- Below the diagonal: Backend.Ether.Account uses a module listed above it, which is the healthy direction.
30→1 Backend.Ether.Server uses Backend✕
- Connections
- 10 pairs of types, where a type in Backend.Ether.Server uses a type in Backend.
- The types involved
GWallet.Backend.Ether.Server.Server→GWallet.Backend.ConsistencySettings`1GWallet.Backend.Ether.Server.Server→GWallet.Backend.CurrencyGWallet.Backend.Ether.Server.Server→GWallet.Backend.CustomCancelSourceGWallet.Backend.Ether.Server.Server→GWallet.Backend.FaultTolerantParallelClientSettings`1GWallet.Backend.Ether.Server.Server→GWallet.Backend.FaultTolerantParallelClient`2GWallet.Backend.Ether.Server.Server→GWallet.Backend.IAccountGWallet.Backend.Ether.Server.Server→GWallet.Backend.ServerDetailsGWallet.Backend.Ether.Server.Server→GWallet.Backend.ServerDiscardedExceptionGWallet.Backend.Ether.Server.Server→GWallet.Backend.ServerSelectionModeGWallet.Backend.Ether.Server.Server→GWallet.Backend.Server`2
- Direction
- Backend.Ether.Server uses Backend, so a change to Backend can break Backend.Ether.Server, while a change to Backend.Ether.Server can't break Backend.
- Position
- Below the diagonal: Backend.Ether.Server uses a module listed above it, which is the healthy direction.
30→16 Backend.Ether.Server uses Backend.Ether✕
- Connections
- 3 pairs of types, where a type in Backend.Ether.Server uses a type in Backend.Ether.
- The types involved
GWallet.Backend.Ether.Server.Server→GWallet.Backend.Ether.BalanceTypeGWallet.Backend.Ether.Server.Server→GWallet.Backend.Ether.SomeWeb3GWallet.Backend.Ether.Server.Server→GWallet.Backend.Ether.TransactionStatusDetails
- Direction
- Backend.Ether.Server uses Backend.Ether, so a change to Backend.Ether can break Backend.Ether.Server, while a change to Backend.Ether.Server can't break Backend.Ether.
- Position
- Below the diagonal: Backend.Ether.Server uses a module listed above it, which is the healthy direction.
31→1 Backend.UtxoCoin.Account uses Backend✕
- Connections
- 12 pairs of types, where a type in Backend.UtxoCoin.Account uses a type in Backend.
- The types involved
GWallet.Backend.UtxoCoin.Account.Account→GWallet.Backend.AccountKindGWallet.Backend.UtxoCoin.Account.Account→GWallet.Backend.CurrencyGWallet.Backend.UtxoCoin.Account.Account→GWallet.Backend.CustomCancelSourceGWallet.Backend.UtxoCoin.Account.Account→GWallet.Backend.FileRepresentationGWallet.Backend.UtxoCoin.Account.Account→GWallet.Backend.IAccountGWallet.Backend.UtxoCoin.Account.Account→GWallet.Backend.ITransactionDetailsGWallet.Backend.UtxoCoin.Account.Account→GWallet.Backend.NormalAccountGWallet.Backend.UtxoCoin.Account.Account→GWallet.Backend.ReadOnlyAccountGWallet.Backend.UtxoCoin.Account.Account→GWallet.Backend.ServerSelectionModeGWallet.Backend.UtxoCoin.Account.Account→GWallet.Backend.SignedTransaction`1GWallet.Backend.UtxoCoin.Account.Account→GWallet.Backend.TransferAmountGWallet.Backend.UtxoCoin.Account.Account→GWallet.Backend.UnsignedTransactionProposal
- Direction
- Backend.UtxoCoin.Account uses Backend, so a change to Backend can break Backend.UtxoCoin.Account, while a change to Backend.UtxoCoin.Account can't break Backend.
- Position
- Below the diagonal: Backend.UtxoCoin.Account uses a module listed above it, which is the healthy direction.
31→25 Backend.UtxoCoin.Account uses Backend.UtxoCoin✕
- Connections
- 7 pairs of types, where a type in Backend.UtxoCoin.Account uses a type in Backend.UtxoCoin.
- The types involved
GWallet.Backend.UtxoCoin.Account.Account→GWallet.Backend.UtxoCoin.ArchivedUtxoAccountGWallet.Backend.UtxoCoin.Account.Account→GWallet.Backend.UtxoCoin.BlockchainScriptHashGetBalanceInnerResultGWallet.Backend.UtxoCoin.Account.Account→GWallet.Backend.UtxoCoin.IUtxoAccountGWallet.Backend.UtxoCoin.Account.Account→GWallet.Backend.UtxoCoin.NormalUtxoAccountGWallet.Backend.UtxoCoin.Account.Account→GWallet.Backend.UtxoCoin.ReadOnlyUtxoAccountGWallet.Backend.UtxoCoin.Account.Account→GWallet.Backend.UtxoCoin.TransactionInputOutpointInfoGWallet.Backend.UtxoCoin.Account.Account→GWallet.Backend.UtxoCoin.TransactionMetadata
- Direction
- Backend.UtxoCoin.Account uses Backend.UtxoCoin, so a change to Backend.UtxoCoin can break Backend.UtxoCoin.Account, while a change to Backend.UtxoCoin.Account can't break Backend.UtxoCoin.
- Position
- Below the diagonal: Backend.UtxoCoin.Account uses a module listed above it, which is the healthy direction.
32→1 Backend.UtxoCoin.ElectrumClient uses Backend✕
- Connections
- 1 pair of types, where a type in Backend.UtxoCoin.ElectrumClient uses a type in Backend.
- The types involved
GWallet.Backend.UtxoCoin.ElectrumClient.ElectrumClient→GWallet.Backend.ServerDetails
- Direction
- Backend.UtxoCoin.ElectrumClient uses Backend, so a change to Backend can break Backend.UtxoCoin.ElectrumClient, while a change to Backend.UtxoCoin.ElectrumClient can't break Backend.
- Position
- Below the diagonal: Backend.UtxoCoin.ElectrumClient uses a module listed above it, which is the healthy direction.
32→25 Backend.UtxoCoin.ElectrumClient uses Backend.UtxoCoin✕
- Connections
- 3 pairs of types, where a type in Backend.UtxoCoin.ElectrumClient uses a type in Backend.UtxoCoin.
- The types involved
GWallet.Backend.UtxoCoin.ElectrumClient.ElectrumClient→GWallet.Backend.UtxoCoin.BlockchainScriptHashGetBalanceInnerResultGWallet.Backend.UtxoCoin.ElectrumClient.ElectrumClient→GWallet.Backend.UtxoCoin.BlockchainScriptHashListUnspentInnerResultGWallet.Backend.UtxoCoin.ElectrumClient.ElectrumClient→GWallet.Backend.UtxoCoin.StratumClient
- Direction
- Backend.UtxoCoin.ElectrumClient uses Backend.UtxoCoin, so a change to Backend.UtxoCoin can break Backend.UtxoCoin.ElectrumClient, while a change to Backend.UtxoCoin.ElectrumClient can't break Backend.UtxoCoin.
- Position
- Below the diagonal: Backend.UtxoCoin.ElectrumClient uses a module listed above it, which is the healthy direction.
33→1 Backend.UtxoCoin.ElectrumServerSeedList uses Backend✕
- Connections
- 2 pairs of types, where a type in Backend.UtxoCoin.ElectrumServerSeedList uses a type in Backend.
- The types involved
GWallet.Backend.UtxoCoin.ElectrumServerSeedList.ElectrumServerSeedList→GWallet.Backend.CurrencyGWallet.Backend.UtxoCoin.ElectrumServerSeedList.ElectrumServerSeedList→GWallet.Backend.ServerDetails
- Direction
- Backend.UtxoCoin.ElectrumServerSeedList uses Backend, so a change to Backend can break Backend.UtxoCoin.ElectrumServerSeedList, while a change to Backend.UtxoCoin.ElectrumServerSeedList can't break Backend.
- Position
- Below the diagonal: Backend.UtxoCoin.ElectrumServerSeedList uses a module listed above it, which is the healthy direction.
33→25 Backend.UtxoCoin.ElectrumServerSeedList uses Backend.UtxoCoin✕
- Connections
- 1 pair of types, where a type in Backend.UtxoCoin.ElectrumServerSeedList uses a type in Backend.UtxoCoin.
- The types involved
GWallet.Backend.UtxoCoin.ElectrumServerSeedList.ElectrumServerSeedList→GWallet.Backend.UtxoCoin.ElectrumServer
- Direction
- Backend.UtxoCoin.ElectrumServerSeedList uses Backend.UtxoCoin, so a change to Backend.UtxoCoin can break Backend.UtxoCoin.ElectrumServerSeedList, while a change to Backend.UtxoCoin.ElectrumServerSeedList can't break Backend.UtxoCoin.
- Position
- Below the diagonal: Backend.UtxoCoin.ElectrumServerSeedList uses a module listed above it, which is the healthy direction.
34→1 Backend.UtxoCoin.Server uses Backend✕
- Connections
- 9 pairs of types, where a type in Backend.UtxoCoin.Server uses a type in Backend.
- The types involved
GWallet.Backend.UtxoCoin.Server.Server→GWallet.Backend.ConsistencySettings`1GWallet.Backend.UtxoCoin.Server.Server→GWallet.Backend.CurrencyGWallet.Backend.UtxoCoin.Server.Server→GWallet.Backend.CustomCancelSourceGWallet.Backend.UtxoCoin.Server.Server→GWallet.Backend.FaultTolerantParallelClientSettings`1GWallet.Backend.UtxoCoin.Server.Server→GWallet.Backend.FaultTolerantParallelClient`2GWallet.Backend.UtxoCoin.Server.Server→GWallet.Backend.ServerDetailsGWallet.Backend.UtxoCoin.Server.Server→GWallet.Backend.ServerDiscardedExceptionGWallet.Backend.UtxoCoin.Server.Server→GWallet.Backend.ServerSelectionModeGWallet.Backend.UtxoCoin.Server.Server→GWallet.Backend.Server`2
- Direction
- Backend.UtxoCoin.Server uses Backend, so a change to Backend can break Backend.UtxoCoin.Server, while a change to Backend.UtxoCoin.Server can't break Backend.
- Position
- Below the diagonal: Backend.UtxoCoin.Server uses a module listed above it, which is the healthy direction.
34→25 Backend.UtxoCoin.Server uses Backend.UtxoCoin✕
- Connections
- 1 pair of types, where a type in Backend.UtxoCoin.Server uses a type in Backend.UtxoCoin.
- The types involved
GWallet.Backend.UtxoCoin.Server.Server→GWallet.Backend.UtxoCoin.QuerySettings`1
- Direction
- Backend.UtxoCoin.Server uses Backend.UtxoCoin, so a change to Backend.UtxoCoin can break Backend.UtxoCoin.Server, while a change to Backend.UtxoCoin.Server can't break Backend.UtxoCoin.
- Position
- Below the diagonal: Backend.UtxoCoin.Server uses a module listed above it, which is the healthy direction.
35→1 Frontend.Console.UserInteraction uses Backend✕
- Connections
- 5 pairs of types, where a type in Frontend.Console.UserInteraction uses a type in Backend.
- The types involved
GWallet.Frontend.Console.UserInteraction.UserInteraction→GWallet.Backend.CurrencyGWallet.Frontend.Console.UserInteraction.UserInteraction→GWallet.Backend.IAccountGWallet.Frontend.Console.UserInteraction.UserInteraction→GWallet.Backend.IBlockchainFeeInfoGWallet.Frontend.Console.UserInteraction.UserInteraction→GWallet.Backend.MaybeCached`1GWallet.Frontend.Console.UserInteraction.UserInteraction→GWallet.Backend.TransferAmount
- Direction
- Frontend.Console.UserInteraction uses Backend, so a change to Backend can break Frontend.Console.UserInteraction, while a change to Frontend.Console.UserInteraction can't break Backend.
- Position
- Below the diagonal: Frontend.Console.UserInteraction uses a module listed above it, which is the healthy direction.
35→26 Frontend.Console.UserInteraction uses Frontend.Console✕
- Connections
- 2 pairs of types, where a type in Frontend.Console.UserInteraction uses a type in Frontend.Console.
- The types involved
GWallet.Frontend.Console.UserInteraction.UserInteraction→GWallet.Frontend.Console.OperationsGWallet.Frontend.Console.UserInteraction.UserInteraction→GWallet.Frontend.Console.WhichAccount
- Direction
- Frontend.Console.UserInteraction uses Frontend.Console, so a change to Frontend.Console can break Frontend.Console.UserInteraction, while a change to Frontend.Console.UserInteraction can't break Frontend.Console.
- Position
- Below the diagonal: Frontend.Console.UserInteraction uses a module listed above it, which is the healthy direction.
36→1 Frontend.XF.FrontendHelpers uses Backend✕
- Connections
- 5 pairs of types, where a type in Frontend.XF.FrontendHelpers uses a type in Backend.
- The types involved
GWallet.Frontend.XF.FrontendHelpers.FrontendHelpers→GWallet.Backend.CurrencyGWallet.Frontend.XF.FrontendHelpers.FrontendHelpers→GWallet.Backend.CustomCancelSourceGWallet.Frontend.XF.FrontendHelpers.FrontendHelpers→GWallet.Backend.IAccountGWallet.Frontend.XF.FrontendHelpers.FrontendHelpers→GWallet.Backend.MaybeCached`1GWallet.Frontend.XF.FrontendHelpers.FrontendHelpers→GWallet.Backend.ServerSelectionMode
- Direction
- Frontend.XF.FrontendHelpers uses Backend, so a change to Backend can break Frontend.XF.FrontendHelpers, while a change to Frontend.XF.FrontendHelpers can't break Backend.
- Position
- Below the diagonal: Frontend.XF.FrontendHelpers uses a module listed above it, which is the healthy direction.
36→25 Frontend.XF.FrontendHelpers uses Backend.UtxoCoin✕
- Connections
- 1 pair of types, where a type in Frontend.XF.FrontendHelpers uses a type in Backend.UtxoCoin.
- The types involved
GWallet.Frontend.XF.FrontendHelpers.FrontendHelpers→GWallet.Backend.UtxoCoin.SubUnit
- Direction
- Frontend.XF.FrontendHelpers uses Backend.UtxoCoin, so a change to Backend.UtxoCoin can break Frontend.XF.FrontendHelpers, while a change to Frontend.XF.FrontendHelpers can't break Backend.UtxoCoin.
- Position
- Below the diagonal: Frontend.XF.FrontendHelpers uses a module listed above it, which is the healthy direction.
36→37 Frontend.XF.FrontendHelpers uses Frontend.XF part of a loop✕
- Connections
- 4 pairs of types, where a type in Frontend.XF.FrontendHelpers uses a type in Frontend.XF.
- The types involved
GWallet.Frontend.XF.FrontendHelpers.FrontendHelpers→GWallet.Frontend.XF.BalanceSetGWallet.Frontend.XF.FrontendHelpers.FrontendHelpers→GWallet.Frontend.XF.BalanceStateGWallet.Frontend.XF.FrontendHelpers.FrontendHelpers→GWallet.Frontend.XF.BalanceWidgetsGWallet.Frontend.XF.FrontendHelpers.FrontendHelpers→GWallet.Frontend.XF.CurrencyImageSize
- Direction
- Frontend.XF.FrontendHelpers uses Frontend.XF, so a change to Frontend.XF can break Frontend.XF.FrontendHelpers, while a change to Frontend.XF.FrontendHelpers can't break Frontend.XF.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
37→1 Frontend.XF uses Backend✕
- Connections
- 17 pairs of types, where a type in Frontend.XF uses a type in Backend.
- The types involved
GWallet.Frontend.XF.BalanceSet→GWallet.Backend.IAccountGWallet.Frontend.XF.BalanceState→GWallet.Backend.MaybeCached`1GWallet.Frontend.XF.BalancesPage→GWallet.Backend.CustomCancelSourceGWallet.Frontend.XF.BalancesPage→GWallet.Backend.MaybeCached`1GWallet.Frontend.XF.ReceivePage→GWallet.Backend.IAccountGWallet.Frontend.XF.ReceivePage→GWallet.Backend.MaybeCached`1GWallet.Frontend.XF.SendPage→GWallet.Backend.CurrencyGWallet.Frontend.XF.SendPage→GWallet.Backend.IAccountGWallet.Frontend.XF.SendPage→GWallet.Backend.IBlockchainFeeInfoGWallet.Frontend.XF.SendPage→GWallet.Backend.NormalAccountGWallet.Frontend.XF.SendPage→GWallet.Backend.SignedTransaction`1GWallet.Frontend.XF.SendPage→GWallet.Backend.TransferAmountGWallet.Frontend.XF.SendPage→GWallet.Backend.UnsignedTransaction`1GWallet.Frontend.XF.TransactionInfo→GWallet.Backend.IBlockchainFeeInfoGWallet.Frontend.XF.TransactionInfo→GWallet.Backend.TransferAmountGWallet.Frontend.XF.TransactionProposal`1→GWallet.Backend.SignedTransaction`1GWallet.Frontend.XF.TransactionProposal`1→GWallet.Backend.UnsignedTransaction`1
- Direction
- Frontend.XF uses Backend, so a change to Backend can break Frontend.XF, while a change to Frontend.XF can't break Backend.
- Position
- Below the diagonal: Frontend.XF uses a module listed above it, which is the healthy direction.
37→36 Frontend.XF uses Frontend.XF.FrontendHelpers✕
- Connections
- 6 pairs of types, where a type in Frontend.XF uses a type in Frontend.XF.FrontendHelpers.
- The types involved
GWallet.Frontend.XF.BalancesPage→GWallet.Frontend.XF.FrontendHelpers.IGlobalAppStateGWallet.Frontend.XF.GlobalState→GWallet.Frontend.XF.FrontendHelpers.IGlobalAppStateGWallet.Frontend.XF.LoadingPage→GWallet.Frontend.XF.FrontendHelpers.IGlobalAppStateGWallet.Frontend.XF.SendPage→GWallet.Frontend.XF.FrontendHelpers.IAugmentablePayPageGWallet.Frontend.XF.WelcomePage→GWallet.Frontend.XF.FrontendHelpers.IGlobalAppStateGWallet.Frontend.XF.WelcomePage2→GWallet.Frontend.XF.FrontendHelpers.IGlobalAppState
- Direction
- Frontend.XF uses Frontend.XF.FrontendHelpers, so a change to Frontend.XF.FrontendHelpers can break Frontend.XF, while a change to Frontend.XF can't break Frontend.XF.FrontendHelpers.
- Position
- Below the diagonal: Frontend.XF uses a module listed above it, which is the healthy direction.
38→36 Frontend.XF.DummyPageConstructorHelper uses Frontend.XF.FrontendHelpers✕
- Connections
- 1 pair of types, where a type in Frontend.XF.DummyPageConstructorHelper uses a type in Frontend.XF.FrontendHelpers.
- The types involved
GWallet.Frontend.XF.DummyPageConstructorHelper.DummyPageConstructorHelper→GWallet.Frontend.XF.FrontendHelpers.IGlobalAppState
- Direction
- Frontend.XF.DummyPageConstructorHelper uses Frontend.XF.FrontendHelpers, so a change to Frontend.XF.FrontendHelpers can break Frontend.XF.DummyPageConstructorHelper, while a change to Frontend.XF.DummyPageConstructorHelper can't break Frontend.XF.FrontendHelpers.
- Position
- Below the diagonal: Frontend.XF.DummyPageConstructorHelper uses a module listed above it, which is the healthy direction.
39→37 Frontend.XF.Initialization uses Frontend.XF✕
- Connections
- 1 pair of types, where a type in Frontend.XF.Initialization uses a type in Frontend.XF.
- The types involved
GWallet.Frontend.XF.Initialization.Initialization→GWallet.Frontend.XF.GlobalState
- Direction
- Frontend.XF.Initialization uses Frontend.XF, so a change to Frontend.XF can break Frontend.XF.Initialization, while a change to Frontend.XF.Initialization can't break Frontend.XF.
- Position
- Below the diagonal: Frontend.XF.Initialization uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 36 | High / Critical |
| A07:2025 — Authentication Failures | 4 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with GWallet.Frontend.ConsoleApp-legacy.fsproj; Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing; Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with GWallet.Frontend.ConsoleApp-legacy.fsproj. | +5.0 pts | Low | ADR Quality |
| Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. | +4.7 pts | Low | REDACTED Scanning |
| Resolve the 6 NoWarnInCsproj finding(s) in Explicit Debt — start with GWallet.Frontend.XF.UWP.csproj (6). | +3.1 pts | Low | Explicit Debt |
| Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing. | +4.8 pts | Medium | Security & performance tooling |
| Resolve the 37 Orphaned file finding(s) in Knowledge Freshness — start with Account.fs, FaultTolerantParallelClient.fs, Caching.fs. | +4.7 pts | Medium | Knowledge Freshness |
| Resolve the 1 No test project references GWallet.Frontend.Console finding(s) in Code Coverage — start with GWallet.Frontend.Console.fsproj. | +1.7 pts | Low | Code Coverage |
| Resolve the 1 No test project references GWallet.Frontend.Console-legacy finding(s) in Code Coverage — start with GWallet.Frontend.Console-legacy.fsproj. | +1.7 pts | Low | Code Coverage |
| Resolve the 1 No test project references GWallet.Frontend.XF finding(s) in Code Coverage — start with GWallet.Frontend.XF.fsproj. | +1.7 pts | Low | Code Coverage |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.2 | Slop | Static Analysis (SAST): High: REDACTED |
| src/GWallet.Frontend.XF.UWP/GWallet.Frontend.XF.UWP.csproj | 3.8 | Slop | Explicit Debt: NoWarnInCsproj |
| src/GWallet.Frontend.ConsoleApp/GWallet.Frontend.ConsoleApp.fsproj | 6.4 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| src/GWallet.Frontend.Console/UserInteraction.fs | 7.0 | Mixed | Cyclomatic Complexity: UserInteraction.DisplayAccountStatuses (cyclomatic 28) |
| src/GWallet.Frontend.XF/SendPage.xaml.fs | 7.0 | Mixed | Cyclomatic Complexity: SendPage.OnSendOrSignButtonClicked (cyclomatic 21) |
| src/GWallet.Backend/Ether/EtherServer.fs | 7.1 | Mixed | Cyclomatic Complexity: Server.MaybeRethrowHttpRequestException (cyclomatic 23) |
| src/GWallet.Backend/Account.fs | 7.2 | Mixed | Cognitive Complexity: Account.GetArchivedAccountsWithPositiveBalance (cognitive 18) |
| REDACTED | 7.2 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
| src/GWallet.Frontend.XF.UWP/App.xaml.cs | 7.3 | Mixed | Explicit Debt: TodoComment |
| src/GWallet.Backend/UtxoCoin/UtxoCoinAccount.fs | 7.4 | Mixed | Cyclomatic Complexity: Account.GetSignedTransactionDetails (cyclomatic 16) |
| src/GWallet.Backend/Networking.fs | 7.8 | Mixed | Cyclomatic Complexity: Networking.FindExceptionToRethrow (cyclomatic 21) |
| src/GWallet.Backend/Ether/EtherAccount.fs | 7.8 | Mixed | Cyclomatic Complexity: Account.GetShowableBalanceAndImminentIncomingPayment (cyclomatic 16) |
| src/GWallet.Backend/Properties/AssemblyInfo.fs | 7.8 | Mixed | Code Duplication: Edited copies of one member (3 members, 24+ corresponding lines) |
| src/GWallet.Backend.Tests/GWallet.Backend.Tests.fsproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| src/GWallet.Frontend.ConsoleApp/GWallet.Frontend.ConsoleApp-legacy.fsproj | 8.0 | Near-clean | Code Coverage: No test project references GWallet.Frontend.ConsoleApp-legacy |
| src/GWallet.Backend/Config.fs | 8.5 | Near-clean | Cognitive Complexity: Config.Init (cognitive 21) |
| src/GWallet.Frontend.Console/Program.fs | 8.5 | Near-clean | Cognitive Complexity: Program.SignOffPayment (cognitive 20) |
| src/GWallet.Backend/UtxoCoin/ElectrumServer.fs | 8.5 | Near-clean | Cognitive Complexity: ElectrumServerSeedList.ExtractServerListFromWebPage (cognitive 17) |
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 36 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 36 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, 147 of 154 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
- 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. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: error: The imported project "/usr/share/dotnet/sdk/10.0.400/Xamarin/Mac/Xamarin.Mac.FSharp.targets" was not found. Confirm that the expression in the Import declaration "$(MSBuildExtensionsPath)/Xamarin/Mac/Xamarin.Mac.FSharp.targets", which evaluated to "/usr/share/dotnet/sdk/10.0.400/Xamarin/Mac/X….
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (21 contributor(s) across 3233 commit(s) sampled, automation and bot accounts excluded). One of them holds 95% of the history; the other 20 hold 0.2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D17 Explicit Debt — 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. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'src/GWallet.Backend/GWallet.Backend.fsproj' because the file extension '.fsproj' is not associated with a language.
- D17 Explicit Debt — 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. The 8 deducted marker(s) and the 2.9/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (10,419 lines, 99% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- 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. 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.
- 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 — 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. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D28 Secrets (history) — 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. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `src/GWallet.Frontend.XF.Mac/Assets.xcassets/Contents.json`, `src/GWallet.Frontend.XF.iOS/Assets.xcassets/Contents.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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. The solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan. 1 of 2 declared ecosystem(s) (nuget packages.config) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: a native UI project (src/GWallet.Frontend.XF.iOS/LaunchScreen.storyboard). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- 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").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- 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.
- 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.
- 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.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
8 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was UserInteraction.DisplayAccountStatuses at 28.
What to do
- Bring the 8 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with UserInteraction.DisplayAccountStatuses (cyclomatic 28), Server.MaybeRethrowHttpRequestException (cyclomatic 23), Networking.FindExceptionToRethrow (cyclomatic 21). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 8 together lifts Cyclomatic Complexity from 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
19 method(s) exceeded the cognitive complexity threshold of 15; the worst was Server.MaybeRethrowHttpRequestException at 42.
What to do
- Bring the 19 bodies over 15 down to 15 or less in Cognitive Complexity — start with Server.MaybeRethrowHttpRequestException (cognitive 42), SendPage.OnSendOrSignButtonClicked (cognitive 42), SendPage.UpdateEquivalentFiatLabel (cognitive 33). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 19 together lifts Cognitive Complexity from 7.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
7 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 7 FileTooLong finding(s) in God Classes — start with SendPage.xaml.fs, Account.fs, FaultTolerantParallelClient.fs. — One of this dimension's main actionable groups (7 warning-level).
D4 · Code Duplication
7 duplicated block group(s) detected. 1.7 % of the production lines (202 of 11,768) are in a reported copy. A further 2 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 2 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with Account.fs, ServerManager.fs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copies of one member (3 members, 24+ corresponding lines) finding(s) in Code Duplication — start with AssemblyInfo.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copies of one member (4 members, 13+ corresponding lines) finding(s) in Code Duplication — start with AssemblyInfo.fs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
1 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 15 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 10.0%, branch coverage 8.7%.
What to do
- Resolve the 1 No test project references GWallet.Frontend.XF finding(s) in Code Coverage — start with GWallet.Frontend.XF.fsproj. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 No test project references GWallet.Frontend.Console finding(s) in Code Coverage — start with GWallet.Frontend.Console.fsproj. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 No test project references GWallet.Frontend.Console-legacy finding(s) in Code Coverage — start with GWallet.Frontend.Console-legacy.fsproj. — One of this dimension's main actionable groups (1 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D13 · REDACTED Scanning
1 secret(s) detected. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
What to do
- Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D14 · License Compliance
0 of 580 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 19 direct `PackageReference`(s), and 486 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
8 deducted debt markers + unmeasured dead symbols across 150 LoC in the .NET projects (2.9/KLoC) → score 4.2. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (99% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What to do
- Resolve the 6 NoWarnInCsproj finding(s) in Explicit Debt — start with GWallet.Frontend.XF.UWP.csproj (6). — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 2 TodoComment finding(s) in Explicit Debt — start with App.xaml.cs (2). — One of this dimension's main actionable groups (2 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 3 document(s) read across 2 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 — start with GWallet.Frontend.ConsoleApp-legacy.fsproj. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
90 % of calls cross a namespace and 2 % go through an interface, but 89 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
2 finding(s): 0 critical, 2 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 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 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)
36 finding(s): 0 critical, 29 high, 7 medium, 0 low. 22 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6). — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 22 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (22 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (nuget packages.config). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (nuget packages.config), and the findings above are real and complete for them. nuget was not scanned (nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan), so this is not the whole dependency surface and the result is reported at reduced confidence.
D34 · Knowledge Freshness
40 of 40 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/GWallet.Frontend.XF/SendPage.xaml.fs. Counted over 40 of the 73 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 37 Orphaned file finding(s) in Knowledge Freshness — start with Account.fs, FaultTolerantParallelClient.fs, Caching.fs. — One of this dimension's main actionable groups (37 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with SendPage.xaml.fs, EtherServer.fs, UtxoCoinAccount.fs. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — 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
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 5 platform declaration(s) and 0 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.
What to do
- Resolve the 2 End-of-life runtime finding(s) in Platform End-of-Life — start with GWallet.Backend.Tests.fsproj, GWallet.Frontend.ConsoleApp.fsproj. — One of this dimension's main actionable groups (2 warning-level).
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX8 · Test isolation
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:5
- `src/GWallet.Backend.Tests/GWallet.Backend.Tests.fsproj` 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`. — src/GWallet.Backend.Tests/GWallet.Backend.Tests.fsproj:31
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — 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.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 59% | Adequate | Acceptable, with room to improve. |
| Architecture | 100% | Exemplary | Solid. |
| Maturity | 49% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 45% | Weak — gated by D8, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 54% | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). 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.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 76 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations detected
- AX6 Interface segregation — no public interfaces
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D10 Test Quality — ~4164 lines of test source are present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (11,768 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — This repository is one project, `GWallet.Frontend.XF.UWP` (150 LoC, 1 public types across 1 namespaces), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 51 value object(s); 5 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- 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
- IC1 Incompleteness & stubs — IC1 reached only 1% of this repository's production lines — fsharp (11,618 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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'.
- P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — coverage data present for 33 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- 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.
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X12 Unreachable branch — X12 reached only 1% of this repository's production lines — fsharp (11,618 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no async method does work a token could cancel
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — X23 reached only 1% of this repository's production lines — fsharp (11,618 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X5 Nullable reference types — no NRT-eligible projects
- 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 — 38 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- NoWarnInCsproj src/GWallet.Frontend.XF.UWP/GWallet.Frontend.XF.UWP.csproj:36
- NoWarnInCsproj src/GWallet.Frontend.XF.UWP/GWallet.Frontend.XF.UWP.csproj:48
- NoWarnInCsproj src/GWallet.Frontend.XF.UWP/GWallet.Frontend.XF.UWP.csproj:60
- NoWarnInCsproj src/GWallet.Frontend.XF.UWP/GWallet.Frontend.XF.UWP.csproj:72
- NoWarnInCsproj src/GWallet.Frontend.XF.UWP/GWallet.Frontend.XF.UWP.csproj:84
- NoWarnInCsproj src/GWallet.Frontend.XF.UWP/GWallet.Frontend.XF.UWP.csproj:96
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 66 finding(s)
- FileTooLong: GWallet.Frontend.XF/SendPage.xaml.fs src/GWallet.Frontend.XF/SendPage.xaml.fs
- FileTooLong: GWallet.Backend/Account.fs src/GWallet.Backend/Account.fs
- FileTooLong: GWallet.Backend/FaultTolerantParallelClient.fs src/GWallet.Backend/FaultTolerantParallelClient.fs
- FileTooLong: Ether/EtherServer.fs src/GWallet.Backend/Ether/EtherServer.fs
- FileTooLong: UtxoCoin/UtxoCoinAccount.fs src/GWallet.Backend/UtxoCoin/UtxoCoinAccount.fs
- FileTooLong: GWallet.Frontend.Console/UserInteraction.fs src/GWallet.Frontend.Console/UserInteraction.fs
- FileTooLong: GWallet.Backend/Caching.fs src/GWallet.Backend/Caching.fs
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment src/GWallet.Frontend.XF.UWP/App.xaml.cs:56
- TodoComment src/GWallet.Frontend.XF.UWP/App.xaml.cs:97
- Duplicated block (13 lines × 2) src/GWallet.Backend/Account.fs:705
- Duplicated block (13 lines × 2) src/GWallet.Backend/ServerManager.fs:30
- End-of-life runtime: .NET net6.0 src/GWallet.Backend.Tests/GWallet.Backend.Tests.fsproj:3
- End-of-life runtime: .NET net6.0 src/GWallet.Frontend.ConsoleApp/GWallet.Frontend.ConsoleApp.fsproj:4
- UserInteraction.DisplayAccountStatuses (cyclomatic 28) src/GWallet.Frontend.Console/UserInteraction.fs:275
- Server.MaybeRethrowHttpRequestException (cyclomatic 23) src/GWallet.Backend/Ether/EtherServer.fs:131
- Networking.FindExceptionToRethrow (cyclomatic 21) src/GWallet.Backend/Networking.fs:129
- SendPage.OnSendOrSignButtonClicked (cyclomatic 21) src/GWallet.Frontend.XF/SendPage.xaml.fs:756
- UserInteraction.AskAmount (cyclomatic 18) src/GWallet.Frontend.Console/UserInteraction.fs:539
- Account.GetShowableBalanceAndImminentIncomingPayment (cyclomatic 16) src/GWallet.Backend/Ether/EtherAccount.fs:81
- Account.GetSignedTransactionDetails (cyclomatic 16) src/GWallet.Backend/UtxoCoin/UtxoCoinAccount.fs:735
- UserInteraction.AskPublicAddress (cyclomatic 16) src/GWallet.Frontend.Console/UserInteraction.fs:409
- Server.MaybeRethrowHttpRequestException (cognitive 42) src/GWallet.Backend/Ether/EtherServer.fs:131
- SendPage.OnSendOrSignButtonClicked (cognitive 42) src/GWallet.Frontend.XF/SendPage.xaml.fs:756
- SendPage.UpdateEquivalentFiatLabel (cognitive 33) src/GWallet.Frontend.XF/SendPage.xaml.fs:476
- UserInteraction.AskPublicAddress (cognitive 32) src/GWallet.Frontend.Console/UserInteraction.fs:409
- SendPage.ValidateAddress (cognitive 32) src/GWallet.Frontend.XF/SendPage.xaml.fs:314
- UserInteraction.DisplayAccountStatuses (cognitive 30) src/GWallet.Frontend.Console/UserInteraction.fs:275
- Account.GetSignedTransactionDetails (cognitive 28) src/GWallet.Backend/UtxoCoin/UtxoCoinAccount.fs:735
- Account.GetShowableBalanceAndImminentIncomingPayment (cognitive 27) src/GWallet.Backend/Ether/EtherAccount.fs:81
- UserInteraction.AskAmount (cognitive 24) src/GWallet.Frontend.Console/UserInteraction.fs:539
- Networking.FindExceptionToRethrow (cognitive 21) src/GWallet.Backend/Networking.fs:129
- Config.Init (cognitive 21) src/GWallet.Backend/Config.fs:181
- Program.SignOffPayment (cognitive 20) src/GWallet.Frontend.Console/Program.fs:108
- Server.MaybeRethrowWebException (cognitive 19) src/GWallet.Backend/Ether/EtherServer.fs:97
- Account.GetArchivedAccountsWithPositiveBalance (cognitive 18) src/GWallet.Backend/Account.fs:147
- Server.MaybeRethrowInnerRpcException (cognitive 17) src/GWallet.Backend/Ether/EtherServer.fs:285
- ElectrumServerSeedList.ExtractServerListFromWebPage (cognitive 17) src/GWallet.Backend/UtxoCoin/ElectrumServer.fs:54
- BalancesPage.ConfigureFiatAmountFrame (cognitive 17) src/GWallet.Frontend.XF/BalancesPage.xaml.fs:397
- Account.CheckValidPassword (cognitive 16) src/GWallet.Backend/Account.fs:321
- SendPage.OnCurrencySelectorTextChanged (cognitive 16) src/GWallet.Frontend.XF/SendPage.xaml.fs:220
- REDACTED
- Edited copies of one member (3 members, 24+ corresponding lines) src/GWallet.Backend/Properties/AssemblyInfo.fs:1
- Edited copies of one member (4 members, 13+ corresponding lines) src/GWallet.Frontend.XF.Gtk/Properties/AssemblyInfo.fs:1
- Duplicated block (10 lines × 2) src/GWallet.Frontend.XF/PairingFromPage.xaml.fs:50
- Duplicated block (9 lines × 2) src/GWallet.Backend/Ether/EtherExceptions.fs:68
- Duplicated block (8 lines × 2) src/GWallet.Frontend.XF/SendPage.xaml.fs:301
- Duplicated block (7 lines × 2) src/GWallet.Backend/WarpKey.fs:26
- Duplicated block (15 lines × 3) src/GWallet.Backend/Properties/AssemblyInfo.fs:4
- No test project references GWallet.Frontend.XF src/GWallet.Frontend.XF/GWallet.Frontend.XF.fsproj
- No test project references GWallet.Frontend.Console src/GWallet.Frontend.Console/GWallet.Frontend.Console.fsproj
- No test project references GWallet.Frontend.Console-legacy src/GWallet.Frontend.Console/GWallet.Frontend.Console-legacy.fsproj
- No test project references GWallet.Frontend.XF.Android src/GWallet.Frontend.XF.Android/GWallet.Frontend.XF.Android.fsproj
- No test project references GWallet.Frontend.XF.Mac src/GWallet.Frontend.XF.Mac/GWallet.Frontend.XF.Mac.fsproj
- No test project references GWallet.Frontend.XF.UWP src/GWallet.Frontend.XF.UWP/GWallet.Frontend.XF.UWP.csproj
- No test project references GWallet.Frontend.ConsoleApp src/GWallet.Frontend.ConsoleApp/GWallet.Frontend.ConsoleApp.fsproj
- No test project references GWallet.Frontend.ConsoleApp-legacy src/GWallet.Frontend.ConsoleApp/GWallet.Frontend.ConsoleApp-legacy.fsproj
- No test project references GWallet.Frontend.XF.Gtk src/GWallet.Frontend.XF.Gtk/GWallet.Frontend.XF.Gtk.fsproj
- No test project references GWallet.Frontend.XF.iOS src/GWallet.Frontend.XF.iOS/GWallet.Frontend.XF.iOS.fsproj
- NuGet dependencies are not locked
Minor — 50 finding(s)
- Orphaned file src/GWallet.Backend/Account.fs:1
- Orphaned file src/GWallet.Backend/FaultTolerantParallelClient.fs:1
- Orphaned file src/GWallet.Backend/Caching.fs:1
- Orphaned file src/GWallet.Backend/FiatValueEstimation.fs:1
- Orphaned file src/GWallet.Frontend.Console/UserInteraction.fs:1
- Orphaned file src/GWallet.Frontend.XF/BalancesPage.xaml.fs:1
- Orphaned file src/GWallet.Backend/Ether/EtherAccount.fs:1
- Orphaned file src/GWallet.Frontend.Console/Program.fs:1
- Orphaned file src/GWallet.Frontend.XF/FrontendHelpers.fs:1
- Orphaned file src/GWallet.Backend/UtxoCoin/StratumClient.fs:1
- Orphaned file src/GWallet.Backend/Marshalling.fs:1
- Orphaned file src/GWallet.Frontend.XF/WelcomePage.xaml.fs:1
- Orphaned file src/GWallet.Backend/Networking.fs:1
- Orphaned file src/GWallet.Backend/Config.fs:1
- Orphaned file src/GWallet.Frontend.XF/Controls/CircleChartView.fs:1
- Orphaned file src/GWallet.Backend/Server.fs:1
- Orphaned file src/GWallet.Backend/ServerManager.fs:1
- Orphaned file src/GWallet.Backend/UtxoCoin/ElectrumClient.fs:1
- Orphaned file REDACTED:1
- Orphaned file src/GWallet.Frontend.XF/ReceivePage.xaml.fs:1
- Orphaned file src/GWallet.Backend/UtxoCoin/ElectrumServer.fs:1
- Orphaned file src/GWallet.Frontend.XF/PairingToPage.xaml.fs:1
- Orphaned file src/GWallet.Backend/UtxoCoin/UtxoCoinServer.fs:1
- Orphaned file src/GWallet.Frontend.XF/LoadingPage.xaml.fs:1
- Orphaned file src/GWallet.Backend/JsonRpcTcpClient.fs:1
- Most significant orphaned file src/GWallet.Frontend.XF/SendPage.xaml.fs:1
- Most significant orphaned file src/GWallet.Backend/Ether/EtherServer.fs:1
- Most significant orphaned file src/GWallet.Backend/UtxoCoin/UtxoCoinAccount.fs:1
- No ADRs found src/GWallet.Frontend.ConsoleApp/GWallet.Frontend.ConsoleApp-legacy.fsproj:9
- REDACTED
- Dormant codebase
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:5
- No dependency-update automation src/GWallet.Backend.Tests/GWallet.Backend.Tests.fsproj:31
- No changelog
- Duplicated predicate src/GWallet.Frontend.XF/PairingFromPage.xaml.fs:48
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-b758445c39e84335be33566c6076215e/history.json --exit-code 0 --source . | 1 | 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-b758445c39e84335be33566c6076215e/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 36 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan | 0 | — |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-5b230496f7334cab86a42054626392c4 | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-5b230496f7334cab86a42054626392c4 | 0 | artifacts/raw/osv-scanner.json |