Executive summary
sierra-db/kameo_es falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 55.5 out of 100 and is rated Adequate, and both of its critical findings are security problems in the packages it uses.
Production Readiness, at 37.1, is the weakest lens and counts most in the score. The best first step is adding an automated build and test pipeline, worth about 8.6 points. Recording design decisions comes next, worth about 6.8 points. Raising Production Readiness to 70 would lift the score to about 67.5.
Two known security holes in the packages the code depends on can be used by attackers. Updating the vulnerable packages would close this risk.
The product code is 5,305 lines, about €5,500 to rebuild.
If Production Readiness rose from 37.1 to 70, the lowest score rated Strong, the score would rise from 55.5 to about 67.5.
Rebuild cost: about €5,500 · Estimate
| Cost to rebuild | €1,800 to €9,200, for 30 to 97 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: 5,305 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 kameo_es.connection_pool | 2 kameo_es_core.stream_id | 3 kameo_es_macros | 4 kameo_es_macros.command_name | 5 kameo_es_macros.event_type | 6 kameo_es_core | 7 kameo_es | 8 kameo_es.command_service | 9 kameo_es.event_handler.mongodb_correlations | 10 kameo_es_core.test_utils | 11 kameo_es.event_handler | 12 kameo_es.transaction | 13 kameo_es.entity_actor | 14 kameo_es.event_handler.file | 15 kameo_es.event_handler.in_memory | 16 kameo_es.event_handler.mongodb | 17 kameo_es.event_handler.mongodb_bulk | 18 kameo_es.error | 19 kameo_es.event_handler.postgres | 20 kameo_es.event_handler.sqlite |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 kameo_es.connection_pool | ||||||||||||||||||||
| 2 kameo_es_core.stream_id | ||||||||||||||||||||
| 3 kameo_es_macros | ||||||||||||||||||||
| 4 kameo_es_macros.command_name | ||||||||||||||||||||
| 5 kameo_es_macros.event_type | ||||||||||||||||||||
| 6 kameo_es_core | 2 | |||||||||||||||||||
| 7 kameo_es | 1 | |||||||||||||||||||
| 8 kameo_es.command_service | 2 | 2 | 5 | |||||||||||||||||
| 9 kameo_es.event_handler.mongodb_correlations | 3 | |||||||||||||||||||
| 10 kameo_es_core.test_utils | 3 | |||||||||||||||||||
| 11 kameo_es.event_handler | 5 | 1 | ||||||||||||||||||
| 12 kameo_es.transaction | 1 | 1 | ||||||||||||||||||
| 13 kameo_es.entity_actor | 3 | 7 | 3 | 3 | ||||||||||||||||
| 14 kameo_es.event_handler.file | 1 | 1 | ||||||||||||||||||
| 15 kameo_es.event_handler.in_memory | 1 | 1 | ||||||||||||||||||
| 16 kameo_es.event_handler.mongodb | 1 | 1 | ||||||||||||||||||
| 17 kameo_es.event_handler.mongodb_bulk | 1 | 1 | ||||||||||||||||||
| 18 kameo_es.error | 1 | 1 | ||||||||||||||||||
| 19 kameo_es.event_handler.postgres | 4 | 2 | 1 | 1 | ||||||||||||||||
| 20 kameo_es.event_handler.sqlite | 4 | 1 | 1 | 1 |
6→2 kameo_es_core uses kameo_es_core.stream_id✕
- Connections
- 2 pairs of types, where a type in kameo_es_core uses a type in kameo_es_core.stream_id.
- The types involved
kameo_es_core.Event→kameo_es_core.stream_id.StreamIdkameo_es_core.EventCausation→kameo_es_core.stream_id.StreamId
- Direction
- kameo_es_core uses kameo_es_core.stream_id, so a change to kameo_es_core.stream_id can break kameo_es_core, while a change to kameo_es_core can't break kameo_es_core.stream_id.
- Position
- Below the diagonal: kameo_es_core uses a module listed above it, which is the healthy direction.
7→6 kameo_es uses kameo_es_core✕
- Connections
- 1 pair of types, where a type in kameo_es uses a type in kameo_es_core.
- The types involved
kameo_es.kameo_es$module→kameo_es_core.Event
- Direction
- kameo_es uses kameo_es_core, so a change to kameo_es_core can break kameo_es, while a change to kameo_es can't break kameo_es_core.
- Position
- Below the diagonal: kameo_es uses a module listed above it, which is the healthy direction.
8→1 kameo_es.command_service uses kameo_es.connection_pool✕
- Connections
- 2 pairs of types, where a type in kameo_es.command_service uses a type in kameo_es.connection_pool.
- The types involved
kameo_es.command_service.CommandService→kameo_es.connection_pool.ConnectionPoolkameo_es.command_service.CommandServiceActor→kameo_es.connection_pool.ConnectionPool
- Direction
- kameo_es.command_service uses kameo_es.connection_pool, so a change to kameo_es.connection_pool can break kameo_es.command_service, while a change to kameo_es.command_service can't break kameo_es.connection_pool.
- Position
- Below the diagonal: kameo_es.command_service uses a module listed above it, which is the healthy direction.
8→2 kameo_es.command_service uses kameo_es_core.stream_id✕
- Connections
- 2 pairs of types, where a type in kameo_es.command_service uses a type in kameo_es_core.stream_id.
- The types involved
kameo_es.command_service.CommandServiceActor→kameo_es_core.stream_id.StreamIdkameo_es.command_service.Execute→kameo_es_core.stream_id.StreamId
- Direction
- kameo_es.command_service uses kameo_es_core.stream_id, so a change to kameo_es_core.stream_id can break kameo_es.command_service, while a change to kameo_es.command_service can't break kameo_es_core.stream_id.
- Position
- Below the diagonal: kameo_es.command_service uses a module listed above it, which is the healthy direction.
8→6 kameo_es.command_service uses kameo_es_core✕
- Connections
- 5 pairs of types, where a type in kameo_es.command_service uses a type in kameo_es_core.
- The types involved
kameo_es.command_service.CommandServiceActor→kameo_es_core.Contextkameo_es.command_service.Execute→kameo_es_core.Eventkameo_es.command_service.Execute→kameo_es_core.EventCausationkameo_es.command_service.Execute→kameo_es_core.Metadatakameo_es.command_service.ExecuteMsg→kameo_es_core.Metadata
- Direction
- kameo_es.command_service uses kameo_es_core, so a change to kameo_es_core can break kameo_es.command_service, while a change to kameo_es.command_service can't break kameo_es_core.
- Position
- Below the diagonal: kameo_es.command_service uses a module listed above it, which is the healthy direction.
9→6 kameo_es.event_handler.mongodb_correlations uses kameo_es_core✕
- Connections
- 3 pairs of types, where a type in kameo_es.event_handler.mongodb_correlations uses a type in kameo_es_core.
- The types involved
kameo_es.event_handler.mongodb_correlations.Coordinator→kameo_es_core.Contextkameo_es.event_handler.mongodb_correlations.CorrelationWorker→kameo_es_core.Contextkameo_es.event_handler.mongodb_correlations.HandleEvent→kameo_es_core.Event
- Direction
- kameo_es.event_handler.mongodb_correlations uses kameo_es_core, so a change to kameo_es_core can break kameo_es.event_handler.mongodb_correlations, while a change to kameo_es.event_handler.mongodb_correlations can't break kameo_es_core.
- Position
- Below the diagonal: kameo_es.event_handler.mongodb_correlations uses a module listed above it, which is the healthy direction.
10→6 kameo_es_core.test_utils uses kameo_es_core✕
- Connections
- 3 pairs of types, where a type in kameo_es_core.test_utils uses a type in kameo_es_core.
- The types involved
kameo_es_core.test_utils.Given→kameo_es_core.Eventkameo_es_core.test_utils.GivenEntity→kameo_es_core.Applykameo_es_core.test_utils.GivenEntity→kameo_es_core.Entity
- Direction
- kameo_es_core.test_utils uses kameo_es_core, so a change to kameo_es_core can break kameo_es_core.test_utils, while a change to kameo_es_core.test_utils can't break kameo_es_core.
- Position
- Below the diagonal: kameo_es_core.test_utils uses a module listed above it, which is the healthy direction.
11→6 kameo_es.event_handler uses kameo_es_core✕
- Connections
- 5 pairs of types, where a type in kameo_es.event_handler uses a type in kameo_es_core.
- The types involved
kameo_es.event_handler.CompositeEventHandler→kameo_es_core.Eventkameo_es.event_handler.EntityEventHandler→kameo_es_core.Eventkameo_es.event_handler.EventHandler→kameo_es_core.Eventkameo_es.event_handler.EventProcessor→kameo_es_core.Eventkameo_es.event_handler.UnprocessedEvent→kameo_es_core.Event
- Direction
- kameo_es.event_handler uses kameo_es_core, so a change to kameo_es_core can break kameo_es.event_handler, while a change to kameo_es.event_handler can't break kameo_es_core.
- Position
- Below the diagonal: kameo_es.event_handler uses a module listed above it, which is the healthy direction.
11→7 kameo_es.event_handler uses kameo_es✕
- Connections
- 1 pair of types, where a type in kameo_es.event_handler uses a type in kameo_es.
- The types involved
kameo_es.event_handler.EventHandlerError→kameo_es.Error
- Direction
- kameo_es.event_handler uses kameo_es, so a change to kameo_es can break kameo_es.event_handler, while a change to kameo_es.event_handler can't break kameo_es.
- Position
- Below the diagonal: kameo_es.event_handler uses a module listed above it, which is the healthy direction.
12→2 kameo_es.transaction uses kameo_es_core.stream_id✕
- Connections
- 1 pair of types, where a type in kameo_es.transaction uses a type in kameo_es_core.stream_id.
- The types involved
kameo_es.transaction.Transaction→kameo_es_core.stream_id.StreamId
- Direction
- kameo_es.transaction uses kameo_es_core.stream_id, so a change to kameo_es_core.stream_id can break kameo_es.transaction, while a change to kameo_es.transaction can't break kameo_es_core.stream_id.
- Position
- Below the diagonal: kameo_es.transaction uses a module listed above it, which is the healthy direction.
12→8 kameo_es.transaction uses kameo_es.command_service✕
- Connections
- 1 pair of types, where a type in kameo_es.transaction uses a type in kameo_es.command_service.
- The types involved
kameo_es.transaction.Transaction→kameo_es.command_service.CommandService
- Direction
- kameo_es.transaction uses kameo_es.command_service, so a change to kameo_es.command_service can break kameo_es.transaction, while a change to kameo_es.transaction can't break kameo_es.command_service.
- Position
- Below the diagonal: kameo_es.transaction uses a module listed above it, which is the healthy direction.
13→2 kameo_es.entity_actor uses kameo_es_core.stream_id✕
- Connections
- 3 pairs of types, where a type in kameo_es.entity_actor uses a type in kameo_es_core.stream_id.
- The types involved
kameo_es.entity_actor.EntityActor→kameo_es_core.stream_id.StreamIdkameo_es.entity_actor.EntityActorState→kameo_es_core.stream_id.StreamIdkameo_es.entity_actor.EntityTransactionActor→kameo_es_core.stream_id.StreamId
- Direction
- kameo_es.entity_actor uses kameo_es_core.stream_id, so a change to kameo_es_core.stream_id can break kameo_es.entity_actor, while a change to kameo_es.entity_actor can't break kameo_es_core.stream_id.
- Position
- Below the diagonal: kameo_es.entity_actor uses a module listed above it, which is the healthy direction.
13→6 kameo_es.entity_actor uses kameo_es_core✕
- Connections
- 7 pairs of types, where a type in kameo_es.entity_actor uses a type in kameo_es_core.
- The types involved
kameo_es.entity_actor.EntityActor→kameo_es_core.Contextkameo_es.entity_actor.EntityActor→kameo_es_core.Eventkameo_es.entity_actor.EntityActor→kameo_es_core.Metadatakameo_es.entity_actor.EntityActorState→kameo_es_core.Eventkameo_es.entity_actor.EntityActorState→kameo_es_core.Metadatakameo_es.entity_actor.EntityTransactionActor→kameo_es_core.Contextkameo_es.entity_actor.Execute→kameo_es_core.Metadata
- Direction
- kameo_es.entity_actor uses kameo_es_core, so a change to kameo_es_core can break kameo_es.entity_actor, while a change to kameo_es.entity_actor can't break kameo_es_core.
- Position
- Below the diagonal: kameo_es.entity_actor uses a module listed above it, which is the healthy direction.
13→8 kameo_es.entity_actor uses kameo_es.command_service✕
- Connections
- 3 pairs of types, where a type in kameo_es.entity_actor uses a type in kameo_es.command_service.
- The types involved
kameo_es.entity_actor.EntityActor→kameo_es.command_service.BeginTransactionkameo_es.entity_actor.EntityActor→kameo_es.command_service.Executekameo_es.entity_actor.EntityTransactionActor→kameo_es.command_service.Execute
- Direction
- kameo_es.entity_actor uses kameo_es.command_service, so a change to kameo_es.command_service can break kameo_es.entity_actor, while a change to kameo_es.entity_actor can't break kameo_es.command_service.
- Position
- Below the diagonal: kameo_es.entity_actor uses a module listed above it, which is the healthy direction.
13→12 kameo_es.entity_actor uses kameo_es.transaction✕
- Connections
- 3 pairs of types, where a type in kameo_es.entity_actor uses a type in kameo_es.transaction.
- The types involved
kameo_es.entity_actor.EntityTransactionActor→kameo_es.transaction.AbortTransactionkameo_es.entity_actor.EntityTransactionActor→kameo_es.transaction.CommitTransactionkameo_es.entity_actor.EntityTransactionActor→kameo_es.transaction.ResetTransaction
- Direction
- kameo_es.entity_actor uses kameo_es.transaction, so a change to kameo_es.transaction can break kameo_es.entity_actor, while a change to kameo_es.entity_actor can't break kameo_es.transaction.
- Position
- Below the diagonal: kameo_es.entity_actor uses a module listed above it, which is the healthy direction.
14→6 kameo_es.event_handler.file uses kameo_es_core✕
- Connections
- 1 pair of types, where a type in kameo_es.event_handler.file uses a type in kameo_es_core.
- The types involved
kameo_es.event_handler.file.FileEventProcessor→kameo_es_core.Event
- Direction
- kameo_es.event_handler.file uses kameo_es_core, so a change to kameo_es_core can break kameo_es.event_handler.file, while a change to kameo_es.event_handler.file can't break kameo_es_core.
- Position
- Below the diagonal: kameo_es.event_handler.file uses a module listed above it, which is the healthy direction.
14→11 kameo_es.event_handler.file uses kameo_es.event_handler✕
- Connections
- 1 pair of types, where a type in kameo_es.event_handler.file uses a type in kameo_es.event_handler.
- The types involved
kameo_es.event_handler.file.FileEventProcessor→kameo_es.event_handler.EventProcessor
- Direction
- kameo_es.event_handler.file uses kameo_es.event_handler, so a change to kameo_es.event_handler can break kameo_es.event_handler.file, while a change to kameo_es.event_handler.file can't break kameo_es.event_handler.
- Position
- Below the diagonal: kameo_es.event_handler.file uses a module listed above it, which is the healthy direction.
15→6 kameo_es.event_handler.in_memory uses kameo_es_core✕
- Connections
- 1 pair of types, where a type in kameo_es.event_handler.in_memory uses a type in kameo_es_core.
- The types involved
kameo_es.event_handler.in_memory.InMemoryEventProcessor→kameo_es_core.Event
- Direction
- kameo_es.event_handler.in_memory uses kameo_es_core, so a change to kameo_es_core can break kameo_es.event_handler.in_memory, while a change to kameo_es.event_handler.in_memory can't break kameo_es_core.
- Position
- Below the diagonal: kameo_es.event_handler.in_memory uses a module listed above it, which is the healthy direction.
15→11 kameo_es.event_handler.in_memory uses kameo_es.event_handler✕
- Connections
- 1 pair of types, where a type in kameo_es.event_handler.in_memory uses a type in kameo_es.event_handler.
- The types involved
kameo_es.event_handler.in_memory.InMemoryEventProcessor→kameo_es.event_handler.EventProcessor
- Direction
- kameo_es.event_handler.in_memory uses kameo_es.event_handler, so a change to kameo_es.event_handler can break kameo_es.event_handler.in_memory, while a change to kameo_es.event_handler.in_memory can't break kameo_es.event_handler.
- Position
- Below the diagonal: kameo_es.event_handler.in_memory uses a module listed above it, which is the healthy direction.
16→6 kameo_es.event_handler.mongodb uses kameo_es_core✕
- Connections
- 1 pair of types, where a type in kameo_es.event_handler.mongodb uses a type in kameo_es_core.
- The types involved
kameo_es.event_handler.mongodb.MongoDBEventProcessor→kameo_es_core.Event
- Direction
- kameo_es.event_handler.mongodb uses kameo_es_core, so a change to kameo_es_core can break kameo_es.event_handler.mongodb, while a change to kameo_es.event_handler.mongodb can't break kameo_es_core.
- Position
- Below the diagonal: kameo_es.event_handler.mongodb uses a module listed above it, which is the healthy direction.
16→11 kameo_es.event_handler.mongodb uses kameo_es.event_handler✕
- Connections
- 1 pair of types, where a type in kameo_es.event_handler.mongodb uses a type in kameo_es.event_handler.
- The types involved
kameo_es.event_handler.mongodb.MongoDBEventProcessor→kameo_es.event_handler.EventProcessor
- Direction
- kameo_es.event_handler.mongodb uses kameo_es.event_handler, so a change to kameo_es.event_handler can break kameo_es.event_handler.mongodb, while a change to kameo_es.event_handler.mongodb can't break kameo_es.event_handler.
- Position
- Below the diagonal: kameo_es.event_handler.mongodb uses a module listed above it, which is the healthy direction.
17→6 kameo_es.event_handler.mongodb_bulk uses kameo_es_core✕
- Connections
- 1 pair of types, where a type in kameo_es.event_handler.mongodb_bulk uses a type in kameo_es_core.
- The types involved
kameo_es.event_handler.mongodb_bulk.MongoDBBulkEventProcessor→kameo_es_core.Event
- Direction
- kameo_es.event_handler.mongodb_bulk uses kameo_es_core, so a change to kameo_es_core can break kameo_es.event_handler.mongodb_bulk, while a change to kameo_es.event_handler.mongodb_bulk can't break kameo_es_core.
- Position
- Below the diagonal: kameo_es.event_handler.mongodb_bulk uses a module listed above it, which is the healthy direction.
17→11 kameo_es.event_handler.mongodb_bulk uses kameo_es.event_handler✕
- Connections
- 1 pair of types, where a type in kameo_es.event_handler.mongodb_bulk uses a type in kameo_es.event_handler.
- The types involved
kameo_es.event_handler.mongodb_bulk.MongoDBBulkEventProcessor→kameo_es.event_handler.EventProcessor
- Direction
- kameo_es.event_handler.mongodb_bulk uses kameo_es.event_handler, so a change to kameo_es.event_handler can break kameo_es.event_handler.mongodb_bulk, while a change to kameo_es.event_handler.mongodb_bulk can't break kameo_es.event_handler.
- Position
- Below the diagonal: kameo_es.event_handler.mongodb_bulk uses a module listed above it, which is the healthy direction.
18→2 kameo_es.error uses kameo_es_core.stream_id✕
- Connections
- 1 pair of types, where a type in kameo_es.error uses a type in kameo_es_core.stream_id.
- The types involved
kameo_es.error.ParsedStream→kameo_es_core.stream_id.StreamId
- Direction
- kameo_es.error uses kameo_es_core.stream_id, so a change to kameo_es_core.stream_id can break kameo_es.error, while a change to kameo_es.error can't break kameo_es_core.stream_id.
- Position
- Below the diagonal: kameo_es.error uses a module listed above it, which is the healthy direction.
18→13 kameo_es.error uses kameo_es.entity_actor✕
- Connections
- 1 pair of types, where a type in kameo_es.error uses a type in kameo_es.entity_actor.
- The types involved
kameo_es.error.ExecuteError→kameo_es.entity_actor.AppendEventsError
- Direction
- kameo_es.error uses kameo_es.entity_actor, so a change to kameo_es.entity_actor can break kameo_es.error, while a change to kameo_es.error can't break kameo_es.entity_actor.
- Position
- Below the diagonal: kameo_es.error uses a module listed above it, which is the healthy direction.
19→6 kameo_es.event_handler.postgres uses kameo_es_core✕
- Connections
- 4 pairs of types, where a type in kameo_es.event_handler.postgres uses a type in kameo_es_core.
- The types involved
kameo_es.event_handler.postgres.HandleEvent→kameo_es_core.Eventkameo_es.event_handler.postgres.PostgresProcessor→kameo_es_core.Contextkameo_es.event_handler.postgres.Worker→kameo_es_core.Contextkameo_es.event_handler.postgres.Worker→kameo_es_core.Event
- Direction
- kameo_es.event_handler.postgres uses kameo_es_core, so a change to kameo_es_core can break kameo_es.event_handler.postgres, while a change to kameo_es.event_handler.postgres can't break kameo_es_core.
- Position
- Below the diagonal: kameo_es.event_handler.postgres uses a module listed above it, which is the healthy direction.
19→9 kameo_es.event_handler.postgres uses kameo_es.event_handler.mongodb_correlations✕
- Connections
- 2 pairs of types, where a type in kameo_es.event_handler.postgres uses a type in kameo_es.event_handler.mongodb_correlations.
- The types involved
kameo_es.event_handler.postgres.PostgresProcessor→kameo_es.event_handler.mongodb_correlations.HandleEventkameo_es.event_handler.postgres.Worker→kameo_es.event_handler.mongodb_correlations.HandleEvent
- Direction
- kameo_es.event_handler.postgres uses kameo_es.event_handler.mongodb_correlations, so a change to kameo_es.event_handler.mongodb_correlations can break kameo_es.event_handler.postgres, while a change to kameo_es.event_handler.postgres can't break kameo_es.event_handler.mongodb_correlations.
- Position
- Below the diagonal: kameo_es.event_handler.postgres uses a module listed above it, which is the healthy direction.
19→12 kameo_es.event_handler.postgres uses kameo_es.transaction✕
- Connections
- 1 pair of types, where a type in kameo_es.event_handler.postgres uses a type in kameo_es.transaction.
- The types involved
kameo_es.event_handler.postgres.Worker→kameo_es.transaction.Transaction
- Direction
- kameo_es.event_handler.postgres uses kameo_es.transaction, so a change to kameo_es.transaction can break kameo_es.event_handler.postgres, while a change to kameo_es.event_handler.postgres can't break kameo_es.transaction.
- Position
- Below the diagonal: kameo_es.event_handler.postgres uses a module listed above it, which is the healthy direction.
19→17 kameo_es.event_handler.postgres uses kameo_es.event_handler.mongodb_bulk✕
- Connections
- 1 pair of types, where a type in kameo_es.event_handler.postgres uses a type in kameo_es.event_handler.mongodb_bulk.
- The types involved
kameo_es.event_handler.postgres.Worker→kameo_es.event_handler.mongodb_bulk.FlushReason
- Direction
- kameo_es.event_handler.postgres uses kameo_es.event_handler.mongodb_bulk, so a change to kameo_es.event_handler.mongodb_bulk can break kameo_es.event_handler.postgres, while a change to kameo_es.event_handler.postgres can't break kameo_es.event_handler.mongodb_bulk.
- Position
- Below the diagonal: kameo_es.event_handler.postgres uses a module listed above it, which is the healthy direction.
20→6 kameo_es.event_handler.sqlite uses kameo_es_core✕
- Connections
- 4 pairs of types, where a type in kameo_es.event_handler.sqlite uses a type in kameo_es_core.
- The types involved
kameo_es.event_handler.sqlite.HandleEvent→kameo_es_core.Eventkameo_es.event_handler.sqlite.SqliteProcessor→kameo_es_core.Eventkameo_es.event_handler.sqlite.Worker→kameo_es_core.Contextkameo_es.event_handler.sqlite.Worker→kameo_es_core.Event
- Direction
- kameo_es.event_handler.sqlite uses kameo_es_core, so a change to kameo_es_core can break kameo_es.event_handler.sqlite, while a change to kameo_es.event_handler.sqlite can't break kameo_es_core.
- Position
- Below the diagonal: kameo_es.event_handler.sqlite uses a module listed above it, which is the healthy direction.
20→9 kameo_es.event_handler.sqlite uses kameo_es.event_handler.mongodb_correlations✕
- Connections
- 1 pair of types, where a type in kameo_es.event_handler.sqlite uses a type in kameo_es.event_handler.mongodb_correlations.
- The types involved
kameo_es.event_handler.sqlite.Worker→kameo_es.event_handler.mongodb_correlations.HandleEvent
- Direction
- kameo_es.event_handler.sqlite uses kameo_es.event_handler.mongodb_correlations, so a change to kameo_es.event_handler.mongodb_correlations can break kameo_es.event_handler.sqlite, while a change to kameo_es.event_handler.sqlite can't break kameo_es.event_handler.mongodb_correlations.
- Position
- Below the diagonal: kameo_es.event_handler.sqlite uses a module listed above it, which is the healthy direction.
20→11 kameo_es.event_handler.sqlite uses kameo_es.event_handler✕
- Connections
- 1 pair of types, where a type in kameo_es.event_handler.sqlite uses a type in kameo_es.event_handler.
- The types involved
kameo_es.event_handler.sqlite.SqliteProcessor→kameo_es.event_handler.EventProcessor
- Direction
- kameo_es.event_handler.sqlite uses kameo_es.event_handler, so a change to kameo_es.event_handler can break kameo_es.event_handler.sqlite, while a change to kameo_es.event_handler.sqlite can't break kameo_es.event_handler.
- Position
- Below the diagonal: kameo_es.event_handler.sqlite uses a module listed above it, which is the healthy direction.
20→17 kameo_es.event_handler.sqlite uses kameo_es.event_handler.mongodb_bulk✕
- Connections
- 1 pair of types, where a type in kameo_es.event_handler.sqlite uses a type in kameo_es.event_handler.mongodb_bulk.
- The types involved
kameo_es.event_handler.sqlite.Worker→kameo_es.event_handler.mongodb_bulk.FlushReason
- Direction
- kameo_es.event_handler.sqlite uses kameo_es.event_handler.mongodb_bulk, so a change to kameo_es.event_handler.mongodb_bulk can break kameo_es.event_handler.sqlite, while a change to kameo_es.event_handler.sqlite can't break kameo_es.event_handler.mongodb_bulk.
- Position
- Below the diagonal: kameo_es.event_handler.sqlite uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 18 | High / Critical |
Roadmap
Top priorities: Add a CI workflow that builds and runs the test suite on every push/PR; 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; Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a CI workflow that builds and runs the test suite on every push/PR. | +8.6 pts | Medium | CI/CD gates |
| 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. | +6.8 pts | Medium | Architecture documentation |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +3.8 pts | Medium | Release Hygiene |
| Interpolated log message defeats structured logging | +2.6 pts | Medium | Structured logging |
| 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. | +2.3 pts | Medium | Documentation (README) |
| Each row is a forced `Option`/`Result` no guard on its path proves present. Handle the absent case where it arises rather than forcing it: `?` to hand it to the caller, `if let` / `match` / `let … else` to branch on it, `unwrap_or` / `unwrap_or_default` / `unwrap_or_else` where a default is right. Where the value genuinely cannot be absent, say so in a way a reader can check from the line: test it first (`if x.is_none() { return … }`), look the key up with `contains_key` or the index against `len()`, or construct the value so it cannot be absent. | +0.5 pts | Medium | Nullable reference types |
| Resolve the 3 FileTooLong finding(s) in God Classes — start with postgres.rs, entity_actor.rs, command_service.rs. | +0.7 pts | High | God Classes |
| Bring the 3 bodies over 15 down to 15 or less in Cognitive Complexity — start with CorrelationWorker::handle (cognitive 30), CommandService::transaction (cognitive 18), EntityActor::handle (cognitive 17). | +0.3 pts | High | Cognitive Complexity |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.6 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| src/event_handler/postgres.rs | 7.1 | Mixed | God Classes: FileTooLong: event_handler/postgres.rs |
| src/command_service.rs | 7.1 | Mixed | Cyclomatic Complexity: Execute::into_future (cyclomatic 16) |
| core/src/test_utils.rs | 7.4 | Mixed | Code Duplication: Edited copies of one member (3 members, 16+ corresponding lines) |
| src/entity_actor.rs | 7.8 | Mixed | Cognitive Complexity: EntityActor::handle (cognitive 17) |
| src/event_handler/file.rs | 7.8 | Mixed | Code Duplication: Edited copy of a member (11 corresponding lines) |
| src/event_handler/mongodb_correlations.rs | 8.5 | Near-clean | Cognitive Complexity: CorrelationWorker::handle (cognitive 30) |
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, 90 of 113 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- 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 Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 3 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 44 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D34 Knowledge Freshness — 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. Too few commits to judge knowledge freshness (44 commit(s) sampled).
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- ED5 Idempotency — 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 decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- 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 reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala, PHP, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala, PHP, Go, Swift, Erlang, F# or Visual Basic was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# and Visual Basic syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin, PHP, F# and Visual Basic source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- 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 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was Execute::into_future at 16.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with Execute::into_future (cyclomatic 16). — Refactoring it lifts Cyclomatic Complexity from 9.9 to about 10.0/10.
D2 · Cognitive Complexity
3 function(s) exceeded the cognitive complexity threshold of 15; the worst was CorrelationWorker::handle at 30.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cognitive Complexity — start with CorrelationWorker::handle (cognitive 30), CommandService::transaction (cognitive 18), EntityActor::handle (cognitive 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 9.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
3 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 3 FileTooLong finding(s) in God Classes — start with postgres.rs, entity_actor.rs, command_service.rs. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
8 duplicated block group(s) detected. 3.9 % of the production lines (207 of 5,305) are in a reported copy. A further 4 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 3 of the 12 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 2 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with command_service.rs, test_utils.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Near-duplicate member pair (40 shared lines) finding(s) in Code Duplication — start with postgres.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with file.rs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
3 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 2 of the 3 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
0 of 25 classes have LCOM4 above 3.
D12 · Dependency Hygiene
18 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 345 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT OR Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 5305 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D26 · Project Cohesion
0 of 3 build units (Cargo) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues.
D30 · Dependency Vulnerabilities
18 finding(s): 0 critical, 2 high, 16 medium, 0 low.
What to do
- Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 7 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (7). — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 7 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7). — One of this dimension's main actionable groups (7 warning-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P10 · Library API & versioning
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add cargo-audit / cargo-deny (or clippy) (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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.
- `Cargo.toml` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — Cargo.toml:5
What to do
- Run what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X4 · Structured logging
- `error!` at line 187 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/command_service.rs:187
- `error!` at line 380 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — src/entity_actor.rs:380, src/event_handler/postgres.rs:380
- `error!` at line 393 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/entity_actor.rs:393
- `warn!` at line 598 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/entity_actor.rs:598
- `warn!` at line 601 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/entity_actor.rs:601
- `trace!` at line 213 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/event_handler.rs:213
- `debug!` at line 279 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/event_handler.rs:279
- `info!` at line 208 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/event_handler/mongodb_bulk.rs:208
- `error!` at line 241 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/event_handler/mongodb_bulk.rs:241
- `error!` at line 207 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/event_handler/mongodb_correlations.rs:207
- `debug!` at line 355 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/event_handler/postgres.rs:355
- `info!` at line 408 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/event_handler/postgres.rs:408
- `info!` at line 424 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/event_handler/postgres.rs:424
- `error!` at line 440 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/event_handler/postgres.rs:440
- `info!` at line 468 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/event_handler/postgres.rs:468
- `info!` at line 505 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/event_handler/postgres.rs:505
- `error!` at line 683 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/event_handler/postgres.rs:683
- `error!` at line 709 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/event_handler/postgres.rs:709
- `debug!` at line 252 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/event_handler/sqlite.rs:252
- `info!` at line 322 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/event_handler/sqlite.rs:322
- `info!` at line 355 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/event_handler/sqlite.rs:355
- `error!` at line 419 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/event_handler/sqlite.rs:419
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- `NonZeroUsize::new(20_000)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `new_with_pool` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/command_service.rs:58
- `partition_key` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `transaction` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/command_service.rs:90
- `message.as_ref()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `transaction` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/command_service.rs:115
- `parse_stream_version_string(message.as_ref().unwrap())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `transaction` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/command_service.rs:115
- `self.transaction.lookup_entity(&stream_id)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `into_future` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/command_service.rs:544
- `actor_ref.downcast_ref::<ActorRef<EntityActor<E>>>().cloned()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `get_or_start_entity_actor` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/command_service.rs:631
- `message.as_ref()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `from_sierra_err` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/entity_actor.rs:694
- `parse_stream_version_string(message.as_ref().unwrap())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `from_sierra_err` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/entity_actor.rs:694
- `Regex::new(r"current stream version is (\S+) but expected (\S+) for partition key ([0-9a-fA-F-]+) and stream id (.+)")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `parse_stream_version_string` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/error.rs:88
- `self.tell(CommitTransaction).send().now_or_never()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `commit_transaction` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/transaction.rs:122
- `self.tell(ResetTransaction).send().now_or_never()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `reset_transaction` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/transaction.rs:126
- `self.tell(AbortTransaction).send().now_or_never()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `abort_transaction` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/transaction.rs:130
- `` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `force_flush` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/event_handler/mongodb_bulk.rs:233
- `` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `process_event` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — src/event_handler/mongodb_correlations.rs:82, src/event_handler/postgres.rs:165
- `` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `handle` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×3) — src/event_handler/mongodb_correlations.rs:159, src/event_handler/mongodb_correlations.rs:166, src/event_handler/mongodb_correlations.rs:231
- `partition_id.try_into()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — src/event_handler/postgres.rs:80, src/event_handler/sqlite.rs:66
- `u64::try_from(sequence)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — src/event_handler/postgres.rs:81, src/event_handler/sqlite.rs:67
- `self.transaction.take()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `flush_checkpoint` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — src/event_handler/postgres.rs:545, src/event_handler/sqlite.rs:387
- `.1` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `next` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/event_handler/postgres.rs:712
- `self.transaction.take()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `handle_event` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/event_handler/sqlite.rs:275
- `` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `next` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/event_handler/sqlite.rs:432
- `self.ids().next()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `cardinal_id` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — core/src/stream_id.rs:143
What to do
- Each row is a forced `Option`/`Result` no guard on its path proves present. Handle the absent case where it arises rather than forcing it: `?` to hand it to the caller, `if let` / `match` / `let … else` to branch on it, `unwrap_or` / `unwrap_or_default` / `unwrap_or_else` where a default is right. Where the value genuinely cannot be absent, say so in a way a reader can check from the line: test it first (`if x.is_none() { return … }`), look the key up with `contains_key` or the index against `len()`, or construct the value so it cannot be absent.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 72.9 | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 100.0 | Exemplary | Strongest area. |
| Maturity | 54.4 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 37.1 | Weak — gated by P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 100.0 | Exemplary | Solid. |
| Performance | 100.0 | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 72 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~166 lines of test source are present (.rs) 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 included — the .rs suite was found but not re-run
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (766 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 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.
- D34 Knowledge Freshness — too few commits to judge knowledge freshness
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- 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.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — Rust suite
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (4 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — Not assessed, and this one is on us: 7 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — no CI workflow found
- P2 Observability — This repository's Rust source (3 module(s), 20 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — sqlx is declared, but this repository defines no table or model of its own, so there is no database schema here 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 `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, 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 — No web surface: 19 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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 — 2 finding(s)
- REDACTED
- REDACTED
Serious — 64 finding(s)
- Symbol treated as nullable, then dereferenced unguarded src/command_service.rs:58
- Symbol treated as nullable, then dereferenced unguarded src/command_service.rs:90
- Symbol treated as nullable, then dereferenced unguarded src/command_service.rs:115
- Symbol treated as nullable, then dereferenced unguarded src/command_service.rs:115
- Symbol treated as nullable, then dereferenced unguarded src/command_service.rs:544
- Symbol treated as nullable, then dereferenced unguarded src/command_service.rs:631
- Symbol treated as nullable, then dereferenced unguarded src/entity_actor.rs:694
- Symbol treated as nullable, then dereferenced unguarded src/entity_actor.rs:694
- Symbol treated as nullable, then dereferenced unguarded src/error.rs:88
- Symbol treated as nullable, then dereferenced unguarded src/transaction.rs:122
- Symbol treated as nullable, then dereferenced unguarded src/transaction.rs:126
- Symbol treated as nullable, then dereferenced unguarded src/transaction.rs:130
- Symbol treated as nullable, then dereferenced unguarded src/event_handler/mongodb_bulk.rs:233
- Symbol treated as nullable, then dereferenced unguarded src/event_handler/mongodb_correlations.rs:82
- Symbol treated as nullable, then dereferenced unguarded src/event_handler/mongodb_correlations.rs:159
- Symbol treated as nullable, then dereferenced unguarded src/event_handler/mongodb_correlations.rs:166
- Symbol treated as nullable, then dereferenced unguarded src/event_handler/mongodb_correlations.rs:231
- Symbol treated as nullable, then dereferenced unguarded src/event_handler/postgres.rs:80
- Symbol treated as nullable, then dereferenced unguarded src/event_handler/postgres.rs:81
- Symbol treated as nullable, then dereferenced unguarded src/event_handler/postgres.rs:165
- Symbol treated as nullable, then dereferenced unguarded src/event_handler/postgres.rs:545
- Symbol treated as nullable, then dereferenced unguarded src/event_handler/postgres.rs:712
- Symbol treated as nullable, then dereferenced unguarded src/event_handler/sqlite.rs:66
- Symbol treated as nullable, then dereferenced unguarded src/event_handler/sqlite.rs:67
- Symbol treated as nullable, then dereferenced unguarded src/event_handler/sqlite.rs:275
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FileTooLong: event_handler/postgres.rs src/event_handler/postgres.rs
- FileTooLong: src/entity_actor.rs src/entity_actor.rs
- FileTooLong: src/command_service.rs src/command_service.rs
- Duplicated block (10 lines × 2) src/command_service.rs:464
- Duplicated block (10 lines × 2) core/src/test_utils.rs:101
- Execute::into_future (cyclomatic 16) src/command_service.rs:494
- CorrelationWorker::handle (cognitive 30) src/event_handler/mongodb_correlations.rs:226
- CommandService::transaction (cognitive 18) src/command_service.rs:71
- EntityActor::handle (cognitive 17) src/entity_actor.rs:422
- REDACTED
- REDACTED
- Near-duplicate member pair (40 shared lines) src/event_handler/postgres.rs:458
- Edited copy of a member (11 corresponding lines) src/event_handler/file.rs:243
- Edited copy of a member (7 corresponding lines) src/event_handler/file.rs:232
- Duplicated block (13–15 lines × 2) src/event_handler/postgres.rs:461
- Duplicated block (15 lines × 2) src/event_handler/postgres.rs:534
- Duplicated block (12–14 lines × 2) src/event_handler/postgres.rs:499
- Duplicated block (13 lines × 2) src/command_service.rs:465
- Duplicated block (7 lines × 2) src/event_handler/postgres.rs:226
- Edited copies of one member (3 members, 16+ corresponding lines) core/src/test_utils.rs:100
- Duplicated block (8 lines × 2) core/src/test_utils.rs:69
- No CI pipeline
Minor — 29 finding(s)
- Interpolated log message defeats structured logging src/command_service.rs:187
- Interpolated log message defeats structured logging src/entity_actor.rs:380
- Interpolated log message defeats structured logging src/entity_actor.rs:393
- Interpolated log message defeats structured logging src/entity_actor.rs:598
- Interpolated log message defeats structured logging src/entity_actor.rs:601
- Interpolated log message defeats structured logging src/event_handler.rs:213
- Interpolated log message defeats structured logging src/event_handler.rs:279
- Interpolated log message defeats structured logging src/event_handler/mongodb_bulk.rs:208
- Interpolated log message defeats structured logging src/event_handler/mongodb_bulk.rs:241
- Interpolated log message defeats structured logging src/event_handler/mongodb_correlations.rs:207
- Interpolated log message defeats structured logging src/event_handler/postgres.rs:355
- Interpolated log message defeats structured logging src/event_handler/postgres.rs:380
- Interpolated log message defeats structured logging src/event_handler/postgres.rs:408
- Interpolated log message defeats structured logging src/event_handler/postgres.rs:424
- Interpolated log message defeats structured logging src/event_handler/postgres.rs:440
- Interpolated log message defeats structured logging src/event_handler/postgres.rs:468
- Interpolated log message defeats structured logging src/event_handler/postgres.rs:505
- Interpolated log message defeats structured logging src/event_handler/postgres.rs:683
- Interpolated log message defeats structured logging src/event_handler/postgres.rs:709
- Interpolated log message defeats structured logging src/event_handler/sqlite.rs:252
- Interpolated log message defeats structured logging src/event_handler/sqlite.rs:322
- Interpolated log message defeats structured logging src/event_handler/sqlite.rs:355
- Interpolated log message defeats structured logging src/event_handler/sqlite.rs:419
- No ADRs
- No architecture diagram/doc
- No SAST
- No dependency-update automation Cargo.toml:5
- No changelog
- Duplicated predicate src/event_handler/mongodb.rs:144
Minor — 18 finding(s)
- Outdated: anyhow
- Outdated: backon
- Outdated: bson
- Outdated: chrono
- Outdated: futures
- Outdated: mongodb
- Outdated: once_cell
- Outdated: proc-macro2
- Outdated: quote
- Outdated: regex
- Outdated: serde
- Outdated: serde_json
- Outdated: thiserror
- Outdated: tokio
- Outdated: tokio-util
- Outdated: tracing
- Outdated: tracing-subscriber
- Outdated: uuid
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-10b386fdf9334251abf54ba3392c48f6/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-10b386fdf9334251abf54ba3392c48f6/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 . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 18 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |