Executive summary
codingteam/emulsion falls short of our standard for production, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 55 out of 100 and is rated Adequate, and 22 of its 24 critical findings are security problems.
Accessibility, at 46, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 7 points. Structuring the pages would lift Accessibility itself, worth about 6 points. Raising Accessibility to 70 would lift the score to about 60.
Sixteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three settings leave the servers or containers unsafe, and two secrets can leak from the build pipeline. Pinning each tool to an exact version, correcting the unsafe settings and limiting each secret to its own step would close these risks. Updating the vulnerable packages would fix the package with a known security hole. The form field without a label needs a label.
The product code is 2,575 lines, about €5,200 to rebuild.
If Accessibility rose from 46 to 70, the lowest score rated Strong, the score would rise from 55 to about 60.
Fixed since the last survey: 1 finding
- A11y enforcement · Accessibility enforcement below the top rung Emulsion.MessageArchive.Frontend/package.json
Rebuild cost: about €5,200 · Estimate
| Cost to rebuild | €1,700 to €8,700, for 29 to 92 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 55. 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: 2,575 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 AutoGeneratedProgram | 2 EFCoreFSharp | 3 Emulsion.ContentProxy.Base58 | 4 Emulsion.ContentProxy.FileCacheModule | 5 Emulsion.ContentProxy.Proxy | 6 Emulsion.Database.Entities | 7 Emulsion.Database.Migrations | 8 Emulsion.Database.QueryableEx | 9 Emulsion.ExceptionUtils | 10 Emulsion.Lifetimes | 11 Emulsion.Messaging | 12 Emulsion.Telegram.Html | 13 Emulsion.Xmpp.SharpXmppHelper.Attributes | 14 Emulsion.Xmpp.SharpXmppHelper.Elements | 15 Emulsion.Xmpp.SharpXmppHelper.Namespaces | 16 Emulsion_MessageArchive_Frontend.app | 17 Emulsion.Database | 18 Emulsion.Messaging.MessageModule | 19 Emulsion.Messaging.MessageSender | 20 Emulsion.Messaging.MessageSystem | 21 Emulsion_MessageArchive_Frontend | 22 Emulsion | 23 Emulsion.ContentProxy.ContentStorage | 24 Emulsion.Database.DataStorage | 25 Emulsion.Settings | 26 Emulsion.ContentProxy | 27 Emulsion.Logging | 28 Emulsion.Program | 29 Emulsion.Telegram | 30 Emulsion.Telegram.Funogram | 31 Emulsion.Telegram.LinkGenerator | 32 Emulsion.Xmpp | 33 Emulsion.Telegram.Funogram.MessageConverter | 34 Emulsion.Web | 35 Emulsion.Web.WebServer | 36 Emulsion.Xmpp.SharpXmppHelper | 37 Emulsion.Xmpp.XmppClient | 38 Emulsion.Xmpp.EmulsionXmpp | 39 Emulsion.Xmpp.SharpXmppClient |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 AutoGeneratedProgram | |||||||||||||||||||||||||||||||||||||||
| 2 EFCoreFSharp | |||||||||||||||||||||||||||||||||||||||
| 3 Emulsion.ContentProxy.Base58 | |||||||||||||||||||||||||||||||||||||||
| 4 Emulsion.ContentProxy.FileCacheModule | |||||||||||||||||||||||||||||||||||||||
| 5 Emulsion.ContentProxy.Proxy | |||||||||||||||||||||||||||||||||||||||
| 6 Emulsion.Database.Entities | |||||||||||||||||||||||||||||||||||||||
| 7 Emulsion.Database.Migrations | |||||||||||||||||||||||||||||||||||||||
| 8 Emulsion.Database.QueryableEx | |||||||||||||||||||||||||||||||||||||||
| 9 Emulsion.ExceptionUtils | |||||||||||||||||||||||||||||||||||||||
| 10 Emulsion.Lifetimes | |||||||||||||||||||||||||||||||||||||||
| 11 Emulsion.Messaging | |||||||||||||||||||||||||||||||||||||||
| 12 Emulsion.Telegram.Html | |||||||||||||||||||||||||||||||||||||||
| 13 Emulsion.Xmpp.SharpXmppHelper.Attributes | |||||||||||||||||||||||||||||||||||||||
| 14 Emulsion.Xmpp.SharpXmppHelper.Elements | |||||||||||||||||||||||||||||||||||||||
| 15 Emulsion.Xmpp.SharpXmppHelper.Namespaces | |||||||||||||||||||||||||||||||||||||||
| 16 Emulsion_MessageArchive_Frontend.app | |||||||||||||||||||||||||||||||||||||||
| 17 Emulsion.Database | 2 | ||||||||||||||||||||||||||||||||||||||
| 18 Emulsion.Messaging.MessageModule | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 Emulsion.Messaging.MessageSender | 3 | ||||||||||||||||||||||||||||||||||||||
| 20 Emulsion.Messaging.MessageSystem | 3 | ||||||||||||||||||||||||||||||||||||||
| 21 Emulsion_MessageArchive_Frontend | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 Emulsion | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 23 Emulsion.ContentProxy.ContentStorage | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 Emulsion.Database.DataStorage | 2 | ||||||||||||||||||||||||||||||||||||||
| 25 Emulsion.Settings | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 Emulsion.ContentProxy | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 Emulsion.Logging | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 Emulsion.Program | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 Emulsion.Telegram | 1 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 30 Emulsion.Telegram.Funogram | 3 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 31 Emulsion.Telegram.LinkGenerator | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 Emulsion.Xmpp | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 Emulsion.Telegram.Funogram.MessageConverter | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 Emulsion.Web | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 35 Emulsion.Web.WebServer | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 36 Emulsion.Xmpp.SharpXmppHelper | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 Emulsion.Xmpp.XmppClient | 3 | ||||||||||||||||||||||||||||||||||||||
| 38 Emulsion.Xmpp.EmulsionXmpp | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 Emulsion.Xmpp.SharpXmppClient | 1 | 2 |
17→6 Emulsion.Database uses Emulsion.Database.Entities✕
- Connections
- 2 pairs of types, where a type in Emulsion.Database uses a type in Emulsion.Database.Entities.
- The types involved
Emulsion.Database.EmulsionDbContext→Emulsion.Database.Entities.ArchiveEntryEmulsion.Database.EmulsionDbContext→Emulsion.Database.Entities.TelegramContent
- Direction
- Emulsion.Database uses Emulsion.Database.Entities, so a change to Emulsion.Database.Entities can break Emulsion.Database, while a change to Emulsion.Database can't break Emulsion.Database.Entities.
- Position
- Below the diagonal: Emulsion.Database uses a module listed above it, which is the healthy direction.
18→11 Emulsion.Messaging.MessageModule uses Emulsion.Messaging✕
- Connections
- 1 pair of types, where a type in Emulsion.Messaging.MessageModule uses a type in Emulsion.Messaging.
- The types involved
Emulsion.Messaging.MessageModule.MessageModule→Emulsion.Messaging.Message
- Direction
- Emulsion.Messaging.MessageModule uses Emulsion.Messaging, so a change to Emulsion.Messaging can break Emulsion.Messaging.MessageModule, while a change to Emulsion.Messaging.MessageModule can't break Emulsion.Messaging.
- Position
- Below the diagonal: Emulsion.Messaging.MessageModule uses a module listed above it, which is the healthy direction.
19→11 Emulsion.Messaging.MessageSender uses Emulsion.Messaging✕
- Connections
- 3 pairs of types, where a type in Emulsion.Messaging.MessageSender uses a type in Emulsion.Messaging.
- The types involved
Emulsion.Messaging.MessageSender.Event→Emulsion.Messaging.OutgoingMessageEmulsion.Messaging.MessageSender.MessageSender→Emulsion.Messaging.OutgoingMessageEmulsion.Messaging.MessageSender.State→Emulsion.Messaging.OutgoingMessage
- Direction
- Emulsion.Messaging.MessageSender uses Emulsion.Messaging, so a change to Emulsion.Messaging can break Emulsion.Messaging.MessageSender, while a change to Emulsion.Messaging.MessageSender can't break Emulsion.Messaging.
- Position
- Below the diagonal: Emulsion.Messaging.MessageSender uses a module listed above it, which is the healthy direction.
20→11 Emulsion.Messaging.MessageSystem uses Emulsion.Messaging✕
- Connections
- 3 pairs of types, where a type in Emulsion.Messaging.MessageSystem uses a type in Emulsion.Messaging.
- The types involved
Emulsion.Messaging.MessageSystem.IMessageSystem→Emulsion.Messaging.OutgoingMessageEmulsion.Messaging.MessageSystem.MessageSystem→Emulsion.Messaging.OutgoingMessageEmulsion.Messaging.MessageSystem.MessageSystemBase→Emulsion.Messaging.OutgoingMessage
- Direction
- Emulsion.Messaging.MessageSystem uses Emulsion.Messaging, so a change to Emulsion.Messaging can break Emulsion.Messaging.MessageSystem, while a change to Emulsion.Messaging.MessageSystem can't break Emulsion.Messaging.
- Position
- Below the diagonal: Emulsion.Messaging.MessageSystem uses a module listed above it, which is the healthy direction.
21→16 Emulsion_MessageArchive_Frontend uses Emulsion_MessageArchive_Frontend.app✕
- Connections
- 1 pair of types, where a type in Emulsion_MessageArchive_Frontend uses a type in Emulsion_MessageArchive_Frontend.app.
- The types involved
Emulsion_MessageArchive_Frontend.app→Emulsion_MessageArchive_Frontend.app.LoadedPage
- Direction
- Emulsion_MessageArchive_Frontend uses Emulsion_MessageArchive_Frontend.app, so a change to Emulsion_MessageArchive_Frontend.app can break Emulsion_MessageArchive_Frontend, while a change to Emulsion_MessageArchive_Frontend can't break Emulsion_MessageArchive_Frontend.app.
- Position
- Below the diagonal: Emulsion_MessageArchive_Frontend uses a module listed above it, which is the healthy direction.
22→11 Emulsion uses Emulsion.Messaging✕
- Connections
- 3 pairs of types, where a type in Emulsion uses a type in Emulsion.Messaging.
- The types involved
Emulsion.IMessageArchive→Emulsion.Messaging.IncomingMessageEmulsion.MessageArchive→Emulsion.Messaging.IncomingMessageEmulsion.MessagingCore→Emulsion.Messaging.IncomingMessage
- Direction
- Emulsion uses Emulsion.Messaging, so a change to Emulsion.Messaging can break Emulsion, while a change to Emulsion can't break Emulsion.Messaging.
- Position
- Below the diagonal: Emulsion uses a module listed above it, which is the healthy direction.
22→17 Emulsion uses Emulsion.Database✕
- Connections
- 1 pair of types, where a type in Emulsion uses a type in Emulsion.Database.
- The types involved
Emulsion.MessageArchive→Emulsion.Database.DatabaseSettings
- Direction
- Emulsion uses Emulsion.Database, so a change to Emulsion.Database can break Emulsion, while a change to Emulsion can't break Emulsion.Database.
- Position
- Below the diagonal: Emulsion uses a module listed above it, which is the healthy direction.
22→20 Emulsion uses Emulsion.Messaging.MessageSystem✕
- Connections
- 1 pair of types, where a type in Emulsion uses a type in Emulsion.Messaging.MessageSystem.
- The types involved
Emulsion.MessagingCore→Emulsion.Messaging.MessageSystem.IMessageSystem
- Direction
- Emulsion uses Emulsion.Messaging.MessageSystem, so a change to Emulsion.Messaging.MessageSystem can break Emulsion, while a change to Emulsion can't break Emulsion.Messaging.MessageSystem.
- Position
- Below the diagonal: Emulsion uses a module listed above it, which is the healthy direction.
23→6 Emulsion.ContentProxy.ContentStorage uses Emulsion.Database.Entities✕
- Connections
- 1 pair of types, where a type in Emulsion.ContentProxy.ContentStorage uses a type in Emulsion.Database.Entities.
- The types involved
Emulsion.ContentProxy.ContentStorage.ContentStorage→Emulsion.Database.Entities.TelegramContent
- Direction
- Emulsion.ContentProxy.ContentStorage uses Emulsion.Database.Entities, so a change to Emulsion.Database.Entities can break Emulsion.ContentProxy.ContentStorage, while a change to Emulsion.ContentProxy.ContentStorage can't break Emulsion.Database.Entities.
- Position
- Below the diagonal: Emulsion.ContentProxy.ContentStorage uses a module listed above it, which is the healthy direction.
23→17 Emulsion.ContentProxy.ContentStorage uses Emulsion.Database✕
- Connections
- 1 pair of types, where a type in Emulsion.ContentProxy.ContentStorage uses a type in Emulsion.Database.
- The types involved
Emulsion.ContentProxy.ContentStorage.ContentStorage→Emulsion.Database.EmulsionDbContext
- Direction
- Emulsion.ContentProxy.ContentStorage uses Emulsion.Database, so a change to Emulsion.Database can break Emulsion.ContentProxy.ContentStorage, while a change to Emulsion.ContentProxy.ContentStorage can't break Emulsion.Database.
- Position
- Below the diagonal: Emulsion.ContentProxy.ContentStorage uses a module listed above it, which is the healthy direction.
24→17 Emulsion.Database.DataStorage uses Emulsion.Database✕
- Connections
- 2 pairs of types, where a type in Emulsion.Database.DataStorage uses a type in Emulsion.Database.
- The types involved
Emulsion.Database.DataStorage.DataStorage→Emulsion.Database.DatabaseSettingsEmulsion.Database.DataStorage.DataStorage→Emulsion.Database.EmulsionDbContext
- Direction
- Emulsion.Database.DataStorage uses Emulsion.Database, so a change to Emulsion.Database can break Emulsion.Database.DataStorage, while a change to Emulsion.Database.DataStorage can't break Emulsion.Database.
- Position
- Below the diagonal: Emulsion.Database.DataStorage uses a module listed above it, which is the healthy direction.
25→17 Emulsion.Settings uses Emulsion.Database✕
- Connections
- 1 pair of types, where a type in Emulsion.Settings uses a type in Emulsion.Database.
- The types involved
Emulsion.Settings.EmulsionSettings→Emulsion.Database.DatabaseSettings
- Direction
- Emulsion.Settings uses Emulsion.Database, so a change to Emulsion.Database can break Emulsion.Settings, while a change to Emulsion.Settings can't break Emulsion.Database.
- Position
- Below the diagonal: Emulsion.Settings uses a module listed above it, which is the healthy direction.
26→25 Emulsion.ContentProxy uses Emulsion.Settings✕
- Connections
- 1 pair of types, where a type in Emulsion.ContentProxy uses a type in Emulsion.Settings.
- The types involved
Emulsion.ContentProxy.FileCache→Emulsion.Settings.FileCacheSettings
- Direction
- Emulsion.ContentProxy uses Emulsion.Settings, so a change to Emulsion.Settings can break Emulsion.ContentProxy, while a change to Emulsion.ContentProxy can't break Emulsion.Settings.
- Position
- Below the diagonal: Emulsion.ContentProxy uses a module listed above it, which is the healthy direction.
27→25 Emulsion.Logging uses Emulsion.Settings✕
- Connections
- 1 pair of types, where a type in Emulsion.Logging uses a type in Emulsion.Settings.
- The types involved
Emulsion.Logging.Logging→Emulsion.Settings.LogSettings
- Direction
- Emulsion.Logging uses Emulsion.Settings, so a change to Emulsion.Settings can break Emulsion.Logging, while a change to Emulsion.Logging can't break Emulsion.Settings.
- Position
- Below the diagonal: Emulsion.Logging uses a module listed above it, which is the healthy direction.
28→17 Emulsion.Program uses Emulsion.Database✕
- Connections
- 1 pair of types, where a type in Emulsion.Program uses a type in Emulsion.Database.
- The types involved
Emulsion.Program.Program→Emulsion.Database.DatabaseSettings
- Direction
- Emulsion.Program uses Emulsion.Database, so a change to Emulsion.Database can break Emulsion.Program, while a change to Emulsion.Program can't break Emulsion.Database.
- Position
- Below the diagonal: Emulsion.Program uses a module listed above it, which is the healthy direction.
28→20 Emulsion.Program uses Emulsion.Messaging.MessageSystem✕
- Connections
- 2 pairs of types, where a type in Emulsion.Program uses a type in Emulsion.Messaging.MessageSystem.
- The types involved
Emulsion.Program.Program→Emulsion.Messaging.MessageSystem.IMessageSystemEmulsion.Program.Program→Emulsion.Messaging.MessageSystem.ServiceContext
- Direction
- Emulsion.Program uses Emulsion.Messaging.MessageSystem, so a change to Emulsion.Messaging.MessageSystem can break Emulsion.Program, while a change to Emulsion.Program can't break Emulsion.Messaging.MessageSystem.
- Position
- Below the diagonal: Emulsion.Program uses a module listed above it, which is the healthy direction.
28→25 Emulsion.Program uses Emulsion.Settings✕
- Connections
- 1 pair of types, where a type in Emulsion.Program uses a type in Emulsion.Settings.
- The types involved
Emulsion.Program.Program→Emulsion.Settings.EmulsionSettings
- Direction
- Emulsion.Program uses Emulsion.Settings, so a change to Emulsion.Settings can break Emulsion.Program, while a change to Emulsion.Program can't break Emulsion.Settings.
- Position
- Below the diagonal: Emulsion.Program uses a module listed above it, which is the healthy direction.
29→11 Emulsion.Telegram uses Emulsion.Messaging✕
- Connections
- 1 pair of types, where a type in Emulsion.Telegram uses a type in Emulsion.Messaging.
- The types involved
Emulsion.Telegram.Client→Emulsion.Messaging.OutgoingMessage
- Direction
- Emulsion.Telegram uses Emulsion.Messaging, so a change to Emulsion.Messaging can break Emulsion.Telegram, while a change to Emulsion.Telegram can't break Emulsion.Messaging.
- Position
- Below the diagonal: Emulsion.Telegram uses a module listed above it, which is the healthy direction.
29→17 Emulsion.Telegram uses Emulsion.Database✕
- Connections
- 1 pair of types, where a type in Emulsion.Telegram uses a type in Emulsion.Database.
- The types involved
Emulsion.Telegram.Client→Emulsion.Database.DatabaseSettings
- Direction
- Emulsion.Telegram uses Emulsion.Database, so a change to Emulsion.Database can break Emulsion.Telegram, while a change to Emulsion.Telegram can't break Emulsion.Database.
- Position
- Below the diagonal: Emulsion.Telegram uses a module listed above it, which is the healthy direction.
29→20 Emulsion.Telegram uses Emulsion.Messaging.MessageSystem✕
- Connections
- 2 pairs of types, where a type in Emulsion.Telegram uses a type in Emulsion.Messaging.MessageSystem.
- The types involved
Emulsion.Telegram.Client→Emulsion.Messaging.MessageSystem.MessageSystemBaseEmulsion.Telegram.Client→Emulsion.Messaging.MessageSystem.ServiceContext
- Direction
- Emulsion.Telegram uses Emulsion.Messaging.MessageSystem, so a change to Emulsion.Messaging.MessageSystem can break Emulsion.Telegram, while a change to Emulsion.Telegram can't break Emulsion.Messaging.MessageSystem.
- Position
- Below the diagonal: Emulsion.Telegram uses a module listed above it, which is the healthy direction.
29→25 Emulsion.Telegram uses Emulsion.Settings✕
- Connections
- 2 pairs of types, where a type in Emulsion.Telegram uses a type in Emulsion.Settings.
- The types involved
Emulsion.Telegram.Client→Emulsion.Settings.HostingSettingsEmulsion.Telegram.Client→Emulsion.Settings.TelegramSettings
- Direction
- Emulsion.Telegram uses Emulsion.Settings, so a change to Emulsion.Settings can break Emulsion.Telegram, while a change to Emulsion.Telegram can't break Emulsion.Settings.
- Position
- Below the diagonal: Emulsion.Telegram uses a module listed above it, which is the healthy direction.
30→11 Emulsion.Telegram.Funogram uses Emulsion.Messaging✕
- Connections
- 3 pairs of types, where a type in Emulsion.Telegram.Funogram uses a type in Emulsion.Messaging.
- The types involved
Emulsion.Telegram.Funogram.Funogram→Emulsion.Messaging.MessageEmulsion.Telegram.Funogram.Funogram→Emulsion.Messaging.OutgoingMessageEmulsion.Telegram.Funogram.ThreadMessage→Emulsion.Messaging.Message
- Direction
- Emulsion.Telegram.Funogram uses Emulsion.Messaging, so a change to Emulsion.Messaging can break Emulsion.Telegram.Funogram, while a change to Emulsion.Telegram.Funogram can't break Emulsion.Messaging.
- Position
- Below the diagonal: Emulsion.Telegram.Funogram uses a module listed above it, which is the healthy direction.
30→17 Emulsion.Telegram.Funogram uses Emulsion.Database✕
- Connections
- 1 pair of types, where a type in Emulsion.Telegram.Funogram uses a type in Emulsion.Database.
- The types involved
Emulsion.Telegram.Funogram.Funogram→Emulsion.Database.DatabaseSettings
- Direction
- Emulsion.Telegram.Funogram uses Emulsion.Database, so a change to Emulsion.Database can break Emulsion.Telegram.Funogram, while a change to Emulsion.Telegram.Funogram can't break Emulsion.Database.
- Position
- Below the diagonal: Emulsion.Telegram.Funogram uses a module listed above it, which is the healthy direction.
30→25 Emulsion.Telegram.Funogram uses Emulsion.Settings✕
- Connections
- 2 pairs of types, where a type in Emulsion.Telegram.Funogram uses a type in Emulsion.Settings.
- The types involved
Emulsion.Telegram.Funogram.Funogram→Emulsion.Settings.HostingSettingsEmulsion.Telegram.Funogram.Funogram→Emulsion.Settings.TelegramSettings
- Direction
- Emulsion.Telegram.Funogram uses Emulsion.Settings, so a change to Emulsion.Settings can break Emulsion.Telegram.Funogram, while a change to Emulsion.Telegram.Funogram can't break Emulsion.Settings.
- Position
- Below the diagonal: Emulsion.Telegram.Funogram uses a module listed above it, which is the healthy direction.
31→17 Emulsion.Telegram.LinkGenerator uses Emulsion.Database✕
- Connections
- 1 pair of types, where a type in Emulsion.Telegram.LinkGenerator uses a type in Emulsion.Database.
- The types involved
Emulsion.Telegram.LinkGenerator.LinkGenerator→Emulsion.Database.DatabaseSettings
- Direction
- Emulsion.Telegram.LinkGenerator uses Emulsion.Database, so a change to Emulsion.Database can break Emulsion.Telegram.LinkGenerator, while a change to Emulsion.Telegram.LinkGenerator can't break Emulsion.Database.
- Position
- Below the diagonal: Emulsion.Telegram.LinkGenerator uses a module listed above it, which is the healthy direction.
31→23 Emulsion.Telegram.LinkGenerator uses Emulsion.ContentProxy.ContentStorage✕
- Connections
- 1 pair of types, where a type in Emulsion.Telegram.LinkGenerator uses a type in Emulsion.ContentProxy.ContentStorage.
- The types involved
Emulsion.Telegram.LinkGenerator.LinkGenerator→Emulsion.ContentProxy.ContentStorage.MessageContentIdentity
- Direction
- Emulsion.Telegram.LinkGenerator uses Emulsion.ContentProxy.ContentStorage, so a change to Emulsion.ContentProxy.ContentStorage can break Emulsion.Telegram.LinkGenerator, while a change to Emulsion.Telegram.LinkGenerator can't break Emulsion.ContentProxy.ContentStorage.
- Position
- Below the diagonal: Emulsion.Telegram.LinkGenerator uses a module listed above it, which is the healthy direction.
31→25 Emulsion.Telegram.LinkGenerator uses Emulsion.Settings✕
- Connections
- 1 pair of types, where a type in Emulsion.Telegram.LinkGenerator uses a type in Emulsion.Settings.
- The types involved
Emulsion.Telegram.LinkGenerator.LinkGenerator→Emulsion.Settings.HostingSettings
- Direction
- Emulsion.Telegram.LinkGenerator uses Emulsion.Settings, so a change to Emulsion.Settings can break Emulsion.Telegram.LinkGenerator, while a change to Emulsion.Telegram.LinkGenerator can't break Emulsion.Settings.
- Position
- Below the diagonal: Emulsion.Telegram.LinkGenerator uses a module listed above it, which is the healthy direction.
32→11 Emulsion.Xmpp uses Emulsion.Messaging✕
- Connections
- 1 pair of types, where a type in Emulsion.Xmpp uses a type in Emulsion.Messaging.
- The types involved
Emulsion.Xmpp.XmppMessageSystem→Emulsion.Messaging.OutgoingMessage
- Direction
- Emulsion.Xmpp uses Emulsion.Messaging, so a change to Emulsion.Messaging can break Emulsion.Xmpp, while a change to Emulsion.Xmpp can't break Emulsion.Messaging.
- Position
- Below the diagonal: Emulsion.Xmpp uses a module listed above it, which is the healthy direction.
32→20 Emulsion.Xmpp uses Emulsion.Messaging.MessageSystem✕
- Connections
- 2 pairs of types, where a type in Emulsion.Xmpp uses a type in Emulsion.Messaging.MessageSystem.
- The types involved
Emulsion.Xmpp.XmppMessageSystem→Emulsion.Messaging.MessageSystem.MessageSystemBaseEmulsion.Xmpp.XmppMessageSystem→Emulsion.Messaging.MessageSystem.ServiceContext
- Direction
- Emulsion.Xmpp uses Emulsion.Messaging.MessageSystem, so a change to Emulsion.Messaging.MessageSystem can break Emulsion.Xmpp, while a change to Emulsion.Xmpp can't break Emulsion.Messaging.MessageSystem.
- Position
- Below the diagonal: Emulsion.Xmpp uses a module listed above it, which is the healthy direction.
32→25 Emulsion.Xmpp uses Emulsion.Settings✕
- Connections
- 1 pair of types, where a type in Emulsion.Xmpp uses a type in Emulsion.Settings.
- The types involved
Emulsion.Xmpp.XmppMessageSystem→Emulsion.Settings.XmppSettings
- Direction
- Emulsion.Xmpp uses Emulsion.Settings, so a change to Emulsion.Settings can break Emulsion.Xmpp, while a change to Emulsion.Xmpp can't break Emulsion.Settings.
- Position
- Below the diagonal: Emulsion.Xmpp uses a module listed above it, which is the healthy direction.
33→11 Emulsion.Telegram.Funogram.MessageConverter uses Emulsion.Messaging✕
- Connections
- 1 pair of types, where a type in Emulsion.Telegram.Funogram.MessageConverter uses a type in Emulsion.Messaging.
- The types involved
Emulsion.Telegram.Funogram.MessageConverter.MessageConverter→Emulsion.Messaging.Message
- Direction
- Emulsion.Telegram.Funogram.MessageConverter uses Emulsion.Messaging, so a change to Emulsion.Messaging can break Emulsion.Telegram.Funogram.MessageConverter, while a change to Emulsion.Telegram.Funogram.MessageConverter can't break Emulsion.Messaging.
- Position
- Below the diagonal: Emulsion.Telegram.Funogram.MessageConverter uses a module listed above it, which is the healthy direction.
33→30 Emulsion.Telegram.Funogram.MessageConverter uses Emulsion.Telegram.Funogram✕
- Connections
- 1 pair of types, where a type in Emulsion.Telegram.Funogram.MessageConverter uses a type in Emulsion.Telegram.Funogram.
- The types involved
Emulsion.Telegram.Funogram.MessageConverter.MessageConverter→Emulsion.Telegram.Funogram.ThreadMessage
- Direction
- Emulsion.Telegram.Funogram.MessageConverter uses Emulsion.Telegram.Funogram, so a change to Emulsion.Telegram.Funogram can break Emulsion.Telegram.Funogram.MessageConverter, while a change to Emulsion.Telegram.Funogram.MessageConverter can't break Emulsion.Telegram.Funogram.
- Position
- Below the diagonal: Emulsion.Telegram.Funogram.MessageConverter uses a module listed above it, which is the healthy direction.
33→31 Emulsion.Telegram.Funogram.MessageConverter uses Emulsion.Telegram.LinkGenerator✕
- Connections
- 1 pair of types, where a type in Emulsion.Telegram.Funogram.MessageConverter uses a type in Emulsion.Telegram.LinkGenerator.
- The types involved
Emulsion.Telegram.Funogram.MessageConverter.MessageConverter→Emulsion.Telegram.LinkGenerator.TelegramThreadLinks
- Direction
- Emulsion.Telegram.Funogram.MessageConverter uses Emulsion.Telegram.LinkGenerator, so a change to Emulsion.Telegram.LinkGenerator can break Emulsion.Telegram.Funogram.MessageConverter, while a change to Emulsion.Telegram.Funogram.MessageConverter can't break Emulsion.Telegram.LinkGenerator.
- Position
- Below the diagonal: Emulsion.Telegram.Funogram.MessageConverter uses a module listed above it, which is the healthy direction.
34→17 Emulsion.Web uses Emulsion.Database✕
- Connections
- 2 pairs of types, where a type in Emulsion.Web uses a type in Emulsion.Database.
- The types involved
Emulsion.Web.ContentController→Emulsion.Database.EmulsionDbContextEmulsion.Web.HistoryController→Emulsion.Database.EmulsionDbContext
- Direction
- Emulsion.Web uses Emulsion.Database, so a change to Emulsion.Database can break Emulsion.Web, while a change to Emulsion.Web can't break Emulsion.Database.
- Position
- Below the diagonal: Emulsion.Web uses a module listed above it, which is the healthy direction.
34→25 Emulsion.Web uses Emulsion.Settings✕
- Connections
- 1 pair of types, where a type in Emulsion.Web uses a type in Emulsion.Settings.
- The types involved
Emulsion.Web.ContentController→Emulsion.Settings.HostingSettings
- Direction
- Emulsion.Web uses Emulsion.Settings, so a change to Emulsion.Settings can break Emulsion.Web, while a change to Emulsion.Web can't break Emulsion.Settings.
- Position
- Below the diagonal: Emulsion.Web uses a module listed above it, which is the healthy direction.
34→26 Emulsion.Web uses Emulsion.ContentProxy✕
- Connections
- 1 pair of types, where a type in Emulsion.Web uses a type in Emulsion.ContentProxy.
- The types involved
Emulsion.Web.ContentController→Emulsion.ContentProxy.FileCache
- Direction
- Emulsion.Web uses Emulsion.ContentProxy, so a change to Emulsion.ContentProxy can break Emulsion.Web, while a change to Emulsion.Web can't break Emulsion.ContentProxy.
- Position
- Below the diagonal: Emulsion.Web uses a module listed above it, which is the healthy direction.
34→29 Emulsion.Web uses Emulsion.Telegram✕
- Connections
- 1 pair of types, where a type in Emulsion.Web uses a type in Emulsion.Telegram.
- The types involved
Emulsion.Web.ContentController→Emulsion.Telegram.ITelegramClient
- Direction
- Emulsion.Web uses Emulsion.Telegram, so a change to Emulsion.Telegram can break Emulsion.Web, while a change to Emulsion.Web can't break Emulsion.Telegram.
- Position
- Below the diagonal: Emulsion.Web uses a module listed above it, which is the healthy direction.
35→17 Emulsion.Web.WebServer uses Emulsion.Database✕
- Connections
- 1 pair of types, where a type in Emulsion.Web.WebServer uses a type in Emulsion.Database.
- The types involved
Emulsion.Web.WebServer.WebServer→Emulsion.Database.DatabaseSettings
- Direction
- Emulsion.Web.WebServer uses Emulsion.Database, so a change to Emulsion.Database can break Emulsion.Web.WebServer, while a change to Emulsion.Web.WebServer can't break Emulsion.Database.
- Position
- Below the diagonal: Emulsion.Web.WebServer uses a module listed above it, which is the healthy direction.
35→25 Emulsion.Web.WebServer uses Emulsion.Settings✕
- Connections
- 2 pairs of types, where a type in Emulsion.Web.WebServer uses a type in Emulsion.Settings.
- The types involved
Emulsion.Web.WebServer.WebServer→Emulsion.Settings.HostingSettingsEmulsion.Web.WebServer.WebServer→Emulsion.Settings.MessageArchiveSettings
- Direction
- Emulsion.Web.WebServer uses Emulsion.Settings, so a change to Emulsion.Settings can break Emulsion.Web.WebServer, while a change to Emulsion.Web.WebServer can't break Emulsion.Settings.
- Position
- Below the diagonal: Emulsion.Web.WebServer uses a module listed above it, which is the healthy direction.
35→26 Emulsion.Web.WebServer uses Emulsion.ContentProxy✕
- Connections
- 1 pair of types, where a type in Emulsion.Web.WebServer uses a type in Emulsion.ContentProxy.
- The types involved
Emulsion.Web.WebServer.WebServer→Emulsion.ContentProxy.FileCache
- Direction
- Emulsion.Web.WebServer uses Emulsion.ContentProxy, so a change to Emulsion.ContentProxy can break Emulsion.Web.WebServer, while a change to Emulsion.Web.WebServer can't break Emulsion.ContentProxy.
- Position
- Below the diagonal: Emulsion.Web.WebServer uses a module listed above it, which is the healthy direction.
35→29 Emulsion.Web.WebServer uses Emulsion.Telegram✕
- Connections
- 1 pair of types, where a type in Emulsion.Web.WebServer uses a type in Emulsion.Telegram.
- The types involved
Emulsion.Web.WebServer.WebServer→Emulsion.Telegram.ITelegramClient
- Direction
- Emulsion.Web.WebServer uses Emulsion.Telegram, so a change to Emulsion.Telegram can break Emulsion.Web.WebServer, while a change to Emulsion.Web.WebServer can't break Emulsion.Telegram.
- Position
- Below the diagonal: Emulsion.Web.WebServer uses a module listed above it, which is the healthy direction.
36→11 Emulsion.Xmpp.SharpXmppHelper uses Emulsion.Messaging✕
- Connections
- 1 pair of types, where a type in Emulsion.Xmpp.SharpXmppHelper uses a type in Emulsion.Messaging.
- The types involved
Emulsion.Xmpp.SharpXmppHelper.SharpXmppHelper→Emulsion.Messaging.Message
- Direction
- Emulsion.Xmpp.SharpXmppHelper uses Emulsion.Messaging, so a change to Emulsion.Messaging can break Emulsion.Xmpp.SharpXmppHelper, while a change to Emulsion.Xmpp.SharpXmppHelper can't break Emulsion.Messaging.
- Position
- Below the diagonal: Emulsion.Xmpp.SharpXmppHelper uses a module listed above it, which is the healthy direction.
36→32 Emulsion.Xmpp.SharpXmppHelper uses Emulsion.Xmpp✕
- Connections
- 1 pair of types, where a type in Emulsion.Xmpp.SharpXmppHelper uses a type in Emulsion.Xmpp.
- The types involved
Emulsion.Xmpp.SharpXmppHelper.SharpXmppHelper→Emulsion.Xmpp.Presence
- Direction
- Emulsion.Xmpp.SharpXmppHelper uses Emulsion.Xmpp, so a change to Emulsion.Xmpp can break Emulsion.Xmpp.SharpXmppHelper, while a change to Emulsion.Xmpp.SharpXmppHelper can't break Emulsion.Xmpp.
- Position
- Below the diagonal: Emulsion.Xmpp.SharpXmppHelper uses a module listed above it, which is the healthy direction.
37→32 Emulsion.Xmpp.XmppClient uses Emulsion.Xmpp✕
- Connections
- 3 pairs of types, where a type in Emulsion.Xmpp.XmppClient uses a type in Emulsion.Xmpp.
- The types involved
Emulsion.Xmpp.XmppClient.XmppClient→Emulsion.Xmpp.MessageDeliveryInfoEmulsion.Xmpp.XmppClient.XmppClient→Emulsion.Xmpp.MessageInfoEmulsion.Xmpp.XmppClient.XmppClient→Emulsion.Xmpp.RoomInfo
- Direction
- Emulsion.Xmpp.XmppClient uses Emulsion.Xmpp, so a change to Emulsion.Xmpp can break Emulsion.Xmpp.XmppClient, while a change to Emulsion.Xmpp.XmppClient can't break Emulsion.Xmpp.
- Position
- Below the diagonal: Emulsion.Xmpp.XmppClient uses a module listed above it, which is the healthy direction.
38→11 Emulsion.Xmpp.EmulsionXmpp uses Emulsion.Messaging✕
- Connections
- 1 pair of types, where a type in Emulsion.Xmpp.EmulsionXmpp uses a type in Emulsion.Messaging.
- The types involved
Emulsion.Xmpp.EmulsionXmpp.EmulsionXmpp→Emulsion.Messaging.Message
- Direction
- Emulsion.Xmpp.EmulsionXmpp uses Emulsion.Messaging, so a change to Emulsion.Messaging can break Emulsion.Xmpp.EmulsionXmpp, while a change to Emulsion.Xmpp.EmulsionXmpp can't break Emulsion.Messaging.
- Position
- Below the diagonal: Emulsion.Xmpp.EmulsionXmpp uses a module listed above it, which is the healthy direction.
38→25 Emulsion.Xmpp.EmulsionXmpp uses Emulsion.Settings✕
- Connections
- 1 pair of types, where a type in Emulsion.Xmpp.EmulsionXmpp uses a type in Emulsion.Settings.
- The types involved
Emulsion.Xmpp.EmulsionXmpp.EmulsionXmpp→Emulsion.Settings.XmppSettings
- Direction
- Emulsion.Xmpp.EmulsionXmpp uses Emulsion.Settings, so a change to Emulsion.Settings can break Emulsion.Xmpp.EmulsionXmpp, while a change to Emulsion.Xmpp.EmulsionXmpp can't break Emulsion.Settings.
- Position
- Below the diagonal: Emulsion.Xmpp.EmulsionXmpp uses a module listed above it, which is the healthy direction.
38→37 Emulsion.Xmpp.EmulsionXmpp uses Emulsion.Xmpp.XmppClient✕
- Connections
- 1 pair of types, where a type in Emulsion.Xmpp.EmulsionXmpp uses a type in Emulsion.Xmpp.XmppClient.
- The types involved
Emulsion.Xmpp.EmulsionXmpp.EmulsionXmpp→Emulsion.Xmpp.XmppClient.IXmppClient
- Direction
- Emulsion.Xmpp.EmulsionXmpp uses Emulsion.Xmpp.XmppClient, so a change to Emulsion.Xmpp.XmppClient can break Emulsion.Xmpp.EmulsionXmpp, while a change to Emulsion.Xmpp.EmulsionXmpp can't break Emulsion.Xmpp.XmppClient.
- Position
- Below the diagonal: Emulsion.Xmpp.EmulsionXmpp uses a module listed above it, which is the healthy direction.
39→25 Emulsion.Xmpp.SharpXmppClient uses Emulsion.Settings✕
- Connections
- 1 pair of types, where a type in Emulsion.Xmpp.SharpXmppClient uses a type in Emulsion.Settings.
- The types involved
Emulsion.Xmpp.SharpXmppClient.SharpXmppClient→Emulsion.Settings.XmppSettings
- Direction
- Emulsion.Xmpp.SharpXmppClient uses Emulsion.Settings, so a change to Emulsion.Settings can break Emulsion.Xmpp.SharpXmppClient, while a change to Emulsion.Xmpp.SharpXmppClient can't break Emulsion.Settings.
- Position
- Below the diagonal: Emulsion.Xmpp.SharpXmppClient uses a module listed above it, which is the healthy direction.
39→37 Emulsion.Xmpp.SharpXmppClient uses Emulsion.Xmpp.XmppClient✕
- Connections
- 2 pairs of types, where a type in Emulsion.Xmpp.SharpXmppClient uses a type in Emulsion.Xmpp.XmppClient.
- The types involved
Emulsion.Xmpp.SharpXmppClient.SharpXmppClient→Emulsion.Xmpp.XmppClient.IXmppClientEmulsion.Xmpp.SharpXmppClient.Wrapper→Emulsion.Xmpp.XmppClient.IXmppClient
- Direction
- Emulsion.Xmpp.SharpXmppClient uses Emulsion.Xmpp.XmppClient, so a change to Emulsion.Xmpp.XmppClient can break Emulsion.Xmpp.SharpXmppClient, while a change to Emulsion.Xmpp.SharpXmppClient can't break Emulsion.Xmpp.XmppClient.
- Position
- Below the diagonal: Emulsion.Xmpp.SharpXmppClient uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 18 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 9 | High / Critical |
| A02:2025 — Security Misconfiguration | 5 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Emulsion.fsproj; Resolve the 14 Orphaned file finding(s) in Knowledge Freshness — start with Funogram.fs, XmppClient.fs, FileCache.fs; Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Emulsion.fsproj. | +6.5 pts | Low | ADR Quality |
| Resolve the 14 Orphaned file finding(s) in Knowledge Freshness — start with Funogram.fs, XmppClient.fs, FileCache.fs. | +6.1 pts | Medium | Knowledge Freshness |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +5.6 pts | Medium | Page structure |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +5.1 pts | Medium | Forms & labels |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +4.9 pts | Medium | Architecture documentation |
| Resolve the 1 Banned license finding(s) in License Compliance — start with Emulsion.fsproj. | +1.4 pts | Low | License Compliance |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +1.9 pts | Medium | Documentation (README) |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +0.8 pts | Low | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| Emulsion/Emulsion.fsproj | 6.7 | Mixed | License Compliance: Banned license: SharpXMPP |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| Emulsion.Telegram/Funogram.fs | 8.5 | Near-clean | Cyclomatic Complexity: MessageConverter.getAuthoredMessageBodyText (cyclomatic 19) |
| Emulsion.Web/ContentController.fs | 8.5 | Near-clean | Cognitive Complexity: ContentController.Get (cognitive 25) |
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 41 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 — 41 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, 48 of 58 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the test suite could not be built/run in-image (commonly external-service dependencies — a database, a broker — we won't provision). To have it measured, make the suite runnable without them. For context only, test code is ≈ 100% of production LoC (2,698 test / 2,575 production) — a rough proxy, NOT a coverage measurement, so it is excluded from the score. You can widen what we reach: optional: make the suite runnable without a database, broker or other service we do not provision, and real coverage is measured on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
- 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: Emulsion.TestFramework/Emulsion.TestFramework.fsproj : error NU1605: Warning As Error: Detected package downgrade: FSharp.Core from 10.1.401 to 10.1.400. Reference the package directly from the project to select a different version. [/tmp/codehea….
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (4 contributor(s) across 742 commit(s) sampled, automation and bot accounts excluded). One of them holds 95% of the history; the other 3 hold 1.7% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- 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.
- 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. 2 of 3 declared ecosystem(s) (npm,osv) 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.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Microsoft.Extensions.DependencyInjection registered from F#, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — 9 | >>> && apt-get install -y nodejs \ 10 | >>> && rm -rf /var/lib/apt/lists/* 11 | -------------------- ERROR: failed to solve: process "/bin/sh -c curl -fsSL https://deb.nodesource.com/setup_18.x | bash - && apt-get install -y nodejs && rm -rf /var/lib/apt/lists/*" did not complete successfully: exit code: 100; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X14 Bypassable address classification — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X32 Type resolved by simple name across every loaded assembly — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MessageConverter.getAuthoredMessageBodyText at 19.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with MessageConverter.getAuthoredMessageBodyText (cyclomatic 19). — Refactoring it lifts Cyclomatic Complexity from 9.7 to about 10.0/10.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was ContentController.Get at 25.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with ContentController.Get (cognitive 25). — Refactoring it lifts Cognitive Complexity from 9.4 to about 10.0/10.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
0 duplicated block group(s) detected. 0.0 % of the production lines (0 of 2,575) are in a reported copy.
D5 · Coupling
9 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 9 classes have LCOM4 above 3.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
1 of 215 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 23 direct `PackageReference`(s), and 188 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. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance — start with Emulsion.fsproj. — One of this dimension's main actionable groups (1 issue-level).
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 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 Emulsion.fsproj. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 8 build units (MSBuild, npm) flagged as possibly oversized/incoherent.
D27 · Navigability
80 % of calls cross a namespace and 2 % go through an interface, but 39 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
18 finding(s): 0 critical, 18 high, 0 medium, 0 low. 16 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 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 16 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 (16 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), 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.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
5 finding(s): 0 critical, 3 high, 2 medium, 0 low.
What to do
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
14 of 15 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Emulsion.Telegram/Funogram.fs. Counted over 15 of the 47 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 14 Orphaned file finding(s) in Knowledge Freshness — start with Funogram.fs, XmppClient.fs, FileCache.fs. — One of this dimension's main actionable groups (14 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge 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.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 9 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.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
- This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — Emulsion.MessageArchive.Frontend/app.tsx:59
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it. — Emulsion.MessageArchive.Frontend/index.html:7
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- 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
P2 · Observability
What to do
- Add a health-check endpoint (ASP.NET Core's MapHealthChecks, or a /health route in your Giraffe/Suave app) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `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 3 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:13
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.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
PF3 · Async & latency hygiene
X23 · Unguarded diagnostic materialisation
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 98% | Checked 4 of 11 | Solid. |
| Architecture | 94% | Exemplary | Solid. |
| Maturity | 48% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 61% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 72% | Checked 5 of 11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 46% | Weak | Largest drag on the score — prioritise here. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 71 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AC6 Visual & motion safety — No styled element found in the parsed markup — AC6 not applicable here.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — no exported interface declares behaviour
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — 9 | >>> && apt-get install -y nodejs \ 10 | >>> && rm -rf /var/lib/apt/lists/* 11 | -------------------- ERROR: failed to solve: process "/bin/sh -c curl -fsSL https://deb.nodesource.com/setup_18.x | bash - && apt-get install -y nodejs && rm -rf /var/lib/apt/lists/*" did not complete successfully: exit code: 100; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~2698 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.
- D11 Test Reliability — Test reliability not measured — no test run produced results
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — 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
- 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
- D8 Code Coverage — Coverage not measured
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 27 value object(s); 2 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 — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — 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 — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- 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 — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 24 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <select> without a programmatic label Emulsion.MessageArchive.Frontend/app.tsx:59
- Banned license: SharpXMPP Emulsion/Emulsion.fsproj:38
- REDACTED
Serious — 10 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Page without a main landmark Emulsion.MessageArchive.Frontend/index.html:7
- MessageConverter.getAuthoredMessageBodyText (cyclomatic 19) Emulsion.Telegram/Funogram.fs:174
- ContentController.Get (cognitive 25) Emulsion.Web/ContentController.fs:37
- REDACTED
- NuGet dependencies are not locked
Minor — 24 finding(s)
- Orphaned file Emulsion.Telegram/Funogram.fs:1
- Orphaned file Emulsion/Xmpp/XmppClient.fs:1
- Orphaned file Emulsion.ContentProxy/FileCache.fs:1
- Orphaned file Emulsion.Telegram/LinkGenerator.fs:1
- Orphaned file Emulsion/Xmpp/SharpXmppHelper.fs:1
- Orphaned file Emulsion/Program.fs:1
- Orphaned file Emulsion/Xmpp/EmulsionXmpp.fs:1
- Orphaned file Emulsion.Settings/Settings.fs:1
- Orphaned file Emulsion.Messaging/MessageSender.fs:1
- Orphaned file Emulsion.Messaging/MessageSystem.fs:1
- Orphaned file Emulsion/Logging.fs:1
- Orphaned file Emulsion.Web/ContentController.fs:1
- Orphaned file Emulsion/Xmpp/SharpXmppClient.fs:1
- Orphaned file Emulsion/MessagingCore.fs:1
- No ADRs found Emulsion/Emulsion.fsproj:9
- Scattered collaborators
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:13
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-d81b2791d9ee433185a04def11b3f5fe/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d81b2791d9ee433185a04def11b3f5fe/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude Emulsion.Database/Migrations . | 18 | 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 | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 1 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 5 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |