Executive summary
bulletproof-ninja/delta falls short of our standard for a preview release 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 48 out of 100 and is rated Adequate, and six of its seven critical findings are security problems in its code.
Production Readiness, at 32, is the weakest lens and counts most in the score. The best first step is improving the documentation, worth about 9 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 7 points. Raising Production Readiness to 62 would lift the score to about 59.
Six weaknesses in the code could be used by an attacker. One package carries licence risk. Fixing the weaknesses the scanner points to and replacing or clearing the banned-licence packages would close both risks.
The product code is 11,219 lines, about €14,000 to rebuild.
If Production Readiness rose from 32 to 62, the lowest score rated Strong, the score would rise from 48 to about 59.
New since the last survey: 1 finding
- License Compliance · Banned license: mysql:mysql-connector-java
Rebuild cost: about €14,000 · Estimate
| Cost to rebuild | €4,700 to €23,000, for 78 to 247 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 48. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 11,219 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 (global) | 2 delta | 3 delta.BufferedRetryPublish | 4 delta.EventFormat | 5 delta.MessageTransport | 6 delta.SubscriptionPooling | 7 delta.cassandra.CassandraEventStore | 8 delta.conv | 9 delta.EventSource | 10 delta.EventStore | 11 delta.MessageHub | 12 delta.Transaction | 13 delta.cassandra | 14 delta.hazelcast.IMapStreamProcessStore | 15 delta.jdbc.JdbcEventStore | 16 delta.mongo | 17 delta.mongo.MongoEventStore | 18 delta.process | 19 delta.process.ConcurrentMapStore | 20 delta.process.MonotonicProcessor | 21 delta.read | 22 delta.util.TransientEventStore | 23 delta.write | 24 delta.write.EventStoreRepository | 25 delta.hazelcast | 26 delta.java | 27 delta.jdbc | 28 delta.process.AsyncCodec | 29 delta.process.PersistentMonotonicProcessing | 30 delta.read.impl | 31 delta.redis | 32 delta.util | 33 delta.util.json | 34 delta.validation | 35 delta.hazelcast.serializers | 36 delta.jdbc.JdbcStreamProcessStore | 37 delta.jdbc.h2 | 38 delta.jdbc.mysql | 39 delta.jdbc.postgresql | 40 delta.validation.ConsistencyValidation |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 delta | ||||||||||||||||||||||||||||||||||||||||
| 3 delta.BufferedRetryPublish | ||||||||||||||||||||||||||||||||||||||||
| 4 delta.EventFormat | ||||||||||||||||||||||||||||||||||||||||
| 5 delta.MessageTransport | ||||||||||||||||||||||||||||||||||||||||
| 6 delta.SubscriptionPooling | ||||||||||||||||||||||||||||||||||||||||
| 7 delta.cassandra.CassandraEventStore | ||||||||||||||||||||||||||||||||||||||||
| 8 delta.conv | ||||||||||||||||||||||||||||||||||||||||
| 9 delta.EventSource | 5 | |||||||||||||||||||||||||||||||||||||||
| 10 delta.EventStore | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 delta.MessageHub | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 delta.Transaction | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 delta.cassandra | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 delta.hazelcast.IMapStreamProcessStore | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 delta.jdbc.JdbcEventStore | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 delta.mongo | 3 | |||||||||||||||||||||||||||||||||||||||
| 17 delta.mongo.MongoEventStore | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 delta.process | 1 | 22 | ||||||||||||||||||||||||||||||||||||||
| 19 delta.process.ConcurrentMapStore | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 delta.process.MonotonicProcessor | 4 | |||||||||||||||||||||||||||||||||||||||
| 21 delta.read | 6 | |||||||||||||||||||||||||||||||||||||||
| 22 delta.util.TransientEventStore | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 delta.write | 2 | |||||||||||||||||||||||||||||||||||||||
| 24 delta.write.EventStoreRepository | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 delta.hazelcast | 1 | 22 | 13 | |||||||||||||||||||||||||||||||||||||
| 26 delta.java | 14 | 16 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 27 delta.jdbc | 1 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 28 delta.process.AsyncCodec | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 delta.process.PersistentMonotonicProcessing | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 30 delta.read.impl | 8 | 1 | 6 | |||||||||||||||||||||||||||||||||||||
| 31 delta.redis | 5 | 3 | ||||||||||||||||||||||||||||||||||||||
| 32 delta.util | 3 | 7 | ||||||||||||||||||||||||||||||||||||||
| 33 delta.util.json | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 delta.validation | 8 | 9 | ||||||||||||||||||||||||||||||||||||||
| 35 delta.hazelcast.serializers | 2 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 36 delta.jdbc.JdbcStreamProcessStore | 2 | |||||||||||||||||||||||||||||||||||||||
| 37 delta.jdbc.h2 | 2 | |||||||||||||||||||||||||||||||||||||||
| 38 delta.jdbc.mysql | 2 | |||||||||||||||||||||||||||||||||||||||
| 39 delta.jdbc.postgresql | 2 | |||||||||||||||||||||||||||||||||||||||
| 40 delta.validation.ConsistencyValidation | 2 | 1 |
9→2 delta.EventSource uses delta✕
- Connections
- 5 pairs of types, where a type in delta.EventSource uses a type in delta.
- The types involved
delta.EventSource.ChannelSelector→delta.Transactiondelta.EventSource.EventSelector→delta.Transactiondelta.EventSource.Everything→delta.Transactiondelta.EventSource.Selector→delta.Transactiondelta.EventSource.SingleStreamSelector→delta.Transaction
- Direction
- delta.EventSource uses delta, so a change to delta can break delta.EventSource, while a change to delta.EventSource can't break delta.
- Position
- Below the diagonal: delta.EventSource uses a module listed above it, which is the healthy direction.
10→2 delta.EventStore uses delta✕
- Connections
- 1 pair of types, where a type in delta.EventStore uses a type in delta.
- The types involved
delta.EventStore.DuplicateRevisionException→delta.Transaction
- Direction
- delta.EventStore uses delta, so a change to delta can break delta.EventStore, while a change to delta.EventStore can't break delta.
- Position
- Below the diagonal: delta.EventStore uses a module listed above it, which is the healthy direction.
11→2 delta.MessageHub uses delta✕
- Connections
- 1 pair of types, where a type in delta.MessageHub uses a type in delta.
- The types involved
delta.MessageHub.MessageTransportHub→delta.MessageHub
- Direction
- delta.MessageHub uses delta, so a change to delta can break delta.MessageHub, while a change to delta.MessageHub can't break delta.
- Position
- Below the diagonal: delta.MessageHub uses a module listed above it, which is the healthy direction.
12→2 delta.Transaction uses delta✕
- Connections
- 1 pair of types, where a type in delta.Transaction uses a type in delta.
- The types involved
delta.Transaction.Serialization→delta.Transaction
- Direction
- delta.Transaction uses delta, so a change to delta can break delta.Transaction, while a change to delta.Transaction can't break delta.
- Position
- Below the diagonal: delta.Transaction uses a module listed above it, which is the healthy direction.
13→8 delta.cassandra uses delta.conv✕
- Connections
- 1 pair of types, where a type in delta.cassandra uses a type in delta.conv.
- The types involved
delta.cassandra.ColumnType→delta.conv.StorageType
- Direction
- delta.cassandra uses delta.conv, so a change to delta.conv can break delta.cassandra, while a change to delta.cassandra can't break delta.conv.
- Position
- Below the diagonal: delta.cassandra uses a module listed above it, which is the healthy direction.
14→2 delta.hazelcast.IMapStreamProcessStore uses delta✕
- Connections
- 2 pairs of types, where a type in delta.hazelcast.IMapStreamProcessStore uses a type in delta.
- The types involved
delta.hazelcast.IMapStreamProcessStore.WriteIfAbsent→delta.Snapshotdelta.hazelcast.IMapStreamProcessStore.WriteReplacement→delta.Snapshot
- Direction
- delta.hazelcast.IMapStreamProcessStore uses delta, so a change to delta can break delta.hazelcast.IMapStreamProcessStore, while a change to delta.hazelcast.IMapStreamProcessStore can't break delta.
- Position
- Below the diagonal: delta.hazelcast.IMapStreamProcessStore uses a module listed above it, which is the healthy direction.
15→2 delta.jdbc.JdbcEventStore uses delta✕
- Connections
- 1 pair of types, where a type in delta.jdbc.JdbcEventStore uses a type in delta.
- The types involved
delta.jdbc.JdbcEventStore.RawEvent→delta.EventFormat
- Direction
- delta.jdbc.JdbcEventStore uses delta, so a change to delta can break delta.jdbc.JdbcEventStore, while a change to delta.jdbc.JdbcEventStore can't break delta.
- Position
- Below the diagonal: delta.jdbc.JdbcEventStore uses a module listed above it, which is the healthy direction.
16→2 delta.mongo uses delta✕
- Connections
- 3 pairs of types, where a type in delta.mongo uses a type in delta.
- The types involved
delta.mongo.MongoSnapshotStore→delta.Snapshotdelta.mongo.MongoSnapshotStore→delta.SnapshotStoredelta.mongo.SnapshotCodec→delta.Snapshot
- Direction
- delta.mongo uses delta, so a change to delta can break delta.mongo, while a change to delta.mongo can't break delta.
- Position
- Below the diagonal: delta.mongo uses a module listed above it, which is the healthy direction.
17→2 delta.mongo.MongoEventStore uses delta✕
- Connections
- 1 pair of types, where a type in delta.mongo.MongoEventStore uses a type in delta.
- The types involved
delta.mongo.MongoEventStore.DefaultTransactionCodec→delta.Transaction
- Direction
- delta.mongo.MongoEventStore uses delta, so a change to delta can break delta.mongo.MongoEventStore, while a change to delta.mongo.MongoEventStore can't break delta.
- Position
- Below the diagonal: delta.mongo.MongoEventStore uses a module listed above it, which is the healthy direction.
18→1 delta.process uses (global)✕
- Connections
- 1 pair of types, where a type in delta.process uses a type in (global).
- The types involved
delta.process.MissingRevisionsReplayer→delta
- Direction
- delta.process uses (global), so a change to (global) can break delta.process, while a change to delta.process can't break (global).
- Position
- Below the diagonal: delta.process uses a module listed above it, which is the healthy direction.
18→2 delta.process uses delta✕
- Connections
- 22 pairs of types, where a type in delta.process uses a type in delta.
- The types involved
delta.process.BlockingCASWrites→delta.Snapshotdelta.process.BlockingRecursiveUpsert→delta.Snapshotdelta.process.EventSourceConsumer→delta.EventSourcedelta.process.EventSourceProcessing→delta.EventSourcedelta.process.Exceptions→delta.Snapshotdelta.process.MissingRevisionsReplay→delta.EventSourcedelta.process.MissingRevisionsReplay→delta.Transactiondelta.process.MonotonicJoinState→delta.Transactiondelta.process.NonBlockingCASWrites→delta.Snapshotdelta.process.NonBlockingRecursiveUpsert→delta.Snapshotdelta.process.PersistentMonotonicJoinProcessing→delta.EventSourcedelta.process.PersistentMonotonicProcessing→delta.EventSourcedelta.process.PersistentMonotonicProcessor→delta.EventSourcedelta.process.RecursiveUpsert→delta.Snapshotdelta.process.SecondaryIndexing→delta.Snapshotdelta.process.SideEffect→delta.Snapshotdelta.process.StreamProcessStore→delta.Snapshotdelta.process.StreamProcessStore→delta.SnapshotStoredelta.process.StreamProcessStoreAdapter→delta.Snapshotdelta.process.TransactionProcessor→delta.Transactiondelta.process.Update→delta.Snapshotdelta.process.UpdateCodec→delta.Snapshot
- Direction
- delta.process uses delta, so a change to delta can break delta.process, while a change to delta.process can't break delta.
- Position
- Below the diagonal: delta.process uses a module listed above it, which is the healthy direction.
19→2 delta.process.ConcurrentMapStore uses delta✕
- Connections
- 1 pair of types, where a type in delta.process.ConcurrentMapStore uses a type in delta.
- The types involved
delta.process.ConcurrentMapStore.State→delta.Snapshot
- Direction
- delta.process.ConcurrentMapStore uses delta, so a change to delta can break delta.process.ConcurrentMapStore, while a change to delta.process.ConcurrentMapStore can't break delta.
- Position
- Below the diagonal: delta.process.ConcurrentMapStore uses a module listed above it, which is the healthy direction.
20→2 delta.process.MonotonicProcessor uses delta✕
- Connections
- 4 pairs of types, where a type in delta.process.MonotonicProcessor uses a type in delta.
- The types involved
delta.process.MonotonicProcessor.Beginning→delta.Snapshotdelta.process.MonotonicProcessor.Finished→delta.Snapshotdelta.process.MonotonicProcessor.Intermediate→delta.Snapshotdelta.process.MonotonicProcessor.ProcessingState→delta.Snapshot
- Direction
- delta.process.MonotonicProcessor uses delta, so a change to delta can break delta.process.MonotonicProcessor, while a change to delta.process.MonotonicProcessor can't break delta.
- Position
- Below the diagonal: delta.process.MonotonicProcessor uses a module listed above it, which is the healthy direction.
21→2 delta.read uses delta✕
- Connections
- 6 pairs of types, where a type in delta.read uses a type in delta.
- The types involved
delta.read.MessageHubSupport→delta.MessageHubdelta.read.MessageTransportSupport→delta.MessageTransportdelta.read.ReadModel→delta.Snapshotdelta.read.SnapshotReaderSupport→delta.Snapshotdelta.read.SnapshotReaderSupport→delta.SnapshotReaderdelta.read.SubscriptionSupport→delta.Snapshot
- Direction
- delta.read uses delta, so a change to delta can break delta.read, while a change to delta.read can't break delta.
- Position
- Below the diagonal: delta.read uses a module listed above it, which is the healthy direction.
22→2 delta.util.TransientEventStore uses delta✕
- Connections
- 1 pair of types, where a type in delta.util.TransientEventStore uses a type in delta.
- The types involved
delta.util.TransientEventStore.Tx→delta.Transaction
- Direction
- delta.util.TransientEventStore uses delta, so a change to delta can break delta.util.TransientEventStore, while a change to delta.util.TransientEventStore can't break delta.
- Position
- Below the diagonal: delta.util.TransientEventStore uses a module listed above it, which is the healthy direction.
23→2 delta.write uses delta✕
- Connections
- 2 pairs of types, where a type in delta.write uses a type in delta.
- The types involved
delta.write.Entity→delta.Transactiondelta.write.EventStoreRepository→delta.Snapshot
- Direction
- delta.write uses delta, so a change to delta can break delta.write, while a change to delta.write can't break delta.
- Position
- Below the diagonal: delta.write uses a module listed above it, which is the healthy direction.
24→1 delta.write.EventStoreRepository uses (global)✕
- Connections
- 1 pair of types, where a type in delta.write.EventStoreRepository uses a type in (global).
- The types involved
delta.write.EventStoreRepository.Loaded→delta
- Direction
- delta.write.EventStoreRepository uses (global), so a change to (global) can break delta.write.EventStoreRepository, while a change to delta.write.EventStoreRepository can't break (global).
- Position
- Below the diagonal: delta.write.EventStoreRepository uses a module listed above it, which is the healthy direction.
25→1 delta.hazelcast uses (global)✕
- Connections
- 1 pair of types, where a type in delta.hazelcast uses a type in (global).
- The types involved
delta.hazelcast.HzMonotonicProcessor→delta
- Direction
- delta.hazelcast uses (global), so a change to (global) can break delta.hazelcast, while a change to delta.hazelcast can't break (global).
- Position
- Below the diagonal: delta.hazelcast uses a module listed above it, which is the healthy direction.
25→2 delta.hazelcast uses delta✕
- Connections
- 22 pairs of types, where a type in delta.hazelcast uses a type in delta.
- The types involved
delta.hazelcast.AtomicLongLamportTicker→delta.EventSourcedelta.hazelcast.AtomicLongLamportTicker→delta.LamportTickerdelta.hazelcast.DistributedMonotonicProcessor→delta.Projectordelta.hazelcast.DistributedMonotonicProcessor→delta.Transactiondelta.hazelcast.EntryState→delta.Snapshotdelta.hazelcast.EntryState→delta.Transactiondelta.hazelcast.EntryStateUpdater→delta.Snapshotdelta.hazelcast.HzMonotonicProcessor→delta.Transactiondelta.hazelcast.HzMonotonicReplayProcessor→delta.Snapshotdelta.hazelcast.HzPersistentMonotonicConsumer→delta.EventSourcedelta.hazelcast.HzPersistentMonotonicConsumer→delta.Projectordelta.hazelcast.HzPersistentMonotonicConsumer→delta.Transactiondelta.hazelcast.IMapAggregationSupport→delta.Snapshotdelta.hazelcast.IMapDuplicateAggregator→delta.Snapshotdelta.hazelcast.IMapSnapshotStore→delta.Snapshotdelta.hazelcast.IMapSnapshotStore→delta.SnapshotStoredelta.hazelcast.IMapStreamProcessStore→delta.Snapshotdelta.hazelcast.IMapValueQueries→delta.Snapshotdelta.hazelcast.KeySnapshotProjection→delta.Snapshotdelta.hazelcast.KeyTickProjection→delta.Snapshotdelta.hazelcast.SnapshotUpdater→delta.Snapshotdelta.hazelcast.TopicMessageTransport→delta.MessageTransport
- Direction
- delta.hazelcast uses delta, so a change to delta can break delta.hazelcast, while a change to delta.hazelcast can't break delta.
- Position
- Below the diagonal: delta.hazelcast uses a module listed above it, which is the healthy direction.
25→18 delta.hazelcast uses delta.process✕
- Connections
- 13 pairs of types, where a type in delta.hazelcast uses a type in delta.process.
- The types involved
delta.hazelcast.DistributedMonotonicProcessor→delta.process.AsyncCodecdelta.hazelcast.HzMonotonicProcessor→delta.process.MissingRevisionsReplaydelta.hazelcast.HzMonotonicReplayProcessor→delta.process.StreamProcessStoredelta.hazelcast.HzPersistentMonotonicConsumer→delta.process.EventSourceConsumerdelta.hazelcast.HzPersistentMonotonicConsumer→delta.process.LiveProcessConfigdelta.hazelcast.HzPersistentMonotonicConsumer→delta.process.ReplayProcessConfigdelta.hazelcast.IMapAggregationSupport→delta.process.AggregationSupportdelta.hazelcast.IMapEntryStateReadModel→delta.process.UpdateCodecdelta.hazelcast.IMapStreamProcessStore→delta.process.NonBlockingCASWritesdelta.hazelcast.IMapStreamProcessStore→delta.process.StreamProcessStoredelta.hazelcast.IMapStreamProcessStore→delta.process.UpdateCodecdelta.hazelcast.IMapValueQueries→delta.process.SecondaryIndexingdelta.hazelcast.Updated→delta.process.Update
- Direction
- delta.hazelcast uses delta.process, so a change to delta.process can break delta.hazelcast, while a change to delta.hazelcast can't break delta.process.
- Position
- Below the diagonal: delta.hazelcast uses a module listed above it, which is the healthy direction.
26→2 delta.java uses delta✕
- Connections
- 14 pairs of types, where a type in delta.java uses a type in delta.
- The types involved
delta.java.Entity→delta.Transactiondelta.java.EventSourceConsumer→delta.EventSourcedelta.java.EventStoreProxy→delta.EventStoredelta.java.EventStoreProxy→delta.MessageTransportdelta.java.EventStoreProxy→delta.Transactiondelta.java.IncrementalReadModel→delta.MessageHubdelta.java.LiveProcessor→delta.Transactiondelta.java.PersistentMonotonicJoinConsumer→delta.EventSourcedelta.java.PersistentMonotonicJoinConsumer→delta.Transactiondelta.java.PrebuiltReadModel→delta.MessageHubdelta.java.PublishingEventStore→delta.EventStoredelta.java.PublishingEventStore→delta.MessageTransportPublishingdelta.java.ScalaHelp→delta.Snapshotdelta.java.SubscriptionAdapter→delta.Snapshot
- Direction
- delta.java uses delta, so a change to delta can break delta.java, while a change to delta.java can't break delta.
- Position
- Below the diagonal: delta.java uses a module listed above it, which is the healthy direction.
26→18 delta.java uses delta.process✕
- Connections
- 16 pairs of types, where a type in delta.java uses a type in delta.process.
- The types involved
delta.java.EventSourceConsumer→delta.process.EventSourceProcessingdelta.java.EventSourceConsumer→delta.process.LiveProcessConfigdelta.java.EventSourceConsumer→delta.process.ReplayProcessConfigdelta.java.IncrementalReadModel→delta.process.StreamProcessStoredelta.java.IncrementalReadModel→delta.process.Updatedelta.java.JoinStateProcessor→delta.process.MonotonicJoinStatedelta.java.JoinStateReplayProcessor→delta.process.MonotonicJoinStatedelta.java.MonotonicProcessor→delta.process.StreamProcessStoredelta.java.MonotonicReplayProcessor→delta.process.StreamProcessStoredelta.java.PersistentMonotonicConsumer→delta.process.PersistentMonotonicProcessingdelta.java.PersistentMonotonicConsumer→delta.process.StreamProcessStoredelta.java.PersistentMonotonicJoinConsumer→delta.process.MissingRevisionsReplaydelta.java.PersistentMonotonicJoinConsumer→delta.process.MonotonicJoinStatedelta.java.PersistentMonotonicJoinConsumer→delta.process.StreamProcessStoredelta.java.PrebuiltReadModel→delta.process.Updatedelta.java.ScalaHelp→delta.process.StreamProcessStore
- Direction
- delta.java uses delta.process, so a change to delta.process can break delta.java, while a change to delta.java can't break delta.process.
- Position
- Below the diagonal: delta.java uses a module listed above it, which is the healthy direction.
26→21 delta.java uses delta.read✕
- Connections
- 1 pair of types, where a type in delta.java uses a type in delta.read.
- The types involved
delta.java.PrebuiltReadModel→delta.read.MessageHubSupport
- Direction
- delta.java uses delta.read, so a change to delta.read can break delta.java, while a change to delta.java can't break delta.read.
- Position
- Below the diagonal: delta.java uses a module listed above it, which is the healthy direction.
26→23 delta.java uses delta.write✕
- Connections
- 2 pairs of types, where a type in delta.java uses a type in delta.write.
- The types involved
delta.java.Entity→delta.write.Statedelta.java.EntityRepository→delta.write.Metadata
- Direction
- delta.java uses delta.write, so a change to delta.write can break delta.java, while a change to delta.java can't break delta.write.
- Position
- Below the diagonal: delta.java uses a module listed above it, which is the healthy direction.
27→2 delta.jdbc uses delta✕
- Connections
- 1 pair of types, where a type in delta.jdbc uses a type in delta.
- The types involved
delta.jdbc.JdbcStreamProcessHistory→delta.Snapshot
- Direction
- delta.jdbc uses delta, so a change to delta can break delta.jdbc, while a change to delta.jdbc can't break delta.
- Position
- Below the diagonal: delta.jdbc uses a module listed above it, which is the healthy direction.
27→8 delta.jdbc uses delta.conv✕
- Connections
- 2 pairs of types, where a type in delta.jdbc uses a type in delta.conv.
- The types involved
delta.jdbc.ColumnType→delta.conv.StorageTypedelta.jdbc.ReadColumn→delta.conv.ReadFromStorage
- Direction
- delta.jdbc uses delta.conv, so a change to delta.conv can break delta.jdbc, while a change to delta.jdbc can't break delta.conv.
- Position
- Below the diagonal: delta.jdbc uses a module listed above it, which is the healthy direction.
27→18 delta.jdbc uses delta.process✕
- Connections
- 3 pairs of types, where a type in delta.jdbc uses a type in delta.process.
- The types involved
delta.jdbc.JdbcStreamProcessHistory→delta.process.BlockingCASWritesdelta.jdbc.JdbcStreamProcessHistory→delta.process.StreamProcessStoredelta.jdbc.JdbcStreamProcessHistory→delta.process.UpdateCodec
- Direction
- delta.jdbc uses delta.process, so a change to delta.process can break delta.jdbc, while a change to delta.jdbc can't break delta.process.
- Position
- Below the diagonal: delta.jdbc uses a module listed above it, which is the healthy direction.
28→18 delta.process.AsyncCodec uses delta.process✕
- Connections
- 1 pair of types, where a type in delta.process.AsyncCodec uses a type in delta.process.
- The types involved
delta.process.AsyncCodec.NoOp→delta.process.AsyncCodec
- Direction
- delta.process.AsyncCodec uses delta.process, so a change to delta.process can break delta.process.AsyncCodec, while a change to delta.process.AsyncCodec can't break delta.process.
- Position
- Below the diagonal: delta.process.AsyncCodec uses a module listed above it, which is the healthy direction.
29→2 delta.process.PersistentMonotonicProcessing uses delta✕
- Connections
- 2 pairs of types, where a type in delta.process.PersistentMonotonicProcessing uses a type in delta.
- The types involved
delta.process.PersistentMonotonicProcessing.LiveConsumer→delta.Transactiondelta.process.PersistentMonotonicProcessing.ReplayConsumer→delta.Transaction
- Direction
- delta.process.PersistentMonotonicProcessing uses delta, so a change to delta can break delta.process.PersistentMonotonicProcessing, while a change to delta.process.PersistentMonotonicProcessing can't break delta.
- Position
- Below the diagonal: delta.process.PersistentMonotonicProcessing uses a module listed above it, which is the healthy direction.
29→18 delta.process.PersistentMonotonicProcessing uses delta.process✕
- Connections
- 3 pairs of types, where a type in delta.process.PersistentMonotonicProcessing uses a type in delta.process.
- The types involved
delta.process.PersistentMonotonicProcessing.LiveConsumer→delta.process.PersistentMonotonicProcessordelta.process.PersistentMonotonicProcessing.LiveConsumer→delta.process.Updatedelta.process.PersistentMonotonicProcessing.ReplayConsumer→delta.process.PersistentMonotonicReplayProcessor
- Direction
- delta.process.PersistentMonotonicProcessing uses delta.process, so a change to delta.process can break delta.process.PersistentMonotonicProcessing, while a change to delta.process.PersistentMonotonicProcessing can't break delta.process.
- Position
- Below the diagonal: delta.process.PersistentMonotonicProcessing uses a module listed above it, which is the healthy direction.
30→2 delta.read.impl uses delta✕
- Connections
- 8 pairs of types, where a type in delta.read.impl uses a type in delta.
- The types involved
delta.read.impl.EventSourceReadModel→delta.EventSourcedelta.read.impl.EventSourceReadModel→delta.Projectordelta.read.impl.EventSourceReadModel→delta.Snapshotdelta.read.impl.EventSourceReadModel→delta.Transactiondelta.read.impl.IncrementalReadModel→delta.Snapshotdelta.read.impl.ProcessStoreSupport→delta.Snapshotdelta.read.impl.StatefulReadModel→delta.Snapshotdelta.read.impl.StatelessReadModel→delta.Snapshot
- Direction
- delta.read.impl uses delta, so a change to delta can break delta.read.impl, while a change to delta.read.impl can't break delta.
- Position
- Below the diagonal: delta.read.impl uses a module listed above it, which is the healthy direction.
30→18 delta.read.impl uses delta.process✕
- Connections
- 1 pair of types, where a type in delta.read.impl uses a type in delta.process.
- The types involved
delta.read.impl.ProcessStoreSupport→delta.process.StreamProcessStore
- Direction
- delta.read.impl uses delta.process, so a change to delta.process can break delta.read.impl, while a change to delta.read.impl can't break delta.process.
- Position
- Below the diagonal: delta.read.impl uses a module listed above it, which is the healthy direction.
30→21 delta.read.impl uses delta.read✕
- Connections
- 6 pairs of types, where a type in delta.read.impl uses a type in delta.read.
- The types involved
delta.read.impl.EventSourceReadModel→delta.read.ReadModeldelta.read.impl.EventSourceReadModel→delta.read.StreamIddelta.read.impl.IncrementalReadModel→delta.read.MessageHubSupportdelta.read.impl.PrebuiltReadModel→delta.read.ReadModeldelta.read.impl.PrebuiltReadModel→delta.read.SubscriptionSupportdelta.read.impl.ProcessStoreSupport→delta.read.StreamId
- Direction
- delta.read.impl uses delta.read, so a change to delta.read can break delta.read.impl, while a change to delta.read.impl can't break delta.read.
- Position
- Below the diagonal: delta.read.impl uses a module listed above it, which is the healthy direction.
31→2 delta.redis uses delta✕
- Connections
- 5 pairs of types, where a type in delta.redis uses a type in delta.
- The types involved
delta.redis.BinaryRedisSnapshotStore→delta.Snapshotdelta.redis.BinaryRedisSnapshotStore→delta.SnapshotStoredelta.redis.BinaryRedisSnapshotStore→delta.Transactiondelta.redis.BinaryRedisStreamProcessStore→delta.Snapshotdelta.redis.SnapshotSerializer→delta.Snapshot
- Direction
- delta.redis uses delta, so a change to delta can break delta.redis, while a change to delta.redis can't break delta.
- Position
- Below the diagonal: delta.redis uses a module listed above it, which is the healthy direction.
31→18 delta.redis uses delta.process✕
- Connections
- 3 pairs of types, where a type in delta.redis uses a type in delta.process.
- The types involved
delta.redis.BinaryRedisStreamProcessStore→delta.process.BlockingCASWritesdelta.redis.BinaryRedisStreamProcessStore→delta.process.StreamProcessStoredelta.redis.BinaryRedisStreamProcessStore→delta.process.UpdateCodec
- Direction
- delta.redis uses delta.process, so a change to delta.process can break delta.redis, while a change to delta.redis can't break delta.process.
- Position
- Below the diagonal: delta.redis uses a module listed above it, which is the healthy direction.
32→2 delta.util uses delta✕
- Connections
- 3 pairs of types, where a type in delta.util uses a type in delta.
- The types involved
delta.util.LocalTransport→delta.MessageTransportdelta.util.TransientEventStore→delta.EventStoredelta.util.TransientEventStore→delta.Transaction
- Direction
- delta.util uses delta, so a change to delta can break delta.util, while a change to delta.util can't break delta.
- Position
- Below the diagonal: delta.util uses a module listed above it, which is the healthy direction.
32→23 delta.util uses delta.write✕
- Connections
- 7 pairs of types, where a type in delta.util uses a type in delta.write.
- The types involved
delta.util.ConcurrentMapRepository→delta.write.ImmutableEntitydelta.util.ConcurrentMapRepository→delta.write.Metadatadelta.util.ConcurrentMapRepository→delta.write.Repositorydelta.util.PublishingRepository→delta.write.Entitydelta.util.PublishingRepository→delta.write.ImmutableEntitydelta.util.PublishingRepository→delta.write.Metadatadelta.util.PublishingRepository→delta.write.Repository
- Direction
- delta.util uses delta.write, so a change to delta.write can break delta.util, while a change to delta.util can't break delta.write.
- Position
- Below the diagonal: delta.util uses a module listed above it, which is the healthy direction.
33→2 delta.util.json uses delta✕
- Connections
- 4 pairs of types, where a type in delta.util.json uses a type in delta.
- The types involved
delta.util.json.JsonEvent→delta.EventFormatdelta.util.json.JsonSnapshot→delta.Snapshotdelta.util.json.JsonTransaction→delta.EventFormatdelta.util.json.JsonTransaction→delta.Transaction
- Direction
- delta.util.json uses delta, so a change to delta can break delta.util.json, while a change to delta.util.json can't break delta.
- Position
- Below the diagonal: delta.util.json uses a module listed above it, which is the healthy direction.
33→18 delta.util.json uses delta.process✕
- Connections
- 1 pair of types, where a type in delta.util.json uses a type in delta.process.
- The types involved
delta.util.json.JsonUpdate→delta.process.Update
- Direction
- delta.util.json uses delta.process, so a change to delta.process can break delta.util.json, while a change to delta.util.json can't break delta.process.
- Position
- Below the diagonal: delta.util.json uses a module listed above it, which is the healthy direction.
34→2 delta.validation uses delta✕
- Connections
- 8 pairs of types, where a type in delta.validation uses a type in delta.
- The types involved
delta.validation.BySeniority→delta.Snapshotdelta.validation.Compensation→delta.Snapshotdelta.validation.ConsistencyValidation→delta.Transactiondelta.validation.ConsistencyValidation→delta.TransactionPublishingdelta.validation.EntityCompensation→delta.Snapshotdelta.validation.EventStoreValidationProcess→delta.EventSourcedelta.validation.GlobalSetValidator→delta.Snapshotdelta.validation.Validator→delta.Snapshot
- Direction
- delta.validation uses delta, so a change to delta can break delta.validation, while a change to delta.validation can't break delta.
- Position
- Below the diagonal: delta.validation uses a module listed above it, which is the healthy direction.
34→18 delta.validation uses delta.process✕
- Connections
- 9 pairs of types, where a type in delta.validation uses a type in delta.process.
- The types involved
delta.validation.ConsistencyValidation→delta.process.LiveProcessConfigdelta.validation.ConsistencyValidation→delta.process.ReplayProcessdelta.validation.ConsistencyValidation→delta.process.ReplayProcessConfigdelta.validation.ConsistencyValidation→delta.process.ReplayResultdelta.validation.EventStoreValidationProcess→delta.process.EventSourceProcessingdelta.validation.EventStoreValidationProcess→delta.process.LiveProcessConfigdelta.validation.EventStoreValidationProcess→delta.process.ReplayCompletiondelta.validation.EventStoreValidationProcess→delta.process.ReplayProcessdelta.validation.EventStoreValidationProcess→delta.process.ReplayProcessConfig
- Direction
- delta.validation uses delta.process, so a change to delta.process can break delta.validation, while a change to delta.validation can't break delta.process.
- Position
- Below the diagonal: delta.validation uses a module listed above it, which is the healthy direction.
35→2 delta.hazelcast.serializers uses delta✕
- Connections
- 2 pairs of types, where a type in delta.hazelcast.serializers uses a type in delta.
- The types involved
delta.hazelcast.serializers.SnapshotSerializer→delta.Snapshotdelta.hazelcast.serializers.TransactionSerializer→delta.Transaction
- Direction
- delta.hazelcast.serializers uses delta, so a change to delta can break delta.hazelcast.serializers, while a change to delta.hazelcast.serializers can't break delta.
- Position
- Below the diagonal: delta.hazelcast.serializers uses a module listed above it, which is the healthy direction.
35→18 delta.hazelcast.serializers uses delta.process✕
- Connections
- 1 pair of types, where a type in delta.hazelcast.serializers uses a type in delta.process.
- The types involved
delta.hazelcast.serializers.UpdateSerializer→delta.process.Update
- Direction
- delta.hazelcast.serializers uses delta.process, so a change to delta.process can break delta.hazelcast.serializers, while a change to delta.hazelcast.serializers can't break delta.process.
- Position
- Below the diagonal: delta.hazelcast.serializers uses a module listed above it, which is the healthy direction.
35→25 delta.hazelcast.serializers uses delta.hazelcast✕
- Connections
- 4 pairs of types, where a type in delta.hazelcast.serializers uses a type in delta.hazelcast.
- The types involved
delta.hazelcast.serializers.DistributedMonotonicProcessorSerializer→delta.hazelcast.DistributedMonotonicProcessordelta.hazelcast.serializers.EntryStateSerializer→delta.hazelcast.EntryStatedelta.hazelcast.serializers.EntryUpdateResultSerializer→delta.hazelcast.EntryUpdateResultdelta.hazelcast.serializers.IMapDuplicateAggregatorSerializer→delta.hazelcast.IMapDuplicateAggregator
- Direction
- delta.hazelcast.serializers uses delta.hazelcast, so a change to delta.hazelcast can break delta.hazelcast.serializers, while a change to delta.hazelcast.serializers can't break delta.hazelcast.
- Position
- Below the diagonal: delta.hazelcast.serializers uses a module listed above it, which is the healthy direction.
36→27 delta.jdbc.JdbcStreamProcessStore uses delta.jdbc✕
- Connections
- 2 pairs of types, where a type in delta.jdbc.JdbcStreamProcessStore uses a type in delta.jdbc.
- The types involved
delta.jdbc.JdbcStreamProcessStore.IndexColumn→delta.jdbc.ColumnTypedelta.jdbc.JdbcStreamProcessStore.PkColumn→delta.jdbc.ColumnType
- Direction
- delta.jdbc.JdbcStreamProcessStore uses delta.jdbc, so a change to delta.jdbc can break delta.jdbc.JdbcStreamProcessStore, while a change to delta.jdbc.JdbcStreamProcessStore can't break delta.jdbc.
- Position
- Below the diagonal: delta.jdbc.JdbcStreamProcessStore uses a module listed above it, which is the healthy direction.
37→27 delta.jdbc.h2 uses delta.jdbc✕
- Connections
- 2 pairs of types, where a type in delta.jdbc.h2 uses a type in delta.jdbc.
- The types involved
delta.jdbc.h2.H2Dialect→delta.jdbc.Dialectdelta.jdbc.h2.UUIDColumn→delta.jdbc.ColumnType
- Direction
- delta.jdbc.h2 uses delta.jdbc, so a change to delta.jdbc can break delta.jdbc.h2, while a change to delta.jdbc.h2 can't break delta.jdbc.
- Position
- Below the diagonal: delta.jdbc.h2 uses a module listed above it, which is the healthy direction.
38→27 delta.jdbc.mysql uses delta.jdbc✕
- Connections
- 2 pairs of types, where a type in delta.jdbc.mysql uses a type in delta.jdbc.
- The types involved
delta.jdbc.mysql.MySQLDialect→delta.jdbc.Dialectdelta.jdbc.mysql.TextColumn→delta.jdbc.ColumnType
- Direction
- delta.jdbc.mysql uses delta.jdbc, so a change to delta.jdbc can break delta.jdbc.mysql, while a change to delta.jdbc.mysql can't break delta.jdbc.
- Position
- Below the diagonal: delta.jdbc.mysql uses a module listed above it, which is the healthy direction.
39→27 delta.jdbc.postgresql uses delta.jdbc✕
- Connections
- 2 pairs of types, where a type in delta.jdbc.postgresql uses a type in delta.jdbc.
- The types involved
delta.jdbc.postgresql.ByteaColumn→delta.jdbc.ColumnTypedelta.jdbc.postgresql.PostgreSQLDialect→delta.jdbc.Dialect
- Direction
- delta.jdbc.postgresql uses delta.jdbc, so a change to delta.jdbc can break delta.jdbc.postgresql, while a change to delta.jdbc.postgresql can't break delta.jdbc.
- Position
- Below the diagonal: delta.jdbc.postgresql uses a module listed above it, which is the healthy direction.
40→2 delta.validation.ConsistencyValidation uses delta✕
- Connections
- 2 pairs of types, where a type in delta.validation.ConsistencyValidation uses a type in delta.
- The types involved
delta.validation.ConsistencyValidation.Activation→delta.Transactiondelta.validation.ConsistencyValidation.StreamStatus→delta.Transaction
- Direction
- delta.validation.ConsistencyValidation uses delta, so a change to delta can break delta.validation.ConsistencyValidation, while a change to delta.validation.ConsistencyValidation can't break delta.
- Position
- Below the diagonal: delta.validation.ConsistencyValidation uses a module listed above it, which is the healthy direction.
40→34 delta.validation.ConsistencyValidation uses delta.validation✕
- Connections
- 1 pair of types, where a type in delta.validation.ConsistencyValidation uses a type in delta.validation.
- The types involved
delta.validation.ConsistencyValidation.Activation→delta.validation.Compensation
- Direction
- delta.validation.ConsistencyValidation uses delta.validation, so a change to delta.validation can break delta.validation.ConsistencyValidation, while a change to delta.validation.ConsistencyValidation can't break delta.validation.
- Position
- Below the diagonal: delta.validation.ConsistencyValidation uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 6 | High / Critical |
Roadmap
Top priorities: Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md; Resolve the 53 Orphaned file finding(s) in Knowledge Freshness — start with package.scala (4), EntityRepository.scala (2), REDACTED; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +9.3 pts | Low | Documentation Quality |
| Resolve the 1 Banned license finding(s) in License Compliance. | +4.6 pts | Low | License Compliance |
| Resolve the 53 Orphaned file finding(s) in Knowledge Freshness — start with package.scala (4), EntityRepository.scala (2), REDACTED. | +9.0 pts | Medium | Knowledge Freshness |
| 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. | +7.6 pts | Medium | Architecture documentation |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +7.1 pts | Medium | CI/CD gates |
| Run what this repository's stack ships: scalafix or scapegoat — 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. | +7.1 pts | Medium | Security & performance tooling |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +3.0 pts | Medium | Release Hygiene |
| Keep implementation types off the public surface (Java: package-private (no modifier), or leave its package out of `module-info` exports) — even for a small library, every public type is a stability contract. | +2.2 pts | Medium | Library API & versioning |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.1 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| delta-jdbc/src/main/scala/delta/jdbc/Dialect.scala | 6.3 | Mixed | God Classes: TooManyMethods: Dialect |
| src/main/scala/delta/validation/ConsistencyValidation.scala | 7.3 | Near-clean | Explicit Debt: TodoComment |
| src/main/scala/delta/read/SubscriptionSupport.scala | 7.8 | Near-clean | Cognitive Complexity: SubscriptionSupport.readMin (cognitive 30) |
| delta-java/src/main/scala/delta/java/ScalaHelp.scala | 7.8 | Near-clean | Cognitive Complexity: ScalaHelp.combine (cognitive 28) |
| delta-hazelcast/src/main/scala/delta/hazelcast/DistributedMonotonicProcessor.scala | 7.8 | Near-clean | Cognitive Complexity: DistributedMonotonicProcessor.processTransaction (cognitive 18) |
| src/test/scala/college/TestCollege.scala | 8.2 | Near-clean | Explicit Debt: FixmeComment |
| src/main/scala/delta/process/MonotonicProcessor.scala | 8.5 | Near-clean | Cognitive Complexity: MonotonicProcessor.setInactive (cognitive 23) |
| delta-hazelcast/src/main/scala/delta/hazelcast/SnapshotUpdater.scala | 8.5 | Near-clean | Cognitive Complexity: SnapshotUpdater.process (cognitive 22) |
| delta-jdbc/src/main/scala/delta/jdbc/JdbcEventStore.scala | 8.5 | Near-clean | Cognitive Complexity: JdbcEventStore.processTransactions (cognitive 17) |
| delta-mongodb/src/main/scala/delta/mongo/package.scala | 8.5 | Near-clean | God Classes: TooManyMethods: mongo |
| src/main/scala/delta/process/PersistentMonotonicJoinProcessing.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (9 lines × 2) |
| delta-java/src/main/scala/delta/java/EventSourceConsumer.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (5 lines × 2) |
| delta-mongodb/src/main/scala/delta/mongo/MongoStreamProcessStore.scala | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: MongoStreamProcessStore (LCOM4 7) |
| delta-redis/src/main/scala/delta/redis/BinaryRedisStreamProcessStore.scala | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: BinaryRedisStreamProcessStore (LCOM4 6) |
| delta-hazelcast/src/main/scala/delta/hazelcast/IMapStreamProcessStore.scala | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: IMapStreamProcessStore (LCOM4 5) |
| delta-hazelcast/src/main/scala/delta/hazelcast/StreamProcessMapStore.scala | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: StreamProcessMapStore (LCOM4 4) |
| delta-jdbc/src/main/scala/delta/jdbc/JdbcStreamProcessHistory.scala | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: JdbcStreamProcessHistory (LCOM4 4) |
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 53 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 53 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, 91 of 100 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: test source is present (.scala) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 1 Maven/Gradle manifest(s) were read, stating a version for 12 dependency(ies) and leaving 7 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- 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 458 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.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (build.gradle), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- 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.
- D32 Data Compliance (PII/GDPR) — 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. `src/main/scala/delta/conv/ScalaEnumType.scala` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'com.mongodb' is imported (delta-mongodb/src/main/scala/delta/mongo/MongoEventStore.scala:13), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'com.mongodb' is imported (delta-mongodb/src/main/scala/delta/mongo/MongoEventStore.scala:13), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'com.mongodb' is imported (delta-mongodb/src/main/scala/delta/mongo/MongoEventStore.scala:13), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
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.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- 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").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
8 method(s) exceeded the cognitive complexity threshold of 15; the worst was SubscriptionSupport.readMin at 30.
What to do
- Bring the 8 bodies over 15 down to 15 or less in Cognitive Complexity — start with SubscriptionSupport.readMin (cognitive 30), ScalaHelp.combine (cognitive 28), MonotonicProcessor.setInactive (cognitive 23). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 8 together lifts Cognitive Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
3 god class(es) detected.
What to do
- Resolve the 3 TooManyMethods finding(s) in God Classes — start with Dialect.scala, REDACTED, package.scala. — One of this dimension's main actionable groups (3 warning-level).
- Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
6 duplicated block group(s) detected.
What to do
- Resolve the 2 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with REDACTED, PersistentMonotonicJoinProcessing.scala. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (22 lines × 2) finding(s) in Code Duplication — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with Dialect.scala. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
7 of 31 classes have LCOM4 above 3.
What to do
- Resolve the 7 Low cohesion finding(s) in Cohesion (LCOM4) — start with Dialect.scala, MongoStreamProcessStore.scala, BinaryRedisStreamProcessStore.scala. — One of this dimension's main actionable groups (7 warning-level).
- Stand up a CI pipeline, then gate Cohesion (LCOM4) in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
60 test methods: 60 unit, 0 integration, 0 BDD, 0 e2e. The Scala suite contributes 58 test case(s) across 28 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
1 of 12 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 1 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 7 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
- Stand up a CI pipeline, then gate License Compliance in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
5 deducted task-comment markers across 11219 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 4 TodoComment finding(s) in Explicit Debt — start with ConsistencyValidation.scala (2), REDACTED (2). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with TestCollege.scala. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 1 document(s) read across 1 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 1 build units (Gradle) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
6 finding(s): 0 critical, 6 high, 0 medium, 0 low. semgrep hit a parse error in 1 file(s) — `gradlew` (line 177) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
D34 · Knowledge Freshness
54 of 54 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is REDACTED. Counted over 54 of the 152 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 53 Orphaned file finding(s) in Knowledge Freshness — start with package.scala (4), EntityRepository.scala (2), REDACTED. — One of this dimension's main actionable groups (53 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Most significant orphaned file finding(s) in Knowledge Freshness — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 14 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
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
What to do
- Keep implementation types off the public surface (Java: package-private (no modifier), or leave its package out of `module-info` exports) — even for a small library, every public type is a stability contract.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add scalafix or scapegoat (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.
What to do
- Run what this repository's stack ships: scalafix or scapegoat — 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
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- No build over this repository's 149 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 74% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 84% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 44% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 32% | Weak — gated by P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 78% | Checked 3 of 8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
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 — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'com.mongodb' (delta-mongodb/src/main/scala/delta/mongo/MongoEventStore.scala:13) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'com.mongodb' (delta-mongodb/src/main/scala/delta/mongo/MongoEventStore.scala:13) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'com.mongodb' (delta-mongodb/src/main/scala/delta/mongo/MongoEventStore.scala:13) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- 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 — 61 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Scala code is a Play controller, a Cask routes object, a Scalatra servlet, a Finatra controller, an Akka/Pekko HTTP routes holder or a JSR-330/Spring singleton, so no instance is shared between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- 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.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~4084 lines of test source are present (.scala) 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 — no .scala test runner
- D12 Dependency Hygiene — Not scored — 1 Maven/Gradle manifest(s) were read, stating a version for 12 dependency(ies) and leaving 7 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- 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 — Naming consistency is measured on C# and TypeScript only; Java, Scala not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .scala, 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 (.scala), 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.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- 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) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- D5 Coupling — Not applicable — this Gradle build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 36 value object(s)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an append-only event-store seam (IEventStore/Append-of-events))
- 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 JVM source (1 module(s), 150 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 JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, 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: 150 Scala 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 artifact (akka-http, pekko-http, http4s, Play, Finagle, zio-http, cask, Scalatra, a tapir server, Jetty, Undertow, …) outside test scope in its build, and no server package imported or server bound 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.
- X2 Cancellation propagation — no C# was loaded; this repository's Scala and Java were read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) would be judged.
- 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 — 7 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Banned license: mysql:mysql-connector-java
Serious — 30 finding(s)
- Low cohesion: Dialect (LCOM4 7) delta-jdbc/src/main/scala/delta/jdbc/Dialect.scala:30
- Low cohesion: MongoStreamProcessStore (LCOM4 7) delta-mongodb/src/main/scala/delta/mongo/MongoStreamProcessStore.scala:37
- Low cohesion: BinaryRedisStreamProcessStore (LCOM4 6) delta-redis/src/main/scala/delta/redis/BinaryRedisStreamProcessStore.scala:18
- Low cohesion: IMapStreamProcessStore (LCOM4 5) delta-hazelcast/src/main/scala/delta/hazelcast/IMapStreamProcessStore.scala:27
- Low cohesion: CassandraEventStore (LCOM4 4) REDACTED:85
- Low cohesion: StreamProcessMapStore (LCOM4 4) delta-hazelcast/src/main/scala/delta/hazelcast/StreamProcessMapStore.scala:23
- Low cohesion: JdbcStreamProcessHistory (LCOM4 4) delta-jdbc/src/main/scala/delta/jdbc/JdbcStreamProcessHistory.scala:20
- TodoComment src/main/scala/delta/validation/ConsistencyValidation.scala:231
- TodoComment src/main/scala/delta/validation/ConsistencyValidation.scala:233
- TodoComment REDACTED:139
- TodoComment REDACTED:162
- TooManyMethods: Dialect delta-jdbc/src/main/scala/delta/jdbc/Dialect.scala:30
- TooManyMethods: JdbcStreamProcessStore REDACTED:57
- TooManyMethods: mongo delta-mongodb/src/main/scala/delta/mongo/package.scala:20
- Duplicated block (9 lines × 2) REDACTED:444
- Duplicated block (9 lines × 2) src/main/scala/delta/process/PersistentMonotonicJoinProcessing.scala:20
- FixmeComment src/test/scala/college/TestCollege.scala:40
- SubscriptionSupport.readMin (cognitive 30) src/main/scala/delta/read/SubscriptionSupport.scala:206
- ScalaHelp.combine (cognitive 28) delta-java/src/main/scala/delta/java/ScalaHelp.scala:101
- MonotonicProcessor.setInactive (cognitive 23) src/main/scala/delta/process/MonotonicProcessor.scala:111
- SnapshotUpdater.process (cognitive 22) delta-hazelcast/src/main/scala/delta/hazelcast/SnapshotUpdater.scala:17
- ScalaHelp.combine (cognitive 21) delta-java/src/main/scala/delta/java/ScalaHelp.scala:89
- SubscriptionSupport.Timeout (cognitive 19) src/main/scala/delta/read/SubscriptionSupport.scala:308
- DistributedMonotonicProcessor.processTransaction (cognitive 18) delta-hazelcast/src/main/scala/delta/hazelcast/DistributedMonotonicProcessor.scala:91
- JdbcEventStore.processTransactions (cognitive 17) delta-jdbc/src/main/scala/delta/jdbc/JdbcEventStore.scala:119
- Duplicated block (22 lines × 2) REDACTED:466
- Duplicated block (8 lines × 2) delta-jdbc/src/main/scala/delta/jdbc/Dialect.scala:313
- Duplicated block (7 lines × 2) delta-hazelcast/src/main/scala/delta/hazelcast/DistributedMonotonicProcessor.scala:37
- Duplicated block (5 lines × 2) delta-java/src/main/scala/delta/java/EventSourceConsumer.scala:30
- No CI pipeline
Minor — 63 finding(s)
- Orphaned file REDACTED:1
- Orphaned file src/main/scala/delta/process/MonotonicProcessor.scala:1
- Orphaned file src/main/scala/delta/process/StreamProcessStore.scala:1
- Orphaned file delta-jdbc/src/main/scala/delta/jdbc/Dialect.scala:1
- Orphaned file delta-mongodb/src/main/scala/delta/mongo/MongoEventStore.scala:1
- Orphaned file src/main/scala/delta/read/SubscriptionSupport.scala:1
- Orphaned file src/main/scala/delta/MessageTransport.scala:1
- Orphaned file delta-jdbc/src/main/scala/delta/jdbc/JdbcStreamProcessHistory.scala:1
- Orphaned file delta-mongodb/src/main/scala/delta/mongo/MongoStreamProcessStore.scala:1
- Orphaned file REDACTED:1
- Orphaned file delta-jdbc/src/main/scala/delta/jdbc/JdbcEventStore.scala:1
- Orphaned file src/main/scala/delta/write/EventStoreRepository.scala:1
- Orphaned file src/main/scala/delta/validation/ConsistencyValidation.scala:1
- Orphaned file delta-mongodb/src/main/scala/delta/mongo/package.scala:1
- Orphaned file delta-hazelcast/src/main/scala/delta/hazelcast/IMapStreamProcessStore.scala:1
- Orphaned file delta-hazelcast/src/main/scala/delta/hazelcast/serializers.scala:1
- Orphaned file delta-hazelcast/src/main/scala/delta/hazelcast/DistributedMonotonicProcessor.scala:1
- Orphaned file src/main/scala/delta/process/ConcurrentMapStore.scala:1
- Orphaned file delta-jdbc/src/main/scala/delta/jdbc/package.scala:1
- Orphaned file delta-redis/src/main/scala/delta/redis/BinaryRedisStreamProcessStore.scala:1
- Orphaned file delta-java/src/main/scala/delta/java/ScalaHelp.scala:1
- Orphaned file src/main/scala/delta/util/ReflectiveDecoder.scala:1
- Orphaned file src/main/scala/delta/EventSource.scala:1
- Orphaned file delta-redis/src/main/scala/delta/redis/RedisMessageHub.scala:1
- Orphaned file delta-hazelcast/src/main/scala/delta/hazelcast/IMapEntryStateReadModel.scala:1
- Documentation: no build, run or usage example README.md:1
- Projects may be oversized for their cohesion
- Dormant codebase
- Most significant orphaned file REDACTED:1
- No ADRs
- No architecture diagram/doc
- No SAST
- No changelog
- Duplicated predicate src/main/scala/delta/util/json/JsonSnapshot.scala:30
- Scala's null is not held to the type system everywhere
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-18ed30aa39834dd79da0c8444c7379c3/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-18ed30aa39834dd79da0c8444c7379c3/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 . | 6 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `src/main/scala/delta/conv/ScalaEnumType.scala` — so the PII/GDPR sweep did not cover them at all. | 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 | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |