Executive summary
serenity-rs/serenity meets our standard for a preview release, though we found no recorded design decisions and no architecture document or diagram, and 144 files are no longer known to anyone active in the project. It scores 67 out of 100 and is rated Strong, and 33 of its 34 critical findings are security problems in the build pipeline.
Maturity, at 56, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 9 points. Writing log messages as searchable templates comes next, worth about 6 points. Raising Maturity to 62 would lift the score to about 70.
Thirty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One secret can leak from the build pipeline, and one set of files in separate parts keeps changing together, which points to a hidden dependency. Pinning each tool to an exact version, limiting the secret to its own step and making the hidden dependencies explicit would close these risks.
The product code is 58,327 lines, about €76,000 to rebuild.
If Maturity rose from 56 to 62, the lowest score rated Strong, the score would rise from 67 to about 70.
New since the last survey: 55 findings
- Code Duplication · Edited copy of a member (34 corresponding lines) command_attr/src/structures.rs
- Code Duplication · Edited copy of a member (32 corresponding lines) src/framework/standard/parse/mod.rs
- Code Duplication · Edited copy of a member (19 corresponding lines) src/framework/standard/structures/buckets.rs
- Code Duplication · Edited copies of one member (4 members, 22+ corresponding lines) src/model/channel/channel_id.rs
- Code Duplication · Edited copies of one member (5 members, 22+ corresponding lines) src/http/client.rs
- Code Duplication · Edited copy of a member (20 corresponding lines) src/framework/standard/parse/map.rs
- Code Duplication · Edited copy of a member (20 corresponding lines) src/framework/standard/args.rs
- Code Duplication · Edited copies of one member (7 members, 24+ corresponding lines) src/http/client.rs
- Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) src/model/guild/mod.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) src/model/channel/channel_id.rs
- Code Duplication · Edited copies of one member (5 members, 14+ corresponding lines) src/builder/create_interaction_response.rs
- Code Duplication · Edited copies of one member (8 members, 20+ corresponding lines) src/http/client.rs
- Code Duplication · Edited copies of one member (4 members, 19+ corresponding lines) src/http/client.rs
- Code Duplication · Edited copy of a member (16 corresponding lines) src/model/guild/guild_id.rs
- Code Duplication · Edited copy of a member (17 corresponding lines) src/http/client.rs
- Code Duplication · Edited copies of one member (3 members, 20+ corresponding lines) src/http/client.rs
- Code Duplication · Edited copy of a member (12 corresponding lines) src/model/guild/guild_id.rs
- Code Duplication · Edited copy of a member (14 corresponding lines) src/model/channel/message.rs
- Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) src/builder/create_command.rs
- Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) src/model/channel/message.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) src/model/utils.rs
- Code Duplication · Edited copy of a member (9 corresponding lines) src/model/application/component_interaction.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) src/model/guild/emoji.rs
- Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) src/http/client.rs
- Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) src/http/client.rs
- Code Duplication · Edited copy of a member (6 corresponding lines) src/model/channel/guild_channel.rs
- Code Duplication · Edited copy of a member (9 corresponding lines) src/builder/create_thread.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) src/http/client.rs
- Code Duplication · Edited copies of one member (6 members, 14+ corresponding lines) src/http/client.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) src/model/guild/mod.rs
- Code Duplication · Edited copy of a member (7 corresponding lines) src/json.rs
- Code Duplication · Edited copies of one member (4 members, 11+ corresponding lines) src/utils/message_builder.rs
- Code Duplication · Edited copy of a member (14 corresponding lines) src/model/guild/mod.rs
- Code Duplication · Edited copy of a member (8 corresponding lines) src/model/application/interaction.rs
- Code Duplication · Edited copies of one member (5 members, 13+ corresponding lines) src/http/client.rs
- Code Duplication · Edited copy of a member (14 corresponding lines) src/model/guild/mod.rs
- Code Duplication · Edited copies of one member (5 members, 6+ corresponding lines) src/builder/create_channel.rs
- Code Duplication · Edited copy of a member (7 corresponding lines) src/model/guild/role.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) src/model/guild/mod.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) src/model/guild/mod.rs
- Code Duplication · Duplicated block (15 lines × 2) src/gateway/bridge/shard_manager.rs
- Code Duplication · Duplicated block (14 lines × 2) src/builder/edit_message.rs
- Code Duplication · Duplicated block (13 lines × 2) src/model/invite.rs
- Code Duplication · Duplicated block (11 lines × 5) src/http/client.rs
- Code Duplication · Duplicated block (11 lines × 3) command_attr/src/lib.rs
- Code Duplication · Duplicated block (11 lines × 3) src/http/client.rs
- Code Duplication · Duplicated block (11 lines × 2) src/framework/standard/parse/mod.rs
- Code Duplication · Duplicated block (8 lines × 2) src/model/application/component_interaction.rs
- Code Duplication · Duplicated block (5 lines × 2) src/builder/edit_message.rs
- Code Duplication · Duplicated block (5 lines × 2) src/builder/edit_message.rs
- Code Duplication · Duplicated block (7 lines × 2) src/model/channel/reaction.rs
- Code Duplication · Duplicated block (12 lines × 2) src/builder/create_interaction_response.rs
- Code Duplication · Duplicated block (11 lines × 2) src/utils/mod.rs
- Change Coupling · Change coupling: create_embed.rs ↔ create_invite.rs src/builder/create_embed.rs
- Change Coupling · Change coupling: create_interaction_response.rs ↔ create_interaction_response_followup.rs src/builder/create_interaction_response.rs
Fixed since the last survey: 25 findings
- Code Duplication · Duplicated block (15 lines × 2) src/gateway/bridge/shard_manager.rs
- Code Duplication · Duplicated block (14 lines × 2) src/builder/edit_message.rs
- Code Duplication · Duplicated block (13 lines × 2) src/model/invite.rs
- Code Duplication · Duplicated block (11 lines × 5) src/http/client.rs
- Code Duplication · Duplicated block (11 lines × 3) command_attr/src/lib.rs
- Code Duplication · Duplicated block (11 lines × 3) src/http/client.rs
- Code Duplication · Duplicated block (8 lines × 2) src/model/application/component_interaction.rs
- Code Duplication · Duplicated block (5 lines × 2) src/builder/edit_message.rs
- Code Duplication · Duplicated block (5 lines × 2) src/builder/edit_message.rs
- Code Duplication · Duplicated block (7 lines × 2) src/model/channel/reaction.rs
- Code Duplication · Duplicated block (12 lines × 2) src/builder/create_interaction_response.rs
- Code Duplication · Duplicated block (11 lines × 2) src/utils/mod.rs
- Secret Scanning · Leaked secret: high-entropy-secret src/http/client.rs
- Secret Scanning · Leaked secret: high-entropy-secret src/http/client.rs
- Secret Scanning · Leaked secret: high-entropy-secret src/http/client.rs
- Secret Scanning · Leaked secret: high-entropy-secret src/http/client.rs
- Secret Scanning · Leaked secret: high-entropy-secret src/model/webhook.rs
- Knowledge Freshness · Orphaned knowledge src/model/gateway.rs
- Knowledge Freshness · Orphaned knowledge src/gateway/shard.rs
- Knowledge Freshness · Orphaned knowledge src/model/guild/automod.rs
- Knowledge Freshness · Orphaned knowledge src/model/application/interaction.rs
- Change Coupling · Boundary-crossing change coupling: mod.rs ↔ custom_message.rs src/cache/mod.rs
- Change Coupling · Change coupling clique: create_interaction_response.rs, create_interaction_response_followup.rs, edit_interaction_response.rs src/builder/create_interaction_response.rs
- Change Coupling · Change-coupling hub: create_embed.rs → create_invite.rs, edit_guild.rs, edit_profile.rs src/builder/create_embed.rs
- Change Coupling · Change coupling: create_command.rs ↔ create_command_permission.rs src/builder/create_command.rs
Rebuild cost: about €76,000 · Estimate
| Cost to rebuild | €25,000 to €130,000, for 419 to 1,330 hours of work, about 0.5 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.9 at a score of 67. 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 | Medium: 58,327 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 client.error | 2 model.permissions | 3 builder.create_interaction_response_followup | 4 builder.edit_interaction_response | 5 model.misc | 6 model.timestamp | 7 model.guild.role | 8 model.user | 9 model.application.command_interaction | 10 model.application.modal_interaction | 11 model.guild.scheduled_event | 12 model.application.interaction | 13 model.guild.audit_log | 14 builder.create_interaction_response | 15 model.guild | 16 model.application.component_interaction | 17 model.gateway | 18 model.guild.partial_guild | 19 gateway | 20 client | 21 http.client | 22 model.channel.private_channel | 23 model.channel | 24 model.invite | 25 model.event | 26 collector | 27 model.channel.guild_channel | 28 model.guild.member | 29 model.channel.reaction | 30 builder.create_components | 31 builder.edit_message | 32 model.channel.message | 33 builder.create_attachment | 34 builder.create_message | 35 model.id | 36 cache | 37 gateway.bridge.shard_runner | 38 client.context | 39 builder | 40 client.event_handler |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 client.error | ||||||||||||||||||||||||||||||||||||||||
| 2 model.permissions | ||||||||||||||||||||||||||||||||||||||||
| 3 builder.create_interaction_response_followup | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 4 builder.edit_interaction_response | 1 | 1 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 5 model.misc | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 6 model.timestamp | 2 | |||||||||||||||||||||||||||||||||||||||
| 7 model.guild.role | 1 | 1 | 6 | |||||||||||||||||||||||||||||||||||||
| 8 model.user | 4 | 1 | 2 | 1 | 1 | 8 | ||||||||||||||||||||||||||||||||||
| 9 model.application.command_interaction | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 12 | 1 | |||||||||||||||||||||||||||||||
| 10 model.application.modal_interaction | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 4 | ||||||||||||||||||||||||||||||||
| 11 model.guild.scheduled_event | 1 | 1 | 2 | 1 | 6 | |||||||||||||||||||||||||||||||||||
| 12 model.application.interaction | 1 | 4 | 1 | 1 | 1 | 1 | 10 | |||||||||||||||||||||||||||||||||
| 13 model.guild.audit_log | 1 | 1 | 8 | |||||||||||||||||||||||||||||||||||||
| 14 builder.create_interaction_response | 1 | 2 | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 15 model.guild | 4 | 2 | 2 | 1 | 2 | 1 | 1 | 1 | 1 | 2 | 1 | 2 | 13 | 1 | ||||||||||||||||||||||||||
| 16 model.application.component_interaction | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 4 | 1 | |||||||||||||||||||||||||||||
| 17 model.gateway | 1 | 9 | 1 | 1 | 5 | |||||||||||||||||||||||||||||||||||
| 18 model.guild.partial_guild | 1 | 1 | 1 | 1 | 8 | 2 | 1 | 2 | 8 | |||||||||||||||||||||||||||||||
| 19 gateway | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 20 client | 1 | 2 | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 21 http.client | 1 | 3 | 1 | 1 | 22 | |||||||||||||||||||||||||||||||||||
| 22 model.channel.private_channel | 1 | 1 | 1 | 2 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||
| 23 model.channel | 2 | 1 | 1 | 2 | 1 | 9 | ||||||||||||||||||||||||||||||||||
| 24 model.invite | 1 | 2 | 2 | 1 | 2 | 1 | 1 | 5 | ||||||||||||||||||||||||||||||||
| 25 model.event | 1 | 4 | 3 | 8 | 3 | 3 | 1 | 2 | 3 | 1 | 3 | 1 | 8 | 7 | 3 | 11 | 71 | 26 | ||||||||||||||||||||||
| 26 collector | 1 | 1 | 1 | 1 | 1 | 15 | ||||||||||||||||||||||||||||||||||
| 27 model.channel.guild_channel | 1 | 1 | 1 | 11 | 2 | 1 | 1 | 1 | 7 | |||||||||||||||||||||||||||||||
| 28 model.guild.member | 2 | 2 | 3 | 1 | 4 | 1 | 8 | |||||||||||||||||||||||||||||||||
| 29 model.channel.reaction | 1 | 1 | 1 | 5 | ||||||||||||||||||||||||||||||||||||
| 30 builder.create_components | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 builder.edit_message | 1 | 1 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 32 model.channel.message | 1 | 1 | 3 | 2 | 2 | 1 | 3 | 1 | 1 | 2 | 1 | 18 | 1 | |||||||||||||||||||||||||||
| 33 builder.create_attachment | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 34 builder.create_message | 1 | 1 | 3 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 35 model.id | 27 | 1 | 1 | 1 | 3 | 1 | 2 | 1 | 3 | 1 | 4 | 1 | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||
| 36 cache | 2 | 5 | ||||||||||||||||||||||||||||||||||||||
| 37 gateway.bridge.shard_runner | 1 | 2 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 38 client.context | 1 | 1 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 39 builder | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 client.event_handler | 1 | 2 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 21 | 2 | 2 | 1 | 1 | 6 | 3 |
3→30 builder.create_interaction_response_followup uses builder.create_components part of a loop✕
- Connections
- 1 pair of types, where a type in builder.create_interaction_response_followup uses a type in builder.create_components.
- The types involved
serenity.builder.create_interaction_response_followup.CreateInteractionResponseFollowup→serenity.builder.create_components.CreateActionRow
- Direction
- builder.create_interaction_response_followup uses builder.create_components, so a change to builder.create_components can break builder.create_interaction_response_followup, while a change to builder.create_interaction_response_followup can't break builder.create_components.
- 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.
3→32 builder.create_interaction_response_followup uses model.channel.message part of a loop✕
- Connections
- 1 pair of types, where a type in builder.create_interaction_response_followup uses a type in model.channel.message.
- The types involved
serenity.builder.create_interaction_response_followup.CreateInteractionResponseFollowup→serenity.model.channel.message.MessageFlags
- Direction
- builder.create_interaction_response_followup uses model.channel.message, so a change to model.channel.message can break builder.create_interaction_response_followup, while a change to builder.create_interaction_response_followup can't break model.channel.message.
- 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.
3→33 builder.create_interaction_response_followup uses builder.create_attachment part of a loop✕
- Connections
- 2 pairs of types, where a type in builder.create_interaction_response_followup uses a type in builder.create_attachment.
- The types involved
serenity.builder.create_interaction_response_followup.CreateInteractionResponseFollowup→serenity.builder.create_attachment.CreateAttachmentserenity.builder.create_interaction_response_followup.CreateInteractionResponseFollowup→serenity.builder.create_attachment.EditAttachments
- Direction
- builder.create_interaction_response_followup uses builder.create_attachment, so a change to builder.create_attachment can break builder.create_interaction_response_followup, while a change to builder.create_interaction_response_followup can't break builder.create_attachment.
- 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.
3→38 builder.create_interaction_response_followup uses client.context part of a loop✕
- Connections
- 1 pair of types, where a type in builder.create_interaction_response_followup uses a type in client.context.
- The types involved
serenity.builder.create_interaction_response_followup.CreateInteractionResponseFollowup→serenity.client.context.Context
- Direction
- builder.create_interaction_response_followup uses client.context, so a change to client.context can break builder.create_interaction_response_followup, while a change to builder.create_interaction_response_followup can't break client.context.
- 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.
3→39 builder.create_interaction_response_followup uses builder part of a loop✕
- Connections
- 1 pair of types, where a type in builder.create_interaction_response_followup uses a type in builder.
- The types involved
serenity.builder.create_interaction_response_followup.CreateInteractionResponseFollowup→serenity.builder.Builder
- Direction
- builder.create_interaction_response_followup uses builder, so a change to builder can break builder.create_interaction_response_followup, while a change to builder.create_interaction_response_followup can't break builder.
- 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.
4→30 builder.edit_interaction_response uses builder.create_components part of a loop✕
- Connections
- 1 pair of types, where a type in builder.edit_interaction_response uses a type in builder.create_components.
- The types involved
serenity.builder.edit_interaction_response.EditInteractionResponse→serenity.builder.create_components.CreateActionRow
- Direction
- builder.edit_interaction_response uses builder.create_components, so a change to builder.create_components can break builder.edit_interaction_response, while a change to builder.edit_interaction_response can't break builder.create_components.
- 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.
4→32 builder.edit_interaction_response uses model.channel.message part of a loop✕
- Connections
- 1 pair of types, where a type in builder.edit_interaction_response uses a type in model.channel.message.
- The types involved
serenity.builder.edit_interaction_response.EditInteractionResponse→serenity.model.channel.message.MessageFlags
- Direction
- builder.edit_interaction_response uses model.channel.message, so a change to model.channel.message can break builder.edit_interaction_response, while a change to builder.edit_interaction_response can't break model.channel.message.
- 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.
4→33 builder.edit_interaction_response uses builder.create_attachment part of a loop✕
- Connections
- 2 pairs of types, where a type in builder.edit_interaction_response uses a type in builder.create_attachment.
- The types involved
serenity.builder.edit_interaction_response.EditInteractionResponse→serenity.builder.create_attachment.CreateAttachmentserenity.builder.edit_interaction_response.EditInteractionResponse→serenity.builder.create_attachment.EditAttachments
- Direction
- builder.edit_interaction_response uses builder.create_attachment, so a change to builder.create_attachment can break builder.edit_interaction_response, while a change to builder.edit_interaction_response can't break builder.create_attachment.
- 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.
4→35 builder.edit_interaction_response uses model.id part of a loop✕
- Connections
- 1 pair of types, where a type in builder.edit_interaction_response uses a type in model.id.
- The types involved
serenity.builder.edit_interaction_response.EditInteractionResponse→serenity.model.id.AttachmentId
- Direction
- builder.edit_interaction_response uses model.id, so a change to model.id can break builder.edit_interaction_response, while a change to builder.edit_interaction_response can't break model.id.
- 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.
4→38 builder.edit_interaction_response uses client.context part of a loop✕
- Connections
- 1 pair of types, where a type in builder.edit_interaction_response uses a type in client.context.
- The types involved
serenity.builder.edit_interaction_response.EditInteractionResponse→serenity.client.context.Context
- Direction
- builder.edit_interaction_response uses client.context, so a change to client.context can break builder.edit_interaction_response, while a change to builder.edit_interaction_response can't break client.context.
- 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.
4→39 builder.edit_interaction_response uses builder part of a loop✕
- Connections
- 1 pair of types, where a type in builder.edit_interaction_response uses a type in builder.
- The types involved
serenity.builder.edit_interaction_response.EditInteractionResponse→serenity.builder.Builder
- Direction
- builder.edit_interaction_response uses builder, so a change to builder can break builder.edit_interaction_response, while a change to builder.edit_interaction_response can't break builder.
- 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.
5→1 model.misc uses client.error✕
- Connections
- 1 pair of types, where a type in model.misc uses a type in client.error.
- The types involved
serenity.model.misc.ImageHashParseError→serenity.client.error.Error
- Direction
- model.misc uses client.error, so a change to client.error can break model.misc, while a change to model.misc can't break client.error.
- Position
- Below the diagonal: model.misc uses a module listed above it, which is the healthy direction.
5→35 model.misc uses model.id part of a loop✕
- Connections
- 1 pair of types, where a type in model.misc uses a type in model.id.
- The types involved
serenity.model.misc.EmojiIdentifier→serenity.model.id.EmojiId
- Direction
- model.misc uses model.id, so a change to model.id can break model.misc, while a change to model.misc can't break model.id.
- 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.
6→1 model.timestamp uses client.error✕
- Connections
- 2 pairs of types, where a type in model.timestamp uses a type in client.error.
- The types involved
serenity.model.timestamp.InvalidTimestamp→serenity.client.error.Errorserenity.model.timestamp.ParseError→serenity.client.error.Error
- Direction
- model.timestamp uses client.error, so a change to client.error can break model.timestamp, while a change to model.timestamp can't break client.error.
- Position
- Below the diagonal: model.timestamp uses a module listed above it, which is the healthy direction.
7→2 model.guild.role uses model.permissions✕
- Connections
- 1 pair of types, where a type in model.guild.role uses a type in model.permissions.
- The types involved
serenity.model.guild.role.Role→serenity.model.permissions.Permissions
- Direction
- model.guild.role uses model.permissions, so a change to model.permissions can break model.guild.role, while a change to model.guild.role can't break model.permissions.
- Position
- Below the diagonal: model.guild.role uses a module listed above it, which is the healthy direction.
7→5 model.guild.role uses model.misc✕
- Connections
- 1 pair of types, where a type in model.guild.role uses a type in model.misc.
- The types involved
serenity.model.guild.role.Role→serenity.model.misc.ImageHash
- Direction
- model.guild.role uses model.misc, so a change to model.misc can break model.guild.role, while a change to model.guild.role can't break model.misc.
- Position
- Below the diagonal: model.guild.role uses a module listed above it, which is the healthy direction.
7→35 model.guild.role uses model.id part of a loop✕
- Connections
- 6 pairs of types, where a type in model.guild.role uses a type in model.id.
- The types involved
serenity.model.guild.role.Role→serenity.model.id.ChannelIdserenity.model.guild.role.Role→serenity.model.id.GuildIdserenity.model.guild.role.Role→serenity.model.id.RoleIdserenity.model.guild.role.RoleTags→serenity.model.id.IntegrationIdserenity.model.guild.role.RoleTags→serenity.model.id.SkuIdserenity.model.guild.role.RoleTags→serenity.model.id.UserId
- Direction
- model.guild.role uses model.id, so a change to model.id can break model.guild.role, while a change to model.guild.role can't break model.id.
- 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.
8→5 model.user uses model.misc✕
- Connections
- 4 pairs of types, where a type in model.user uses a type in model.misc.
- The types involved
serenity.model.user.AvatarDecorationData→serenity.model.misc.ImageHashserenity.model.user.PrimaryGuild→serenity.model.misc.ImageHashserenity.model.user.User→serenity.model.misc.ImageHashserenity.model.user.user$module→serenity.model.misc.ImageHash
- Direction
- model.user uses model.misc, so a change to model.misc can break model.user, while a change to model.user can't break model.misc.
- Position
- Below the diagonal: model.user uses a module listed above it, which is the healthy direction.
8→6 model.user uses model.timestamp✕
- Connections
- 1 pair of types, where a type in model.user uses a type in model.timestamp.
- The types involved
serenity.model.user.User→serenity.model.timestamp.Timestamp
- Direction
- model.user uses model.timestamp, so a change to model.timestamp can break model.user, while a change to model.user can't break model.timestamp.
- Position
- Below the diagonal: model.user uses a module listed above it, which is the healthy direction.
8→26 model.user uses collector part of a loop✕
- Connections
- 2 pairs of types, where a type in model.user uses a type in collector.
- The types involved
serenity.model.user.User→serenity.collector.MessageCollectorserenity.model.user.User→serenity.collector.ReactionCollector
- Direction
- model.user uses collector, so a change to collector can break model.user, while a change to model.user can't break collector.
- 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.
8→28 model.user uses model.guild.member part of a loop✕
- Connections
- 1 pair of types, where a type in model.user uses a type in model.guild.member.
- The types involved
serenity.model.user.User→serenity.model.guild.member.PartialMember
- Direction
- model.user uses model.guild.member, so a change to model.guild.member can break model.user, while a change to model.user can't break model.guild.member.
- 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.
8→34 model.user uses builder.create_message part of a loop✕
- Connections
- 1 pair of types, where a type in model.user uses a type in builder.create_message.
- The types involved
serenity.model.user.User→serenity.builder.create_message.CreateMessage
- Direction
- model.user uses builder.create_message, so a change to builder.create_message can break model.user, while a change to model.user can't break builder.create_message.
- 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.
8→35 model.user uses model.id part of a loop✕
- Connections
- 8 pairs of types, where a type in model.user uses a type in model.id.
- The types involved
serenity.model.user.AvatarDecorationData→serenity.model.id.SkuIdserenity.model.user.Nameplate→serenity.model.id.SkuIdserenity.model.user.PrimaryGuild→serenity.model.id.GuildIdserenity.model.user.User→serenity.model.id.ChannelIdserenity.model.user.User→serenity.model.id.GuildIdserenity.model.user.User→serenity.model.id.UserIdserenity.model.user.user$module→serenity.model.id.GuildIdserenity.model.user.user$module→serenity.model.id.UserId
- Direction
- model.user uses model.id, so a change to model.id can break model.user, while a change to model.user can't break model.id.
- 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→2 model.application.command_interaction uses model.permissions✕
- Connections
- 1 pair of types, where a type in model.application.command_interaction uses a type in model.permissions.
- The types involved
serenity.model.application.command_interaction.CommandInteraction→serenity.model.permissions.Permissions
- Direction
- model.application.command_interaction uses model.permissions, so a change to model.permissions can break model.application.command_interaction, while a change to model.application.command_interaction can't break model.permissions.
- Position
- Below the diagonal: model.application.command_interaction uses a module listed above it, which is the healthy direction.
9→3 model.application.command_interaction uses builder.create_interaction_response_followup✕
- Connections
- 1 pair of types, where a type in model.application.command_interaction uses a type in builder.create_interaction_response_followup.
- The types involved
serenity.model.application.command_interaction.CommandInteraction→serenity.builder.create_interaction_response_followup.CreateInteractionResponseFollowup
- Direction
- model.application.command_interaction uses builder.create_interaction_response_followup, so a change to builder.create_interaction_response_followup can break model.application.command_interaction, while a change to model.application.command_interaction can't break builder.create_interaction_response_followup.
- Position
- Below the diagonal: model.application.command_interaction uses a module listed above it, which is the healthy direction.
9→4 model.application.command_interaction uses builder.edit_interaction_response✕
- Connections
- 1 pair of types, where a type in model.application.command_interaction uses a type in builder.edit_interaction_response.
- The types involved
serenity.model.application.command_interaction.CommandInteraction→serenity.builder.edit_interaction_response.EditInteractionResponse
- Direction
- model.application.command_interaction uses builder.edit_interaction_response, so a change to builder.edit_interaction_response can break model.application.command_interaction, while a change to model.application.command_interaction can't break builder.edit_interaction_response.
- Position
- Below the diagonal: model.application.command_interaction uses a module listed above it, which is the healthy direction.
9→8 model.application.command_interaction uses model.user✕
- Connections
- 1 pair of types, where a type in model.application.command_interaction uses a type in model.user.
- The types involved
serenity.model.application.command_interaction.CommandInteraction→serenity.model.user.User
- Direction
- model.application.command_interaction uses model.user, so a change to model.user can break model.application.command_interaction, while a change to model.application.command_interaction can't break model.user.
- Position
- Below the diagonal: model.application.command_interaction uses a module listed above it, which is the healthy direction.
9→12 model.application.command_interaction uses model.application.interaction part of a loop✕
- Connections
- 1 pair of types, where a type in model.application.command_interaction uses a type in model.application.interaction.
- The types involved
serenity.model.application.command_interaction.CommandInteraction→serenity.model.application.interaction.AuthorizingIntegrationOwners
- Direction
- model.application.command_interaction uses model.application.interaction, so a change to model.application.interaction can break model.application.command_interaction, while a change to model.application.command_interaction can't break model.application.interaction.
- 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→14 model.application.command_interaction uses builder.create_interaction_response part of a loop✕
- Connections
- 1 pair of types, where a type in model.application.command_interaction uses a type in builder.create_interaction_response.
- The types involved
serenity.model.application.command_interaction.CommandInteraction→serenity.builder.create_interaction_response.CreateInteractionResponse
- Direction
- model.application.command_interaction uses builder.create_interaction_response, so a change to builder.create_interaction_response can break model.application.command_interaction, while a change to model.application.command_interaction can't break builder.create_interaction_response.
- 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→28 model.application.command_interaction uses model.guild.member part of a loop✕
- Connections
- 1 pair of types, where a type in model.application.command_interaction uses a type in model.guild.member.
- The types involved
serenity.model.application.command_interaction.CommandInteraction→serenity.model.guild.member.Member
- Direction
- model.application.command_interaction uses model.guild.member, so a change to model.guild.member can break model.application.command_interaction, while a change to model.application.command_interaction can't break model.guild.member.
- 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→35 model.application.command_interaction uses model.id part of a loop✕
- Connections
- 12 pairs of types, where a type in model.application.command_interaction uses a type in model.id.
- The types involved
serenity.model.application.command_interaction.CommandData→serenity.model.id.CommandIdserenity.model.application.command_interaction.CommandData→serenity.model.id.GuildIdserenity.model.application.command_interaction.CommandData→serenity.model.id.TargetIdserenity.model.application.command_interaction.CommandDataOptionValue→serenity.model.id.AttachmentIdserenity.model.application.command_interaction.CommandDataOptionValue→serenity.model.id.ChannelIdserenity.model.application.command_interaction.CommandDataOptionValue→serenity.model.id.GenericIdserenity.model.application.command_interaction.CommandDataOptionValue→serenity.model.id.RoleIdserenity.model.application.command_interaction.CommandDataOptionValue→serenity.model.id.UserIdserenity.model.application.command_interaction.CommandInteraction→serenity.model.id.ApplicationIdserenity.model.application.command_interaction.CommandInteraction→serenity.model.id.ChannelIdserenity.model.application.command_interaction.CommandInteraction→serenity.model.id.GuildIdserenity.model.application.command_interaction.CommandInteraction→serenity.model.id.InteractionId
- Direction
- model.application.command_interaction uses model.id, so a change to model.id can break model.application.command_interaction, while a change to model.application.command_interaction can't break model.id.
- 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→38 model.application.command_interaction uses client.context part of a loop✕
- Connections
- 1 pair of types, where a type in model.application.command_interaction uses a type in client.context.
- The types involved
serenity.model.application.command_interaction.CommandInteraction→serenity.client.context.Context
- Direction
- model.application.command_interaction uses client.context, so a change to client.context can break model.application.command_interaction, while a change to model.application.command_interaction can't break client.context.
- 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 model.application.modal_interaction uses model.permissions✕
- Connections
- 1 pair of types, where a type in model.application.modal_interaction uses a type in model.permissions.
- The types involved
serenity.model.application.modal_interaction.ModalInteraction→serenity.model.permissions.Permissions
- Direction
- model.application.modal_interaction uses model.permissions, so a change to model.permissions can break model.application.modal_interaction, while a change to model.application.modal_interaction can't break model.permissions.
- Position
- Below the diagonal: model.application.modal_interaction uses a module listed above it, which is the healthy direction.
10→3 model.application.modal_interaction uses builder.create_interaction_response_followup✕
- Connections
- 1 pair of types, where a type in model.application.modal_interaction uses a type in builder.create_interaction_response_followup.
- The types involved
serenity.model.application.modal_interaction.ModalInteraction→serenity.builder.create_interaction_response_followup.CreateInteractionResponseFollowup
- Direction
- model.application.modal_interaction uses builder.create_interaction_response_followup, so a change to builder.create_interaction_response_followup can break model.application.modal_interaction, while a change to model.application.modal_interaction can't break builder.create_interaction_response_followup.
- Position
- Below the diagonal: model.application.modal_interaction uses a module listed above it, which is the healthy direction.
10→4 model.application.modal_interaction uses builder.edit_interaction_response✕
- Connections
- 1 pair of types, where a type in model.application.modal_interaction uses a type in builder.edit_interaction_response.
- The types involved
serenity.model.application.modal_interaction.ModalInteraction→serenity.builder.edit_interaction_response.EditInteractionResponse
- Direction
- model.application.modal_interaction uses builder.edit_interaction_response, so a change to builder.edit_interaction_response can break model.application.modal_interaction, while a change to model.application.modal_interaction can't break builder.edit_interaction_response.
- Position
- Below the diagonal: model.application.modal_interaction uses a module listed above it, which is the healthy direction.
10→8 model.application.modal_interaction uses model.user✕
- Connections
- 1 pair of types, where a type in model.application.modal_interaction uses a type in model.user.
- The types involved
serenity.model.application.modal_interaction.ModalInteraction→serenity.model.user.User
- Direction
- model.application.modal_interaction uses model.user, so a change to model.user can break model.application.modal_interaction, while a change to model.application.modal_interaction can't break model.user.
- Position
- Below the diagonal: model.application.modal_interaction uses a module listed above it, which is the healthy direction.
10→14 model.application.modal_interaction uses builder.create_interaction_response part of a loop✕
- Connections
- 1 pair of types, where a type in model.application.modal_interaction uses a type in builder.create_interaction_response.
- The types involved
serenity.model.application.modal_interaction.ModalInteraction→serenity.builder.create_interaction_response.CreateInteractionResponse
- Direction
- model.application.modal_interaction uses builder.create_interaction_response, so a change to builder.create_interaction_response can break model.application.modal_interaction, while a change to model.application.modal_interaction can't break builder.create_interaction_response.
- 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→28 model.application.modal_interaction uses model.guild.member part of a loop✕
- Connections
- 1 pair of types, where a type in model.application.modal_interaction uses a type in model.guild.member.
- The types involved
serenity.model.application.modal_interaction.ModalInteraction→serenity.model.guild.member.Member
- Direction
- model.application.modal_interaction uses model.guild.member, so a change to model.guild.member can break model.application.modal_interaction, while a change to model.application.modal_interaction can't break model.guild.member.
- 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→32 model.application.modal_interaction uses model.channel.message part of a loop✕
- Connections
- 1 pair of types, where a type in model.application.modal_interaction uses a type in model.channel.message.
- The types involved
serenity.model.application.modal_interaction.ModalInteraction→serenity.model.channel.message.Message
- Direction
- model.application.modal_interaction uses model.channel.message, so a change to model.channel.message can break model.application.modal_interaction, while a change to model.application.modal_interaction can't break model.channel.message.
- 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→35 model.application.modal_interaction uses model.id part of a loop✕
- Connections
- 4 pairs of types, where a type in model.application.modal_interaction uses a type in model.id.
- The types involved
serenity.model.application.modal_interaction.ModalInteraction→serenity.model.id.ApplicationIdserenity.model.application.modal_interaction.ModalInteraction→serenity.model.id.ChannelIdserenity.model.application.modal_interaction.ModalInteraction→serenity.model.id.GuildIdserenity.model.application.modal_interaction.ModalInteraction→serenity.model.id.InteractionId
- Direction
- model.application.modal_interaction uses model.id, so a change to model.id can break model.application.modal_interaction, while a change to model.application.modal_interaction can't break model.id.
- 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.
11→5 model.guild.scheduled_event uses model.misc✕
- Connections
- 1 pair of types, where a type in model.guild.scheduled_event uses a type in model.misc.
- The types involved
serenity.model.guild.scheduled_event.ScheduledEvent→serenity.model.misc.ImageHash
- Direction
- model.guild.scheduled_event uses model.misc, so a change to model.misc can break model.guild.scheduled_event, while a change to model.guild.scheduled_event can't break model.misc.
- Position
- Below the diagonal: model.guild.scheduled_event uses a module listed above it, which is the healthy direction.
11→6 model.guild.scheduled_event uses model.timestamp✕
- Connections
- 1 pair of types, where a type in model.guild.scheduled_event uses a type in model.timestamp.
- The types involved
serenity.model.guild.scheduled_event.ScheduledEvent→serenity.model.timestamp.Timestamp
- Direction
- model.guild.scheduled_event uses model.timestamp, so a change to model.timestamp can break model.guild.scheduled_event, while a change to model.guild.scheduled_event can't break model.timestamp.
- Position
- Below the diagonal: model.guild.scheduled_event uses a module listed above it, which is the healthy direction.
11→8 model.guild.scheduled_event uses model.user✕
- Connections
- 2 pairs of types, where a type in model.guild.scheduled_event uses a type in model.user.
- The types involved
serenity.model.guild.scheduled_event.ScheduledEvent→serenity.model.user.Userserenity.model.guild.scheduled_event.ScheduledEventUser→serenity.model.user.User
- Direction
- model.guild.scheduled_event uses model.user, so a change to model.user can break model.guild.scheduled_event, while a change to model.guild.scheduled_event can't break model.user.
- Position
- Below the diagonal: model.guild.scheduled_event uses a module listed above it, which is the healthy direction.
11→28 model.guild.scheduled_event uses model.guild.member part of a loop✕
- Connections
- 1 pair of types, where a type in model.guild.scheduled_event uses a type in model.guild.member.
- The types involved
serenity.model.guild.scheduled_event.ScheduledEventUser→serenity.model.guild.member.Member
- Direction
- model.guild.scheduled_event uses model.guild.member, so a change to model.guild.member can break model.guild.scheduled_event, while a change to model.guild.scheduled_event can't break model.guild.member.
- 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.
11→35 model.guild.scheduled_event uses model.id part of a loop✕
- Connections
- 6 pairs of types, where a type in model.guild.scheduled_event uses a type in model.id.
- The types involved
serenity.model.guild.scheduled_event.ScheduledEvent→serenity.model.id.ChannelIdserenity.model.guild.scheduled_event.ScheduledEvent→serenity.model.id.GenericIdserenity.model.guild.scheduled_event.ScheduledEvent→serenity.model.id.GuildIdserenity.model.guild.scheduled_event.ScheduledEvent→serenity.model.id.ScheduledEventIdserenity.model.guild.scheduled_event.ScheduledEvent→serenity.model.id.UserIdserenity.model.guild.scheduled_event.ScheduledEventUser→serenity.model.id.ScheduledEventId
- Direction
- model.guild.scheduled_event uses model.id, so a change to model.id can break model.guild.scheduled_event, while a change to model.guild.scheduled_event can't break model.id.
- 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.
12→2 model.application.interaction uses model.permissions✕
- Connections
- 1 pair of types, where a type in model.application.interaction uses a type in model.permissions.
- The types involved
serenity.model.application.interaction.Interaction→serenity.model.permissions.Permissions
- Direction
- model.application.interaction uses model.permissions, so a change to model.permissions can break model.application.interaction, while a change to model.application.interaction can't break model.permissions.
- Position
- Below the diagonal: model.application.interaction uses a module listed above it, which is the healthy direction.
12→8 model.application.interaction uses model.user✕
- Connections
- 4 pairs of types, where a type in model.application.interaction uses a type in model.user.
- The types involved
serenity.model.application.interaction.MessageCommandInteractionMetadata→serenity.model.user.Userserenity.model.application.interaction.MessageComponentInteractionMetadata→serenity.model.user.Userserenity.model.application.interaction.MessageInteraction→serenity.model.user.Userserenity.model.application.interaction.MessageModalSubmitInteractionMetadata→serenity.model.user.User
- Direction
- model.application.interaction uses model.user, so a change to model.user can break model.application.interaction, while a change to model.application.interaction can't break model.user.
- Position
- Below the diagonal: model.application.interaction uses a module listed above it, which is the healthy direction.
12→9 model.application.interaction uses model.application.command_interaction✕
- Connections
- 1 pair of types, where a type in model.application.interaction uses a type in model.application.command_interaction.
- The types involved
serenity.model.application.interaction.Interaction→serenity.model.application.command_interaction.CommandInteraction
- Direction
- model.application.interaction uses model.application.command_interaction, so a change to model.application.command_interaction can break model.application.interaction, while a change to model.application.interaction can't break model.application.command_interaction.
- Position
- Below the diagonal: model.application.interaction uses a module listed above it, which is the healthy direction.
12→10 model.application.interaction uses model.application.modal_interaction✕
- Connections
- 1 pair of types, where a type in model.application.interaction uses a type in model.application.modal_interaction.
- The types involved
serenity.model.application.interaction.Interaction→serenity.model.application.modal_interaction.ModalInteraction
- Direction
- model.application.interaction uses model.application.modal_interaction, so a change to model.application.modal_interaction can break model.application.interaction, while a change to model.application.interaction can't break model.application.modal_interaction.
- Position
- Below the diagonal: model.application.interaction uses a module listed above it, which is the healthy direction.
12→16 model.application.interaction uses model.application.component_interaction part of a loop✕
- Connections
- 1 pair of types, where a type in model.application.interaction uses a type in model.application.component_interaction.
- The types involved
serenity.model.application.interaction.Interaction→serenity.model.application.component_interaction.ComponentInteraction
- Direction
- model.application.interaction uses model.application.component_interaction, so a change to model.application.component_interaction can break model.application.interaction, while a change to model.application.interaction can't break model.application.component_interaction.
- 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.
12→28 model.application.interaction uses model.guild.member part of a loop✕
- Connections
- 1 pair of types, where a type in model.application.interaction uses a type in model.guild.member.
- The types involved
serenity.model.application.interaction.MessageInteraction→serenity.model.guild.member.PartialMember
- Direction
- model.application.interaction uses model.guild.member, so a change to model.guild.member can break model.application.interaction, while a change to model.application.interaction can't break model.guild.member.
- 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.
12→35 model.application.interaction uses model.id part of a loop✕
- Connections
- 10 pairs of types, where a type in model.application.interaction uses a type in model.id.
- The types involved
serenity.model.application.interaction.Interaction→serenity.model.id.ApplicationIdserenity.model.application.interaction.Interaction→serenity.model.id.GuildIdserenity.model.application.interaction.Interaction→serenity.model.id.InteractionIdserenity.model.application.interaction.MessageCommandInteractionMetadata→serenity.model.id.InteractionIdserenity.model.application.interaction.MessageCommandInteractionMetadata→serenity.model.id.MessageIdserenity.model.application.interaction.MessageComponentInteractionMetadata→serenity.model.id.InteractionIdserenity.model.application.interaction.MessageComponentInteractionMetadata→serenity.model.id.MessageIdserenity.model.application.interaction.MessageInteraction→serenity.model.id.InteractionIdserenity.model.application.interaction.MessageModalSubmitInteractionMetadata→serenity.model.id.InteractionIdserenity.model.application.interaction.MessageModalSubmitInteractionMetadata→serenity.model.id.MessageId
- Direction
- model.application.interaction uses model.id, so a change to model.id can break model.application.interaction, while a change to model.application.interaction can't break model.id.
- 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→11 model.guild.audit_log uses model.guild.scheduled_event✕
- Connections
- 1 pair of types, where a type in model.guild.audit_log uses a type in model.guild.scheduled_event.
- The types involved
serenity.model.guild.audit_log.AuditLogs→serenity.model.guild.scheduled_event.ScheduledEvent
- Direction
- model.guild.audit_log uses model.guild.scheduled_event, so a change to model.guild.scheduled_event can break model.guild.audit_log, while a change to model.guild.audit_log can't break model.guild.scheduled_event.
- Position
- Below the diagonal: model.guild.audit_log uses a module listed above it, which is the healthy direction.
13→27 model.guild.audit_log uses model.channel.guild_channel part of a loop✕
- Connections
- 1 pair of types, where a type in model.guild.audit_log uses a type in model.channel.guild_channel.
- The types involved
serenity.model.guild.audit_log.AuditLogs→serenity.model.channel.guild_channel.GuildChannel
- Direction
- model.guild.audit_log uses model.channel.guild_channel, so a change to model.channel.guild_channel can break model.guild.audit_log, while a change to model.guild.audit_log can't break model.channel.guild_channel.
- 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→35 model.guild.audit_log uses model.id part of a loop✕
- Connections
- 8 pairs of types, where a type in model.guild.audit_log uses a type in model.id.
- The types involved
serenity.model.guild.audit_log.AuditLogEntry→serenity.model.id.AuditLogEntryIdserenity.model.guild.audit_log.AuditLogEntry→serenity.model.id.GenericIdserenity.model.guild.audit_log.AuditLogEntry→serenity.model.id.UserIdserenity.model.guild.audit_log.Options→serenity.model.id.ApplicationIdserenity.model.guild.audit_log.Options→serenity.model.id.ChannelIdserenity.model.guild.audit_log.Options→serenity.model.id.GenericIdserenity.model.guild.audit_log.Options→serenity.model.id.MessageIdserenity.model.guild.audit_log.PartialIntegration→serenity.model.id.IntegrationId
- Direction
- model.guild.audit_log uses model.id, so a change to model.id can break model.guild.audit_log, while a change to model.guild.audit_log can't break model.id.
- 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→12 builder.create_interaction_response uses model.application.interaction✕
- Connections
- 1 pair of types, where a type in builder.create_interaction_response uses a type in model.application.interaction.
- The types involved
serenity.builder.create_interaction_response.CreateInteractionResponseMessage→serenity.model.application.interaction.InteractionResponseFlags
- Direction
- builder.create_interaction_response uses model.application.interaction, so a change to model.application.interaction can break builder.create_interaction_response, while a change to builder.create_interaction_response can't break model.application.interaction.
- Position
- Below the diagonal: builder.create_interaction_response uses a module listed above it, which is the healthy direction.
14→30 builder.create_interaction_response uses builder.create_components part of a loop✕
- Connections
- 2 pairs of types, where a type in builder.create_interaction_response uses a type in builder.create_components.
- The types involved
serenity.builder.create_interaction_response.CreateInteractionResponseMessage→serenity.builder.create_components.CreateActionRowserenity.builder.create_interaction_response.CreateModal→serenity.builder.create_components.CreateActionRow
- Direction
- builder.create_interaction_response uses builder.create_components, so a change to builder.create_components can break builder.create_interaction_response, while a change to builder.create_interaction_response can't break builder.create_components.
- 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→33 builder.create_interaction_response uses builder.create_attachment part of a loop✕
- Connections
- 2 pairs of types, where a type in builder.create_interaction_response uses a type in builder.create_attachment.
- The types involved
serenity.builder.create_interaction_response.CreateInteractionResponseMessage→serenity.builder.create_attachment.CreateAttachmentserenity.builder.create_interaction_response.CreateInteractionResponseMessage→serenity.builder.create_attachment.EditAttachments
- Direction
- builder.create_interaction_response uses builder.create_attachment, so a change to builder.create_attachment can break builder.create_interaction_response, while a change to builder.create_interaction_response can't break builder.create_attachment.
- 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→38 builder.create_interaction_response uses client.context part of a loop✕
- Connections
- 2 pairs of types, where a type in builder.create_interaction_response uses a type in client.context.
- The types involved
serenity.builder.create_interaction_response.CreateAutocompleteResponse→serenity.client.context.Contextserenity.builder.create_interaction_response.CreateInteractionResponse→serenity.client.context.Context
- Direction
- builder.create_interaction_response uses client.context, so a change to client.context can break builder.create_interaction_response, while a change to builder.create_interaction_response can't break client.context.
- 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→39 builder.create_interaction_response uses builder part of a loop✕
- Connections
- 2 pairs of types, where a type in builder.create_interaction_response uses a type in builder.
- The types involved
serenity.builder.create_interaction_response.CreateAutocompleteResponse→serenity.builder.Builderserenity.builder.create_interaction_response.CreateInteractionResponse→serenity.builder.Builder
- Direction
- builder.create_interaction_response uses builder, so a change to builder can break builder.create_interaction_response, while a change to builder.create_interaction_response can't break builder.
- 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→2 model.guild uses model.permissions✕
- Connections
- 4 pairs of types, where a type in model.guild uses a type in model.permissions.
- The types involved
serenity.model.guild.CalculatePermissions→serenity.model.permissions.Permissionsserenity.model.guild.Guild→serenity.model.permissions.Permissionsserenity.model.guild.GuildInfo→serenity.model.permissions.Permissionsserenity.model.guild.guild$module→serenity.model.permissions.Permissions
- Direction
- model.guild uses model.permissions, so a change to model.permissions can break model.guild, while a change to model.guild can't break model.permissions.
- Position
- Below the diagonal: model.guild uses a module listed above it, which is the healthy direction.
15→5 model.guild uses model.misc✕
- Connections
- 2 pairs of types, where a type in model.guild uses a type in model.misc.
- The types involved
serenity.model.guild.Guild→serenity.model.misc.ImageHashserenity.model.guild.GuildInfo→serenity.model.misc.ImageHash
- Direction
- model.guild uses model.misc, so a change to model.misc can break model.guild, while a change to model.guild can't break model.misc.
- Position
- Below the diagonal: model.guild uses a module listed above it, which is the healthy direction.
15→6 model.guild uses model.timestamp✕
- Connections
- 2 pairs of types, where a type in model.guild uses a type in model.timestamp.
- The types involved
serenity.model.guild.Guild→serenity.model.timestamp.Timestampserenity.model.guild.IncidentsData→serenity.model.timestamp.Timestamp
- Direction
- model.guild uses model.timestamp, so a change to model.timestamp can break model.guild, while a change to model.guild can't break model.timestamp.
- Position
- Below the diagonal: model.guild uses a module listed above it, which is the healthy direction.
15→7 model.guild uses model.guild.role✕
- Connections
- 1 pair of types, where a type in model.guild uses a type in model.guild.role.
- The types involved
serenity.model.guild.Guild→serenity.model.guild.role.Role
- Direction
- model.guild uses model.guild.role, so a change to model.guild.role can break model.guild, while a change to model.guild can't break model.guild.role.
- Position
- Below the diagonal: model.guild uses a module listed above it, which is the healthy direction.
15→8 model.guild uses model.user✕
- Connections
- 2 pairs of types, where a type in model.guild uses a type in model.user.
- The types involved
serenity.model.guild.Ban→serenity.model.user.Userserenity.model.guild.Guild→serenity.model.user.OnlineStatus
- Direction
- model.guild uses model.user, so a change to model.user can break model.guild, while a change to model.guild can't break model.user.
- Position
- Below the diagonal: model.guild uses a module listed above it, which is the healthy direction.
15→11 model.guild uses model.guild.scheduled_event✕
- Connections
- 1 pair of types, where a type in model.guild uses a type in model.guild.scheduled_event.
- The types involved
serenity.model.guild.Guild→serenity.model.guild.scheduled_event.ScheduledEvent
- Direction
- model.guild uses model.guild.scheduled_event, so a change to model.guild.scheduled_event can break model.guild, while a change to model.guild can't break model.guild.scheduled_event.
- Position
- Below the diagonal: model.guild uses a module listed above it, which is the healthy direction.
15→13 model.guild uses model.guild.audit_log✕
- Connections
- 1 pair of types, where a type in model.guild uses a type in model.guild.audit_log.
- The types involved
serenity.model.guild.Guild→serenity.model.guild.audit_log.Action
- Direction
- model.guild uses model.guild.audit_log, so a change to model.guild.audit_log can break model.guild, while a change to model.guild can't break model.guild.audit_log.
- Position
- Below the diagonal: model.guild uses a module listed above it, which is the healthy direction.
15→21 model.guild uses http.client part of a loop✕
- Connections
- 1 pair of types, where a type in model.guild uses a type in http.client.
- The types involved
serenity.model.guild.Guild→serenity.http.client.Http
- Direction
- model.guild uses http.client, so a change to http.client can break model.guild, while a change to model.guild can't break http.client.
- 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→23 model.guild uses model.channel part of a loop✕
- Connections
- 1 pair of types, where a type in model.guild uses a type in model.channel.
- The types involved
serenity.model.guild.Guild→serenity.model.channel.StageInstance
- Direction
- model.guild uses model.channel, so a change to model.channel can break model.guild, while a change to model.guild can't break model.channel.
- 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→26 model.guild uses collector part of a loop✕
- Connections
- 2 pairs of types, where a type in model.guild uses a type in collector.
- The types involved
serenity.model.guild.Guild→serenity.collector.MessageCollectorserenity.model.guild.Guild→serenity.collector.ReactionCollector
- Direction
- model.guild uses collector, so a change to collector can break model.guild, while a change to model.guild can't break collector.
- 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→27 model.guild uses model.channel.guild_channel part of a loop✕
- Connections
- 1 pair of types, where a type in model.guild uses a type in model.channel.guild_channel.
- The types involved
serenity.model.guild.Guild→serenity.model.channel.guild_channel.GuildChannel
- Direction
- model.guild uses model.channel.guild_channel, so a change to model.channel.guild_channel can break model.guild, while a change to model.guild can't break model.channel.guild_channel.
- 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→28 model.guild uses model.guild.member part of a loop✕
- Connections
- 2 pairs of types, where a type in model.guild uses a type in model.guild.member.
- The types involved
serenity.model.guild.Guild→serenity.model.guild.member.Memberserenity.model.guild.Guild→serenity.model.guild.member.PartialMember
- Direction
- model.guild uses model.guild.member, so a change to model.guild.member can break model.guild, while a change to model.guild can't break model.guild.member.
- 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→35 model.guild uses model.id part of a loop✕
- Connections
- 13 pairs of types, where a type in model.guild uses a type in model.id.
- The types involved
serenity.model.guild.AfkMetadata→serenity.model.id.ChannelIdserenity.model.guild.BulkBanResponse→serenity.model.id.UserIdserenity.model.guild.Guild→serenity.model.id.ApplicationIdserenity.model.guild.Guild→serenity.model.id.AuditLogEntryIdserenity.model.guild.Guild→serenity.model.id.ChannelIdserenity.model.guild.Guild→serenity.model.id.CommandIdserenity.model.guild.Guild→serenity.model.id.EmojiIdserenity.model.guild.Guild→serenity.model.id.GuildIdserenity.model.guild.Guild→serenity.model.id.SoundIdserenity.model.guild.Guild→serenity.model.id.UserIdserenity.model.guild.GuildInfo→serenity.model.id.GuildIdserenity.model.guild.GuildWidget→serenity.model.id.ChannelIdserenity.model.guild.UnavailableGuild→serenity.model.id.GuildId
- Direction
- model.guild uses model.id, so a change to model.id can break model.guild, while a change to model.guild can't break model.id.
- 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→36 model.guild uses cache part of a loop✕
- Connections
- 1 pair of types, where a type in model.guild uses a type in cache.
- The types involved
serenity.model.guild.Guild→serenity.cache.Cache
- Direction
- model.guild uses cache, so a change to cache can break model.guild, while a change to model.guild can't break cache.
- 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→2 model.application.component_interaction uses model.permissions✕
- Connections
- 1 pair of types, where a type in model.application.component_interaction uses a type in model.permissions.
- The types involved
serenity.model.application.component_interaction.ComponentInteraction→serenity.model.permissions.Permissions
- Direction
- model.application.component_interaction uses model.permissions, so a change to model.permissions can break model.application.component_interaction, while a change to model.application.component_interaction can't break model.permissions.
- Position
- Below the diagonal: model.application.component_interaction uses a module listed above it, which is the healthy direction.
16→3 model.application.component_interaction uses builder.create_interaction_response_followup✕
- Connections
- 1 pair of types, where a type in model.application.component_interaction uses a type in builder.create_interaction_response_followup.
- The types involved
serenity.model.application.component_interaction.ComponentInteraction→serenity.builder.create_interaction_response_followup.CreateInteractionResponseFollowup
- Direction
- model.application.component_interaction uses builder.create_interaction_response_followup, so a change to builder.create_interaction_response_followup can break model.application.component_interaction, while a change to model.application.component_interaction can't break builder.create_interaction_response_followup.
- Position
- Below the diagonal: model.application.component_interaction uses a module listed above it, which is the healthy direction.
16→4 model.application.component_interaction uses builder.edit_interaction_response✕
- Connections
- 1 pair of types, where a type in model.application.component_interaction uses a type in builder.edit_interaction_response.
- The types involved
serenity.model.application.component_interaction.ComponentInteraction→serenity.builder.edit_interaction_response.EditInteractionResponse
- Direction
- model.application.component_interaction uses builder.edit_interaction_response, so a change to builder.edit_interaction_response can break model.application.component_interaction, while a change to model.application.component_interaction can't break builder.edit_interaction_response.
- Position
- Below the diagonal: model.application.component_interaction uses a module listed above it, which is the healthy direction.
16→8 model.application.component_interaction uses model.user✕
- Connections
- 1 pair of types, where a type in model.application.component_interaction uses a type in model.user.
- The types involved
serenity.model.application.component_interaction.ComponentInteraction→serenity.model.user.User
- Direction
- model.application.component_interaction uses model.user, so a change to model.user can break model.application.component_interaction, while a change to model.application.component_interaction can't break model.user.
- Position
- Below the diagonal: model.application.component_interaction uses a module listed above it, which is the healthy direction.
16→9 model.application.component_interaction uses model.application.command_interaction✕
- Connections
- 1 pair of types, where a type in model.application.component_interaction uses a type in model.application.command_interaction.
- The types involved
serenity.model.application.component_interaction.ComponentInteractionData→serenity.model.application.command_interaction.CommandDataResolved
- Direction
- model.application.component_interaction uses model.application.command_interaction, so a change to model.application.command_interaction can break model.application.component_interaction, while a change to model.application.component_interaction can't break model.application.command_interaction.
- Position
- Below the diagonal: model.application.component_interaction uses a module listed above it, which is the healthy direction.
16→12 model.application.component_interaction uses model.application.interaction✕
- Connections
- 1 pair of types, where a type in model.application.component_interaction uses a type in model.application.interaction.
- The types involved
serenity.model.application.component_interaction.ComponentInteraction→serenity.model.application.interaction.AuthorizingIntegrationOwners
- Direction
- model.application.component_interaction uses model.application.interaction, so a change to model.application.interaction can break model.application.component_interaction, while a change to model.application.component_interaction can't break model.application.interaction.
- Position
- Below the diagonal: model.application.component_interaction uses a module listed above it, which is the healthy direction.
16→14 model.application.component_interaction uses builder.create_interaction_response✕
- Connections
- 1 pair of types, where a type in model.application.component_interaction uses a type in builder.create_interaction_response.
- The types involved
serenity.model.application.component_interaction.ComponentInteraction→serenity.builder.create_interaction_response.CreateInteractionResponse
- Direction
- model.application.component_interaction uses builder.create_interaction_response, so a change to builder.create_interaction_response can break model.application.component_interaction, while a change to model.application.component_interaction can't break builder.create_interaction_response.
- Position
- Below the diagonal: model.application.component_interaction uses a module listed above it, which is the healthy direction.
16→28 model.application.component_interaction uses model.guild.member part of a loop✕
- Connections
- 1 pair of types, where a type in model.application.component_interaction uses a type in model.guild.member.
- The types involved
serenity.model.application.component_interaction.ComponentInteraction→serenity.model.guild.member.Member
- Direction
- model.application.component_interaction uses model.guild.member, so a change to model.guild.member can break model.application.component_interaction, while a change to model.application.component_interaction can't break model.guild.member.
- 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→32 model.application.component_interaction uses model.channel.message part of a loop✕
- Connections
- 1 pair of types, where a type in model.application.component_interaction uses a type in model.channel.message.
- The types involved
serenity.model.application.component_interaction.ComponentInteraction→serenity.model.channel.message.Message
- Direction
- model.application.component_interaction uses model.channel.message, so a change to model.channel.message can break model.application.component_interaction, while a change to model.application.component_interaction can't break model.channel.message.
- 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→35 model.application.component_interaction uses model.id part of a loop✕
- Connections
- 4 pairs of types, where a type in model.application.component_interaction uses a type in model.id.
- The types involved
serenity.model.application.component_interaction.ComponentInteraction→serenity.model.id.ApplicationIdserenity.model.application.component_interaction.ComponentInteraction→serenity.model.id.ChannelIdserenity.model.application.component_interaction.ComponentInteraction→serenity.model.id.GuildIdserenity.model.application.component_interaction.ComponentInteraction→serenity.model.id.InteractionId
- Direction
- model.application.component_interaction uses model.id, so a change to model.id can break model.application.component_interaction, while a change to model.application.component_interaction can't break model.id.
- 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→38 model.application.component_interaction uses client.context part of a loop✕
- Connections
- 1 pair of types, where a type in model.application.component_interaction uses a type in client.context.
- The types involved
serenity.model.application.component_interaction.ComponentInteraction→serenity.client.context.Context
- Direction
- model.application.component_interaction uses client.context, so a change to client.context can break model.application.component_interaction, while a change to model.application.component_interaction can't break client.context.
- 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.
17→5 model.gateway uses model.misc✕
- Connections
- 1 pair of types, where a type in model.gateway uses a type in model.misc.
- The types involved
serenity.model.gateway.PresenceUser→serenity.model.misc.ImageHash
- Direction
- model.gateway uses model.misc, so a change to model.misc can break model.gateway, while a change to model.gateway can't break model.misc.
- Position
- Below the diagonal: model.gateway uses a module listed above it, which is the healthy direction.
17→8 model.gateway uses model.user✕
- Connections
- 9 pairs of types, where a type in model.gateway uses a type in model.user.
- The types involved
serenity.model.gateway.ClientStatus→serenity.model.user.OnlineStatusserenity.model.gateway.Presence→serenity.model.user.OnlineStatusserenity.model.gateway.PresenceUser→serenity.model.user.AvatarDecorationDataserenity.model.gateway.PresenceUser→serenity.model.user.Collectiblesserenity.model.gateway.PresenceUser→serenity.model.user.PremiumTypeserenity.model.gateway.PresenceUser→serenity.model.user.PrimaryGuildserenity.model.gateway.PresenceUser→serenity.model.user.Userserenity.model.gateway.PresenceUser→serenity.model.user.UserPublicFlagsserenity.model.gateway.Ready→serenity.model.user.CurrentUser
- Direction
- model.gateway uses model.user, so a change to model.user can break model.gateway, while a change to model.gateway can't break model.user.
- Position
- Below the diagonal: model.gateway uses a module listed above it, which is the healthy direction.
17→15 model.gateway uses model.guild✕
- Connections
- 1 pair of types, where a type in model.gateway uses a type in model.guild.
- The types involved
serenity.model.gateway.Ready→serenity.model.guild.UnavailableGuild
- Direction
- model.gateway uses model.guild, so a change to model.guild can break model.gateway, while a change to model.gateway can't break model.guild.
- Position
- Below the diagonal: model.gateway uses a module listed above it, which is the healthy direction.
17→28 model.gateway uses model.guild.member part of a loop✕
- Connections
- 1 pair of types, where a type in model.gateway uses a type in model.guild.member.
- The types involved
serenity.model.gateway.PresenceUser→serenity.model.guild.member.PartialMember
- Direction
- model.gateway uses model.guild.member, so a change to model.guild.member can break model.gateway, while a change to model.gateway can't break model.guild.member.
- 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.
17→35 model.gateway uses model.id part of a loop✕
- Connections
- 5 pairs of types, where a type in model.gateway uses a type in model.id.
- The types involved
serenity.model.gateway.Activity→serenity.model.id.ApplicationIdserenity.model.gateway.ActivityEmoji→serenity.model.id.EmojiIdserenity.model.gateway.Presence→serenity.model.id.GuildIdserenity.model.gateway.PresenceUser→serenity.model.id.UserIdserenity.model.gateway.ShardInfo→serenity.model.id.ShardId
- Direction
- model.gateway uses model.id, so a change to model.id can break model.gateway, while a change to model.gateway can't break model.id.
- 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→2 model.guild.partial_guild uses model.permissions✕
- Connections
- 1 pair of types, where a type in model.guild.partial_guild uses a type in model.permissions.
- The types involved
serenity.model.guild.partial_guild.PartialGuild→serenity.model.permissions.Permissions
- Direction
- model.guild.partial_guild uses model.permissions, so a change to model.permissions can break model.guild.partial_guild, while a change to model.guild.partial_guild can't break model.permissions.
- Position
- Below the diagonal: model.guild.partial_guild uses a module listed above it, which is the healthy direction.
18→5 model.guild.partial_guild uses model.misc✕
- Connections
- 1 pair of types, where a type in model.guild.partial_guild uses a type in model.misc.
- The types involved
serenity.model.guild.partial_guild.PartialGuild→serenity.model.misc.ImageHash
- Direction
- model.guild.partial_guild uses model.misc, so a change to model.misc can break model.guild.partial_guild, while a change to model.guild.partial_guild can't break model.misc.
- Position
- Below the diagonal: model.guild.partial_guild uses a module listed above it, which is the healthy direction.
18→7 model.guild.partial_guild uses model.guild.role✕
- Connections
- 1 pair of types, where a type in model.guild.partial_guild uses a type in model.guild.role.
- The types involved
serenity.model.guild.partial_guild.PartialGuild→serenity.model.guild.role.Role
- Direction
- model.guild.partial_guild uses model.guild.role, so a change to model.guild.role can break model.guild.partial_guild, while a change to model.guild.partial_guild can't break model.guild.role.
- Position
- Below the diagonal: model.guild.partial_guild uses a module listed above it, which is the healthy direction.
18→13 model.guild.partial_guild uses model.guild.audit_log✕
- Connections
- 1 pair of types, where a type in model.guild.partial_guild uses a type in model.guild.audit_log.
- The types involved
serenity.model.guild.partial_guild.PartialGuild→serenity.model.guild.audit_log.Action
- Direction
- model.guild.partial_guild uses model.guild.audit_log, so a change to model.guild.audit_log can break model.guild.partial_guild, while a change to model.guild.partial_guild can't break model.guild.audit_log.
- Position
- Below the diagonal: model.guild.partial_guild uses a module listed above it, which is the healthy direction.
18→15 model.guild.partial_guild uses model.guild✕
- Connections
- 8 pairs of types, where a type in model.guild.partial_guild uses a type in model.guild.
- The types involved
serenity.model.guild.partial_guild.PartialGuild→serenity.model.guild.AfkMetadataserenity.model.guild.partial_guild.PartialGuild→serenity.model.guild.DefaultMessageNotificationLevelserenity.model.guild.partial_guild.PartialGuild→serenity.model.guild.ExplicitContentFilterserenity.model.guild.partial_guild.PartialGuild→serenity.model.guild.Guildserenity.model.guild.partial_guild.PartialGuild→serenity.model.guild.IncidentsDataserenity.model.guild.partial_guild.PartialGuild→serenity.model.guild.MfaLevelserenity.model.guild.partial_guild.PartialGuild→serenity.model.guild.NsfwLevelserenity.model.guild.partial_guild.PartialGuild→serenity.model.guild.VerificationLevel
- Direction
- model.guild.partial_guild uses model.guild, so a change to model.guild can break model.guild.partial_guild, while a change to model.guild.partial_guild can't break model.guild.
- Position
- Below the diagonal: model.guild.partial_guild uses a module listed above it, which is the healthy direction.
18→26 model.guild.partial_guild uses collector part of a loop✕
- Connections
- 2 pairs of types, where a type in model.guild.partial_guild uses a type in collector.
- The types involved
serenity.model.guild.partial_guild.PartialGuild→serenity.collector.MessageCollectorserenity.model.guild.partial_guild.PartialGuild→serenity.collector.ReactionCollector
- Direction
- model.guild.partial_guild uses collector, so a change to collector can break model.guild.partial_guild, while a change to model.guild.partial_guild can't break collector.
- 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→27 model.guild.partial_guild uses model.channel.guild_channel part of a loop✕
- Connections
- 1 pair of types, where a type in model.guild.partial_guild uses a type in model.channel.guild_channel.
- The types involved
serenity.model.guild.partial_guild.PartialGuild→serenity.model.channel.guild_channel.GuildChannel
- Direction
- model.guild.partial_guild uses model.channel.guild_channel, so a change to model.channel.guild_channel can break model.guild.partial_guild, while a change to model.guild.partial_guild can't break model.channel.guild_channel.
- 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→28 model.guild.partial_guild uses model.guild.member part of a loop✕
- Connections
- 2 pairs of types, where a type in model.guild.partial_guild uses a type in model.guild.member.
- The types involved
serenity.model.guild.partial_guild.PartialGuild→serenity.model.guild.member.Memberserenity.model.guild.partial_guild.PartialGuild→serenity.model.guild.member.PartialMember
- Direction
- model.guild.partial_guild uses model.guild.member, so a change to model.guild.member can break model.guild.partial_guild, while a change to model.guild.partial_guild can't break model.guild.member.
- 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→35 model.guild.partial_guild uses model.id part of a loop✕
- Connections
- 8 pairs of types, where a type in model.guild.partial_guild uses a type in model.id.
- The types involved
serenity.model.guild.partial_guild.PartialGuild→serenity.model.id.ApplicationIdserenity.model.guild.partial_guild.PartialGuild→serenity.model.id.AuditLogEntryIdserenity.model.guild.partial_guild.PartialGuild→serenity.model.id.ChannelIdserenity.model.guild.partial_guild.PartialGuild→serenity.model.id.CommandIdserenity.model.guild.partial_guild.PartialGuild→serenity.model.id.EmojiIdserenity.model.guild.partial_guild.PartialGuild→serenity.model.id.GuildIdserenity.model.guild.partial_guild.PartialGuild→serenity.model.id.SoundIdserenity.model.guild.partial_guild.PartialGuild→serenity.model.id.UserId
- Direction
- model.guild.partial_guild uses model.id, so a change to model.id can break model.guild.partial_guild, while a change to model.guild.partial_guild can't break model.id.
- 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→8 gateway uses model.user✕
- Connections
- 1 pair of types, where a type in gateway uses a type in model.user.
- The types involved
serenity.gateway.PresenceData→serenity.model.user.OnlineStatus
- Direction
- gateway uses model.user, so a change to model.user can break gateway, while a change to gateway can't break model.user.
- Position
- Below the diagonal: gateway uses a module listed above it, which is the healthy direction.
19→17 gateway uses model.gateway✕
- Connections
- 2 pairs of types, where a type in gateway uses a type in model.gateway.
- The types involved
serenity.gateway.ActivityData→serenity.model.gateway.Activityserenity.gateway.ActivityData→serenity.model.gateway.ActivityType
- Direction
- gateway uses model.gateway, so a change to model.gateway can break gateway, while a change to gateway can't break model.gateway.
- Position
- Below the diagonal: gateway uses a module listed above it, which is the healthy direction.
20→8 client uses model.user✕
- Connections
- 1 pair of types, where a type in client uses a type in model.user.
- The types involved
serenity.client.ClientBuilder→serenity.model.user.OnlineStatus
- Direction
- client uses model.user, so a change to model.user can break client, while a change to client can't break model.user.
- Position
- Below the diagonal: client uses a module listed above it, which is the healthy direction.
20→17 client uses model.gateway✕
- Connections
- 2 pairs of types, where a type in client uses a type in model.gateway.
- The types involved
serenity.client.Client→serenity.model.gateway.GatewayIntentsserenity.client.ClientBuilder→serenity.model.gateway.GatewayIntents
- Direction
- client uses model.gateway, so a change to model.gateway can break client, while a change to client can't break model.gateway.
- Position
- Below the diagonal: client uses a module listed above it, which is the healthy direction.
20→19 client uses gateway✕
- Connections
- 2 pairs of types, where a type in client uses a type in gateway.
- The types involved
serenity.client.ClientBuilder→serenity.gateway.ActivityDataserenity.client.ClientBuilder→serenity.gateway.PresenceData
- Direction
- client uses gateway, so a change to gateway can break client, while a change to client can't break gateway.
- Position
- Below the diagonal: client uses a module listed above it, which is the healthy direction.
20→21 client uses http.client part of a loop✕
- Connections
- 2 pairs of types, where a type in client uses a type in http.client.
- The types involved
serenity.client.Client→serenity.http.client.Httpserenity.client.ClientBuilder→serenity.http.client.Http
- Direction
- client uses http.client, so a change to http.client can break client, while a change to client can't break http.client.
- 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→35 client uses model.id part of a loop✕
- Connections
- 1 pair of types, where a type in client uses a type in model.id.
- The types involved
serenity.client.ClientBuilder→serenity.model.id.ApplicationId
- Direction
- client uses model.id, so a change to model.id can break client, while a change to client can't break model.id.
- 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→36 client uses cache part of a loop✕
- Connections
- 1 pair of types, where a type in client uses a type in cache.
- The types involved
serenity.client.Client→serenity.cache.Cache
- Direction
- client uses cache, so a change to cache can break client, while a change to client can't break cache.
- 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→13 http.client uses model.guild.audit_log✕
- Connections
- 1 pair of types, where a type in http.client uses a type in model.guild.audit_log.
- The types involved
serenity.http.client.Http→serenity.model.guild.audit_log.Action
- Direction
- http.client uses model.guild.audit_log, so a change to model.guild.audit_log can break http.client, while a change to http.client can't break model.guild.audit_log.
- Position
- Below the diagonal: http.client uses a module listed above it, which is the healthy direction.
21→20 http.client uses client✕
- Connections
- 3 pairs of types, where a type in http.client uses a type in client.
- The types involved
serenity.http.client.Http→serenity.client.Clientserenity.http.client.HttpBuilder→serenity.client.Clientserenity.http.client.client$module→serenity.client.ClientBuilder
- Direction
- http.client uses client, so a change to client can break http.client, while a change to http.client can't break client.
- Position
- Below the diagonal: http.client uses a module listed above it, which is the healthy direction.
21→29 http.client uses model.channel.reaction part of a loop✕
- Connections
- 1 pair of types, where a type in http.client uses a type in model.channel.reaction.
- The types involved
serenity.http.client.Http→serenity.model.channel.reaction.ReactionType
- Direction
- http.client uses model.channel.reaction, so a change to model.channel.reaction can break http.client, while a change to http.client can't break model.channel.reaction.
- 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→33 http.client uses builder.create_attachment part of a loop✕
- Connections
- 1 pair of types, where a type in http.client uses a type in builder.create_attachment.
- The types involved
serenity.http.client.Http→serenity.builder.create_attachment.CreateAttachment
- Direction
- http.client uses builder.create_attachment, so a change to builder.create_attachment can break http.client, while a change to http.client can't break builder.create_attachment.
- 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→35 http.client uses model.id part of a loop✕
- Connections
- 22 pairs of types, where a type in http.client uses a type in model.id.
- The types involved
serenity.http.client.Http→serenity.model.id.AnswerIdserenity.http.client.Http→serenity.model.id.ApplicationIdserenity.http.client.Http→serenity.model.id.AuditLogEntryIdserenity.http.client.Http→serenity.model.id.ChannelIdserenity.http.client.Http→serenity.model.id.CommandIdserenity.http.client.Http→serenity.model.id.EmojiIdserenity.http.client.Http→serenity.model.id.EntitlementIdserenity.http.client.Http→serenity.model.id.GuildIdserenity.http.client.Http→serenity.model.id.IntegrationIdserenity.http.client.Http→serenity.model.id.InteractionIdserenity.http.client.Http→serenity.model.id.MessageIdserenity.http.client.Http→serenity.model.id.RoleIdserenity.http.client.Http→serenity.model.id.RuleIdserenity.http.client.Http→serenity.model.id.ScheduledEventIdserenity.http.client.Http→serenity.model.id.SkuIdserenity.http.client.Http→serenity.model.id.SoundIdserenity.http.client.Http→serenity.model.id.StickerIdserenity.http.client.Http→serenity.model.id.StickerPackIdserenity.http.client.Http→serenity.model.id.TargetIdserenity.http.client.Http→serenity.model.id.UserIdserenity.http.client.Http→serenity.model.id.WebhookIdserenity.http.client.HttpBuilder→serenity.model.id.ApplicationId
- Direction
- http.client uses model.id, so a change to model.id can break http.client, while a change to http.client can't break model.id.
- 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.
22→6 model.channel.private_channel uses model.timestamp✕
- Connections
- 1 pair of types, where a type in model.channel.private_channel uses a type in model.timestamp.
- The types involved
serenity.model.channel.private_channel.PrivateChannel→serenity.model.timestamp.Timestamp
- Direction
- model.channel.private_channel uses model.timestamp, so a change to model.timestamp can break model.channel.private_channel, while a change to model.channel.private_channel can't break model.timestamp.
- Position
- Below the diagonal: model.channel.private_channel uses a module listed above it, which is the healthy direction.
22→8 model.channel.private_channel uses model.user✕
- Connections
- 1 pair of types, where a type in model.channel.private_channel uses a type in model.user.
- The types involved
serenity.model.channel.private_channel.PrivateChannel→serenity.model.user.User
- Direction
- model.channel.private_channel uses model.user, so a change to model.user can break model.channel.private_channel, while a change to model.channel.private_channel can't break model.user.
- Position
- Below the diagonal: model.channel.private_channel uses a module listed above it, which is the healthy direction.
22→21 model.channel.private_channel uses http.client✕
- Connections
- 1 pair of types, where a type in model.channel.private_channel uses a type in http.client.
- The types involved
serenity.model.channel.private_channel.PrivateChannel→serenity.http.client.Http
- Direction
- model.channel.private_channel uses http.client, so a change to http.client can break model.channel.private_channel, while a change to model.channel.private_channel can't break http.client.
- Position
- Below the diagonal: model.channel.private_channel uses a module listed above it, which is the healthy direction.
22→23 model.channel.private_channel uses model.channel part of a loop✕
- Connections
- 2 pairs of types, where a type in model.channel.private_channel uses a type in model.channel.
- The types involved
serenity.model.channel.private_channel.PrivateChannel→serenity.model.channel.ChannelTypeserenity.model.channel.private_channel.PrivateChannel→serenity.model.channel.PermissionOverwriteType
- Direction
- model.channel.private_channel uses model.channel, so a change to model.channel can break model.channel.private_channel, while a change to model.channel.private_channel can't break model.channel.
- 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.
22→31 model.channel.private_channel uses builder.edit_message part of a loop✕
- Connections
- 1 pair of types, where a type in model.channel.private_channel uses a type in builder.edit_message.
- The types involved
serenity.model.channel.private_channel.PrivateChannel→serenity.builder.edit_message.EditMessage
- Direction
- model.channel.private_channel uses builder.edit_message, so a change to builder.edit_message can break model.channel.private_channel, while a change to model.channel.private_channel can't break builder.edit_message.
- 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.
22→34 model.channel.private_channel uses builder.create_message part of a loop✕
- Connections
- 1 pair of types, where a type in model.channel.private_channel uses a type in builder.create_message.
- The types involved
serenity.model.channel.private_channel.PrivateChannel→serenity.builder.create_message.CreateMessage
- Direction
- model.channel.private_channel uses builder.create_message, so a change to builder.create_message can break model.channel.private_channel, while a change to model.channel.private_channel can't break builder.create_message.
- 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.
22→35 model.channel.private_channel uses model.id part of a loop✕
- Connections
- 3 pairs of types, where a type in model.channel.private_channel uses a type in model.id.
- The types involved
serenity.model.channel.private_channel.PrivateChannel→serenity.model.id.ChannelIdserenity.model.channel.private_channel.PrivateChannel→serenity.model.id.MessageIdserenity.model.channel.private_channel.PrivateChannel→serenity.model.id.UserId
- Direction
- model.channel.private_channel uses model.id, so a change to model.id can break model.channel.private_channel, while a change to model.channel.private_channel can't break model.id.
- 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.
23→2 model.channel uses model.permissions✕
- Connections
- 2 pairs of types, where a type in model.channel uses a type in model.permissions.
- The types involved
serenity.model.channel.PermissionOverwrite→serenity.model.permissions.Permissionsserenity.model.channel.PermissionOverwriteData→serenity.model.permissions.Permissions
- Direction
- model.channel uses model.permissions, so a change to model.permissions can break model.channel, while a change to model.channel can't break model.permissions.
- Position
- Below the diagonal: model.channel uses a module listed above it, which is the healthy direction.
23→6 model.channel uses model.timestamp✕
- Connections
- 1 pair of types, where a type in model.channel uses a type in model.timestamp.
- The types involved
serenity.model.channel.ThreadMetadata→serenity.model.timestamp.Timestamp
- Direction
- model.channel uses model.timestamp, so a change to model.timestamp can break model.channel, while a change to model.channel can't break model.timestamp.
- Position
- Below the diagonal: model.channel uses a module listed above it, which is the healthy direction.
23→22 model.channel uses model.channel.private_channel✕
- Connections
- 1 pair of types, where a type in model.channel uses a type in model.channel.private_channel.
- The types involved
serenity.model.channel.Channel→serenity.model.channel.private_channel.PrivateChannel
- Direction
- model.channel uses model.channel.private_channel, so a change to model.channel.private_channel can break model.channel, while a change to model.channel can't break model.channel.private_channel.
- Position
- Below the diagonal: model.channel uses a module listed above it, which is the healthy direction.
23→27 model.channel uses model.channel.guild_channel part of a loop✕
- Connections
- 2 pairs of types, where a type in model.channel uses a type in model.channel.guild_channel.
- The types involved
serenity.model.channel.Channel→serenity.model.channel.guild_channel.GuildChannelserenity.model.channel.ThreadsData→serenity.model.channel.guild_channel.GuildChannel
- Direction
- model.channel uses model.channel.guild_channel, so a change to model.channel.guild_channel can break model.channel, while a change to model.channel can't break model.channel.guild_channel.
- 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.
23→28 model.channel uses model.guild.member part of a loop✕
- Connections
- 1 pair of types, where a type in model.channel uses a type in model.guild.member.
- The types involved
serenity.model.channel.ThreadsData→serenity.model.guild.member.ThreadMember
- Direction
- model.channel uses model.guild.member, so a change to model.guild.member can break model.channel, while a change to model.channel can't break model.guild.member.
- 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.
23→35 model.channel uses model.id part of a loop✕
- Connections
- 9 pairs of types, where a type in model.channel uses a type in model.id.
- The types involved
serenity.model.channel.Channel→serenity.model.id.ChannelIdserenity.model.channel.Channel→serenity.model.id.GuildIdserenity.model.channel.ForumTag→serenity.model.id.ForumTagIdserenity.model.channel.PermissionOverwriteData→serenity.model.id.TargetIdserenity.model.channel.RawForumEmoji→serenity.model.id.EmojiIdserenity.model.channel.StageInstance→serenity.model.id.ChannelIdserenity.model.channel.StageInstance→serenity.model.id.GuildIdserenity.model.channel.StageInstance→serenity.model.id.ScheduledEventIdserenity.model.channel.StageInstance→serenity.model.id.StageInstanceId
- Direction
- model.channel uses model.id, so a change to model.id can break model.channel, while a change to model.channel can't break model.id.
- 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.
24→5 model.invite uses model.misc✕
- Connections
- 1 pair of types, where a type in model.invite uses a type in model.misc.
- The types involved
serenity.model.invite.InviteGuild→serenity.model.misc.ImageHash
- Direction
- model.invite uses model.misc, so a change to model.misc can break model.invite, while a change to model.invite can't break model.misc.
- Position
- Below the diagonal: model.invite uses a module listed above it, which is the healthy direction.
24→6 model.invite uses model.timestamp✕
- Connections
- 2 pairs of types, where a type in model.invite uses a type in model.timestamp.
- The types involved
serenity.model.invite.Invite→serenity.model.timestamp.Timestampserenity.model.invite.RichInvite→serenity.model.timestamp.Timestamp
- Direction
- model.invite uses model.timestamp, so a change to model.timestamp can break model.invite, while a change to model.invite can't break model.timestamp.
- Position
- Below the diagonal: model.invite uses a module listed above it, which is the healthy direction.
24→8 model.invite uses model.user✕
- Connections
- 2 pairs of types, where a type in model.invite uses a type in model.user.
- The types involved
serenity.model.invite.Invite→serenity.model.user.Userserenity.model.invite.RichInvite→serenity.model.user.User
- Direction
- model.invite uses model.user, so a change to model.user can break model.invite, while a change to model.invite can't break model.user.
- Position
- Below the diagonal: model.invite uses a module listed above it, which is the healthy direction.
24→11 model.invite uses model.guild.scheduled_event✕
- Connections
- 1 pair of types, where a type in model.invite uses a type in model.guild.scheduled_event.
- The types involved
serenity.model.invite.Invite→serenity.model.guild.scheduled_event.ScheduledEvent
- Direction
- model.invite uses model.guild.scheduled_event, so a change to model.guild.scheduled_event can break model.invite, while a change to model.invite can't break model.guild.scheduled_event.
- Position
- Below the diagonal: model.invite uses a module listed above it, which is the healthy direction.
24→15 model.invite uses model.guild✕
- Connections
- 2 pairs of types, where a type in model.invite uses a type in model.guild.
- The types involved
serenity.model.invite.InviteGuild→serenity.model.guild.NsfwLevelserenity.model.invite.InviteGuild→serenity.model.guild.VerificationLevel
- Direction
- model.invite uses model.guild, so a change to model.guild can break model.invite, while a change to model.invite can't break model.guild.
- Position
- Below the diagonal: model.invite uses a module listed above it, which is the healthy direction.
24→23 model.invite uses model.channel✕
- Connections
- 1 pair of types, where a type in model.invite uses a type in model.channel.
- The types involved
serenity.model.invite.InviteChannel→serenity.model.channel.ChannelType
- Direction
- model.invite uses model.channel, so a change to model.channel can break model.invite, while a change to model.invite can't break model.channel.
- Position
- Below the diagonal: model.invite uses a module listed above it, which is the healthy direction.
24→28 model.invite uses model.guild.member part of a loop✕
- Connections
- 1 pair of types, where a type in model.invite uses a type in model.guild.member.
- The types involved
serenity.model.invite.InviteStageInstance→serenity.model.guild.member.PartialMember
- Direction
- model.invite uses model.guild.member, so a change to model.guild.member can break model.invite, while a change to model.invite can't break model.guild.member.
- 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.
24→35 model.invite uses model.id part of a loop✕
- Connections
- 5 pairs of types, where a type in model.invite uses a type in model.id.
- The types involved
serenity.model.invite.Invite→serenity.model.id.ApplicationIdserenity.model.invite.Invite→serenity.model.id.ScheduledEventIdserenity.model.invite.Invite→serenity.model.id.UserIdserenity.model.invite.InviteChannel→serenity.model.id.ChannelIdserenity.model.invite.InviteGuild→serenity.model.id.GuildId
- Direction
- model.invite uses model.id, so a change to model.id can break model.invite, while a change to model.invite can't break model.id.
- 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.
25→5 model.event uses model.misc✕
- Connections
- 1 pair of types, where a type in model.event uses a type in model.misc.
- The types involved
serenity.model.event.GuildMemberUpdateEvent→serenity.model.misc.ImageHash
- Direction
- model.event uses model.misc, so a change to model.misc can break model.event, while a change to model.event can't break model.misc.
- Position
- Below the diagonal: model.event uses a module listed above it, which is the healthy direction.
25→6 model.event uses model.timestamp✕
- Connections
- 4 pairs of types, where a type in model.event uses a type in model.timestamp.
- The types involved
serenity.model.event.ChannelPinsUpdateEvent→serenity.model.timestamp.Timestampserenity.model.event.GuildMemberUpdateEvent→serenity.model.timestamp.Timestampserenity.model.event.InviteCreateEvent→serenity.model.timestamp.Timestampserenity.model.event.MessageUpdateEvent→serenity.model.timestamp.Timestamp
- Direction
- model.event uses model.timestamp, so a change to model.timestamp can break model.event, while a change to model.event can't break model.timestamp.
- Position
- Below the diagonal: model.event uses a module listed above it, which is the healthy direction.
25→7 model.event uses model.guild.role✕
- Connections
- 3 pairs of types, where a type in model.event uses a type in model.guild.role.
- The types involved
serenity.model.event.GuildRoleCreateEvent→serenity.model.guild.role.Roleserenity.model.event.GuildRoleUpdateEvent→serenity.model.guild.role.Roleserenity.model.event.RoleEventHelper→serenity.model.guild.role.Role
- Direction
- model.event uses model.guild.role, so a change to model.guild.role can break model.event, while a change to model.event can't break model.guild.role.
- Position
- Below the diagonal: model.event uses a module listed above it, which is the healthy direction.
25→8 model.event uses model.user✕
- Connections
- 8 pairs of types, where a type in model.event uses a type in model.user.
- The types involved
serenity.model.event.GuildBanAddEvent→serenity.model.user.Userserenity.model.event.GuildBanRemoveEvent→serenity.model.user.Userserenity.model.event.GuildMemberRemoveEvent→serenity.model.user.Userserenity.model.event.GuildMemberUpdateEvent→serenity.model.user.AvatarDecorationDataserenity.model.event.GuildMemberUpdateEvent→serenity.model.user.Userserenity.model.event.InviteCreateEvent→serenity.model.user.Userserenity.model.event.MessageUpdateEvent→serenity.model.user.Userserenity.model.event.UserUpdateEvent→serenity.model.user.CurrentUser
- Direction
- model.event uses model.user, so a change to model.user can break model.event, while a change to model.event can't break model.user.
- Position
- Below the diagonal: model.event uses a module listed above it, which is the healthy direction.
25→11 model.event uses model.guild.scheduled_event✕
- Connections
- 3 pairs of types, where a type in model.event uses a type in model.guild.scheduled_event.
- The types involved
serenity.model.event.GuildScheduledEventCreateEvent→serenity.model.guild.scheduled_event.ScheduledEventserenity.model.event.GuildScheduledEventDeleteEvent→serenity.model.guild.scheduled_event.ScheduledEventserenity.model.event.GuildScheduledEventUpdateEvent→serenity.model.guild.scheduled_event.ScheduledEvent
- Direction
- model.event uses model.guild.scheduled_event, so a change to model.guild.scheduled_event can break model.event, while a change to model.event can't break model.guild.scheduled_event.
- Position
- Below the diagonal: model.event uses a module listed above it, which is the healthy direction.
25→12 model.event uses model.application.interaction✕
- Connections
- 3 pairs of types, where a type in model.event uses a type in model.application.interaction.
- The types involved
serenity.model.event.InteractionCreateEvent→serenity.model.application.interaction.Interactionserenity.model.event.MessageUpdateEvent→serenity.model.application.interaction.MessageInteractionserenity.model.event.MessageUpdateEvent→serenity.model.application.interaction.MessageInteractionMetadata
- Direction
- model.event uses model.application.interaction, so a change to model.application.interaction can break model.event, while a change to model.event can't break model.application.interaction.
- Position
- Below the diagonal: model.event uses a module listed above it, which is the healthy direction.
25→13 model.event uses model.guild.audit_log✕
- Connections
- 1 pair of types, where a type in model.event uses a type in model.guild.audit_log.
- The types involved
serenity.model.event.GuildAuditLogEntryCreateEvent→serenity.model.guild.audit_log.AuditLogEntry
- Direction
- model.event uses model.guild.audit_log, so a change to model.guild.audit_log can break model.event, while a change to model.event can't break model.guild.audit_log.
- Position
- Below the diagonal: model.event uses a module listed above it, which is the healthy direction.
25→15 model.event uses model.guild✕
- Connections
- 2 pairs of types, where a type in model.event uses a type in model.guild.
- The types involved
serenity.model.event.GuildCreateEvent→serenity.model.guild.Guildserenity.model.event.GuildDeleteEvent→serenity.model.guild.UnavailableGuild
- Direction
- model.event uses model.guild, so a change to model.guild can break model.event, while a change to model.event can't break model.guild.
- Position
- Below the diagonal: model.event uses a module listed above it, which is the healthy direction.
25→17 model.event uses model.gateway✕
- Connections
- 3 pairs of types, where a type in model.event uses a type in model.gateway.
- The types involved
serenity.model.event.GuildMembersChunkEvent→serenity.model.gateway.Presenceserenity.model.event.PresenceUpdateEvent→serenity.model.gateway.Presenceserenity.model.event.PresencesReplaceEvent→serenity.model.gateway.Presence
- Direction
- model.event uses model.gateway, so a change to model.gateway can break model.event, while a change to model.event can't break model.gateway.
- Position
- Below the diagonal: model.event uses a module listed above it, which is the healthy direction.
25→18 model.event uses model.guild.partial_guild✕
- Connections
- 1 pair of types, where a type in model.event uses a type in model.guild.partial_guild.
- The types involved
serenity.model.event.GuildUpdateEvent→serenity.model.guild.partial_guild.PartialGuild
- Direction
- model.event uses model.guild.partial_guild, so a change to model.guild.partial_guild can break model.event, while a change to model.event can't break model.guild.partial_guild.
- Position
- Below the diagonal: model.event uses a module listed above it, which is the healthy direction.
25→23 model.event uses model.channel✕
- Connections
- 3 pairs of types, where a type in model.event uses a type in model.channel.
- The types involved
serenity.model.event.StageInstanceCreateEvent→serenity.model.channel.StageInstanceserenity.model.event.StageInstanceDeleteEvent→serenity.model.channel.StageInstanceserenity.model.event.StageInstanceUpdateEvent→serenity.model.channel.StageInstance
- Direction
- model.event uses model.channel, so a change to model.channel can break model.event, while a change to model.event can't break model.channel.
- Position
- Below the diagonal: model.event uses a module listed above it, which is the healthy direction.
25→24 model.event uses model.invite✕
- Connections
- 1 pair of types, where a type in model.event uses a type in model.invite.
- The types involved
serenity.model.event.InviteCreateEvent→serenity.model.invite.InviteTargetType
- Direction
- model.event uses model.invite, so a change to model.invite can break model.event, while a change to model.event can't break model.invite.
- Position
- Below the diagonal: model.event uses a module listed above it, which is the healthy direction.
25→27 model.event uses model.channel.guild_channel part of a loop✕
- Connections
- 8 pairs of types, where a type in model.event uses a type in model.channel.guild_channel.
- The types involved
serenity.model.event.ChannelCreateEvent→serenity.model.channel.guild_channel.GuildChannelserenity.model.event.ChannelDeleteEvent→serenity.model.channel.guild_channel.GuildChannelserenity.model.event.ChannelUpdateEvent→serenity.model.channel.guild_channel.GuildChannelserenity.model.event.MessageUpdateEvent→serenity.model.channel.guild_channel.GuildChannelserenity.model.event.ThreadCreateEvent→serenity.model.channel.guild_channel.GuildChannelserenity.model.event.ThreadDeleteEvent→serenity.model.channel.guild_channel.PartialGuildChannelserenity.model.event.ThreadListSyncEvent→serenity.model.channel.guild_channel.GuildChannelserenity.model.event.ThreadUpdateEvent→serenity.model.channel.guild_channel.GuildChannel
- Direction
- model.event uses model.channel.guild_channel, so a change to model.channel.guild_channel can break model.event, while a change to model.event can't break model.channel.guild_channel.
- 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.
25→28 model.event uses model.guild.member part of a loop✕
- Connections
- 7 pairs of types, where a type in model.event uses a type in model.guild.member.
- The types involved
serenity.model.event.GuildMemberAddEvent→serenity.model.guild.member.Memberserenity.model.event.GuildMemberUpdateEvent→serenity.model.guild.member.GuildMemberFlagsserenity.model.event.MessageUpdateEvent→serenity.model.guild.member.PartialMemberserenity.model.event.ThreadListSyncEvent→serenity.model.guild.member.ThreadMemberserenity.model.event.ThreadMemberUpdateEvent→serenity.model.guild.member.ThreadMemberserenity.model.event.ThreadMembersUpdateEvent→serenity.model.guild.member.ThreadMemberserenity.model.event.TypingStartEvent→serenity.model.guild.member.Member
- Direction
- model.event uses model.guild.member, so a change to model.guild.member can break model.event, while a change to model.event can't break model.guild.member.
- 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.
25→29 model.event uses model.channel.reaction part of a loop✕
- Connections
- 3 pairs of types, where a type in model.event uses a type in model.channel.reaction.
- The types involved
serenity.model.event.ReactionAddEvent→serenity.model.channel.reaction.Reactionserenity.model.event.ReactionRemoveEmojiEvent→serenity.model.channel.reaction.Reactionserenity.model.event.ReactionRemoveEvent→serenity.model.channel.reaction.Reaction
- Direction
- model.event uses model.channel.reaction, so a change to model.channel.reaction can break model.event, while a change to model.event can't break model.channel.reaction.
- 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.
25→32 model.event uses model.channel.message part of a loop✕
- Connections
- 11 pairs of types, where a type in model.event uses a type in model.channel.message.
- The types involved
serenity.model.event.ChannelDeleteEvent→serenity.model.channel.message.Messageserenity.model.event.MessageCreateEvent→serenity.model.channel.message.Messageserenity.model.event.MessageUpdateEvent→serenity.model.channel.message.ChannelMentionserenity.model.event.MessageUpdateEvent→serenity.model.channel.message.Messageserenity.model.event.MessageUpdateEvent→serenity.model.channel.message.MessageActivityserenity.model.event.MessageUpdateEvent→serenity.model.channel.message.MessageApplicationserenity.model.event.MessageUpdateEvent→serenity.model.channel.message.MessageFlagsserenity.model.event.MessageUpdateEvent→serenity.model.channel.message.MessageReactionserenity.model.event.MessageUpdateEvent→serenity.model.channel.message.MessageReferenceserenity.model.event.MessageUpdateEvent→serenity.model.channel.message.MessageTypeserenity.model.event.MessageUpdateEvent→serenity.model.channel.message.RoleSubscriptionData
- Direction
- model.event uses model.channel.message, so a change to model.channel.message can break model.event, while a change to model.event can't break model.channel.message.
- 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.
25→35 model.event uses model.id part of a loop✕
- Connections
- 71 pairs of types, where a type in model.event uses a type in model.id. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
serenity.model.event.ChannelPinsUpdateEvent→serenity.model.id.ChannelIdserenity.model.event.ChannelPinsUpdateEvent→serenity.model.id.GuildIdserenity.model.event.GuildAuditLogEntryCreateEvent→serenity.model.id.GuildIdserenity.model.event.GuildBanAddEvent→serenity.model.id.GuildIdserenity.model.event.GuildBanRemoveEvent→serenity.model.id.GuildIdserenity.model.event.GuildEmojisUpdateEvent→serenity.model.id.GuildIdserenity.model.event.GuildIntegrationsUpdateEvent→serenity.model.id.GuildIdserenity.model.event.GuildMemberRemoveEvent→serenity.model.id.GuildIdserenity.model.event.GuildMemberUpdateEvent→serenity.model.id.GuildIdserenity.model.event.GuildMemberUpdateEvent→serenity.model.id.RoleIdserenity.model.event.GuildMembersChunkEvent→serenity.model.id.GenericIdserenity.model.event.GuildMembersChunkEvent→serenity.model.id.GuildIdserenity.model.event.GuildRoleDeleteEvent→serenity.model.id.GuildIdserenity.model.event.GuildRoleDeleteEvent→serenity.model.id.RoleIdserenity.model.event.GuildScheduledEventUserAddEvent→serenity.model.id.GuildIdserenity.model.event.GuildScheduledEventUserAddEvent→serenity.model.id.ScheduledEventIdserenity.model.event.GuildScheduledEventUserAddEvent→serenity.model.id.UserIdserenity.model.event.GuildScheduledEventUserRemoveEvent→serenity.model.id.GuildIdserenity.model.event.GuildScheduledEventUserRemoveEvent→serenity.model.id.ScheduledEventIdserenity.model.event.GuildScheduledEventUserRemoveEvent→serenity.model.id.UserIdserenity.model.event.GuildStickersUpdateEvent→serenity.model.id.GuildIdserenity.model.event.IntegrationDeleteEvent→serenity.model.id.ApplicationIdserenity.model.event.IntegrationDeleteEvent→serenity.model.id.GuildIdserenity.model.event.IntegrationDeleteEvent→serenity.model.id.IntegrationIdserenity.model.event.InviteCreateEvent→serenity.model.id.ChannelId
- Direction
- model.event uses model.id, so a change to model.id can break model.event, while a change to model.event can't break model.id.
- 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.
25→36 model.event uses cache part of a loop✕
- Connections
- 26 pairs of types, where a type in model.event uses a type in cache. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
serenity.model.event.ChannelCreateEvent→serenity.cache.Cacheserenity.model.event.ChannelDeleteEvent→serenity.cache.Cacheserenity.model.event.ChannelPinsUpdateEvent→serenity.cache.Cacheserenity.model.event.ChannelUpdateEvent→serenity.cache.Cacheserenity.model.event.GuildCreateEvent→serenity.cache.Cacheserenity.model.event.GuildDeleteEvent→serenity.cache.Cacheserenity.model.event.GuildEmojisUpdateEvent→serenity.cache.Cacheserenity.model.event.GuildMemberAddEvent→serenity.cache.Cacheserenity.model.event.GuildMemberRemoveEvent→serenity.cache.Cacheserenity.model.event.GuildMemberUpdateEvent→serenity.cache.Cacheserenity.model.event.GuildMembersChunkEvent→serenity.cache.Cacheserenity.model.event.GuildRoleCreateEvent→serenity.cache.Cacheserenity.model.event.GuildRoleDeleteEvent→serenity.cache.Cacheserenity.model.event.GuildRoleUpdateEvent→serenity.cache.Cacheserenity.model.event.GuildStickersUpdateEvent→serenity.cache.Cacheserenity.model.event.GuildUpdateEvent→serenity.cache.Cacheserenity.model.event.MessageCreateEvent→serenity.cache.Cacheserenity.model.event.MessageUpdateEvent→serenity.cache.Cacheserenity.model.event.PresenceUpdateEvent→serenity.cache.Cacheserenity.model.event.ReadyEvent→serenity.cache.Cacheserenity.model.event.ThreadCreateEvent→serenity.cache.Cacheserenity.model.event.ThreadDeleteEvent→serenity.cache.Cacheserenity.model.event.ThreadUpdateEvent→serenity.cache.Cacheserenity.model.event.UserUpdateEvent→serenity.cache.Cacheserenity.model.event.VoiceChannelStatusUpdateEvent→serenity.cache.Cache
- Direction
- model.event uses cache, so a change to cache can break model.event, while a change to model.event can't break cache.
- 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.
26→10 collector uses model.application.modal_interaction✕
- Connections
- 1 pair of types, where a type in collector uses a type in model.application.modal_interaction.
- The types involved
serenity.collector.ModalInteractionCollector→serenity.model.application.modal_interaction.ModalInteraction
- Direction
- collector uses model.application.modal_interaction, so a change to model.application.modal_interaction can break collector, while a change to collector can't break model.application.modal_interaction.
- Position
- Below the diagonal: collector uses a module listed above it, which is the healthy direction.
26→16 collector uses model.application.component_interaction✕
- Connections
- 1 pair of types, where a type in collector uses a type in model.application.component_interaction.
- The types involved
serenity.collector.ComponentInteractionCollector→serenity.model.application.component_interaction.ComponentInteraction
- Direction
- collector uses model.application.component_interaction, so a change to model.application.component_interaction can break collector, while a change to collector can't break model.application.component_interaction.
- Position
- Below the diagonal: collector uses a module listed above it, which is the healthy direction.
26→25 collector uses model.event✕
- Connections
- 1 pair of types, where a type in collector uses a type in model.event.
- The types involved
serenity.collector.EventCollector→serenity.model.event.Event
- Direction
- collector uses model.event, so a change to model.event can break collector, while a change to collector can't break model.event.
- Position
- Below the diagonal: collector uses a module listed above it, which is the healthy direction.
26→29 collector uses model.channel.reaction part of a loop✕
- Connections
- 1 pair of types, where a type in collector uses a type in model.channel.reaction.
- The types involved
serenity.collector.ReactionCollector→serenity.model.channel.reaction.Reaction
- Direction
- collector uses model.channel.reaction, so a change to model.channel.reaction can break collector, while a change to collector can't break model.channel.reaction.
- 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.
26→32 collector uses model.channel.message part of a loop✕
- Connections
- 1 pair of types, where a type in collector uses a type in model.channel.message.
- The types involved
serenity.collector.MessageCollector→serenity.model.channel.message.Message
- Direction
- collector uses model.channel.message, so a change to model.channel.message can break collector, while a change to collector can't break model.channel.message.
- 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.
26→35 collector uses model.id part of a loop✕
- Connections
- 15 pairs of types, where a type in collector uses a type in model.id.
- The types involved
serenity.collector.ComponentInteractionCollector→serenity.model.id.ChannelIdserenity.collector.ComponentInteractionCollector→serenity.model.id.GuildIdserenity.collector.ComponentInteractionCollector→serenity.model.id.MessageIdserenity.collector.ComponentInteractionCollector→serenity.model.id.UserIdserenity.collector.MessageCollector→serenity.model.id.ChannelIdserenity.collector.MessageCollector→serenity.model.id.GuildIdserenity.collector.MessageCollector→serenity.model.id.UserIdserenity.collector.ModalInteractionCollector→serenity.model.id.ChannelIdserenity.collector.ModalInteractionCollector→serenity.model.id.GuildIdserenity.collector.ModalInteractionCollector→serenity.model.id.MessageIdserenity.collector.ModalInteractionCollector→serenity.model.id.UserIdserenity.collector.ReactionCollector→serenity.model.id.ChannelIdserenity.collector.ReactionCollector→serenity.model.id.GuildIdserenity.collector.ReactionCollector→serenity.model.id.MessageIdserenity.collector.ReactionCollector→serenity.model.id.UserId
- Direction
- collector uses model.id, so a change to model.id can break collector, while a change to collector can't break model.id.
- 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.
27→2 model.channel.guild_channel uses model.permissions✕
- Connections
- 1 pair of types, where a type in model.channel.guild_channel uses a type in model.permissions.
- The types involved
serenity.model.channel.guild_channel.GuildChannel→serenity.model.permissions.Permissions
- Direction
- model.channel.guild_channel uses model.permissions, so a change to model.permissions can break model.channel.guild_channel, while a change to model.channel.guild_channel can't break model.permissions.
- Position
- Below the diagonal: model.channel.guild_channel uses a module listed above it, which is the healthy direction.
27→6 model.channel.guild_channel uses model.timestamp✕
- Connections
- 1 pair of types, where a type in model.channel.guild_channel uses a type in model.timestamp.
- The types involved
serenity.model.channel.guild_channel.GuildChannel→serenity.model.timestamp.Timestamp
- Direction
- model.channel.guild_channel uses model.timestamp, so a change to model.timestamp can break model.channel.guild_channel, while a change to model.channel.guild_channel can't break model.timestamp.
- Position
- Below the diagonal: model.channel.guild_channel uses a module listed above it, which is the healthy direction.
27→21 model.channel.guild_channel uses http.client✕
- Connections
- 1 pair of types, where a type in model.channel.guild_channel uses a type in http.client.
- The types involved
serenity.model.channel.guild_channel.GuildChannel→serenity.http.client.Http
- Direction
- model.channel.guild_channel uses http.client, so a change to http.client can break model.channel.guild_channel, while a change to model.channel.guild_channel can't break http.client.
- Position
- Below the diagonal: model.channel.guild_channel uses a module listed above it, which is the healthy direction.
27→23 model.channel.guild_channel uses model.channel✕
- Connections
- 11 pairs of types, where a type in model.channel.guild_channel uses a type in model.channel.
- The types involved
serenity.model.channel.guild_channel.GuildChannel→serenity.model.channel.AutoArchiveDurationserenity.model.channel.guild_channel.GuildChannel→serenity.model.channel.ChannelFlagsserenity.model.channel.guild_channel.GuildChannel→serenity.model.channel.ChannelTypeserenity.model.channel.guild_channel.GuildChannel→serenity.model.channel.ForumEmojiserenity.model.channel.guild_channel.GuildChannel→serenity.model.channel.ForumTagserenity.model.channel.guild_channel.GuildChannel→serenity.model.channel.PermissionOverwriteserenity.model.channel.guild_channel.GuildChannel→serenity.model.channel.PermissionOverwriteTypeserenity.model.channel.guild_channel.GuildChannel→serenity.model.channel.SortOrderserenity.model.channel.guild_channel.GuildChannel→serenity.model.channel.ThreadMetadataserenity.model.channel.guild_channel.GuildChannel→serenity.model.channel.VideoQualityModeserenity.model.channel.guild_channel.PartialGuildChannel→serenity.model.channel.ChannelType
- Direction
- model.channel.guild_channel uses model.channel, so a change to model.channel can break model.channel.guild_channel, while a change to model.channel.guild_channel can't break model.channel.
- Position
- Below the diagonal: model.channel.guild_channel uses a module listed above it, which is the healthy direction.
27→26 model.channel.guild_channel uses collector✕
- Connections
- 2 pairs of types, where a type in model.channel.guild_channel uses a type in collector.
- The types involved
serenity.model.channel.guild_channel.GuildChannel→serenity.collector.MessageCollectorserenity.model.channel.guild_channel.GuildChannel→serenity.collector.ReactionCollector
- Direction
- model.channel.guild_channel uses collector, so a change to collector can break model.channel.guild_channel, while a change to model.channel.guild_channel can't break collector.
- Position
- Below the diagonal: model.channel.guild_channel uses a module listed above it, which is the healthy direction.
27→28 model.channel.guild_channel uses model.guild.member part of a loop✕
- Connections
- 1 pair of types, where a type in model.channel.guild_channel uses a type in model.guild.member.
- The types involved
serenity.model.channel.guild_channel.GuildChannel→serenity.model.guild.member.PartialThreadMember
- Direction
- model.channel.guild_channel uses model.guild.member, so a change to model.guild.member can break model.channel.guild_channel, while a change to model.channel.guild_channel can't break model.guild.member.
- 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.
27→31 model.channel.guild_channel uses builder.edit_message part of a loop✕
- Connections
- 1 pair of types, where a type in model.channel.guild_channel uses a type in builder.edit_message.
- The types involved
serenity.model.channel.guild_channel.GuildChannel→serenity.builder.edit_message.EditMessage
- Direction
- model.channel.guild_channel uses builder.edit_message, so a change to builder.edit_message can break model.channel.guild_channel, while a change to model.channel.guild_channel can't break builder.edit_message.
- 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.
27→34 model.channel.guild_channel uses builder.create_message part of a loop✕
- Connections
- 1 pair of types, where a type in model.channel.guild_channel uses a type in builder.create_message.
- The types involved
serenity.model.channel.guild_channel.GuildChannel→serenity.builder.create_message.CreateMessage
- Direction
- model.channel.guild_channel uses builder.create_message, so a change to builder.create_message can break model.channel.guild_channel, while a change to model.channel.guild_channel can't break builder.create_message.
- 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.
27→35 model.channel.guild_channel uses model.id part of a loop✕
- Connections
- 7 pairs of types, where a type in model.channel.guild_channel uses a type in model.id.
- The types involved
serenity.model.channel.guild_channel.GuildChannel→serenity.model.id.ChannelIdserenity.model.channel.guild_channel.GuildChannel→serenity.model.id.ForumTagIdserenity.model.channel.guild_channel.GuildChannel→serenity.model.id.GuildIdserenity.model.channel.guild_channel.GuildChannel→serenity.model.id.MessageIdserenity.model.channel.guild_channel.GuildChannel→serenity.model.id.UserIdserenity.model.channel.guild_channel.PartialGuildChannel→serenity.model.id.ChannelIdserenity.model.channel.guild_channel.PartialGuildChannel→serenity.model.id.GuildId
- Direction
- model.channel.guild_channel uses model.id, so a change to model.id can break model.channel.guild_channel, while a change to model.channel.guild_channel can't break model.id.
- 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.
28→2 model.guild.member uses model.permissions✕
- Connections
- 2 pairs of types, where a type in model.guild.member uses a type in model.permissions.
- The types involved
serenity.model.guild.member.Member→serenity.model.permissions.Permissionsserenity.model.guild.member.PartialMember→serenity.model.permissions.Permissions
- Direction
- model.guild.member uses model.permissions, so a change to model.permissions can break model.guild.member, while a change to model.guild.member can't break model.permissions.
- Position
- Below the diagonal: model.guild.member uses a module listed above it, which is the healthy direction.
28→5 model.guild.member uses model.misc✕
- Connections
- 2 pairs of types, where a type in model.guild.member uses a type in model.misc.
- The types involved
serenity.model.guild.member.Member→serenity.model.misc.ImageHashserenity.model.guild.member.PartialMember→serenity.model.misc.ImageHash
- Direction
- model.guild.member uses model.misc, so a change to model.misc can break model.guild.member, while a change to model.guild.member can't break model.misc.
- Position
- Below the diagonal: model.guild.member uses a module listed above it, which is the healthy direction.
28→6 model.guild.member uses model.timestamp✕
- Connections
- 3 pairs of types, where a type in model.guild.member uses a type in model.timestamp.
- The types involved
serenity.model.guild.member.Member→serenity.model.timestamp.Timestampserenity.model.guild.member.PartialMember→serenity.model.timestamp.Timestampserenity.model.guild.member.PartialThreadMember→serenity.model.timestamp.Timestamp
- Direction
- model.guild.member uses model.timestamp, so a change to model.timestamp can break model.guild.member, while a change to model.guild.member can't break model.timestamp.
- Position
- Below the diagonal: model.guild.member uses a module listed above it, which is the healthy direction.
28→7 model.guild.member uses model.guild.role✕
- Connections
- 1 pair of types, where a type in model.guild.member uses a type in model.guild.role.
- The types involved
serenity.model.guild.member.Member→serenity.model.guild.role.Role
- Direction
- model.guild.member uses model.guild.role, so a change to model.guild.role can break model.guild.member, while a change to model.guild.member can't break model.guild.role.
- Position
- Below the diagonal: model.guild.member uses a module listed above it, which is the healthy direction.
28→8 model.guild.member uses model.user✕
- Connections
- 4 pairs of types, where a type in model.guild.member uses a type in model.user.
- The types involved
serenity.model.guild.member.Member→serenity.model.user.AvatarDecorationDataserenity.model.guild.member.Member→serenity.model.user.Userserenity.model.guild.member.PartialMember→serenity.model.user.AvatarDecorationDataserenity.model.guild.member.PartialMember→serenity.model.user.User
- Direction
- model.guild.member uses model.user, so a change to model.user can break model.guild.member, while a change to model.guild.member can't break model.user.
- Position
- Below the diagonal: model.guild.member uses a module listed above it, which is the healthy direction.
28→27 model.guild.member uses model.channel.guild_channel✕
- Connections
- 1 pair of types, where a type in model.guild.member uses a type in model.channel.guild_channel.
- The types involved
serenity.model.guild.member.Member→serenity.model.channel.guild_channel.GuildChannel
- Direction
- model.guild.member uses model.channel.guild_channel, so a change to model.channel.guild_channel can break model.guild.member, while a change to model.guild.member can't break model.channel.guild_channel.
- Position
- Below the diagonal: model.guild.member uses a module listed above it, which is the healthy direction.
28→35 model.guild.member uses model.id part of a loop✕
- Connections
- 8 pairs of types, where a type in model.guild.member uses a type in model.id.
- The types involved
serenity.model.guild.member.Member→serenity.model.id.ChannelIdserenity.model.guild.member.Member→serenity.model.id.GuildIdserenity.model.guild.member.Member→serenity.model.id.RoleIdserenity.model.guild.member.PartialMember→serenity.model.id.GuildIdserenity.model.guild.member.PartialMember→serenity.model.id.RoleIdserenity.model.guild.member.ThreadMember→serenity.model.id.ChannelIdserenity.model.guild.member.ThreadMember→serenity.model.id.GuildIdserenity.model.guild.member.ThreadMember→serenity.model.id.UserId
- Direction
- model.guild.member uses model.id, so a change to model.id can break model.guild.member, while a change to model.guild.member can't break model.id.
- 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.
29→1 model.channel.reaction uses client.error✕
- Connections
- 1 pair of types, where a type in model.channel.reaction uses a type in client.error.
- The types involved
serenity.model.channel.reaction.ReactionConversionError→serenity.client.error.Error
- Direction
- model.channel.reaction uses client.error, so a change to client.error can break model.channel.reaction, while a change to model.channel.reaction can't break client.error.
- Position
- Below the diagonal: model.channel.reaction uses a module listed above it, which is the healthy direction.
29→5 model.channel.reaction uses model.misc✕
- Connections
- 1 pair of types, where a type in model.channel.reaction uses a type in model.misc.
- The types involved
serenity.model.channel.reaction.ReactionType→serenity.model.misc.EmojiIdentifier
- Direction
- model.channel.reaction uses model.misc, so a change to model.misc can break model.channel.reaction, while a change to model.channel.reaction can't break model.misc.
- Position
- Below the diagonal: model.channel.reaction uses a module listed above it, which is the healthy direction.
29→28 model.channel.reaction uses model.guild.member✕
- Connections
- 1 pair of types, where a type in model.channel.reaction uses a type in model.guild.member.
- The types involved
serenity.model.channel.reaction.Reaction→serenity.model.guild.member.Member
- Direction
- model.channel.reaction uses model.guild.member, so a change to model.guild.member can break model.channel.reaction, while a change to model.channel.reaction can't break model.guild.member.
- Position
- Below the diagonal: model.channel.reaction uses a module listed above it, which is the healthy direction.
29→35 model.channel.reaction uses model.id part of a loop✕
- Connections
- 5 pairs of types, where a type in model.channel.reaction uses a type in model.id.
- The types involved
serenity.model.channel.reaction.Reaction→serenity.model.id.ChannelIdserenity.model.channel.reaction.Reaction→serenity.model.id.GuildIdserenity.model.channel.reaction.Reaction→serenity.model.id.MessageIdserenity.model.channel.reaction.Reaction→serenity.model.id.UserIdserenity.model.channel.reaction.ReactionType→serenity.model.id.EmojiId
- Direction
- model.channel.reaction uses model.id, so a change to model.id can break model.channel.reaction, while a change to model.channel.reaction can't break model.id.
- 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.
30→29 builder.create_components uses model.channel.reaction✕
- Connections
- 1 pair of types, where a type in builder.create_components uses a type in model.channel.reaction.
- The types involved
serenity.builder.create_components.CreateSelectMenuOption→serenity.model.channel.reaction.ReactionType
- Direction
- builder.create_components uses model.channel.reaction, so a change to model.channel.reaction can break builder.create_components, while a change to builder.create_components can't break model.channel.reaction.
- Position
- Below the diagonal: builder.create_components uses a module listed above it, which is the healthy direction.
31→30 builder.edit_message uses builder.create_components✕
- Connections
- 1 pair of types, where a type in builder.edit_message uses a type in builder.create_components.
- The types involved
serenity.builder.edit_message.EditMessage→serenity.builder.create_components.CreateActionRow
- Direction
- builder.edit_message uses builder.create_components, so a change to builder.create_components can break builder.edit_message, while a change to builder.edit_message can't break builder.create_components.
- Position
- Below the diagonal: builder.edit_message uses a module listed above it, which is the healthy direction.
31→32 builder.edit_message uses model.channel.message part of a loop✕
- Connections
- 1 pair of types, where a type in builder.edit_message uses a type in model.channel.message.
- The types involved
serenity.builder.edit_message.EditMessage→serenity.model.channel.message.MessageFlags
- Direction
- builder.edit_message uses model.channel.message, so a change to model.channel.message can break builder.edit_message, while a change to builder.edit_message can't break model.channel.message.
- 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.
31→33 builder.edit_message uses builder.create_attachment part of a loop✕
- Connections
- 2 pairs of types, where a type in builder.edit_message uses a type in builder.create_attachment.
- The types involved
serenity.builder.edit_message.EditMessage→serenity.builder.create_attachment.CreateAttachmentserenity.builder.edit_message.EditMessage→serenity.builder.create_attachment.EditAttachments
- Direction
- builder.edit_message uses builder.create_attachment, so a change to builder.create_attachment can break builder.edit_message, while a change to builder.edit_message can't break builder.create_attachment.
- 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.
31→35 builder.edit_message uses model.id part of a loop✕
- Connections
- 1 pair of types, where a type in builder.edit_message uses a type in model.id.
- The types involved
serenity.builder.edit_message.EditMessage→serenity.model.id.AttachmentId
- Direction
- builder.edit_message uses model.id, so a change to model.id can break builder.edit_message, while a change to builder.edit_message can't break model.id.
- 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.
31→38 builder.edit_message uses client.context part of a loop✕
- Connections
- 1 pair of types, where a type in builder.edit_message uses a type in client.context.
- The types involved
serenity.builder.edit_message.EditMessage→serenity.client.context.Context
- Direction
- builder.edit_message uses client.context, so a change to client.context can break builder.edit_message, while a change to builder.edit_message can't break client.context.
- 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.
31→39 builder.edit_message uses builder part of a loop✕
- Connections
- 1 pair of types, where a type in builder.edit_message uses a type in builder.
- The types involved
serenity.builder.edit_message.EditMessage→serenity.builder.Builder
- Direction
- builder.edit_message uses builder, so a change to builder can break builder.edit_message, while a change to builder.edit_message can't break builder.
- 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.
32→2 model.channel.message uses model.permissions✕
- Connections
- 1 pair of types, where a type in model.channel.message uses a type in model.permissions.
- The types involved
serenity.model.channel.message.Message→serenity.model.permissions.Permissions
- Direction
- model.channel.message uses model.permissions, so a change to model.permissions can break model.channel.message, while a change to model.channel.message can't break model.permissions.
- Position
- Below the diagonal: model.channel.message uses a module listed above it, which is the healthy direction.
32→5 model.channel.message uses model.misc✕
- Connections
- 1 pair of types, where a type in model.channel.message uses a type in model.misc.
- The types involved
serenity.model.channel.message.MessageApplication→serenity.model.misc.ImageHash
- Direction
- model.channel.message uses model.misc, so a change to model.misc can break model.channel.message, while a change to model.channel.message can't break model.misc.
- Position
- Below the diagonal: model.channel.message uses a module listed above it, which is the healthy direction.
32→6 model.channel.message uses model.timestamp✕
- Connections
- 3 pairs of types, where a type in model.channel.message uses a type in model.timestamp.
- The types involved
serenity.model.channel.message.Message→serenity.model.timestamp.Timestampserenity.model.channel.message.MessageSnapshot→serenity.model.timestamp.Timestampserenity.model.channel.message.Poll→serenity.model.timestamp.Timestamp
- Direction
- model.channel.message uses model.timestamp, so a change to model.timestamp can break model.channel.message, while a change to model.channel.message can't break model.timestamp.
- Position
- Below the diagonal: model.channel.message uses a module listed above it, which is the healthy direction.
32→8 model.channel.message uses model.user✕
- Connections
- 2 pairs of types, where a type in model.channel.message uses a type in model.user.
- The types involved
serenity.model.channel.message.Message→serenity.model.user.Userserenity.model.channel.message.MessageSnapshot→serenity.model.user.User
- Direction
- model.channel.message uses model.user, so a change to model.user can break model.channel.message, while a change to model.channel.message can't break model.user.
- Position
- Below the diagonal: model.channel.message uses a module listed above it, which is the healthy direction.
32→12 model.channel.message uses model.application.interaction✕
- Connections
- 2 pairs of types, where a type in model.channel.message uses a type in model.application.interaction.
- The types involved
serenity.model.channel.message.Message→serenity.model.application.interaction.MessageInteractionserenity.model.channel.message.Message→serenity.model.application.interaction.MessageInteractionMetadata
- Direction
- model.channel.message uses model.application.interaction, so a change to model.application.interaction can break model.channel.message, while a change to model.channel.message can't break model.application.interaction.
- Position
- Below the diagonal: model.channel.message uses a module listed above it, which is the healthy direction.
32→23 model.channel.message uses model.channel✕
- Connections
- 1 pair of types, where a type in model.channel.message uses a type in model.channel.
- The types involved
serenity.model.channel.message.ChannelMention→serenity.model.channel.ChannelType
- Direction
- model.channel.message uses model.channel, so a change to model.channel can break model.channel.message, while a change to model.channel.message can't break model.channel.
- Position
- Below the diagonal: model.channel.message uses a module listed above it, which is the healthy direction.
32→26 model.channel.message uses collector✕
- Connections
- 3 pairs of types, where a type in model.channel.message uses a type in collector.
- The types involved
serenity.model.channel.message.Message→serenity.collector.ComponentInteractionCollectorserenity.model.channel.message.Message→serenity.collector.ModalInteractionCollectorserenity.model.channel.message.Message→serenity.collector.ReactionCollector
- Direction
- model.channel.message uses collector, so a change to collector can break model.channel.message, while a change to model.channel.message can't break collector.
- Position
- Below the diagonal: model.channel.message uses a module listed above it, which is the healthy direction.
32→27 model.channel.message uses model.channel.guild_channel✕
- Connections
- 1 pair of types, where a type in model.channel.message uses a type in model.channel.guild_channel.
- The types involved
serenity.model.channel.message.Message→serenity.model.channel.guild_channel.GuildChannel
- Direction
- model.channel.message uses model.channel.guild_channel, so a change to model.channel.guild_channel can break model.channel.message, while a change to model.channel.message can't break model.channel.guild_channel.
- Position
- Below the diagonal: model.channel.message uses a module listed above it, which is the healthy direction.
32→28 model.channel.message uses model.guild.member✕
- Connections
- 1 pair of types, where a type in model.channel.message uses a type in model.guild.member.
- The types involved
serenity.model.channel.message.Message→serenity.model.guild.member.PartialMember
- Direction
- model.channel.message uses model.guild.member, so a change to model.guild.member can break model.channel.message, while a change to model.channel.message can't break model.guild.member.
- Position
- Below the diagonal: model.channel.message uses a module listed above it, which is the healthy direction.
32→29 model.channel.message uses model.channel.reaction✕
- Connections
- 2 pairs of types, where a type in model.channel.message uses a type in model.channel.reaction.
- The types involved
serenity.model.channel.message.Message→serenity.model.channel.reaction.ReactionTypeserenity.model.channel.message.MessageReaction→serenity.model.channel.reaction.ReactionType
- Direction
- model.channel.message uses model.channel.reaction, so a change to model.channel.reaction can break model.channel.message, while a change to model.channel.message can't break model.channel.reaction.
- Position
- Below the diagonal: model.channel.message uses a module listed above it, which is the healthy direction.
32→31 model.channel.message uses builder.edit_message✕
- Connections
- 1 pair of types, where a type in model.channel.message uses a type in builder.edit_message.
- The types involved
serenity.model.channel.message.Message→serenity.builder.edit_message.EditMessage
- Direction
- model.channel.message uses builder.edit_message, so a change to builder.edit_message can break model.channel.message, while a change to model.channel.message can't break builder.edit_message.
- Position
- Below the diagonal: model.channel.message uses a module listed above it, which is the healthy direction.
32→35 model.channel.message uses model.id part of a loop✕
- Connections
- 18 pairs of types, where a type in model.channel.message uses a type in model.id.
- The types involved
serenity.model.channel.message.ChannelMention→serenity.model.id.ChannelIdserenity.model.channel.message.ChannelMention→serenity.model.id.GuildIdserenity.model.channel.message.Message→serenity.model.id.ApplicationIdserenity.model.channel.message.Message→serenity.model.id.ChannelIdserenity.model.channel.message.Message→serenity.model.id.GuildIdserenity.model.channel.message.Message→serenity.model.id.MessageIdserenity.model.channel.message.Message→serenity.model.id.RoleIdserenity.model.channel.message.Message→serenity.model.id.UserIdserenity.model.channel.message.Message→serenity.model.id.WebhookIdserenity.model.channel.message.MessageApplication→serenity.model.id.ApplicationIdserenity.model.channel.message.MessageReference→serenity.model.id.ChannelIdserenity.model.channel.message.MessageReference→serenity.model.id.GuildIdserenity.model.channel.message.MessageReference→serenity.model.id.MessageIdserenity.model.channel.message.MessageSnapshot→serenity.model.id.RoleIdserenity.model.channel.message.PollAnswer→serenity.model.id.AnswerIdserenity.model.channel.message.PollAnswerCount→serenity.model.id.AnswerIdserenity.model.channel.message.PollMediaEmoji→serenity.model.id.EmojiIdserenity.model.channel.message.RoleSubscriptionData→serenity.model.id.SkuId
- Direction
- model.channel.message uses model.id, so a change to model.id can break model.channel.message, while a change to model.channel.message can't break model.id.
- 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.
32→36 model.channel.message uses cache part of a loop✕
- Connections
- 1 pair of types, where a type in model.channel.message uses a type in cache.
- The types involved
serenity.model.channel.message.Message→serenity.cache.Cache
- Direction
- model.channel.message uses cache, so a change to cache can break model.channel.message, while a change to model.channel.message can't break cache.
- 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.
33→32 builder.create_attachment uses model.channel.message✕
- Connections
- 1 pair of types, where a type in builder.create_attachment uses a type in model.channel.message.
- The types involved
serenity.builder.create_attachment.EditAttachments→serenity.model.channel.message.Message
- Direction
- builder.create_attachment uses model.channel.message, so a change to model.channel.message can break builder.create_attachment, while a change to builder.create_attachment can't break model.channel.message.
- Position
- Below the diagonal: builder.create_attachment uses a module listed above it, which is the healthy direction.
33→35 builder.create_attachment uses model.id part of a loop✕
- Connections
- 2 pairs of types, where a type in builder.create_attachment uses a type in model.id.
- The types involved
serenity.builder.create_attachment.EditAttachments→serenity.model.id.AttachmentIdserenity.builder.create_attachment.ExistingAttachment→serenity.model.id.AttachmentId
- Direction
- builder.create_attachment uses model.id, so a change to model.id can break builder.create_attachment, while a change to builder.create_attachment can't break model.id.
- 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.
34→29 builder.create_message uses model.channel.reaction✕
- Connections
- 1 pair of types, where a type in builder.create_message uses a type in model.channel.reaction.
- The types involved
serenity.builder.create_message.CreateMessage→serenity.model.channel.reaction.ReactionType
- Direction
- builder.create_message uses model.channel.reaction, so a change to model.channel.reaction can break builder.create_message, while a change to builder.create_message can't break model.channel.reaction.
- Position
- Below the diagonal: builder.create_message uses a module listed above it, which is the healthy direction.
34→30 builder.create_message uses builder.create_components✕
- Connections
- 1 pair of types, where a type in builder.create_message uses a type in builder.create_components.
- The types involved
serenity.builder.create_message.CreateMessage→serenity.builder.create_components.CreateActionRow
- Direction
- builder.create_message uses builder.create_components, so a change to builder.create_components can break builder.create_message, while a change to builder.create_message can't break builder.create_components.
- Position
- Below the diagonal: builder.create_message uses a module listed above it, which is the healthy direction.
34→32 builder.create_message uses model.channel.message✕
- Connections
- 3 pairs of types, where a type in builder.create_message uses a type in model.channel.message.
- The types involved
serenity.builder.create_message.CreateMessage→serenity.model.channel.message.MessageFlagsserenity.builder.create_message.CreateMessage→serenity.model.channel.message.MessageReferenceserenity.builder.create_message.CreateMessage→serenity.model.channel.message.Nonce
- Direction
- builder.create_message uses model.channel.message, so a change to model.channel.message can break builder.create_message, while a change to builder.create_message can't break model.channel.message.
- Position
- Below the diagonal: builder.create_message uses a module listed above it, which is the healthy direction.
34→33 builder.create_message uses builder.create_attachment✕
- Connections
- 2 pairs of types, where a type in builder.create_message uses a type in builder.create_attachment.
- The types involved
serenity.builder.create_message.CreateMessage→serenity.builder.create_attachment.CreateAttachmentserenity.builder.create_message.CreateMessage→serenity.builder.create_attachment.EditAttachments
- Direction
- builder.create_message uses builder.create_attachment, so a change to builder.create_attachment can break builder.create_message, while a change to builder.create_message can't break builder.create_attachment.
- Position
- Below the diagonal: builder.create_message uses a module listed above it, which is the healthy direction.
34→35 builder.create_message uses model.id part of a loop✕
- Connections
- 1 pair of types, where a type in builder.create_message uses a type in model.id.
- The types involved
serenity.builder.create_message.CreateMessage→serenity.model.id.StickerId
- Direction
- builder.create_message uses model.id, so a change to model.id can break builder.create_message, while a change to builder.create_message can't break model.id.
- 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.
34→38 builder.create_message uses client.context part of a loop✕
- Connections
- 1 pair of types, where a type in builder.create_message uses a type in client.context.
- The types involved
serenity.builder.create_message.CreateMessage→serenity.client.context.Context
- Direction
- builder.create_message uses client.context, so a change to client.context can break builder.create_message, while a change to builder.create_message can't break client.context.
- 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.
34→39 builder.create_message uses builder part of a loop✕
- Connections
- 1 pair of types, where a type in builder.create_message uses a type in builder.
- The types involved
serenity.builder.create_message.CreateMessage→serenity.builder.Builder
- Direction
- builder.create_message uses builder, so a change to builder can break builder.create_message, while a change to builder.create_message can't break builder.
- 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.
35→6 model.id uses model.timestamp✕
- Connections
- 27 pairs of types, where a type in model.id uses a type in model.timestamp. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
serenity.model.id.ApplicationId→serenity.model.timestamp.Timestampserenity.model.id.AttachmentId→serenity.model.timestamp.Timestampserenity.model.id.AuditLogEntryId→serenity.model.timestamp.Timestampserenity.model.id.ChannelId→serenity.model.timestamp.Timestampserenity.model.id.CommandId→serenity.model.timestamp.Timestampserenity.model.id.CommandPermissionId→serenity.model.timestamp.Timestampserenity.model.id.CommandVersionId→serenity.model.timestamp.Timestampserenity.model.id.EmojiId→serenity.model.timestamp.Timestampserenity.model.id.EntitlementId→serenity.model.timestamp.Timestampserenity.model.id.ForumTagId→serenity.model.timestamp.Timestampserenity.model.id.GenericId→serenity.model.timestamp.Timestampserenity.model.id.GuildId→serenity.model.timestamp.Timestampserenity.model.id.IntegrationId→serenity.model.timestamp.Timestampserenity.model.id.InteractionId→serenity.model.timestamp.Timestampserenity.model.id.MessageId→serenity.model.timestamp.Timestampserenity.model.id.RoleId→serenity.model.timestamp.Timestampserenity.model.id.RuleId→serenity.model.timestamp.Timestampserenity.model.id.ScheduledEventId→serenity.model.timestamp.Timestampserenity.model.id.SkuId→serenity.model.timestamp.Timestampserenity.model.id.SoundId→serenity.model.timestamp.Timestampserenity.model.id.StageInstanceId→serenity.model.timestamp.Timestampserenity.model.id.StickerId→serenity.model.timestamp.Timestampserenity.model.id.StickerPackBannerId→serenity.model.timestamp.Timestampserenity.model.id.StickerPackId→serenity.model.timestamp.Timestampserenity.model.id.TargetId→serenity.model.timestamp.Timestamp
- Direction
- model.id uses model.timestamp, so a change to model.timestamp can break model.id, while a change to model.id can't break model.timestamp.
- Position
- Below the diagonal: model.id uses a module listed above it, which is the healthy direction.
35→7 model.id uses model.guild.role✕
- Connections
- 1 pair of types, where a type in model.id uses a type in model.guild.role.
- The types involved
serenity.model.id.RoleId→serenity.model.guild.role.Role
- Direction
- model.id uses model.guild.role, so a change to model.guild.role can break model.id, while a change to model.id can't break model.guild.role.
- Position
- Below the diagonal: model.id uses a module listed above it, which is the healthy direction.
35→8 model.id uses model.user✕
- Connections
- 1 pair of types, where a type in model.id uses a type in model.user.
- The types involved
serenity.model.id.UserId→serenity.model.user.User
- Direction
- model.id uses model.user, so a change to model.user can break model.id, while a change to model.id can't break model.user.
- Position
- Below the diagonal: model.id uses a module listed above it, which is the healthy direction.
35→13 model.id uses model.guild.audit_log✕
- Connections
- 1 pair of types, where a type in model.id uses a type in model.guild.audit_log.
- The types involved
serenity.model.id.GuildId→serenity.model.guild.audit_log.Action
- Direction
- model.id uses model.guild.audit_log, so a change to model.guild.audit_log can break model.id, while a change to model.id can't break model.guild.audit_log.
- Position
- Below the diagonal: model.id uses a module listed above it, which is the healthy direction.
35→15 model.id uses model.guild✕
- Connections
- 3 pairs of types, where a type in model.id uses a type in model.guild.
- The types involved
serenity.model.id.GuildId→serenity.model.guild.Guildserenity.model.id.GuildId→serenity.model.guild.GuildInfoserenity.model.id.GuildId→serenity.model.guild.MfaLevel
- Direction
- model.id uses model.guild, so a change to model.guild can break model.id, while a change to model.id can't break model.guild.
- Position
- Below the diagonal: model.id uses a module listed above it, which is the healthy direction.
35→18 model.id uses model.guild.partial_guild✕
- Connections
- 1 pair of types, where a type in model.id uses a type in model.guild.partial_guild.
- The types involved
serenity.model.id.GuildId→serenity.model.guild.partial_guild.PartialGuild
- Direction
- model.id uses model.guild.partial_guild, so a change to model.guild.partial_guild can break model.id, while a change to model.id can't break model.guild.partial_guild.
- Position
- Below the diagonal: model.id uses a module listed above it, which is the healthy direction.
35→21 model.id uses http.client✕
- Connections
- 2 pairs of types, where a type in model.id uses a type in http.client.
- The types involved
serenity.model.id.ChannelId→serenity.http.client.Httpserenity.model.id.GuildId→serenity.http.client.Http
- Direction
- model.id uses http.client, so a change to http.client can break model.id, while a change to model.id can't break http.client.
- Position
- Below the diagonal: model.id uses a module listed above it, which is the healthy direction.
35→22 model.id uses model.channel.private_channel✕
- Connections
- 1 pair of types, where a type in model.id uses a type in model.channel.private_channel.
- The types involved
serenity.model.id.ChannelId→serenity.model.channel.private_channel.PrivateChannel
- Direction
- model.id uses model.channel.private_channel, so a change to model.channel.private_channel can break model.id, while a change to model.id can't break model.channel.private_channel.
- Position
- Below the diagonal: model.id uses a module listed above it, which is the healthy direction.
35→23 model.id uses model.channel✕
- Connections
- 3 pairs of types, where a type in model.id uses a type in model.channel.
- The types involved
serenity.model.id.ChannelId→serenity.model.channel.Channelserenity.model.id.ChannelId→serenity.model.channel.PermissionOverwriteserenity.model.id.ChannelId→serenity.model.channel.PermissionOverwriteType
- Direction
- model.id uses model.channel, so a change to model.channel can break model.id, while a change to model.id can't break model.channel.
- Position
- Below the diagonal: model.id uses a module listed above it, which is the healthy direction.
35→24 model.id uses model.invite✕
- Connections
- 1 pair of types, where a type in model.id uses a type in model.invite.
- The types involved
serenity.model.id.GuildId→serenity.model.invite.InviteGuild
- Direction
- model.id uses model.invite, so a change to model.invite can break model.id, while a change to model.id can't break model.invite.
- Position
- Below the diagonal: model.id uses a module listed above it, which is the healthy direction.
35→26 model.id uses collector✕
- Connections
- 4 pairs of types, where a type in model.id uses a type in collector.
- The types involved
serenity.model.id.ChannelId→serenity.collector.MessageCollectorserenity.model.id.ChannelId→serenity.collector.ReactionCollectorserenity.model.id.GuildId→serenity.collector.MessageCollectorserenity.model.id.GuildId→serenity.collector.ReactionCollector
- Direction
- model.id uses collector, so a change to collector can break model.id, while a change to model.id can't break collector.
- Position
- Below the diagonal: model.id uses a module listed above it, which is the healthy direction.
35→27 model.id uses model.channel.guild_channel✕
- Connections
- 1 pair of types, where a type in model.id uses a type in model.channel.guild_channel.
- The types involved
serenity.model.id.ChannelId→serenity.model.channel.guild_channel.GuildChannel
- Direction
- model.id uses model.channel.guild_channel, so a change to model.channel.guild_channel can break model.id, while a change to model.id can't break model.channel.guild_channel.
- Position
- Below the diagonal: model.id uses a module listed above it, which is the healthy direction.
35→28 model.id uses model.guild.member✕
- Connections
- 1 pair of types, where a type in model.id uses a type in model.guild.member.
- The types involved
serenity.model.id.UserId→serenity.model.guild.member.Member
- Direction
- model.id uses model.guild.member, so a change to model.guild.member can break model.id, while a change to model.id can't break model.guild.member.
- Position
- Below the diagonal: model.id uses a module listed above it, which is the healthy direction.
35→31 model.id uses builder.edit_message✕
- Connections
- 1 pair of types, where a type in model.id uses a type in builder.edit_message.
- The types involved
serenity.model.id.ChannelId→serenity.builder.edit_message.EditMessage
- Direction
- model.id uses builder.edit_message, so a change to builder.edit_message can break model.id, while a change to model.id can't break builder.edit_message.
- Position
- Below the diagonal: model.id uses a module listed above it, which is the healthy direction.
35→32 model.id uses model.channel.message✕
- Connections
- 1 pair of types, where a type in model.id uses a type in model.channel.message.
- The types involved
serenity.model.id.MessageId→serenity.model.channel.message.Message
- Direction
- model.id uses model.channel.message, so a change to model.channel.message can break model.id, while a change to model.id can't break model.channel.message.
- Position
- Below the diagonal: model.id uses a module listed above it, which is the healthy direction.
35→34 model.id uses builder.create_message✕
- Connections
- 2 pairs of types, where a type in model.id uses a type in builder.create_message.
- The types involved
serenity.model.id.ChannelId→serenity.builder.create_message.CreateMessageserenity.model.id.UserId→serenity.builder.create_message.CreateMessage
- Direction
- model.id uses builder.create_message, so a change to builder.create_message can break model.id, while a change to model.id can't break builder.create_message.
- Position
- Below the diagonal: model.id uses a module listed above it, which is the healthy direction.
35→36 model.id uses cache part of a loop✕
- Connections
- 1 pair of types, where a type in model.id uses a type in cache.
- The types involved
serenity.model.id.ChannelId→serenity.cache.Cache
- Direction
- model.id uses cache, so a change to cache can break model.id, while a change to model.id can't break cache.
- 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.
36→8 cache uses model.user✕
- Connections
- 2 pairs of types, where a type in cache uses a type in model.user.
- The types involved
serenity.cache.Cache→serenity.model.user.CurrentUserserenity.cache.Cache→serenity.model.user.User
- Direction
- cache uses model.user, so a change to model.user can break cache, while a change to cache can't break model.user.
- Position
- Below the diagonal: cache uses a module listed above it, which is the healthy direction.
36→35 cache uses model.id✕
- Connections
- 5 pairs of types, where a type in cache uses a type in model.id.
- The types involved
serenity.cache.Cache→serenity.model.id.ChannelIdserenity.cache.Cache→serenity.model.id.GuildIdserenity.cache.Cache→serenity.model.id.MessageIdserenity.cache.Cache→serenity.model.id.RoleIdserenity.cache.Cache→serenity.model.id.UserId
- Direction
- cache uses model.id, so a change to model.id can break cache, while a change to cache can't break model.id.
- Position
- Below the diagonal: cache uses a module listed above it, which is the healthy direction.
37→19 gateway.bridge.shard_runner uses gateway✕
- Connections
- 1 pair of types, where a type in gateway.bridge.shard_runner uses a type in gateway.
- The types involved
serenity.gateway.bridge.shard_runner.ShardRunner→serenity.gateway.ShardAction
- Direction
- gateway.bridge.shard_runner uses gateway, so a change to gateway can break gateway.bridge.shard_runner, while a change to gateway.bridge.shard_runner can't break gateway.
- Position
- Below the diagonal: gateway.bridge.shard_runner uses a module listed above it, which is the healthy direction.
37→21 gateway.bridge.shard_runner uses http.client✕
- Connections
- 2 pairs of types, where a type in gateway.bridge.shard_runner uses a type in http.client.
- The types involved
serenity.gateway.bridge.shard_runner.ShardRunner→serenity.http.client.Httpserenity.gateway.bridge.shard_runner.ShardRunnerOptions→serenity.http.client.Http
- Direction
- gateway.bridge.shard_runner uses http.client, so a change to http.client can break gateway.bridge.shard_runner, while a change to gateway.bridge.shard_runner can't break http.client.
- Position
- Below the diagonal: gateway.bridge.shard_runner uses a module listed above it, which is the healthy direction.
37→25 gateway.bridge.shard_runner uses model.event✕
- Connections
- 1 pair of types, where a type in gateway.bridge.shard_runner uses a type in model.event.
- The types involved
serenity.gateway.bridge.shard_runner.ShardRunner→serenity.model.event.Event
- Direction
- gateway.bridge.shard_runner uses model.event, so a change to model.event can break gateway.bridge.shard_runner, while a change to gateway.bridge.shard_runner can't break model.event.
- Position
- Below the diagonal: gateway.bridge.shard_runner uses a module listed above it, which is the healthy direction.
37→35 gateway.bridge.shard_runner uses model.id✕
- Connections
- 1 pair of types, where a type in gateway.bridge.shard_runner uses a type in model.id.
- The types involved
serenity.gateway.bridge.shard_runner.ShardRunner→serenity.model.id.ShardId
- Direction
- gateway.bridge.shard_runner uses model.id, so a change to model.id can break gateway.bridge.shard_runner, while a change to gateway.bridge.shard_runner can't break model.id.
- Position
- Below the diagonal: gateway.bridge.shard_runner uses a module listed above it, which is the healthy direction.
37→36 gateway.bridge.shard_runner uses cache✕
- Connections
- 2 pairs of types, where a type in gateway.bridge.shard_runner uses a type in cache.
- The types involved
serenity.gateway.bridge.shard_runner.ShardRunner→serenity.cache.Cacheserenity.gateway.bridge.shard_runner.ShardRunnerOptions→serenity.cache.Cache
- Direction
- gateway.bridge.shard_runner uses cache, so a change to cache can break gateway.bridge.shard_runner, while a change to gateway.bridge.shard_runner can't break cache.
- Position
- Below the diagonal: gateway.bridge.shard_runner uses a module listed above it, which is the healthy direction.
37→38 gateway.bridge.shard_runner uses client.context part of a loop✕
- Connections
- 1 pair of types, where a type in gateway.bridge.shard_runner uses a type in client.context.
- The types involved
serenity.gateway.bridge.shard_runner.ShardRunner→serenity.client.context.Context
- Direction
- gateway.bridge.shard_runner uses client.context, so a change to client.context can break gateway.bridge.shard_runner, while a change to gateway.bridge.shard_runner can't break client.context.
- 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→8 client.context uses model.user✕
- Connections
- 1 pair of types, where a type in client.context uses a type in model.user.
- The types involved
serenity.client.context.Context→serenity.model.user.OnlineStatus
- Direction
- client.context uses model.user, so a change to model.user can break client.context, while a change to client.context can't break model.user.
- Position
- Below the diagonal: client.context uses a module listed above it, which is the healthy direction.
38→19 client.context uses gateway✕
- Connections
- 1 pair of types, where a type in client.context uses a type in gateway.
- The types involved
serenity.client.context.Context→serenity.gateway.ActivityData
- Direction
- client.context uses gateway, so a change to gateway can break client.context, while a change to client.context can't break gateway.
- Position
- Below the diagonal: client.context uses a module listed above it, which is the healthy direction.
38→21 client.context uses http.client✕
- Connections
- 1 pair of types, where a type in client.context uses a type in http.client.
- The types involved
serenity.client.context.Context→serenity.http.client.Http
- Direction
- client.context uses http.client, so a change to http.client can break client.context, while a change to client.context can't break http.client.
- Position
- Below the diagonal: client.context uses a module listed above it, which is the healthy direction.
38→35 client.context uses model.id✕
- Connections
- 2 pairs of types, where a type in client.context uses a type in model.id.
- The types involved
serenity.client.context.Context→serenity.model.id.EmojiIdserenity.client.context.Context→serenity.model.id.ShardId
- Direction
- client.context uses model.id, so a change to model.id can break client.context, while a change to client.context can't break model.id.
- Position
- Below the diagonal: client.context uses a module listed above it, which is the healthy direction.
38→36 client.context uses cache✕
- Connections
- 1 pair of types, where a type in client.context uses a type in cache.
- The types involved
serenity.client.context.Context→serenity.cache.Cache
- Direction
- client.context uses cache, so a change to cache can break client.context, while a change to client.context can't break cache.
- Position
- Below the diagonal: client.context uses a module listed above it, which is the healthy direction.
38→37 client.context uses gateway.bridge.shard_runner✕
- Connections
- 1 pair of types, where a type in client.context uses a type in gateway.bridge.shard_runner.
- The types involved
serenity.client.context.Context→serenity.gateway.bridge.shard_runner.ShardRunner
- Direction
- client.context uses gateway.bridge.shard_runner, so a change to gateway.bridge.shard_runner can break client.context, while a change to client.context can't break gateway.bridge.shard_runner.
- Position
- Below the diagonal: client.context uses a module listed above it, which is the healthy direction.
39→38 builder uses client.context✕
- Connections
- 1 pair of types, where a type in builder uses a type in client.context.
- The types involved
serenity.builder.Builder→serenity.client.context.Context
- Direction
- builder uses client.context, so a change to client.context can break builder, while a change to builder can't break client.context.
- Position
- Below the diagonal: builder uses a module listed above it, which is the healthy direction.
40→7 client.event_handler uses model.guild.role✕
- Connections
- 1 pair of types, where a type in client.event_handler uses a type in model.guild.role.
- The types involved
serenity.client.event_handler.EventHandler→serenity.model.guild.role.Role
- Direction
- client.event_handler uses model.guild.role, so a change to model.guild.role can break client.event_handler, while a change to client.event_handler can't break model.guild.role.
- Position
- Below the diagonal: client.event_handler uses a module listed above it, which is the healthy direction.
40→8 client.event_handler uses model.user✕
- Connections
- 2 pairs of types, where a type in client.event_handler uses a type in model.user.
- The types involved
serenity.client.event_handler.EventHandler→serenity.model.user.CurrentUserserenity.client.event_handler.EventHandler→serenity.model.user.User
- Direction
- client.event_handler uses model.user, so a change to model.user can break client.event_handler, while a change to client.event_handler can't break model.user.
- Position
- Below the diagonal: client.event_handler uses a module listed above it, which is the healthy direction.
40→11 client.event_handler uses model.guild.scheduled_event✕
- Connections
- 1 pair of types, where a type in client.event_handler uses a type in model.guild.scheduled_event.
- The types involved
serenity.client.event_handler.EventHandler→serenity.model.guild.scheduled_event.ScheduledEvent
- Direction
- client.event_handler uses model.guild.scheduled_event, so a change to model.guild.scheduled_event can break client.event_handler, while a change to client.event_handler can't break model.guild.scheduled_event.
- Position
- Below the diagonal: client.event_handler uses a module listed above it, which is the healthy direction.
40→12 client.event_handler uses model.application.interaction✕
- Connections
- 1 pair of types, where a type in client.event_handler uses a type in model.application.interaction.
- The types involved
serenity.client.event_handler.EventHandler→serenity.model.application.interaction.Interaction
- Direction
- client.event_handler uses model.application.interaction, so a change to model.application.interaction can break client.event_handler, while a change to client.event_handler can't break model.application.interaction.
- Position
- Below the diagonal: client.event_handler uses a module listed above it, which is the healthy direction.
40→13 client.event_handler uses model.guild.audit_log✕
- Connections
- 1 pair of types, where a type in client.event_handler uses a type in model.guild.audit_log.
- The types involved
serenity.client.event_handler.EventHandler→serenity.model.guild.audit_log.AuditLogEntry
- Direction
- client.event_handler uses model.guild.audit_log, so a change to model.guild.audit_log can break client.event_handler, while a change to client.event_handler can't break model.guild.audit_log.
- Position
- Below the diagonal: client.event_handler uses a module listed above it, which is the healthy direction.
40→15 client.event_handler uses model.guild✕
- Connections
- 2 pairs of types, where a type in client.event_handler uses a type in model.guild.
- The types involved
serenity.client.event_handler.EventHandler→serenity.model.guild.Guildserenity.client.event_handler.EventHandler→serenity.model.guild.UnavailableGuild
- Direction
- client.event_handler uses model.guild, so a change to model.guild can break client.event_handler, while a change to client.event_handler can't break model.guild.
- Position
- Below the diagonal: client.event_handler uses a module listed above it, which is the healthy direction.
40→17 client.event_handler uses model.gateway✕
- Connections
- 1 pair of types, where a type in client.event_handler uses a type in model.gateway.
- The types involved
serenity.client.event_handler.EventHandler→serenity.model.gateway.Presence
- Direction
- client.event_handler uses model.gateway, so a change to model.gateway can break client.event_handler, while a change to client.event_handler can't break model.gateway.
- Position
- Below the diagonal: client.event_handler uses a module listed above it, which is the healthy direction.
40→18 client.event_handler uses model.guild.partial_guild✕
- Connections
- 1 pair of types, where a type in client.event_handler uses a type in model.guild.partial_guild.
- The types involved
serenity.client.event_handler.EventHandler→serenity.model.guild.partial_guild.PartialGuild
- Direction
- client.event_handler uses model.guild.partial_guild, so a change to model.guild.partial_guild can break client.event_handler, while a change to client.event_handler can't break model.guild.partial_guild.
- Position
- Below the diagonal: client.event_handler uses a module listed above it, which is the healthy direction.
40→23 client.event_handler uses model.channel✕
- Connections
- 1 pair of types, where a type in client.event_handler uses a type in model.channel.
- The types involved
serenity.client.event_handler.EventHandler→serenity.model.channel.StageInstance
- Direction
- client.event_handler uses model.channel, so a change to model.channel can break client.event_handler, while a change to client.event_handler can't break model.channel.
- Position
- Below the diagonal: client.event_handler uses a module listed above it, which is the healthy direction.
40→25 client.event_handler uses model.event✕
- Connections
- 21 pairs of types, where a type in client.event_handler uses a type in model.event.
- The types involved
serenity.client.event_handler.EventHandler→serenity.model.event.ChannelPinsUpdateEventserenity.client.event_handler.EventHandler→serenity.model.event.GuildMemberUpdateEventserenity.client.event_handler.EventHandler→serenity.model.event.GuildMembersChunkEventserenity.client.event_handler.EventHandler→serenity.model.event.GuildScheduledEventUserAddEventserenity.client.event_handler.EventHandler→serenity.model.event.GuildScheduledEventUserRemoveEventserenity.client.event_handler.EventHandler→serenity.model.event.InviteCreateEventserenity.client.event_handler.EventHandler→serenity.model.event.InviteDeleteEventserenity.client.event_handler.EventHandler→serenity.model.event.MessagePollVoteAddEventserenity.client.event_handler.EventHandler→serenity.model.event.MessagePollVoteRemoveEventserenity.client.event_handler.EventHandler→serenity.model.event.MessageUpdateEventserenity.client.event_handler.EventHandler→serenity.model.event.ResumedEventserenity.client.event_handler.EventHandler→serenity.model.event.SoundboardSoundCreateEventserenity.client.event_handler.EventHandler→serenity.model.event.SoundboardSoundDeleteEventserenity.client.event_handler.EventHandler→serenity.model.event.SoundboardSoundUpdateEventserenity.client.event_handler.EventHandler→serenity.model.event.SoundboardSoundsEventserenity.client.event_handler.EventHandler→serenity.model.event.SoundboardSoundsUpdateEventserenity.client.event_handler.EventHandler→serenity.model.event.ThreadListSyncEventserenity.client.event_handler.EventHandler→serenity.model.event.ThreadMembersUpdateEventserenity.client.event_handler.EventHandler→serenity.model.event.TypingStartEventserenity.client.event_handler.EventHandler→serenity.model.event.VoiceServerUpdateEventserenity.client.event_handler.RawEventHandler→serenity.model.event.Event
- Direction
- client.event_handler uses model.event, so a change to model.event can break client.event_handler, while a change to client.event_handler can't break model.event.
- Position
- Below the diagonal: client.event_handler uses a module listed above it, which is the healthy direction.
40→27 client.event_handler uses model.channel.guild_channel✕
- Connections
- 2 pairs of types, where a type in client.event_handler uses a type in model.channel.guild_channel.
- The types involved
serenity.client.event_handler.EventHandler→serenity.model.channel.guild_channel.GuildChannelserenity.client.event_handler.EventHandler→serenity.model.channel.guild_channel.PartialGuildChannel
- Direction
- client.event_handler uses model.channel.guild_channel, so a change to model.channel.guild_channel can break client.event_handler, while a change to client.event_handler can't break model.channel.guild_channel.
- Position
- Below the diagonal: client.event_handler uses a module listed above it, which is the healthy direction.
40→28 client.event_handler uses model.guild.member✕
- Connections
- 2 pairs of types, where a type in client.event_handler uses a type in model.guild.member.
- The types involved
serenity.client.event_handler.EventHandler→serenity.model.guild.member.Memberserenity.client.event_handler.EventHandler→serenity.model.guild.member.ThreadMember
- Direction
- client.event_handler uses model.guild.member, so a change to model.guild.member can break client.event_handler, while a change to client.event_handler can't break model.guild.member.
- Position
- Below the diagonal: client.event_handler uses a module listed above it, which is the healthy direction.
40→29 client.event_handler uses model.channel.reaction✕
- Connections
- 1 pair of types, where a type in client.event_handler uses a type in model.channel.reaction.
- The types involved
serenity.client.event_handler.EventHandler→serenity.model.channel.reaction.Reaction
- Direction
- client.event_handler uses model.channel.reaction, so a change to model.channel.reaction can break client.event_handler, while a change to client.event_handler can't break model.channel.reaction.
- Position
- Below the diagonal: client.event_handler uses a module listed above it, which is the healthy direction.
40→32 client.event_handler uses model.channel.message✕
- Connections
- 1 pair of types, where a type in client.event_handler uses a type in model.channel.message.
- The types involved
serenity.client.event_handler.EventHandler→serenity.model.channel.message.Message
- Direction
- client.event_handler uses model.channel.message, so a change to model.channel.message can break client.event_handler, while a change to client.event_handler can't break model.channel.message.
- Position
- Below the diagonal: client.event_handler uses a module listed above it, which is the healthy direction.
40→35 client.event_handler uses model.id✕
- Connections
- 6 pairs of types, where a type in client.event_handler uses a type in model.id.
- The types involved
serenity.client.event_handler.EventHandler→serenity.model.id.ApplicationIdserenity.client.event_handler.EventHandler→serenity.model.id.ChannelIdserenity.client.event_handler.EventHandler→serenity.model.id.GuildIdserenity.client.event_handler.EventHandler→serenity.model.id.IntegrationIdserenity.client.event_handler.EventHandler→serenity.model.id.MessageIdserenity.client.event_handler.EventHandler→serenity.model.id.RoleId
- Direction
- client.event_handler uses model.id, so a change to model.id can break client.event_handler, while a change to client.event_handler can't break model.id.
- Position
- Below the diagonal: client.event_handler uses a module listed above it, which is the healthy direction.
40→38 client.event_handler uses client.context✕
- Connections
- 3 pairs of types, where a type in client.event_handler uses a type in client.context.
- The types involved
serenity.client.event_handler.EventHandler→serenity.client.context.Contextserenity.client.event_handler.FullEvent→serenity.client.context.Contextserenity.client.event_handler.RawEventHandler→serenity.client.context.Context
- Direction
- client.event_handler uses client.context, so a change to client.context can break client.event_handler, while a change to client.event_handler can't break client.context.
- Position
- Below the diagonal: client.event_handler 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 — Event Sourcing
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 33 | High / Critical |
Roadmap
Top priorities: Resolve the 144 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (17), error.rs (4), message.rs (2); 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; Interpolated log message defeats structured logging.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| 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. | +8.6 pts | Medium | Architecture documentation |
| Interpolated log message defeats structured logging | +6.0 pts | Medium | Structured logging |
| Resolve the 144 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (17), error.rs (4), message.rs (2). | +8.9 pts | High | Knowledge Freshness |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +0.9 pts | Low | Project Cohesion |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +1.3 pts | Medium | Documentation (README) |
| Resolve the 1 Off the main sequence finding(s) in Coupling. | +0.6 pts | Low | Coupling |
| Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with create_invite.rs. | +0.5 pts | Low | Change Coupling |
| Bring the 20 bodies over 15 down to 15 or less in Cognitive Complexity — start with StandardFramework::dispatch (cognitive 58), serenity::framework::standard::help_commands::nested_commands_search (cognitive 44), serenity::utils::content_safe::clean_mentions (cognitive 38). | +1.9 pts | High | Cognitive Complexity |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| src/builder/create_interaction_response.rs | 5.5 | Mixed | Code Duplication: Edited copies of one member (5 members, 14+ corresponding lines) |
| src/builder/edit_message.rs | 5.7 | Mixed | Code Duplication: Duplicated block (14 lines × 2) |
| src/model/channel/guild_channel.rs | 5.9 | Mixed | God Classes: TooManyMethods: GuildChannel |
| src/framework/standard/mod.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| src/framework/standard/parse/mod.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| src/http/client.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/model/channel/message.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| command_attr/src/structures.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| src/model/application/command_interaction.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/builder/create_command.rs | 6.3 | Mixed | Code Duplication: Edited copies of one member (3 members, 9+ corresponding lines) |
| src/model/application/component_interaction.rs | 6.3 | Mixed | Code Duplication: Edited copy of a member (9 corresponding lines) |
| src/builder/create_invite.rs | 6.5 | Mixed | Change Coupling: Boundary-crossing change coupling: create_invite.rs ↔ mod.rs |
| src/builder/edit_automod_rule.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/builder/edit_role.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/model/guild/mod.rs | 7.0 | Near-clean | Cognitive Complexity: Guild::user_permissions_in_ (cognitive 19) |
| src/builder/create_thread.rs | 7.0 | Near-clean | Code Duplication: Edited copy of a member (9 corresponding lines) |
| src/builder/create_channel.rs | 7.0 | Near-clean | Code Duplication: Edited copies of one member (5 members, 6+ corresponding lines) |
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 40 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 — 40 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, 400 of 407 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 — evaluation did not complete — Code Coverage not included (check did not complete) — excluded from the score.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P9 Domain vs controller 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. The self-contained coverage run failed with IOException: No space left on device : '/tmp/codehealth-cargo-cov-W5az1H/profiles.txt' before it produced a report, so this card measured nothing. That failure is the analyzer's, not a statement about this repository's tests.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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. 53 further occurrence(s) are not listed individually; the score already reflects all 93.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
7 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was serenity::client::dispatch::update_cache_with_event at 79. A further 11 function(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Route::ratelimiting_bucket at 112 — they are counted neither in the figure above nor in this dimension's score. 7 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: src/http/routing.rs (Route::ratelimiting_bucket at 112), src/model/guild/audit_log/change.rs (Change::key at 82), src/client/event_handler.rs (FullEvent::snake_case_name at 79), command_attr/src/structures.rs (Permissions::from_str at 52), src/model/error.rs (Error::fmt at 26), and 2 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 3 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with serenity::client::dispatch::update_cache_with_event (cyclomatic 79), EventVisitor::visit_map (cyclomatic 32), StandardFramework::dispatch (cyclomatic 31). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 7.7 to about 8.7/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D2 · Cognitive Complexity
20 function(s) exceeded the cognitive complexity threshold of 15; the worst was StandardFramework::dispatch at 58.
What to do
- Bring the 20 bodies over 15 down to 15 or less in Cognitive Complexity — start with StandardFramework::dispatch (cognitive 58), serenity::framework::standard::help_commands::nested_commands_search (cognitive 44), serenity::utils::content_safe::clean_mentions (cognitive 38). — 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 20 together lifts Cognitive Complexity from 7.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
27 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 9 TooManyMethods finding(s) in God Classes — start with mod.rs (2), id.rs (2), client.rs. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 7 FileTooLong finding(s) in God Classes — start with client.rs, mod.rs, help_commands.rs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 5 TooManyFields finding(s) in God Classes — start with mod.rs, partial_guild.rs, message.rs. — One of this dimension's main actionable groups (5 warning-level).
D4 · Code Duplication
39 duplicated block group(s) detected. 3.7 % of the production lines (2,138 of 58,327) are in a reported copy. A further 43 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 (14 corresponding lines) finding(s) in Code Duplication — start with mod.rs (2), message.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with mod.rs (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with client.rs (2), edit_message.rs. — One of this dimension's main actionable groups (3 warning-level).
D5 · Coupling
3 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 2 of the 3 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
16 of 112 classes have LCOM4 above 3.
What to do
- Resolve the 16 Low cohesion finding(s) in Cohesion (LCOM4) — start with edit_guild.rs, edit_channel.rs, create_channel.rs. — One of this dimension's main actionable groups (16 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 47 test files): measured (0 flaky).
D12 · Dependency Hygiene
1 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from Cargo.lock there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 428 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository commits no Cargo.lock, so its graph was resolved here: its manifests' `[dependencies]` and `[build-dependencies]` closed over the crates.io index, each crate at the newest release its requirement admits (what a fresh `cargo generate-lockfile` picks, not a graph the repository has pinned). Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under ISC, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
No source file's living knowledge is concentrated in a single author. Counted over 148 of the 182 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
14 deducted task-comment markers across 58327 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 11 TodoComment finding(s) in Explicit Debt — start with message.rs (2), gateway.rs, automod.rs. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 3 FixmeComment finding(s) in Explicit Debt — start with mod.rs (2), structures.rs. — One of this dimension's main actionable groups (3 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 3 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
33 finding(s): 0 critical, 33 high, 0 medium, 0 low. 32 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.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 32 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 (32 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
147 of 148 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/http/client.rs. Counted over 148 of the 182 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 144 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (17), error.rs (4), message.rs (2). — One of this dimension's main actionable groups (144 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with mod.rs, client.rs, partial_guild.rs. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: component_interaction.rs↔modal_interaction.rs 77%; command_interaction.rs↔modal_interaction.rs 69%; create_embed.rs↔create_invite.rs 69%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with create_invite.rs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 10 Change coupling finding(s) in Change Coupling — start with component_interaction.rs, command_interaction.rs, create_embed.rs. — One of this dimension's main actionable groups (10 warning-level).
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 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
ES2 · Immutable events
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
P8 · Schema migrations
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
X1 · Async correctness
X21 · Side-effecting pattern guard
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `warn!` at line 133 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/utils/quick_modal.rs:133
- `warn!` at line 148 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/model/misc.rs:148
- `warn!` at line 203 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/model/utils.rs:203
- `debug!` at line 519 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/model/utils.rs:519
- `error!` at line 2067 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/model/guild/mod.rs:2067
- `warn!` at line 2076 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/model/guild/mod.rs:2076
- `warn!` at line 544 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/model/application/interaction.rs:544
- `warn!` at line 5241 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/http/client.rs:5241
- `debug!` at line 5247 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/http/client.rs:5247
- `debug!` at line 225 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/http/ratelimiting.rs:225
- `debug!` at line 305 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/http/ratelimiting.rs:305
- `debug!` at line 364 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/http/ratelimiting.rs:364
- `debug!` at line 209 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:209
- `warn!` at line 213 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:213
- `warn!` at line 282 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:282
- `debug!` at line 287 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:287
- `info!` at line 297 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:297
- `warn!` at line 322 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:322
- `warn!` at line 325 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:325
- `warn!` at line 328 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:328
- `error!` at line 333 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:333
- `warn!` at line 338 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:338
- `warn!` at line 341 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:341
- `warn!` at line 346 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:346
- `warn!` at line 349 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:349
- `error!` at line 354 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:354
- `info!` at line 359 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:359
- `error!` at line 364 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:364
- `error!` at line 369 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:369
- `warn!` at line 374 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:374
- `info!` at line 419 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:419
- `trace!` at line 427 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:427
- `debug!` at line 432 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:432
- `debug!` at line 443 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:443
- `info!` at line 449 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:449
- `info!` at line 462 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:462
- `info!` at line 463 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:463
- `warn!` at line 468 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:468
- `debug!` at line 503 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:503
- `warn!` at line 510 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/gateway/shard.rs:510
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 63% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 84% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 56% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 86% | Exemplary | Solid. |
| Security | 95% | Exemplary | Solid. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
| Performance | 91% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 3 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 74 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~3354 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (9377 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- 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 — Code Coverage not included (check did not complete)
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 24 value object(s); 2 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Fold determinism — not applicable — the code was read and holds no event-replay fold, so there is nothing for this check to judge
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, 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 — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's Rust source (3 module(s), 182 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — No web surface: 181 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — 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
- X13 Undrained process stream — 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
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not 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
- X17 Uncapped recursion over a caller-supplied document — 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
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 34 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: create_invite.rs ↔ mod.rs src/builder/create_invite.rs:1
Serious — 180 finding(s)
- Low cohesion: EditGuild (LCOM4 20) src/builder/edit_guild.rs:15
- Low cohesion: EditChannel (LCOM4 19) src/builder/edit_channel.rs:35
- Low cohesion: CreateChannel (LCOM4 17) src/builder/create_channel.rs:16
- Low cohesion: CreateCommand (LCOM4 13) src/builder/create_command.rs:302
- Low cohesion: CreateScheduledEvent (LCOM4 9) src/builder/create_scheduled_event.rs:13
- Low cohesion: CreateInteractionResponseMessage (LCOM4 8) src/builder/create_interaction_response.rs:179
- Low cohesion: CreateInvite (LCOM4 8) src/builder/create_invite.rs:30
- Low cohesion: CreateMessage (LCOM4 8) src/builder/create_message.rs:56
- Low cohesion: EditAutoModRule (LCOM4 8) src/builder/edit_automod_rule.rs:19
- Low cohesion: EditRole (LCOM4 8) src/builder/edit_role.rs:48
- Low cohesion: ExecuteWebhook (LCOM4 8) src/builder/execute_webhook.rs:61
- Low cohesion: CreateSoundboard (LCOM4 6) src/builder/create_soundboard.rs:15
- Low cohesion: CreateThread (LCOM4 6) src/builder/create_thread.rs:14
- Low cohesion: CreateForumPost (LCOM4 5) src/builder/create_forum_post.rs:13
- Low cohesion: CreateInteractionResponseFollowup (LCOM4 5) src/builder/create_interaction_response_followup.rs:23
- Low cohesion: EditWebhook (LCOM4 4) src/builder/edit_webhook.rs:13
- TodoComment src/model/gateway.rs:274
- TodoComment src/model/guild/automod.rs:16
- TodoComment src/model/guild/audit_log/mod.rs:359
- TodoComment src/model/channel/message.rs:137
- TodoComment src/model/channel/message.rs:1169
- TodoComment src/model/application/command_interaction.rs:78
- TodoComment src/http/client.rs:3704
- TodoComment src/client/event_handler.rs:31
- TodoComment src/builder/edit_automod_rule.rs:142
- TodoComment src/builder/edit_role.rs:93
- TodoComment examples/e15_simple_dashboard/src/main.rs:320
- serenity::framework::standard::help_commands::nested_commands_search (cognitive 44) src/framework/standard/help_commands.rs:299
- serenity::utils::content_safe::clean_mentions (cognitive 38) src/utils/content_safe.rs:161
- serenity::framework::standard::parse::permissions_in (cognitive 31) src/framework/standard/parse/mod.rs:25
- serenity::framework::standard::parse::command (cognitive 24) src/framework/standard/parse/mod.rs:425
- serenity::utils::parse_quotes (cognitive 24) src/utils/mod.rs:339
- serenity::utils::parse_emoji (cognitive 22) src/utils/mod.rs:272
- serenity::utils::content_safe::clean_mention (cognitive 22) src/utils/content_safe.rs:217
- serenity::framework::standard::help_commands::create_customised_help_data (cognitive 20) src/framework/standard/help_commands.rs:818
- serenity::framework::standard::help_commands::nested_group_command_search (cognitive 19) src/framework/standard/help_commands.rs:436
- serenity::framework::standard::parse::check_discrepancy (cognitive 19) src/framework/standard/parse/mod.rs:198
- Change coupling: component_interaction.rs ↔ modal_interaction.rs src/model/application/component_interaction.rs:1
- Change coupling: command_interaction.rs ↔ modal_interaction.rs src/model/application/command_interaction.rs:1
- Change coupling: create_embed.rs ↔ create_invite.rs src/builder/create_embed.rs:1
- Change coupling: create_interaction_response.rs ↔ create_interaction_response_followup.rs src/builder/create_interaction_response.rs:1
- Change coupling: guild_channel.rs ↔ private_channel.rs src/model/channel/guild_channel.rs:1
- Change coupling: edit_webhook_message.rs ↔ execute_webhook.rs src/builder/edit_webhook_message.rs:1
- Change coupling: shard_messenger.rs ↔ shard.rs src/gateway/bridge/shard_messenger.rs:1
- Change coupling: shard_runner_message.rs ↔ shard.rs src/gateway/bridge/shard_runner_message.rs:1
- Change coupling: create_message.rs ↔ edit_guild.rs src/builder/create_message.rs:1
- Change coupling: edit_message.rs ↔ edit_webhook_message.rs src/builder/edit_message.rs:1
- TooManyMethods: Http src/http/client.rs:197
- TooManyMethods: Guild src/model/guild/mod.rs:111
- TooManyMethods: GuildId src/model/id.rs:194
- TooManyMethods: PartialGuild src/model/guild/partial_guild.rs:40
- TooManyMethods: ChannelId src/model/id.rs:191
- TooManyMethods: GuildChannel src/model/channel/guild_channel.rs:44
- TooManyMethods: MessageBuilder src/utils/message_builder.rs:36
- TooManyMethods: Message src/model/channel/message.rs:36
- TooManyMethods: Cache src/cache/mod.rs:179
- FileTooLong: http/client.rs src/http/client.rs
- FileTooLong: guild/mod.rs src/model/guild/mod.rs
- FileTooLong: standard/help_commands.rs src/framework/standard/help_commands.rs
- FileTooLong: model/event.rs src/model/event.rs
- FileTooLong: guild/guild_id.rs src/model/guild/guild_id.rs
- FileTooLong: channel/message.rs src/model/channel/message.rs
- FileTooLong: guild/partial_guild.rs src/model/guild/partial_guild.rs
- TooManyFields: Guild src/model/guild/mod.rs:111
- TooManyFields: PartialGuild src/model/guild/partial_guild.rs:40
- TooManyFields: Message src/model/channel/message.rs:36
- TooManyFields: GuildChannel src/model/channel/guild_channel.rs:44
- TooManyFields: MessageUpdateEvent src/model/event.rs:560
- serenity::client::dispatch::update_cache_with_event (cyclomatic 79) src/client/dispatch.rs:95
- serenity::framework::standard::parse::permissions_in (cyclomatic 16) src/framework/standard/parse/mod.rs:25
- serenity::framework::standard::parse::check_discrepancy (cyclomatic 16) src/framework/standard/parse/mod.rs:198
- FixmeComment src/framework/standard/mod.rs:724
- FixmeComment src/framework/standard/parse/mod.rs:11
- FixmeComment command_attr/src/structures.rs:116
- ClassTooLong: Http src/http/client.rs:197
- ClassTooLong: Guild src/model/guild/mod.rs:111
- ClassTooLong: PartialGuild src/model/guild/partial_guild.rs:40
- FunctionTooLong: serenity::client::dispatch::update_cache_with_event src/client/dispatch.rs:95
- FunctionTooLong: command_attr::help command_attr/src/lib.rs:279
- FunctionTooLong: command_attr::command command_attr/src/lib.rs:96
- Edited copy of a member (14 corresponding lines) src/model/channel/message.rs:343
- Edited copy of a member (14 corresponding lines) src/model/guild/mod.rs:2008
- Edited copy of a member (14 corresponding lines) src/model/guild/mod.rs:1948
- Edited copy of a member (10 corresponding lines) src/model/guild/mod.rs:502
- Edited copy of a member (10 corresponding lines) src/model/guild/mod.rs:1986
- Edited copy of a member (10 corresponding lines) src/model/guild/mod.rs:1923
- Duplicated block (14 lines × 2) src/builder/edit_message.rs:64
- Duplicated block (14 lines × 2) src/http/client.rs:2159
- Duplicated block (14 lines × 2) src/http/client.rs:2257
- Duplicated block (13 lines × 2) command_attr/src/structures.rs:153
- Duplicated block (13 lines × 2) src/framework/standard/args.rs:790
- Duplicated block (13 lines × 2) src/model/invite.rs:100
- Duplicated block (12 lines × 2) src/http/client.rs:2773
- Duplicated block (12 lines × 2) src/model/guild/mod.rs:1759
- Duplicated block (12 lines × 2) src/builder/create_interaction_response.rs:291
- Duplicated block (11 lines × 3) command_attr/src/lib.rs:108
- Duplicated block (11 lines × 3) src/http/client.rs:2115
- Duplicated block (11 lines × 3) src/http/client.rs:3039
- Duplicated block (11 lines × 2) src/framework/standard/parse/mod.rs:294
- Duplicated block (11 lines × 2) src/cache/event.rs:508
- Duplicated block (11 lines × 2) src/utils/mod.rs:182
- Duplicated block (10 lines × 2) src/http/client.rs:551
- Duplicated block (10 lines × 2) src/model/guild/mod.rs:1861
- Duplicated block (10 lines × 2) src/utils/message_builder.rs:555
- Duplicated block (8 lines × 2) command_attr/src/lib.rs:476
- Duplicated block (8 lines × 2) src/model/application/component_interaction.rs:236
- Duplicated block (8 lines × 2) src/model/channel/channel_id.rs:1280
- StandardFramework::dispatch (cyclomatic 31) src/framework/standard/mod.rs:612
- StandardFramework::should_fail (cyclomatic 21) src/framework/standard/mod.rs:210
- StandardFramework::dispatch (cognitive 58) src/framework/standard/mod.rs:612
- StandardFramework::should_fail (cognitive 34) src/framework/standard/mod.rs:210
- REDACTED
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) command_attr/src/lib.rs:96
- Members sharing a duplicated core (4 members, 50+ identical tokens) command_attr/src/lib.rs:96
- Edited copy of a member (20 corresponding lines) src/framework/standard/parse/map.rs:26
- Edited copy of a member (20 corresponding lines) src/framework/standard/args.rs:789
- Edited copies of one member (3 members, 16+ corresponding lines) src/model/guild/mod.rs:1803
- Edited copies of one member (3 members, 16+ corresponding lines) src/model/channel/message.rs:270
- Edited copy of a member (13 corresponding lines) src/model/channel/channel_id.rs:1275
- Edited copy of a member (13 corresponding lines) src/http/client.rs:303
- Edited copy of a member (11 corresponding lines) src/model/utils.rs:27
- Edited copy of a member (11 corresponding lines) src/model/guild/emoji.rs:193
- Edited copy of a member (9 corresponding lines) src/model/application/component_interaction.rs:234
- Edited copy of a member (9 corresponding lines) src/builder/create_thread.rs:113
- Edited copy of a member (7 corresponding lines) src/json.rs:44
- Edited copy of a member (7 corresponding lines) src/model/guild/role.rs:159
- Duplicated block (9 lines × 2) command_attr/src/structures.rs:168
- Duplicated block (9 lines × 2) src/framework/standard/parse/mod.rs:483
- Duplicated block (7 lines × 2) src/builder/create_command.rs:131
- Duplicated block (7 lines × 2) src/model/channel/reaction.rs:76
- Duplicated block (5 lines × 2) src/builder/edit_message.rs:191
- Duplicated block (5 lines × 2) src/builder/edit_message.rs:198
- EventVisitor::visit_map (cyclomatic 32) voice-model/src/event/mod.rs:103
- MessageUpdateEvent::apply_to_message (cyclomatic 29) src/model/event.rs:610
- ShardRunner::run (cognitive 29) src/gateway/bridge/shard_runner.rs:102
- TicketCounter::take (cognitive 28) src/framework/standard/structures/buckets.rs:173
- MessageUpdateEvent::apply_to_message (cognitive 28) src/model/event.rs:610
- command_attr::help (cognitive 24) command_attr/src/lib.rs:279
- ComponentInteractionCollector::stream (cognitive 20) src/collector.rs:99
- ModalInteractionCollector::stream (cognitive 20) src/collector.rs:99
- Guild::user_permissions_in_ (cognitive 19) src/model/guild/mod.rs:2024
- ReactionCollector::stream (cognitive 17) src/collector.rs:99
- REDACTED
- Members sharing a duplicated core (5 members, 50+ identical tokens) src/http/client.rs:2181
- Edited copy of a member (34 corresponding lines) command_attr/src/structures.rs:145
- Edited copy of a member (32 corresponding lines) src/framework/standard/parse/mod.rs:278
- Edited copy of a member (19 corresponding lines) src/framework/standard/structures/buckets.rs:59
- Edited copies of one member (4 members, 22+ corresponding lines) src/model/channel/channel_id.rs:395
- Edited copies of one member (5 members, 22+ corresponding lines) src/http/client.rs:2766
- Edited copies of one member (7 members, 24+ corresponding lines) src/http/client.rs:544
- Edited copies of one member (5 members, 14+ corresponding lines) src/builder/create_interaction_response.rs:113
- Edited copies of one member (8 members, 20+ corresponding lines) src/http/client.rs:863
- Edited copies of one member (4 members, 19+ corresponding lines) src/http/client.rs:3038
- Edited copy of a member (16 corresponding lines) src/model/guild/guild_id.rs:1129
- Edited copy of a member (17 corresponding lines) src/http/client.rs:473
- Edited copies of one member (3 members, 20+ corresponding lines) src/http/client.rs:2730
- Edited copy of a member (12 corresponding lines) src/model/guild/guild_id.rs:964
- Edited copies of one member (3 members, 9+ corresponding lines) src/builder/create_command.rs:129
- Edited copies of one member (3 members, 15+ corresponding lines) src/http/client.rs:804
- Edited copies of one member (3 members, 17+ corresponding lines) src/http/client.rs:3781
- Edited copy of a member (6 corresponding lines) src/model/channel/guild_channel.rs:770
- Edited copies of one member (6 members, 14+ corresponding lines) src/http/client.rs:617
- Edited copies of one member (4 members, 11+ corresponding lines) src/utils/message_builder.rs:580
- Edited copy of a member (8 corresponding lines) src/model/application/interaction.rs:104
- Edited copies of one member (5 members, 13+ corresponding lines) src/http/client.rs:2652
- Edited copies of one member (5 members, 6+ corresponding lines) src/builder/create_channel.rs:277
- Duplicated block (22 lines × 2) src/framework/standard/structures/buckets.rs:196
- Duplicated block (16–17 lines × 2) src/http/client.rs:2113
- Duplicated block (16 lines × 2) src/model/guild/mod.rs:1126
- Duplicated block (15 lines × 2) src/gateway/bridge/shard_manager.rs:305
- Duplicated block (13 lines × 5) src/http/client.rs:2198
- Duplicated block (11 lines × 5) src/http/client.rs:555
- Duplicated block (10 lines × 4) command_attr/src/lib.rs:107
- Duplicated block (10 lines × 3) src/builder/create_interaction_response_followup.rs:50
- Duplicated block (8 lines × 4) command_attr/src/lib.rs:226
- Duplicated block (6 lines × 2) src/builder/edit_message.rs:266
- Duplicated block (6 lines × 3) src/model/application/command_interaction.rs:232
- Duplicated block (9 lines × 4) src/http/client.rs:2846
- Off the main sequence: serenity-voice-model
Minor — 192 finding(s)
- Orphaned file src/model/channel/message.rs:1
- Orphaned file src/model/event.rs:1
- Orphaned file command_attr/src/lib.rs:1
- Orphaned file src/framework/standard/help_commands.rs:1
- Orphaned file src/model/channel/guild_channel.rs:1
- Orphaned file src/model/channel/channel_id.rs:1
- Orphaned file src/utils/message_builder.rs:1
- Orphaned file src/model/user.rs:1
- Orphaned file src/client/mod.rs:1
- Orphaned file src/model/application/command_interaction.rs:1
- Orphaned file src/cache/mod.rs:1
- Orphaned file src/model/gateway.rs:1
- Orphaned file src/framework/standard/mod.rs:1
- Orphaned file src/gateway/shard.rs:1
- Orphaned file src/framework/standard/args.rs:1
- Orphaned file src/model/guild/member.rs:1
- Orphaned file src/client/event_handler.rs:1
- Orphaned file src/model/guild/automod.rs:1
- Orphaned file src/model/channel/mod.rs:1
- Orphaned file src/http/routing.rs:1
- Orphaned file src/cache/event.rs:1
- Orphaned file src/model/application/interaction.rs:1
- Orphaned file src/model/permissions.rs:1
- Orphaned file src/framework/standard/configuration.rs:1
- Orphaned file src/model/webhook.rs:1
- Interpolated log message defeats structured logging src/utils/quick_modal.rs:133
- Interpolated log message defeats structured logging src/model/misc.rs:148
- Interpolated log message defeats structured logging src/model/utils.rs:203
- Interpolated log message defeats structured logging src/model/utils.rs:519
- Interpolated log message defeats structured logging src/model/guild/mod.rs:2067
- Interpolated log message defeats structured logging src/model/guild/mod.rs:2076
- Interpolated log message defeats structured logging src/model/application/interaction.rs:544
- Interpolated log message defeats structured logging src/http/client.rs:5241
- Interpolated log message defeats structured logging src/http/client.rs:5247
- Interpolated log message defeats structured logging src/http/ratelimiting.rs:225
- Interpolated log message defeats structured logging src/http/ratelimiting.rs:305
- Interpolated log message defeats structured logging src/http/ratelimiting.rs:364
- Interpolated log message defeats structured logging src/gateway/shard.rs:209
- Interpolated log message defeats structured logging src/gateway/shard.rs:213
- Interpolated log message defeats structured logging src/gateway/shard.rs:282
- Interpolated log message defeats structured logging src/gateway/shard.rs:287
- Interpolated log message defeats structured logging src/gateway/shard.rs:297
- Interpolated log message defeats structured logging src/gateway/shard.rs:322
- Interpolated log message defeats structured logging src/gateway/shard.rs:325
- Interpolated log message defeats structured logging src/gateway/shard.rs:328
- Interpolated log message defeats structured logging src/gateway/shard.rs:333
- Interpolated log message defeats structured logging src/gateway/shard.rs:338
- Interpolated log message defeats structured logging src/gateway/shard.rs:341
- Interpolated log message defeats structured logging src/gateway/shard.rs:346
- Interpolated log message defeats structured logging src/gateway/shard.rs:349
- Most significant orphaned file src/model/guild/mod.rs:1
- Most significant orphaned file src/http/client.rs:1
- Most significant orphaned file src/model/guild/partial_guild.rs:1
- Projects may be oversized for their cohesion
- Concentrated knowledge decay
- REDACTED
- No ADRs
- No architecture diagram/doc
Minor — 1 finding(s)
- Outdated: reqwest
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-aae580f2bbdb49ab8019e34ffdfcbc5e/history.json --exit-code 0 --source . | 26 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-aae580f2bbdb49ab8019e34ffdfcbc5e/tree.json --exit-code 0 --source . | 5 | 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 . | 33 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |