Executive summary
opensearch-project/cross-cluster-replication falls short of our standard for production because we found no automated security scanning of the code, its secrets or its dependencies. It scores 59.3 out of 100 and is rated Adequate, and all ten of its critical findings are security problems.
Production Readiness, at 49.6, is the weakest lens and counts most in the score. The best first step is adding automated security scanning, worth about 7.8 points. Adding a release approval comes next, worth about 4.0 points. Raising Production Readiness to 70 would lift the score to about 66.7.
Seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two secrets can leak from the build pipeline. Pinning each tool to an exact version and limiting each secret to its own step would close both risks. Giving the pull-request workflow read-only access would fix the pipeline that outsiders can trigger with write access.
The product code is 15,085 lines, about €28,000 to rebuild. Three of our security checks couldn't finish, among them the one for known security holes in its packages, so those results are missing, not clean passes.
If Production Readiness rose from 49.6 to 70, the lowest score rated Strong, the score would rise from 59.3 to about 66.7.
Rebuild cost: about €28,000 · Estimate
| Cost to rebuild | €9,300 to €47,000, for 155 to 491 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 59. 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: 15,085 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 action.index.block | 2 action.replicationstatedetails.UpdateReplicationStateDetailsRequest | 3 metadata.UpdateMetadataRequest | 4 metadata.store | 5 seqno.RemoteShardMetric | 6 task.CrossClusterReplicationTask | 7 task.shard.FollowerShardMetric | 8 action.autofollow.UpdateAutoFollowPatternRequest | 9 action.index | 10 action.replicationstatedetails | 11 action.setup | 12 metadata.state.ReplicationStateMetadata | 13 seqno | 14 task | 15 task.index.IndexReplicationTask | 16 action.autofollow.UpdateAutoFollowPatternRequest.Action | 17 action.changes | 18 task.shard | 19 task.index | 20 action.bulk | 21 action.bulk.BatchStopClusterStateAction | 22 action.bulk.BulkPauseReplicationAction | 23 action.bulk.BulkReplicationRequest | 24 action.bulk.BulkResumeReplicationAction | 25 task.bulk | 26 metadata.state | 27 metadata | 28 task.bulk.BulkReplicationTaskStatus | 29 org.opensearch.replication | 30 action.autofollow | 31 action.pause | 32 action.resume | 33 action.status | 34 action.update | 35 action.autofollow.AutoFollowClusterManagerNodeAction | 36 action.autofollow.UpdateAutoFollowPatternAction | 37 repository | 38 task.autofollow | 39 action.repository | 40 action.stats |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 action.index.block | ||||||||||||||||||||||||||||||||||||||||
| 2 action.replicationstatedetails.UpdateReplicationStateDetailsRequest | ||||||||||||||||||||||||||||||||||||||||
| 3 metadata.UpdateMetadataRequest | ||||||||||||||||||||||||||||||||||||||||
| 4 metadata.store | ||||||||||||||||||||||||||||||||||||||||
| 5 seqno.RemoteShardMetric | ||||||||||||||||||||||||||||||||||||||||
| 6 task.CrossClusterReplicationTask | ||||||||||||||||||||||||||||||||||||||||
| 7 task.shard.FollowerShardMetric | ||||||||||||||||||||||||||||||||||||||||
| 8 action.autofollow.UpdateAutoFollowPatternRequest | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 action.index | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 action.replicationstatedetails | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 action.setup | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 metadata.state.ReplicationStateMetadata | 3 | |||||||||||||||||||||||||||||||||||||||
| 13 seqno | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 task | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 15 task.index.IndexReplicationTask | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 action.autofollow.UpdateAutoFollowPatternRequest.Action | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 action.changes | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 task.shard | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 4 | ||||||||||||||||||||||||||||||||
| 19 task.index | 1 | 1 | 2 | 1 | 3 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 20 action.bulk | 10 | 1 | 2 | 1 | 5 | 5 | ||||||||||||||||||||||||||||||||||
| 21 action.bulk.BatchStopClusterStateAction | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 action.bulk.BulkPauseReplicationAction | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 action.bulk.BulkReplicationRequest | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 action.bulk.BulkResumeReplicationAction | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 task.bulk | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 26 metadata.state | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 metadata | 1 | 1 | 5 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 28 task.bulk.BulkReplicationTaskStatus | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 org.opensearch.replication | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 action.autofollow | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 action.pause | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 action.resume | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 action.status | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 action.update | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 action.autofollow.AutoFollowClusterManagerNodeAction | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 action.autofollow.UpdateAutoFollowPatternAction | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 repository | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 task.autofollow | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 39 action.repository | 3 | |||||||||||||||||||||||||||||||||||||||
| 40 action.stats | 3 | 3 | 3 | 2 | 1 | 3 |
8→30 action.autofollow.UpdateAutoFollowPatternRequest uses action.autofollow part of a loop✕
- Connections
- 1 pair of types, where a type in action.autofollow.UpdateAutoFollowPatternRequest uses a type in action.autofollow.
- The types involved
org.opensearch.replication.action.autofollow.UpdateAutoFollowPatternRequest.Companion→org.opensearch.replication.action.autofollow.UpdateAutoFollowPatternRequest
- Direction
- action.autofollow.UpdateAutoFollowPatternRequest uses action.autofollow, so a change to action.autofollow can break action.autofollow.UpdateAutoFollowPatternRequest, while a change to action.autofollow.UpdateAutoFollowPatternRequest can't break action.autofollow.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→27 action.index uses metadata part of a loop✕
- Connections
- 1 pair of types, where a type in action.index uses a type in metadata.
- The types involved
org.opensearch.replication.action.index.TransportReplicateIndexClusterManagerNodeAction→org.opensearch.replication.metadata.ReplicationMetadataManager
- Direction
- action.index uses metadata, so a change to metadata can break action.index, while a change to action.index can't break metadata.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→2 action.replicationstatedetails uses action.replicationstatedetails.UpdateReplicationStateDetailsRequest✕
- Connections
- 1 pair of types, where a type in action.replicationstatedetails uses a type in action.replicationstatedetails.UpdateReplicationStateDetailsRequest.
- The types involved
org.opensearch.replication.action.replicationstatedetails.UpdateReplicationStateDetailsRequest→org.opensearch.replication.action.replicationstatedetails.UpdateReplicationStateDetailsRequest.UpdateType
- Direction
- action.replicationstatedetails uses action.replicationstatedetails.UpdateReplicationStateDetailsRequest, so a change to action.replicationstatedetails.UpdateReplicationStateDetailsRequest can break action.replicationstatedetails, while a change to action.replicationstatedetails can't break action.replicationstatedetails.UpdateReplicationStateDetailsRequest.
- Position
- Below the diagonal: action.replicationstatedetails uses a module listed above it, which is the healthy direction.
11→4 action.setup uses metadata.store✕
- Connections
- 2 pairs of types, where a type in action.setup uses a type in metadata.store.
- The types involved
org.opensearch.replication.action.setup.SetupChecksRequest→org.opensearch.replication.metadata.store.ReplicationContextorg.opensearch.replication.action.setup.TransportSetupChecksAction→org.opensearch.replication.metadata.store.ReplicationContext
- Direction
- action.setup uses metadata.store, so a change to metadata.store can break action.setup, while a change to action.setup can't break metadata.store.
- Position
- Below the diagonal: action.setup uses a module listed above it, which is the healthy direction.
12→26 metadata.state.ReplicationStateMetadata uses metadata.state part of a loop✕
- Connections
- 3 pairs of types, where a type in metadata.state.ReplicationStateMetadata uses a type in metadata.state.
- The types involved
org.opensearch.replication.metadata.state.ReplicationStateMetadata.Builder→org.opensearch.replication.metadata.state.ReplicationStateMetadataorg.opensearch.replication.metadata.state.ReplicationStateMetadata.Companion→org.opensearch.replication.metadata.state.ReplicationStateMetadataorg.opensearch.replication.metadata.state.ReplicationStateMetadata.Diff→org.opensearch.replication.metadata.state.ReplicationStateMetadata
- Direction
- metadata.state.ReplicationStateMetadata uses metadata.state, so a change to metadata.state can break metadata.state.ReplicationStateMetadata, while a change to metadata.state.ReplicationStateMetadata can't break metadata.state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→4 seqno uses metadata.store✕
- Connections
- 1 pair of types, where a type in seqno uses a type in metadata.store.
- The types involved
org.opensearch.replication.seqno.RemoteClusterRetentionLeaseHelper→org.opensearch.replication.metadata.store.ReplicationMetadata
- Direction
- seqno uses metadata.store, so a change to metadata.store can break seqno, while a change to seqno can't break metadata.store.
- Position
- Below the diagonal: seqno uses a module listed above it, which is the healthy direction.
13→5 seqno uses seqno.RemoteShardMetric✕
- Connections
- 1 pair of types, where a type in seqno uses a type in seqno.RemoteShardMetric.
- The types involved
org.opensearch.replication.seqno.RemoteShardMetric→org.opensearch.replication.seqno.RemoteShardMetric.RemoteStats
- Direction
- seqno uses seqno.RemoteShardMetric, so a change to seqno.RemoteShardMetric can break seqno, while a change to seqno can't break seqno.RemoteShardMetric.
- Position
- Below the diagonal: seqno uses a module listed above it, which is the healthy direction.
14→4 task uses metadata.store✕
- Connections
- 1 pair of types, where a type in task uses a type in metadata.store.
- The types involved
org.opensearch.replication.task.CrossClusterReplicationTask→org.opensearch.replication.metadata.store.ReplicationMetadata
- Direction
- task uses metadata.store, so a change to metadata.store can break task, while a change to task can't break metadata.store.
- Position
- Below the diagonal: task uses a module listed above it, which is the healthy direction.
14→6 task uses task.CrossClusterReplicationTask✕
- Connections
- 1 pair of types, where a type in task uses a type in task.CrossClusterReplicationTask.
- The types involved
org.opensearch.replication.task.CrossClusterReplicationTask→org.opensearch.replication.task.CrossClusterReplicationTask.CrossClusterReplicationTaskResponse
- Direction
- task uses task.CrossClusterReplicationTask, so a change to task.CrossClusterReplicationTask can break task, while a change to task can't break task.CrossClusterReplicationTask.
- Position
- Below the diagonal: task uses a module listed above it, which is the healthy direction.
14→27 task uses metadata part of a loop✕
- Connections
- 1 pair of types, where a type in task uses a type in metadata.
- The types involved
org.opensearch.replication.task.CrossClusterReplicationTask→org.opensearch.replication.metadata.ReplicationMetadataManager
- Direction
- task uses metadata, so a change to metadata can break task, while a change to task can't break metadata.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→29 task uses org.opensearch.replication part of a loop✕
- Connections
- 1 pair of types, where a type in task uses a type in org.opensearch.replication.
- The types involved
org.opensearch.replication.task.CrossClusterReplicationTask→org.opensearch.replication.ReplicationSettings
- Direction
- task uses org.opensearch.replication, so a change to org.opensearch.replication can break task, while a change to task can't break org.opensearch.replication.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→6 task.index.IndexReplicationTask uses task.CrossClusterReplicationTask✕
- Connections
- 1 pair of types, where a type in task.index.IndexReplicationTask uses a type in task.CrossClusterReplicationTask.
- The types involved
org.opensearch.replication.task.index.IndexReplicationTask.IndexReplicationTaskResponse→org.opensearch.replication.task.CrossClusterReplicationTask.CrossClusterReplicationTaskResponse
- Direction
- task.index.IndexReplicationTask uses task.CrossClusterReplicationTask, so a change to task.CrossClusterReplicationTask can break task.index.IndexReplicationTask, while a change to task.index.IndexReplicationTask can't break task.CrossClusterReplicationTask.
- Position
- Below the diagonal: task.index.IndexReplicationTask uses a module listed above it, which is the healthy direction.
15→19 task.index.IndexReplicationTask uses task.index part of a loop✕
- Connections
- 1 pair of types, where a type in task.index.IndexReplicationTask uses a type in task.index.
- The types involved
org.opensearch.replication.task.index.IndexReplicationTask.IndexReplicationTaskResponse→org.opensearch.replication.task.index.IndexReplicationState
- Direction
- task.index.IndexReplicationTask uses task.index, so a change to task.index can break task.index.IndexReplicationTask, while a change to task.index.IndexReplicationTask can't break task.index.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→8 action.autofollow.UpdateAutoFollowPatternRequest.Action uses action.autofollow.UpdateAutoFollowPatternRequest✕
- Connections
- 2 pairs of types, where a type in action.autofollow.UpdateAutoFollowPatternRequest.Action uses a type in action.autofollow.UpdateAutoFollowPatternRequest.
- The types involved
org.opensearch.replication.action.autofollow.UpdateAutoFollowPatternRequest.Action.ADD→org.opensearch.replication.action.autofollow.UpdateAutoFollowPatternRequest.Actionorg.opensearch.replication.action.autofollow.UpdateAutoFollowPatternRequest.Action.REMOVE→org.opensearch.replication.action.autofollow.UpdateAutoFollowPatternRequest.Action
- Direction
- action.autofollow.UpdateAutoFollowPatternRequest.Action uses action.autofollow.UpdateAutoFollowPatternRequest, so a change to action.autofollow.UpdateAutoFollowPatternRequest can break action.autofollow.UpdateAutoFollowPatternRequest.Action, while a change to action.autofollow.UpdateAutoFollowPatternRequest.Action can't break action.autofollow.UpdateAutoFollowPatternRequest.
- Position
- Below the diagonal: action.autofollow.UpdateAutoFollowPatternRequest.Action uses a module listed above it, which is the healthy direction.
17→13 action.changes uses seqno✕
- Connections
- 2 pairs of types, where a type in action.changes uses a type in seqno.
- The types involved
org.opensearch.replication.action.changes.TransportGetChangesAction→org.opensearch.replication.seqno.RemoteClusterStatsorg.opensearch.replication.action.changes.TransportGetChangesAction→org.opensearch.replication.seqno.RemoteClusterTranslogService
- Direction
- action.changes uses seqno, so a change to seqno can break action.changes, while a change to action.changes can't break seqno.
- Position
- Below the diagonal: action.changes uses a module listed above it, which is the healthy direction.
18→4 task.shard uses metadata.store✕
- Connections
- 1 pair of types, where a type in task.shard uses a type in metadata.store.
- The types involved
org.opensearch.replication.task.shard.TranslogSequencer→org.opensearch.replication.metadata.store.ReplicationMetadata
- Direction
- task.shard uses metadata.store, so a change to metadata.store can break task.shard, while a change to task.shard can't break metadata.store.
- Position
- Below the diagonal: task.shard uses a module listed above it, which is the healthy direction.
18→6 task.shard uses task.CrossClusterReplicationTask✕
- Connections
- 1 pair of types, where a type in task.shard uses a type in task.CrossClusterReplicationTask.
- The types involved
org.opensearch.replication.task.shard.ShardReplicationTask→org.opensearch.replication.task.CrossClusterReplicationTask.CrossClusterReplicationTaskResponse
- Direction
- task.shard uses task.CrossClusterReplicationTask, so a change to task.CrossClusterReplicationTask can break task.shard, while a change to task.shard can't break task.CrossClusterReplicationTask.
- Position
- Below the diagonal: task.shard uses a module listed above it, which is the healthy direction.
18→7 task.shard uses task.shard.FollowerShardMetric✕
- Connections
- 1 pair of types, where a type in task.shard uses a type in task.shard.FollowerShardMetric.
- The types involved
org.opensearch.replication.task.shard.FollowerShardMetric→org.opensearch.replication.task.shard.FollowerShardMetric.FollowerStats
- Direction
- task.shard uses task.shard.FollowerShardMetric, so a change to task.shard.FollowerShardMetric can break task.shard, while a change to task.shard can't break task.shard.FollowerShardMetric.
- Position
- Below the diagonal: task.shard uses a module listed above it, which is the healthy direction.
18→13 task.shard uses seqno✕
- Connections
- 1 pair of types, where a type in task.shard uses a type in seqno.
- The types involved
org.opensearch.replication.task.shard.ShardReplicationTask→org.opensearch.replication.seqno.RemoteClusterRetentionLeaseHelper
- Direction
- task.shard uses seqno, so a change to seqno can break task.shard, while a change to task.shard can't break seqno.
- Position
- Below the diagonal: task.shard uses a module listed above it, which is the healthy direction.
18→14 task.shard uses task✕
- Connections
- 2 pairs of types, where a type in task.shard uses a type in task.
- The types involved
org.opensearch.replication.task.shard.ShardReplicationState→org.opensearch.replication.task.ReplicationStateorg.opensearch.replication.task.shard.ShardReplicationTask→org.opensearch.replication.task.CrossClusterReplicationTask
- Direction
- task.shard uses task, so a change to task can break task.shard, while a change to task.shard can't break task.
- Position
- Below the diagonal: task.shard uses a module listed above it, which is the healthy direction.
18→17 task.shard uses action.changes✕
- Connections
- 2 pairs of types, where a type in task.shard uses a type in action.changes.
- The types involved
org.opensearch.replication.task.shard.ShardReplicationTask→org.opensearch.replication.action.changes.GetChangesResponseorg.opensearch.replication.task.shard.TranslogSequencer→org.opensearch.replication.action.changes.GetChangesResponse
- Direction
- task.shard uses action.changes, so a change to action.changes can break task.shard, while a change to task.shard can't break action.changes.
- Position
- Below the diagonal: task.shard uses a module listed above it, which is the healthy direction.
18→27 task.shard uses metadata part of a loop✕
- Connections
- 2 pairs of types, where a type in task.shard uses a type in metadata.
- The types involved
org.opensearch.replication.task.shard.ShardReplicationExecutor→org.opensearch.replication.metadata.ReplicationMetadataManagerorg.opensearch.replication.task.shard.ShardReplicationTask→org.opensearch.replication.metadata.ReplicationMetadataManager
- Direction
- task.shard uses metadata, so a change to metadata can break task.shard, while a change to task.shard can't break metadata.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→29 task.shard uses org.opensearch.replication part of a loop✕
- Connections
- 4 pairs of types, where a type in task.shard uses a type in org.opensearch.replication.
- The types involved
org.opensearch.replication.task.shard.BatchSizeSettings→org.opensearch.replication.ReplicationSettingsorg.opensearch.replication.task.shard.ShardReplicationChangesTracker→org.opensearch.replication.ReplicationSettingsorg.opensearch.replication.task.shard.ShardReplicationExecutor→org.opensearch.replication.ReplicationSettingsorg.opensearch.replication.task.shard.ShardReplicationTask→org.opensearch.replication.ReplicationSettings
- Direction
- task.shard uses org.opensearch.replication, so a change to org.opensearch.replication can break task.shard, while a change to task.shard can't break org.opensearch.replication.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→6 task.index uses task.CrossClusterReplicationTask✕
- Connections
- 1 pair of types, where a type in task.index uses a type in task.CrossClusterReplicationTask.
- The types involved
org.opensearch.replication.task.index.IndexReplicationTask→org.opensearch.replication.task.CrossClusterReplicationTask.CrossClusterReplicationTaskResponse
- Direction
- task.index uses task.CrossClusterReplicationTask, so a change to task.CrossClusterReplicationTask can break task.index, while a change to task.index can't break task.CrossClusterReplicationTask.
- Position
- Below the diagonal: task.index uses a module listed above it, which is the healthy direction.
19→13 task.index uses seqno✕
- Connections
- 1 pair of types, where a type in task.index uses a type in seqno.
- The types involved
org.opensearch.replication.task.index.IndexReplicationTask→org.opensearch.replication.seqno.RemoteClusterRetentionLeaseHelper
- Direction
- task.index uses seqno, so a change to seqno can break task.index, while a change to task.index can't break seqno.
- Position
- Below the diagonal: task.index uses a module listed above it, which is the healthy direction.
19→14 task.index uses task✕
- Connections
- 2 pairs of types, where a type in task.index uses a type in task.
- The types involved
org.opensearch.replication.task.index.IndexReplicationState→org.opensearch.replication.task.ReplicationStateorg.opensearch.replication.task.index.IndexReplicationTask→org.opensearch.replication.task.CrossClusterReplicationTask
- Direction
- task.index uses task, so a change to task can break task.index, while a change to task.index can't break task.
- Position
- Below the diagonal: task.index uses a module listed above it, which is the healthy direction.
19→15 task.index uses task.index.IndexReplicationTask✕
- Connections
- 1 pair of types, where a type in task.index uses a type in task.index.IndexReplicationTask.
- The types involved
org.opensearch.replication.task.index.IndexReplicationTask→org.opensearch.replication.task.index.IndexReplicationTask.MetadataUpdate
- Direction
- task.index uses task.index.IndexReplicationTask, so a change to task.index.IndexReplicationTask can break task.index, while a change to task.index can't break task.index.IndexReplicationTask.
- Position
- Below the diagonal: task.index uses a module listed above it, which is the healthy direction.
19→18 task.index uses task.shard✕
- Connections
- 3 pairs of types, where a type in task.index uses a type in task.shard.
- The types involved
org.opensearch.replication.task.index.FailedState→org.opensearch.replication.task.shard.ShardReplicationParamsorg.opensearch.replication.task.index.FollowingState→org.opensearch.replication.task.shard.ShardReplicationParamsorg.opensearch.replication.task.index.IndexReplicationTask→org.opensearch.replication.task.shard.ShardReplicationParams
- Direction
- task.index uses task.shard, so a change to task.shard can break task.index, while a change to task.index can't break task.shard.
- Position
- Below the diagonal: task.index uses a module listed above it, which is the healthy direction.
19→27 task.index uses metadata part of a loop✕
- Connections
- 2 pairs of types, where a type in task.index uses a type in metadata.
- The types involved
org.opensearch.replication.task.index.IndexReplicationExecutor→org.opensearch.replication.metadata.ReplicationMetadataManagerorg.opensearch.replication.task.index.IndexReplicationTask→org.opensearch.replication.metadata.ReplicationMetadataManager
- Direction
- task.index uses metadata, so a change to metadata can break task.index, while a change to task.index can't break metadata.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→29 task.index uses org.opensearch.replication part of a loop✕
- Connections
- 2 pairs of types, where a type in task.index uses a type in org.opensearch.replication.
- The types involved
org.opensearch.replication.task.index.IndexReplicationExecutor→org.opensearch.replication.ReplicationSettingsorg.opensearch.replication.task.index.IndexReplicationTask→org.opensearch.replication.ReplicationSettings
- Direction
- task.index uses org.opensearch.replication, so a change to org.opensearch.replication can break task.index, while a change to task.index can't break org.opensearch.replication.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→9 action.bulk uses action.index✕
- Connections
- 10 pairs of types, where a type in action.bulk uses a type in action.index.
- The types involved
org.opensearch.replication.action.bulk.TransportBulkPauseReplicationAction→org.opensearch.replication.action.index.TransportReplicateIndexActionorg.opensearch.replication.action.bulk.TransportBulkPauseReplicationAction→org.opensearch.replication.action.index.TransportReplicateIndexClusterManagerNodeActionorg.opensearch.replication.action.bulk.TransportBulkReplicationAction→org.opensearch.replication.action.index.TransportReplicateIndexActionorg.opensearch.replication.action.bulk.TransportBulkReplicationAction→org.opensearch.replication.action.index.TransportReplicateIndexClusterManagerNodeActionorg.opensearch.replication.action.bulk.TransportBulkResumeReplicationAction→org.opensearch.replication.action.index.TransportReplicateIndexActionorg.opensearch.replication.action.bulk.TransportBulkResumeReplicationAction→org.opensearch.replication.action.index.TransportReplicateIndexClusterManagerNodeActionorg.opensearch.replication.action.bulk.TransportBulkStartReplicationAction→org.opensearch.replication.action.index.TransportReplicateIndexActionorg.opensearch.replication.action.bulk.TransportBulkStartReplicationAction→org.opensearch.replication.action.index.TransportReplicateIndexClusterManagerNodeActionorg.opensearch.replication.action.bulk.TransportBulkStopReplicationAction→org.opensearch.replication.action.index.TransportReplicateIndexActionorg.opensearch.replication.action.bulk.TransportBulkStopReplicationAction→org.opensearch.replication.action.index.TransportReplicateIndexClusterManagerNodeAction
- Direction
- action.bulk uses action.index, so a change to action.index can break action.bulk, while a change to action.bulk can't break action.index.
- Position
- Below the diagonal: action.bulk uses a module listed above it, which is the healthy direction.
20→19 action.bulk uses task.index✕
- Connections
- 1 pair of types, where a type in action.bulk uses a type in task.index.
- The types involved
org.opensearch.replication.action.bulk.TransportBulkReplicationAction→org.opensearch.replication.task.index.IndexReplicationParams
- Direction
- action.bulk uses task.index, so a change to task.index can break action.bulk, while a change to action.bulk can't break task.index.
- Position
- Below the diagonal: action.bulk uses a module listed above it, which is the healthy direction.
20→25 action.bulk uses task.bulk part of a loop✕
- Connections
- 2 pairs of types, where a type in action.bulk uses a type in task.bulk.
- The types involved
org.opensearch.replication.action.bulk.TransportBulkReplicationAction→org.opensearch.replication.task.bulk.BulkOperationTypeorg.opensearch.replication.action.bulk.TransportBulkReplicationAction→org.opensearch.replication.task.bulk.FailedIndex
- Direction
- action.bulk uses task.bulk, so a change to task.bulk can break action.bulk, while a change to action.bulk can't break task.bulk.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→26 action.bulk uses metadata.state part of a loop✕
- Connections
- 1 pair of types, where a type in action.bulk uses a type in metadata.state.
- The types involved
org.opensearch.replication.action.bulk.UpdateBulkTaskStateRequest→org.opensearch.replication.metadata.state.BulkTaskState
- Direction
- action.bulk uses metadata.state, so a change to metadata.state can break action.bulk, while a change to action.bulk can't break metadata.state.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→27 action.bulk uses metadata part of a loop✕
- Connections
- 5 pairs of types, where a type in action.bulk uses a type in metadata.
- The types involved
org.opensearch.replication.action.bulk.TransportBulkPauseReplicationAction→org.opensearch.replication.metadata.ReplicationMetadataManagerorg.opensearch.replication.action.bulk.TransportBulkReplicationAction→org.opensearch.replication.metadata.ReplicationMetadataManagerorg.opensearch.replication.action.bulk.TransportBulkResumeReplicationAction→org.opensearch.replication.metadata.ReplicationMetadataManagerorg.opensearch.replication.action.bulk.TransportBulkStartReplicationAction→org.opensearch.replication.metadata.ReplicationMetadataManagerorg.opensearch.replication.action.bulk.TransportBulkStopReplicationAction→org.opensearch.replication.metadata.ReplicationMetadataManager
- Direction
- action.bulk uses metadata, so a change to metadata can break action.bulk, while a change to action.bulk can't break metadata.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→29 action.bulk uses org.opensearch.replication part of a loop✕
- Connections
- 5 pairs of types, where a type in action.bulk uses a type in org.opensearch.replication.
- The types involved
org.opensearch.replication.action.bulk.TransportBulkPauseReplicationAction→org.opensearch.replication.ReplicationSettingsorg.opensearch.replication.action.bulk.TransportBulkReplicationAction→org.opensearch.replication.ReplicationSettingsorg.opensearch.replication.action.bulk.TransportBulkResumeReplicationAction→org.opensearch.replication.ReplicationSettingsorg.opensearch.replication.action.bulk.TransportBulkStartReplicationAction→org.opensearch.replication.ReplicationSettingsorg.opensearch.replication.action.bulk.TransportBulkStopReplicationAction→org.opensearch.replication.ReplicationSettings
- Direction
- action.bulk uses org.opensearch.replication, so a change to org.opensearch.replication can break action.bulk, while a change to action.bulk can't break org.opensearch.replication.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→20 action.bulk.BatchStopClusterStateAction uses action.bulk✕
- Connections
- 1 pair of types, where a type in action.bulk.BatchStopClusterStateAction uses a type in action.bulk.
- The types involved
org.opensearch.replication.action.bulk.BatchStopClusterStateAction.Companion→org.opensearch.replication.action.bulk.BatchStopClusterStateAction
- Direction
- action.bulk.BatchStopClusterStateAction uses action.bulk, so a change to action.bulk can break action.bulk.BatchStopClusterStateAction, while a change to action.bulk.BatchStopClusterStateAction can't break action.bulk.
- Position
- Below the diagonal: action.bulk.BatchStopClusterStateAction uses a module listed above it, which is the healthy direction.
22→20 action.bulk.BulkPauseReplicationAction uses action.bulk✕
- Connections
- 1 pair of types, where a type in action.bulk.BulkPauseReplicationAction uses a type in action.bulk.
- The types involved
org.opensearch.replication.action.bulk.BulkPauseReplicationAction.Companion→org.opensearch.replication.action.bulk.BulkPauseReplicationAction
- Direction
- action.bulk.BulkPauseReplicationAction uses action.bulk, so a change to action.bulk can break action.bulk.BulkPauseReplicationAction, while a change to action.bulk.BulkPauseReplicationAction can't break action.bulk.
- Position
- Below the diagonal: action.bulk.BulkPauseReplicationAction uses a module listed above it, which is the healthy direction.
23→20 action.bulk.BulkReplicationRequest uses action.bulk✕
- Connections
- 1 pair of types, where a type in action.bulk.BulkReplicationRequest uses a type in action.bulk.
- The types involved
org.opensearch.replication.action.bulk.BulkReplicationRequest.Companion→org.opensearch.replication.action.bulk.BulkReplicationRequest
- Direction
- action.bulk.BulkReplicationRequest uses action.bulk, so a change to action.bulk can break action.bulk.BulkReplicationRequest, while a change to action.bulk.BulkReplicationRequest can't break action.bulk.
- Position
- Below the diagonal: action.bulk.BulkReplicationRequest uses a module listed above it, which is the healthy direction.
24→20 action.bulk.BulkResumeReplicationAction uses action.bulk✕
- Connections
- 1 pair of types, where a type in action.bulk.BulkResumeReplicationAction uses a type in action.bulk.
- The types involved
org.opensearch.replication.action.bulk.BulkResumeReplicationAction.Companion→org.opensearch.replication.action.bulk.BulkResumeReplicationAction
- Direction
- action.bulk.BulkResumeReplicationAction uses action.bulk, so a change to action.bulk can break action.bulk.BulkResumeReplicationAction, while a change to action.bulk.BulkResumeReplicationAction can't break action.bulk.
- Position
- Below the diagonal: action.bulk.BulkResumeReplicationAction uses a module listed above it, which is the healthy direction.
25→14 task.bulk uses task✕
- Connections
- 1 pair of types, where a type in task.bulk uses a type in task.
- The types involved
org.opensearch.replication.task.bulk.BulkReplicationTask→org.opensearch.replication.task.ReplicationState
- Direction
- task.bulk uses task, so a change to task can break task.bulk, while a change to task.bulk can't break task.
- Position
- Below the diagonal: task.bulk uses a module listed above it, which is the healthy direction.
25→19 task.bulk uses task.index✕
- Connections
- 1 pair of types, where a type in task.bulk uses a type in task.index.
- The types involved
org.opensearch.replication.task.bulk.BulkReplicationTask→org.opensearch.replication.task.index.IndexReplicationState
- Direction
- task.bulk uses task.index, so a change to task.index can break task.bulk, while a change to task.bulk can't break task.index.
- Position
- Below the diagonal: task.bulk uses a module listed above it, which is the healthy direction.
25→20 task.bulk uses action.bulk✕
- Connections
- 2 pairs of types, where a type in task.bulk uses a type in action.bulk.
- The types involved
org.opensearch.replication.task.bulk.BulkReplicationTask→org.opensearch.replication.action.bulk.BulkReplicationRequestorg.opensearch.replication.task.bulk.BulkReplicationTask→org.opensearch.replication.action.bulk.TransportBulkReplicationAction
- Direction
- task.bulk uses action.bulk, so a change to action.bulk can break task.bulk, while a change to task.bulk can't break action.bulk.
- Position
- Below the diagonal: task.bulk uses a module listed above it, which is the healthy direction.
26→12 metadata.state uses metadata.state.ReplicationStateMetadata✕
- Connections
- 1 pair of types, where a type in metadata.state uses a type in metadata.state.ReplicationStateMetadata.
- The types involved
org.opensearch.replication.metadata.state.ReplicationStateMetadata→org.opensearch.replication.metadata.state.ReplicationStateMetadata.Diff
- Direction
- metadata.state uses metadata.state.ReplicationStateMetadata, so a change to metadata.state.ReplicationStateMetadata can break metadata.state, while a change to metadata.state can't break metadata.state.ReplicationStateMetadata.
- Position
- Below the diagonal: metadata.state uses a module listed above it, which is the healthy direction.
26→25 metadata.state uses task.bulk✕
- Connections
- 1 pair of types, where a type in metadata.state uses a type in task.bulk.
- The types involved
org.opensearch.replication.metadata.state.BulkTaskState→org.opensearch.replication.task.bulk.FailedIndex
- Direction
- metadata.state uses task.bulk, so a change to task.bulk can break metadata.state, while a change to metadata.state can't break task.bulk.
- Position
- Below the diagonal: metadata.state uses a module listed above it, which is the healthy direction.
27→1 metadata uses action.index.block✕
- Connections
- 1 pair of types, where a type in metadata uses a type in action.index.block.
- The types involved
org.opensearch.replication.metadata.UpdateIndexBlockTaskExecutor→org.opensearch.replication.action.index.block.UpdateIndexBlockRequest
- Direction
- metadata uses action.index.block, so a change to action.index.block can break metadata, while a change to metadata can't break action.index.block.
- Position
- Below the diagonal: metadata uses a module listed above it, which is the healthy direction.
27→3 metadata uses metadata.UpdateMetadataRequest✕
- Connections
- 1 pair of types, where a type in metadata uses a type in metadata.UpdateMetadataRequest.
- The types involved
org.opensearch.replication.metadata.UpdateMetadataRequest→org.opensearch.replication.metadata.UpdateMetadataRequest.Type
- Direction
- metadata uses metadata.UpdateMetadataRequest, so a change to metadata.UpdateMetadataRequest can break metadata, while a change to metadata can't break metadata.UpdateMetadataRequest.
- Position
- Below the diagonal: metadata uses a module listed above it, which is the healthy direction.
27→4 metadata uses metadata.store✕
- Connections
- 5 pairs of types, where a type in metadata uses a type in metadata.store.
- The types involved
org.opensearch.replication.metadata.ReplicationMetadataManager→org.opensearch.replication.metadata.store.AddReplicationMetadataRequestorg.opensearch.replication.metadata.ReplicationMetadataManager→org.opensearch.replication.metadata.store.DeleteReplicationMetadataRequestorg.opensearch.replication.metadata.ReplicationMetadataManager→org.opensearch.replication.metadata.store.ReplicationMetadataorg.opensearch.replication.metadata.ReplicationMetadataManager→org.opensearch.replication.metadata.store.ReplicationMetadataStoreorg.opensearch.replication.metadata.ReplicationMetadataManager→org.opensearch.replication.metadata.store.UpdateReplicationMetadataRequest
- Direction
- metadata uses metadata.store, so a change to metadata.store can break metadata, while a change to metadata can't break metadata.store.
- Position
- Below the diagonal: metadata uses a module listed above it, which is the healthy direction.
27→10 metadata uses action.replicationstatedetails✕
- Connections
- 1 pair of types, where a type in metadata uses a type in action.replicationstatedetails.
- The types involved
org.opensearch.replication.metadata.UpdateReplicationStateDetailsTaskExecutor→org.opensearch.replication.action.replicationstatedetails.UpdateReplicationStateDetailsRequest
- Direction
- metadata uses action.replicationstatedetails, so a change to action.replicationstatedetails can break metadata, while a change to metadata can't break action.replicationstatedetails.
- Position
- Below the diagonal: metadata uses a module listed above it, which is the healthy direction.
27→26 metadata uses metadata.state✕
- Connections
- 2 pairs of types, where a type in metadata uses a type in metadata.state.
- The types involved
org.opensearch.replication.metadata.UpdateReplicationMetadata→org.opensearch.replication.metadata.state.ReplicationStateMetadataorg.opensearch.replication.metadata.UpdateReplicationStateDetailsTaskExecutor→org.opensearch.replication.metadata.state.ReplicationStateMetadata
- Direction
- metadata uses metadata.state, so a change to metadata.state can break metadata, while a change to metadata can't break metadata.state.
- Position
- Below the diagonal: metadata uses a module listed above it, which is the healthy direction.
28→25 task.bulk.BulkReplicationTaskStatus uses task.bulk✕
- Connections
- 1 pair of types, where a type in task.bulk.BulkReplicationTaskStatus uses a type in task.bulk.
- The types involved
org.opensearch.replication.task.bulk.BulkReplicationTaskStatus.Companion→org.opensearch.replication.task.bulk.BulkReplicationTaskStatus
- Direction
- task.bulk.BulkReplicationTaskStatus uses task.bulk, so a change to task.bulk can break task.bulk.BulkReplicationTaskStatus, while a change to task.bulk.BulkReplicationTaskStatus can't break task.bulk.
- Position
- Below the diagonal: task.bulk.BulkReplicationTaskStatus uses a module listed above it, which is the healthy direction.
28→26 task.bulk.BulkReplicationTaskStatus uses metadata.state✕
- Connections
- 1 pair of types, where a type in task.bulk.BulkReplicationTaskStatus uses a type in metadata.state.
- The types involved
org.opensearch.replication.task.bulk.BulkReplicationTaskStatus.Companion→org.opensearch.replication.metadata.state.BulkTaskState
- Direction
- task.bulk.BulkReplicationTaskStatus uses metadata.state, so a change to metadata.state can break task.bulk.BulkReplicationTaskStatus, while a change to task.bulk.BulkReplicationTaskStatus can't break metadata.state.
- Position
- Below the diagonal: task.bulk.BulkReplicationTaskStatus uses a module listed above it, which is the healthy direction.
29→18 org.opensearch.replication uses task.shard✕
- Connections
- 1 pair of types, where a type in org.opensearch.replication uses a type in task.shard.
- The types involved
org.opensearch.replication.ReplicationPlugin→org.opensearch.replication.task.shard.FollowerClusterStats
- Direction
- org.opensearch.replication uses task.shard, so a change to task.shard can break org.opensearch.replication, while a change to org.opensearch.replication can't break task.shard.
- Position
- Below the diagonal: org.opensearch.replication uses a module listed above it, which is the healthy direction.
29→27 org.opensearch.replication uses metadata✕
- Connections
- 1 pair of types, where a type in org.opensearch.replication uses a type in metadata.
- The types involved
org.opensearch.replication.ReplicationPlugin→org.opensearch.replication.metadata.ReplicationMetadataManager
- Direction
- org.opensearch.replication uses metadata, so a change to metadata can break org.opensearch.replication, while a change to org.opensearch.replication can't break metadata.
- Position
- Below the diagonal: org.opensearch.replication uses a module listed above it, which is the healthy direction.
30→8 action.autofollow uses action.autofollow.UpdateAutoFollowPatternRequest✕
- Connections
- 1 pair of types, where a type in action.autofollow uses a type in action.autofollow.UpdateAutoFollowPatternRequest.
- The types involved
org.opensearch.replication.action.autofollow.UpdateAutoFollowPatternRequest→org.opensearch.replication.action.autofollow.UpdateAutoFollowPatternRequest.Action
- Direction
- action.autofollow uses action.autofollow.UpdateAutoFollowPatternRequest, so a change to action.autofollow.UpdateAutoFollowPatternRequest can break action.autofollow, while a change to action.autofollow can't break action.autofollow.UpdateAutoFollowPatternRequest.
- Position
- Below the diagonal: action.autofollow uses a module listed above it, which is the healthy direction.
30→27 action.autofollow uses metadata✕
- Connections
- 1 pair of types, where a type in action.autofollow uses a type in metadata.
- The types involved
org.opensearch.replication.action.autofollow.TransportAutoFollowClusterManagerNodeAction→org.opensearch.replication.metadata.ReplicationMetadataManager
- Direction
- action.autofollow uses metadata, so a change to metadata can break action.autofollow, while a change to action.autofollow can't break metadata.
- Position
- Below the diagonal: action.autofollow uses a module listed above it, which is the healthy direction.
31→27 action.pause uses metadata✕
- Connections
- 1 pair of types, where a type in action.pause uses a type in metadata.
- The types involved
org.opensearch.replication.action.pause.TransportPauseIndexReplicationAction→org.opensearch.replication.metadata.ReplicationMetadataManager
- Direction
- action.pause uses metadata, so a change to metadata can break action.pause, while a change to action.pause can't break metadata.
- Position
- Below the diagonal: action.pause uses a module listed above it, which is the healthy direction.
32→4 action.resume uses metadata.store✕
- Connections
- 1 pair of types, where a type in action.resume uses a type in metadata.store.
- The types involved
org.opensearch.replication.action.resume.TransportResumeIndexReplicationAction→org.opensearch.replication.metadata.store.ReplicationMetadata
- Direction
- action.resume uses metadata.store, so a change to metadata.store can break action.resume, while a change to action.resume can't break metadata.store.
- Position
- Below the diagonal: action.resume uses a module listed above it, which is the healthy direction.
32→19 action.resume uses task.index✕
- Connections
- 1 pair of types, where a type in action.resume uses a type in task.index.
- The types involved
org.opensearch.replication.action.resume.TransportResumeIndexReplicationAction→org.opensearch.replication.task.index.IndexReplicationParams
- Direction
- action.resume uses task.index, so a change to task.index can break action.resume, while a change to action.resume can't break task.index.
- Position
- Below the diagonal: action.resume uses a module listed above it, which is the healthy direction.
32→27 action.resume uses metadata✕
- Connections
- 1 pair of types, where a type in action.resume uses a type in metadata.
- The types involved
org.opensearch.replication.action.resume.TransportResumeIndexReplicationAction→org.opensearch.replication.metadata.ReplicationMetadataManager
- Direction
- action.resume uses metadata, so a change to metadata can break action.resume, while a change to action.resume can't break metadata.
- Position
- Below the diagonal: action.resume uses a module listed above it, which is the healthy direction.
33→27 action.status uses metadata✕
- Connections
- 1 pair of types, where a type in action.status uses a type in metadata.
- The types involved
org.opensearch.replication.action.status.TransportReplicationStatusAction→org.opensearch.replication.metadata.ReplicationMetadataManager
- Direction
- action.status uses metadata, so a change to metadata can break action.status, while a change to action.status can't break metadata.
- Position
- Below the diagonal: action.status uses a module listed above it, which is the healthy direction.
34→27 action.update uses metadata✕
- Connections
- 1 pair of types, where a type in action.update uses a type in metadata.
- The types involved
org.opensearch.replication.action.update.TransportUpdateIndexReplicationAction→org.opensearch.replication.metadata.ReplicationMetadataManager
- Direction
- action.update uses metadata, so a change to metadata can break action.update, while a change to action.update can't break metadata.
- Position
- Below the diagonal: action.update uses a module listed above it, which is the healthy direction.
35→30 action.autofollow.AutoFollowClusterManagerNodeAction uses action.autofollow✕
- Connections
- 1 pair of types, where a type in action.autofollow.AutoFollowClusterManagerNodeAction uses a type in action.autofollow.
- The types involved
org.opensearch.replication.action.autofollow.AutoFollowClusterManagerNodeAction.Companion→org.opensearch.replication.action.autofollow.AutoFollowClusterManagerNodeAction
- Direction
- action.autofollow.AutoFollowClusterManagerNodeAction uses action.autofollow, so a change to action.autofollow can break action.autofollow.AutoFollowClusterManagerNodeAction, while a change to action.autofollow.AutoFollowClusterManagerNodeAction can't break action.autofollow.
- Position
- Below the diagonal: action.autofollow.AutoFollowClusterManagerNodeAction uses a module listed above it, which is the healthy direction.
36→30 action.autofollow.UpdateAutoFollowPatternAction uses action.autofollow✕
- Connections
- 1 pair of types, where a type in action.autofollow.UpdateAutoFollowPatternAction uses a type in action.autofollow.
- The types involved
org.opensearch.replication.action.autofollow.UpdateAutoFollowPatternAction.Companion→org.opensearch.replication.action.autofollow.UpdateAutoFollowPatternAction
- Direction
- action.autofollow.UpdateAutoFollowPatternAction uses action.autofollow, so a change to action.autofollow can break action.autofollow.UpdateAutoFollowPatternAction, while a change to action.autofollow.UpdateAutoFollowPatternAction can't break action.autofollow.
- Position
- Below the diagonal: action.autofollow.UpdateAutoFollowPatternAction uses a module listed above it, which is the healthy direction.
37→4 repository uses metadata.store✕
- Connections
- 2 pairs of types, where a type in repository uses a type in metadata.store.
- The types involved
org.opensearch.replication.repository.RemoteClusterMultiChunkTransfer→org.opensearch.replication.metadata.store.ReplicationMetadataorg.opensearch.replication.repository.RemoteClusterRepository→org.opensearch.replication.metadata.store.ReplicationMetadata
- Direction
- repository uses metadata.store, so a change to metadata.store can break repository, while a change to repository can't break metadata.store.
- Position
- Below the diagonal: repository uses a module listed above it, which is the healthy direction.
37→27 repository uses metadata✕
- Connections
- 1 pair of types, where a type in repository uses a type in metadata.
- The types involved
org.opensearch.replication.repository.RemoteClusterRepository→org.opensearch.replication.metadata.ReplicationMetadataManager
- Direction
- repository uses metadata, so a change to metadata can break repository, while a change to repository can't break metadata.
- Position
- Below the diagonal: repository uses a module listed above it, which is the healthy direction.
37→29 repository uses org.opensearch.replication✕
- Connections
- 1 pair of types, where a type in repository uses a type in org.opensearch.replication.
- The types involved
org.opensearch.replication.repository.RemoteClusterRepository→org.opensearch.replication.ReplicationSettings
- Direction
- repository uses org.opensearch.replication, so a change to org.opensearch.replication can break repository, while a change to repository can't break org.opensearch.replication.
- Position
- Below the diagonal: repository uses a module listed above it, which is the healthy direction.
37→39 repository uses action.repository part of a loop✕
- Connections
- 1 pair of types, where a type in repository uses a type in action.repository.
- The types involved
org.opensearch.replication.repository.RemoteClusterRestoreLeaderService→org.opensearch.replication.action.repository.RemoteClusterRepositoryRequest
- Direction
- repository uses action.repository, so a change to action.repository can break repository, while a change to repository can't break action.repository.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
38→6 task.autofollow uses task.CrossClusterReplicationTask✕
- Connections
- 1 pair of types, where a type in task.autofollow uses a type in task.CrossClusterReplicationTask.
- The types involved
org.opensearch.replication.task.autofollow.AutoFollowTask→org.opensearch.replication.task.CrossClusterReplicationTask.CrossClusterReplicationTaskResponse
- Direction
- task.autofollow uses task.CrossClusterReplicationTask, so a change to task.CrossClusterReplicationTask can break task.autofollow, while a change to task.autofollow can't break task.CrossClusterReplicationTask.
- Position
- Below the diagonal: task.autofollow uses a module listed above it, which is the healthy direction.
38→14 task.autofollow uses task✕
- Connections
- 1 pair of types, where a type in task.autofollow uses a type in task.
- The types involved
org.opensearch.replication.task.autofollow.AutoFollowTask→org.opensearch.replication.task.CrossClusterReplicationTask
- Direction
- task.autofollow uses task, so a change to task can break task.autofollow, while a change to task.autofollow can't break task.
- Position
- Below the diagonal: task.autofollow uses a module listed above it, which is the healthy direction.
38→27 task.autofollow uses metadata✕
- Connections
- 2 pairs of types, where a type in task.autofollow uses a type in metadata.
- The types involved
org.opensearch.replication.task.autofollow.AutoFollowExecutor→org.opensearch.replication.metadata.ReplicationMetadataManagerorg.opensearch.replication.task.autofollow.AutoFollowTask→org.opensearch.replication.metadata.ReplicationMetadataManager
- Direction
- task.autofollow uses metadata, so a change to metadata can break task.autofollow, while a change to task.autofollow can't break metadata.
- Position
- Below the diagonal: task.autofollow uses a module listed above it, which is the healthy direction.
38→29 task.autofollow uses org.opensearch.replication✕
- Connections
- 2 pairs of types, where a type in task.autofollow uses a type in org.opensearch.replication.
- The types involved
org.opensearch.replication.task.autofollow.AutoFollowExecutor→org.opensearch.replication.ReplicationSettingsorg.opensearch.replication.task.autofollow.AutoFollowTask→org.opensearch.replication.ReplicationSettings
- Direction
- task.autofollow uses org.opensearch.replication, so a change to org.opensearch.replication can break task.autofollow, while a change to task.autofollow can't break org.opensearch.replication.
- Position
- Below the diagonal: task.autofollow uses a module listed above it, which is the healthy direction.
39→37 action.repository uses repository✕
- Connections
- 3 pairs of types, where a type in action.repository uses a type in repository.
- The types involved
org.opensearch.replication.action.repository.TransportGetFileChunkAction→org.opensearch.replication.repository.RemoteClusterRestoreLeaderServiceorg.opensearch.replication.action.repository.TransportGetStoreMetadataAction→org.opensearch.replication.repository.RemoteClusterRestoreLeaderServiceorg.opensearch.replication.action.repository.TransportReleaseLeaderResourcesAction→org.opensearch.replication.repository.RemoteClusterRestoreLeaderService
- Direction
- action.repository uses repository, so a change to repository can break action.repository, while a change to action.repository can't break repository.
- Position
- Below the diagonal: action.repository uses a module listed above it, which is the healthy direction.
40→5 action.stats uses seqno.RemoteShardMetric✕
- Connections
- 3 pairs of types, where a type in action.stats uses a type in seqno.RemoteShardMetric.
- The types involved
org.opensearch.replication.action.stats.LeaderNodeStatsResponse→org.opensearch.replication.seqno.RemoteShardMetric.RemoteStatsorg.opensearch.replication.action.stats.LeaderStatsResponse→org.opensearch.replication.seqno.RemoteShardMetric.RemoteStatsorg.opensearch.replication.action.stats.LeaderStatsResponse→org.opensearch.replication.seqno.RemoteShardMetric.RemoteStatsFrag
- Direction
- action.stats uses seqno.RemoteShardMetric, so a change to seqno.RemoteShardMetric can break action.stats, while a change to action.stats can't break seqno.RemoteShardMetric.
- Position
- Below the diagonal: action.stats uses a module listed above it, which is the healthy direction.
40→7 action.stats uses task.shard.FollowerShardMetric✕
- Connections
- 3 pairs of types, where a type in action.stats uses a type in task.shard.FollowerShardMetric.
- The types involved
org.opensearch.replication.action.stats.FollowerNodeStatsResponse→org.opensearch.replication.task.shard.FollowerShardMetric.FollowerStatsorg.opensearch.replication.action.stats.FollowerStatsResponse→org.opensearch.replication.task.shard.FollowerShardMetric.FollowerStatsorg.opensearch.replication.action.stats.FollowerStatsResponse→org.opensearch.replication.task.shard.FollowerShardMetric.FollowerStatsFragment
- Direction
- action.stats uses task.shard.FollowerShardMetric, so a change to task.shard.FollowerShardMetric can break action.stats, while a change to action.stats can't break task.shard.FollowerShardMetric.
- Position
- Below the diagonal: action.stats uses a module listed above it, which is the healthy direction.
40→13 action.stats uses seqno✕
- Connections
- 3 pairs of types, where a type in action.stats uses a type in seqno.
- The types involved
org.opensearch.replication.action.stats.LeaderNodeStatsResponse→org.opensearch.replication.seqno.RemoteShardMetricorg.opensearch.replication.action.stats.TransportFollowerStatsAction→org.opensearch.replication.seqno.RemoteClusterStatsorg.opensearch.replication.action.stats.TransportLeaderStatsAction→org.opensearch.replication.seqno.RemoteClusterStats
- Direction
- action.stats uses seqno, so a change to seqno can break action.stats, while a change to action.stats can't break seqno.
- Position
- Below the diagonal: action.stats uses a module listed above it, which is the healthy direction.
40→18 action.stats uses task.shard✕
- Connections
- 2 pairs of types, where a type in action.stats uses a type in task.shard.
- The types involved
org.opensearch.replication.action.stats.FollowerNodeStatsResponse→org.opensearch.replication.task.shard.FollowerShardMetricorg.opensearch.replication.action.stats.TransportFollowerStatsAction→org.opensearch.replication.task.shard.FollowerClusterStats
- Direction
- action.stats uses task.shard, so a change to task.shard can break action.stats, while a change to action.stats can't break task.shard.
- Position
- Below the diagonal: action.stats uses a module listed above it, which is the healthy direction.
40→26 action.stats uses metadata.state✕
- Connections
- 1 pair of types, where a type in action.stats uses a type in metadata.state.
- The types involved
org.opensearch.replication.action.stats.FollowerStatsResponse→org.opensearch.replication.metadata.state.ReplicationStateMetadata
- Direction
- action.stats uses metadata.state, so a change to metadata.state can break action.stats, while a change to action.stats can't break metadata.state.
- Position
- Below the diagonal: action.stats uses a module listed above it, which is the healthy direction.
40→38 action.stats uses task.autofollow✕
- Connections
- 3 pairs of types, where a type in action.stats uses a type in task.autofollow.
- The types involved
org.opensearch.replication.action.stats.AutoFollowStatsResponse→org.opensearch.replication.task.autofollow.AutoFollowStatorg.opensearch.replication.action.stats.AutoFollowStatsResponses→org.opensearch.replication.task.autofollow.AutoFollowStatorg.opensearch.replication.action.stats.TransportAutoFollowStatsAction→org.opensearch.replication.task.autofollow.AutoFollowTask
- Direction
- action.stats uses task.autofollow, so a change to task.autofollow can break action.stats, while a change to action.stats can't break task.autofollow.
- Position
- Below the diagonal: action.stats 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 | 13 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 11 | High / Critical |
Roadmap
Top priorities: Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it; Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +7.8 pts | Medium | Security & performance tooling |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +4.0 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +4.0 pts | Medium | Release Hygiene |
| 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. | +2.5 pts | Medium | Architecture documentation |
| Interpolated log message defeats structured logging | +2.1 pts | Medium | Structured logging |
| Resolve the 28 Orphaned file finding(s) in Knowledge Freshness — start with ReplicationMetadataStore.kt, TransportUpdateMetadataAction.kt, RemoteClusterRetentionLeaseHelper.kt. | +1.6 pts | Medium | Knowledge Freshness |
| Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +0.4 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +0.4 pts | Low | Bus Factor |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/main/kotlin/org/opensearch/replication/action/replay/TransportReplayChangesAction.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/kotlin/org/opensearch/replication/repository/RemoteClusterRepository.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/main/kotlin/org/opensearch/replication/metadata/ReplicationMetadataManager.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/main/kotlin/org/opensearch/replication/task/index/IndexReplicationTask.kt | 7.0 | Mixed | Cyclomatic Complexity: IndexReplicationTask.pollForMetadata (cyclomatic 28) |
| src/main/kotlin/org/opensearch/replication/action/bulk/TransportBulkReplicationAction.kt | 7.0 | Mixed | Cyclomatic Complexity: TransportBulkReplicationAction.executeBatchStart (cyclomatic 26) |
| src/main/kotlin/org/opensearch/replication/action/changes/TransportGetChangesAction.kt | 7.3 | Mixed | Explicit Debt: TodoComment |
| src/main/kotlin/org/opensearch/replication/metadata/state/BulkReplicationTaskMetadata.kt | 7.4 | Mixed | Code Duplication: Edited copy of a member (16 corresponding lines) |
| src/main/kotlin/org/opensearch/replication/task/bulk/BulkReplicationTask.kt | 7.8 | Mixed | Cyclomatic Complexity: BulkReplicationTask.processStartResume (cyclomatic 32) |
| src/main/kotlin/org/opensearch/replication/rest/BulkReplicationStatusHandler.kt | 7.8 | Mixed | Cyclomatic Complexity: BulkReplicationStatusHandler.prepareRequest (cyclomatic 17) |
| src/main/kotlin/org/opensearch/replication/metadata/TransportUpdateMetadataAction.kt | 7.8 | Mixed | Cognitive Complexity: TransportUpdateMetadataAction.performAliasUpdate (cognitive 19) |
| src/main/kotlin/org/opensearch/replication/action/autofollow/UpdateAutoFollowPatternRequest.kt | 7.8 | Mixed | Cognitive Complexity: UpdateAutoFollowPatternRequest.validate (cognitive 16) |
| src/main/kotlin/org/opensearch/replication/action/index/TransportReplicateIndexAction.kt | 7.8 | Mixed | Code Duplication: Edited copy of a member (14 corresponding lines) |
| src/main/kotlin/org/opensearch/replication/task/index/IndexReplicationState.kt | 7.8 | Mixed | Code Duplication: Edited copy of a member (17 corresponding lines) |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
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 43 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 43 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, 169 of 181 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: this repository's production source spans .py, .kt, and our analyzer cannot run the .kt test suite(s) — so no coverage was collected for the repository as a whole. The Python half did build and run, and its own line coverage came back at 1.3% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
- 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 (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because ci.opensearch.org — the registry that answers it — was asked and did not reply (the build stopped because ci.opensearch.org, a repository this project declares, refused it with HTTP 403 — what this scan's egress allowlist returns for a host that is not on it, so the dependency graph was not resolved). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add ci.opensearch.org to the allowlist and re-run — not to build anything.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- 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.
- D30 Dependency Vulnerabilities — 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. Osv: osv-scanner exited 1 with no findings — dependency CVEs were not measured. 'osv-scanner' exited 1 and produced no findings, and that exit code has no documented repo-side meaning — so this run measured nothing, and nothing here is a statement about the 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/kotlin/org/opensearch/replication/seqno/RemoteClusterRetentionLeaseHelper.kt` 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.
- D43 Malicious Dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Osv: osv-scanner exited 1 with no findings — dependency CVEs were not measured. 'osv-scanner' exited 1 and produced no findings, and that exit code has no documented repo-side meaning — so this run measured nothing, and nothing here is a statement about the repository.
- 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.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's Kotlin, Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust was found, and this repository's Kotlin, Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X4 Structured logging — 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. 233 further occurrence(s) are not listed individually; the score already reflects all 273.
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.
- 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.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
6 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was BulkReplicationTask.processStartResume at 32.
What to do
- Bring the 6 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with BulkReplicationTask.processStartResume (cyclomatic 32), IndexReplicationTask.pollForMetadata (cyclomatic 28), TransportBulkReplicationAction.executeBatchStart (cyclomatic 26). — 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 6 together lifts Cyclomatic Complexity from 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
14 method(s) exceeded the cognitive complexity threshold of 15; the worst was IndexReplicationTask.pollForMetadata at 78.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with IndexReplicationTask.pollForMetadata (cognitive 78). — Refactoring it lifts Cognitive Complexity from 7.2 to about 7.4/10.
D3 · God Classes
8 god class(es) detected.
What to do
- Resolve the 2 ClassTooLong finding(s) in God Classes — start with IndexReplicationTask.kt, TransportBulkReplicationAction.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with IndexReplicationTask.kt, TransportBulkReplicationAction.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 MethodTooLong finding(s) in God Classes — start with TransportBulkReplicationAction.kt, IndexReplicationTask.kt. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
7 duplicated block group(s) detected. 3.4 % of the production lines (515 of 15,085) are in a reported copy. A further 16 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 3 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with ReplicationEngine.kt, ReplicationMetadataManager.kt, AutoFollowClusterManagerNodeRequest.kt. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copies of one member (3 members, 13+ corresponding lines) finding(s) in Code Duplication — start with AutoFollowStatsHandler.kt, ReplicateIndexHandler.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with BulkReplicationTaskMetadata.kt, UpdateAutoFollowPatternRequest.kt. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
0 of 73 classes have LCOM4 above 3.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 6 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. 10 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. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
8 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/main/kotlin/org/opensearch/replication/util/Coroutines.kt. Counted over 80 of the 163 production source files in this repository: 77 are under the ~2,400-byte size floor this dimension measures over, and the remaining 6 have no attributable history left to measure.
D17 · Explicit Debt
22 deducted task-comment markers across 15085 LoC (0.1/KLoC) → score 9.7. 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 21 TodoComment finding(s) in Explicit Debt — start with REDACTED (4), TransportReplayChangesAction.kt (2), TransportGetChangesAction.kt (2). — One of this dimension's main actionable groups (21 warning-level).
- Resolve the 1 HackComment finding(s) in Explicit Debt — start with IndexReplicationTaskTests.kt. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 4 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 2 build units (Gradle, Python) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle. — 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)
13 finding(s): 0 critical, 9 high, 1 medium, 3 low. 7 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `gradlew` (line 74, line 178) — 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 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- No action in Static Analysis (SAST) — all 7 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (7 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
28 of 86 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/main/kotlin/org/opensearch/replication/metadata/store/ReplicationMetadataStore.kt. Counted over 86 of the 163 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 28 Orphaned file finding(s) in Knowledge Freshness — start with ReplicationMetadataStore.kt, TransportUpdateMetadataAction.kt, RemoteClusterRetentionLeaseHelper.kt. — One of this dimension's main actionable groups (28 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
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 25 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
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- CONTRIBUTING.md links to `LICENSE.txt`, but `LICENSE.txt` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:56
What to do
- Reconcile the README with reality: CONTRIBUTING.md links to `LICENSE.txt`, but `LICENSE.txt` does not exist.
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 10 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
- `build.gradle` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — build.gradle:82
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
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
- `restoreShardUsingMultiChunkTransfer` is async and calls Thread.sleep — a blocking call inside async code stalls the coroutine's thread, and every coroutine dispatched to it for as long as it runs. — src/main/kotlin/org/opensearch/replication/repository/RemoteClusterRepository.kt:286
What to do
- Kotlin: call the suspend function directly instead of wrapping it in runBlocking, use delay() instead of Thread.sleep, and move unavoidable blocking I/O into withContext(Dispatchers.IO).
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — src/main/kotlin/org/opensearch/replication/task/bulk/BulkReplicationTask.kt:299
- `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — src/main/kotlin/org/opensearch/replication/seqno/RemoteClusterRetentionLeaseHelper.kt:78
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×2) — src/main/kotlin/org/opensearch/replication/metadata/ReplicationMetadataManager.kt:141, src/main/kotlin/org/opensearch/replication/action/bulk/TransportBulkReplicationAction.kt:555
What to do
- Swallowed exception (caught, then discarded)
X4 · Structured logging
- `error` at line 20 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — perf_workflow/run_perf_suite/perf_runner.py:20
- `info` at line 81 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — perf_workflow/run_perf_suite/run_perf_suite.py:81
- `info` at line 88 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — perf_workflow/run_perf_suite/run_perf_suite.py:88
- `debug` at line 118 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/util/Extensions.kt:118
- `warn` at line 141 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/util/Extensions.kt:141
- `warn` at line 182 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/util/Extensions.kt:182
- `error` at line 187 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/util/Extensions.kt:187
- `warn` at line 73 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/util/SecurityContext.kt:73
- `warn` at line 85 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/util/SecurityContext.kt:85
- `info` at line 90 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:90
- `info` at line 94 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:94
- `info` at line 98 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:98
- `info` at line 121 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:121
- `warn` at line 134 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:134
- `info` at line 139 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:139
- `info` at line 145 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:145
- `info` at line 160 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:160
- `info` at line 164 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:164
- `info` at line 168 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:168
- `info` at line 175 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:175
- `info` at line 186 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:186
- `info` at line 189 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:189
- `debug` at line 192 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:192
- `debug` at line 196 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:196
- `error` at line 199 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:199
- `error` at line 218 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:218
- `error` at line 100 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/task/CrossClusterReplicationTask.kt:100
- `info` at line 104 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/task/CrossClusterReplicationTask.kt:104
- `info` at line 125 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/task/CrossClusterReplicationTask.kt:125
- `warn` at line 128 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/task/CrossClusterReplicationTask.kt:128
- `error` at line 136 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/task/CrossClusterReplicationTask.kt:136
- `error` at line 214 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/task/CrossClusterReplicationTask.kt:214
- `error` at line 64 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/task/shard/ShardReplicationExecutor.kt:64
- `info` at line 71 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/task/shard/ShardReplicationExecutor.kt:71
- `debug` at line 206 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/task/shard/ShardReplicationTask.kt:206
- `error` at line 210 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/task/shard/ShardReplicationTask.kt:210
- `debug` at line 299 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/task/shard/ShardReplicationTask.kt:299
- `error` at line 308 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/task/shard/ShardReplicationTask.kt:308
- `error` at line 312 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/task/shard/ShardReplicationTask.kt:312
- `debug` at line 334 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/org/opensearch/replication/task/shard/ShardReplicationTask.kt:334
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 64.7 | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 85.7 | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 63.2 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 49.6 | Weak — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 72.9 | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 85.0 | Strong | 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 — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 72 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Kotlin 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 Python 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 Kotlin code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module 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 — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- 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.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~11165 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .kt suite was found but not re-run
- D12 Dependency Hygiene — Dependency currency not established — ci.opensearch.org did not answer
- 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 — D21 withholds its case and prefix conventions rows: 13 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .kt, .py, 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 — symbol resolution incomplete — navigability not assessed
- D30 Dependency Vulnerabilities — Scanner failed to run — not a clean result
- 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
- 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 — Scanner failed to run — not a clean result
- 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 measured — polyglot repository, one half has no runner
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (21 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 none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- P2 Observability — This repository's JVM, Python source (2 module(s), 161 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, Python 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 — coverage data present for 3 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — 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 — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Python and Kotlin were read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Kotlin request outside a suspend function has no caller's cancellation to honour
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 10 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 85 finding(s)
- TodoComment src/test/kotlin/org/opensearch/replication/MultiClusterRestTestCase.kt:698
- TodoComment src/test/kotlin/org/opensearch/replication/integ/rest/PauseReplicationIT.kt:156
- TodoComment src/test/kotlin/org/opensearch/replication/integ/rest/StopReplicationIT.kt:152
- TodoComment src/main/kotlin/org/opensearch/replication/ReplicationSettings.kt:20
- TodoComment src/main/kotlin/org/opensearch/replication/util/Extensions.kt:123
- TodoComment src/main/kotlin/org/opensearch/replication/repository/RemoteClusterRepositoriesService.kt:37
- TodoComment src/main/kotlin/org/opensearch/replication/repository/RemoteClusterRepository.kt:197
- TodoComment src/main/kotlin/org/opensearch/replication/repository/RemoteClusterRestoreLeaderService.kt:42
- TodoComment src/main/kotlin/org/opensearch/replication/metadata/ReplicationMetadataManager.kt:36
- TodoComment src/main/kotlin/org/opensearch/replication/action/status/ReplicationStatusResponse.kt:102
- TodoComment src/main/kotlin/org/opensearch/replication/action/stats/AutoFollowStatsAction.kt:30
- TodoComment src/main/kotlin/org/opensearch/replication/action/stats/FollowerStatsAction.kt:19
- TodoComment src/main/kotlin/org/opensearch/replication/action/stats/LeaderStatsAction.kt:19
- TodoComment src/main/kotlin/org/opensearch/replication/action/replay/TransportReplayChangesAction.kt:137
- TodoComment src/main/kotlin/org/opensearch/replication/action/replay/TransportReplayChangesAction.kt:194
- TodoComment src/main/kotlin/org/opensearch/replication/action/changes/TransportGetChangesAction.kt:72
- TodoComment src/main/kotlin/org/opensearch/replication/action/changes/TransportGetChangesAction.kt:92
- TodoComment REDACTED:33
- TodoComment REDACTED:84
- TodoComment REDACTED:154
- TodoComment REDACTED:211
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (8 corresponding lines) src/main/kotlin/org/opensearch/replication/ReplicationEngine.kt:39
- Edited copy of a member (8 corresponding lines) src/main/kotlin/org/opensearch/replication/metadata/ReplicationMetadataManager.kt:86
- Edited copy of a member (8 corresponding lines) src/main/kotlin/org/opensearch/replication/action/autofollow/AutoFollowClusterManagerNodeRequest.kt:48
- ClassTooLong: IndexReplicationTask src/main/kotlin/org/opensearch/replication/task/index/IndexReplicationTask.kt:114
- ClassTooLong: TransportBulkReplicationAction src/main/kotlin/org/opensearch/replication/action/bulk/TransportBulkReplicationAction.kt:84
- FileTooLong: index/IndexReplicationTask.kt src/main/kotlin/org/opensearch/replication/task/index/IndexReplicationTask.kt
- FileTooLong: bulk/TransportBulkReplicationAction.kt src/main/kotlin/org/opensearch/replication/action/bulk/TransportBulkReplicationAction.kt
- MethodTooLong: TransportBulkReplicationAction.executeBatchStart src/main/kotlin/org/opensearch/replication/action/bulk/TransportBulkReplicationAction.kt:407
- MethodTooLong: IndexReplicationTask.pollForMetadata src/main/kotlin/org/opensearch/replication/task/index/IndexReplicationTask.kt:518
- TooManyMethods: IndexReplicationTask src/main/kotlin/org/opensearch/replication/task/index/IndexReplicationTask.kt:114
- TooManyMethods: RemoteClusterRepository src/main/kotlin/org/opensearch/replication/repository/RemoteClusterRepository.kt:83
- Edited copies of one member (3 members, 13+ corresponding lines) src/main/kotlin/org/opensearch/replication/rest/AutoFollowStatsHandler.kt:36
- Edited copies of one member (3 members, 13+ corresponding lines) src/main/kotlin/org/opensearch/replication/rest/ReplicateIndexHandler.kt:37
- Duplicated block (9 lines × 2) src/main/kotlin/org/opensearch/replication/metadata/state/BulkReplicationTaskMetadata.kt:52
- Duplicated block (9 lines × 2) src/main/kotlin/org/opensearch/replication/action/autofollow/UpdateAutoFollowPatternRequest.kt:69
- Swallowed exception (caught, then discarded) src/main/kotlin/org/opensearch/replication/task/bulk/BulkReplicationTask.kt:299
- Swallowed exception (caught, then discarded) src/main/kotlin/org/opensearch/replication/seqno/RemoteClusterRetentionLeaseHelper.kt:78
- Swallowed exception (empty catch) src/main/kotlin/org/opensearch/replication/metadata/ReplicationMetadataManager.kt:141
- Swallowed exception (empty catch) src/main/kotlin/org/opensearch/replication/action/bulk/TransportBulkReplicationAction.kt:555
- BulkReplicationTask.processStartResume (cyclomatic 32) src/main/kotlin/org/opensearch/replication/task/bulk/BulkReplicationTask.kt:140
- IndexReplicationTask.pollForMetadata (cyclomatic 28) src/main/kotlin/org/opensearch/replication/task/index/IndexReplicationTask.kt:518
- TransportBulkReplicationAction.executeBatchStart (cyclomatic 26) src/main/kotlin/org/opensearch/replication/action/bulk/TransportBulkReplicationAction.kt:407
- IndexReplicationTask.execute (cyclomatic 23) src/main/kotlin/org/opensearch/replication/task/index/IndexReplicationTask.kt:213
- TransportBulkReplicationAction.executeBatchResume (cyclomatic 22) src/main/kotlin/org/opensearch/replication/action/bulk/TransportBulkReplicationAction.kt:633
- BulkReplicationStatusHandler.prepareRequest (cyclomatic 17) src/main/kotlin/org/opensearch/replication/rest/BulkReplicationStatusHandler.kt:45
- HackComment src/test/kotlin/org/opensearch/replication/task/index/IndexReplicationTaskTests.kt:337
- IndexReplicationTask.pollForMetadata (cognitive 78) src/main/kotlin/org/opensearch/replication/task/index/IndexReplicationTask.kt:518
- BulkReplicationTask.processStartResume (cognitive 58) src/main/kotlin/org/opensearch/replication/task/bulk/BulkReplicationTask.kt:140
- IndexReplicationTask.execute (cognitive 42) src/main/kotlin/org/opensearch/replication/task/index/IndexReplicationTask.kt:213
- TransportBulkReplicationAction.executeBatchResume (cognitive 41) src/main/kotlin/org/opensearch/replication/action/bulk/TransportBulkReplicationAction.kt:633
- BulkReplicationStatusHandler.prepareRequest (cognitive 41) src/main/kotlin/org/opensearch/replication/rest/BulkReplicationStatusHandler.kt:45
- TransportBulkReplicationAction.executeBatchStart (cognitive 36) src/main/kotlin/org/opensearch/replication/action/bulk/TransportBulkReplicationAction.kt:407
- ShardReplicationTask.replicate (cognitive 32) src/main/kotlin/org/opensearch/replication/task/shard/ShardReplicationTask.kt:196
- StaleTaskUtils.removeStaleTasksForIndex (cognitive 23) src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:85
- TransportUpdateMetadataAction.performAliasUpdate (cognitive 19) src/main/kotlin/org/opensearch/replication/metadata/TransportUpdateMetadataAction.kt:153
- ReplicationMetadataStore.getSchemaVersion (cognitive 18) src/main/kotlin/org/opensearch/replication/metadata/store/ReplicationMetadataStore.kt:66
- FollowerStatsResponse.<init> (cognitive 17) src/main/kotlin/org/opensearch/replication/action/stats/FollowerStatsResponse.kt:54
- TransportReplicationStatusAction.doExecute (cognitive 17) src/main/kotlin/org/opensearch/replication/action/status/TransportReplicationStatusAction.kt:46
- UpdateAutoFollowPatternRequest.validate (cognitive 16) src/main/kotlin/org/opensearch/replication/action/autofollow/UpdateAutoFollowPatternRequest.kt:106
- TransportStopIndexReplicationAction.clusterManagerOperation (cognitive 16) src/main/kotlin/org/opensearch/replication/action/stop/TransportStopIndexReplicationAction.kt:86
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (16 corresponding lines) src/main/kotlin/org/opensearch/replication/metadata/state/BulkReplicationTaskMetadata.kt:83
- Edited copy of a member (14 corresponding lines) src/main/kotlin/org/opensearch/replication/action/index/TransportReplicateIndexAction.kt:151
- Edited copies of one member (4 members, 17+ corresponding lines) src/main/kotlin/org/opensearch/replication/metadata/TransportUpdateMetadataAction.kt:113
- Edited copy of a member (17 corresponding lines) src/main/kotlin/org/opensearch/replication/task/index/IndexReplicationState.kt:84
- Edited copies of one member (3 members, 12+ corresponding lines) src/main/kotlin/org/opensearch/replication/action/index/TransportReplicateIndexAction.kt:172
- Edited copy of a member (15 corresponding lines) src/main/kotlin/org/opensearch/replication/seqno/RemoteClusterRetentionLeaseHelper.kt:164
- Edited copy of a member (11 corresponding lines) src/main/kotlin/org/opensearch/replication/metadata/UpdateReplicationMetadata.kt:27
- Edited copy of a member (10 corresponding lines) src/main/kotlin/org/opensearch/replication/metadata/state/BulkReplicationTaskMetadata.kt:50
- Edited copy of a member (12 corresponding lines) src/main/kotlin/org/opensearch/replication/task/index/IndexReplicationState.kt:36
- Edited copies of one member (3 members, 4+ corresponding lines) src/main/kotlin/org/opensearch/replication/action/stats/FollowerNodeStatsResponse.kt:35
- Edited copy of a member (4 corresponding lines) src/main/kotlin/org/opensearch/replication/action/bulk/UpdateBulkTaskStateAction.kt:57
- Duplicated block (10 lines × 2) src/main/kotlin/org/opensearch/replication/action/resume/TransportResumeIndexReplicationAction.kt:226
- Duplicated block (6 lines × 3) src/main/kotlin/org/opensearch/replication/action/index/TransportReplicateIndexClusterManagerNodeAction.kt:155
- Duplicated block (14 lines × 2) src/main/kotlin/org/opensearch/replication/action/setup/TransportSetupChecksAction.kt:93
- Duplicated block (7 lines × 2) src/main/kotlin/org/opensearch/replication/action/bulk/TransportBulkReplicationAction.kt:518
- Duplicated block (5 lines × 2) src/main/kotlin/org/opensearch/replication/action/replay/TransportReplayChangesAction.kt:192
- Sync-over-async blocking src/main/kotlin/org/opensearch/replication/repository/RemoteClusterRepository.kt:286
Minor — 86 finding(s)
- Interpolated log message defeats structured logging perf_workflow/run_perf_suite/perf_runner.py:20
- Interpolated log message defeats structured logging perf_workflow/run_perf_suite/run_perf_suite.py:81
- Interpolated log message defeats structured logging perf_workflow/run_perf_suite/run_perf_suite.py:88
- Interpolated log message defeats structured logging src/main/kotlin/org/opensearch/replication/util/Extensions.kt:118
- Interpolated log message defeats structured logging src/main/kotlin/org/opensearch/replication/util/Extensions.kt:141
- Interpolated log message defeats structured logging src/main/kotlin/org/opensearch/replication/util/Extensions.kt:182
- Interpolated log message defeats structured logging src/main/kotlin/org/opensearch/replication/util/Extensions.kt:187
- Interpolated log message defeats structured logging src/main/kotlin/org/opensearch/replication/util/SecurityContext.kt:73
- Interpolated log message defeats structured logging src/main/kotlin/org/opensearch/replication/util/SecurityContext.kt:85
- Interpolated log message defeats structured logging src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:90
- Interpolated log message defeats structured logging src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:94
- Interpolated log message defeats structured logging src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:98
- Interpolated log message defeats structured logging src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:121
- Interpolated log message defeats structured logging src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:134
- Interpolated log message defeats structured logging src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:139
- Interpolated log message defeats structured logging src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:145
- Interpolated log message defeats structured logging src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:160
- Interpolated log message defeats structured logging src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:164
- Interpolated log message defeats structured logging src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:168
- Interpolated log message defeats structured logging src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:175
- Interpolated log message defeats structured logging src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:186
- Interpolated log message defeats structured logging src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:189
- Interpolated log message defeats structured logging src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:192
- Interpolated log message defeats structured logging src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:196
- Interpolated log message defeats structured logging src/main/kotlin/org/opensearch/replication/util/StaleTaskUtils.kt:199
- Orphaned file src/main/kotlin/org/opensearch/replication/metadata/store/ReplicationMetadataStore.kt:1
- Orphaned file src/main/kotlin/org/opensearch/replication/metadata/TransportUpdateMetadataAction.kt:1
- Orphaned file src/main/kotlin/org/opensearch/replication/seqno/RemoteClusterRetentionLeaseHelper.kt:1
- Orphaned file src/main/kotlin/org/opensearch/replication/metadata/ReplicationMetadataManager.kt:1
- Orphaned file src/main/kotlin/org/opensearch/replication/action/setup/TransportSetupChecksAction.kt:1
- Orphaned file src/main/kotlin/org/opensearch/replication/action/status/TransportReplicationStatusAction.kt:1
- Orphaned file src/main/kotlin/org/opensearch/replication/action/status/ShardInfoResponse.kt:1
- Orphaned file src/main/kotlin/org/opensearch/replication/metadata/state/ReplicationStateMetadata.kt:1
- Orphaned file src/main/kotlin/org/opensearch/replication/metadata/store/ReplicationMetadata.kt:1
- Orphaned file src/main/kotlin/org/opensearch/index/translog/ReplicationTranslogDeletionPolicy.kt:1
- Orphaned file src/main/kotlin/org/opensearch/replication/action/pause/TransportPauseIndexReplicationAction.kt:1
- Orphaned file src/main/kotlin/org/opensearch/replication/action/update/TransportUpdateIndexReplicationAction.kt:1
- Orphaned file src/main/kotlin/org/opensearch/replication/action/status/TranportShardsInfoAction.kt:1
- Orphaned file src/main/kotlin/org/opensearch/replication/seqno/RemoteClusterStats.kt:1
- Orphaned file src/main/kotlin/org/opensearch/replication/action/stats/TransportLeaderStatsAction.kt:1
- Orphaned file src/main/kotlin/org/opensearch/replication/action/status/ReplicationStatusResponse.kt:1
- Orphaned file src/main/kotlin/org/opensearch/replication/action/stats/AutoFollowStatsAction.kt:1
- Orphaned file src/main/kotlin/org/opensearch/replication/action/stop/TransportInternalStopIndexReplicationAction.kt:1
- Orphaned file src/main/kotlin/org/opensearch/replication/action/stats/TransportFollowerStatsAction.kt:1
- Orphaned file perf_workflow/run_perf_suite/run_perf_suite.py:1
- Orphaned file src/main/kotlin/org/opensearch/replication/action/stats/LeaderStatsResponse.kt:1
- Orphaned file src/main/kotlin/org/opensearch/replication/action/update/UpdateIndexReplicationRequest.kt:1
- Orphaned file src/main/kotlin/org/opensearch/replication/action/pause/PauseIndexReplicationRequest.kt:1
- Orphaned file src/main/kotlin/org/opensearch/replication/seqno/RemoteClusterTranslogService.kt:1
- Orphaned file src/main/kotlin/org/opensearch/replication/action/resume/ResumeIndexReplicationRequest.kt:1
- REDACTED
- REDACTED
- REDACTED
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Projects may be oversized for their cohesion build.gradle:1
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- README/code drift CONTRIBUTING.md:56
- No SAST REDACTED:4
- No dependency-update automation build.gradle:82
- No release approval gate
- No changelog
- Duplicated predicate src/main/kotlin/org/opensearch/replication/task/autofollow/AutoFollowTask.kt:85
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 --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-7faaadfdf4434875a159782bcdc0e6db/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=633" --report-format json --report-path /tmp/watchdog-gitleaks-7faaadfdf4434875a159782bcdc0e6db/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.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-7faaadfdf4434875a159782bcdc0e6db/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 . | 13 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `src/main/kotlin/org/opensearch/replication/seqno/RemoteClusterRetentionLeaseHelper.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |