{"$schema":"https://json.schemastore.org/sarif-2.1.0.json","version":"2.1.0","runs":[{"tool":{"driver":{"name":"codehealth","informationUri":"https://codehealth.canine.dev","rules":[{"id":"D1","name":"Cyclomatic Complexity","shortDescription":{"text":"Cyclomatic Complexity"},"helpUri":"https://codehealth.canine.dev/dimensions/D1"},{"id":"D2","name":"Cognitive Complexity","shortDescription":{"text":"Cognitive Complexity"},"helpUri":"https://codehealth.canine.dev/dimensions/D2"},{"id":"D3","name":"God Classes","shortDescription":{"text":"God Classes"},"helpUri":"https://codehealth.canine.dev/dimensions/D3"},{"id":"D4","name":"Code Duplication","shortDescription":{"text":"Code Duplication"},"helpUri":"https://codehealth.canine.dev/dimensions/D4"},{"id":"D6","name":"Cohesion (LCOM4)","shortDescription":{"text":"Cohesion (LCOM4)"},"helpUri":"https://codehealth.canine.dev/dimensions/D6"},{"id":"D9","name":"Test Distribution","shortDescription":{"text":"Test Distribution"},"helpUri":"https://codehealth.canine.dev/dimensions/D9"},{"id":"D12","name":"Dependency Hygiene","shortDescription":{"text":"Dependency Hygiene"},"helpUri":"https://codehealth.canine.dev/dimensions/D12"},{"id":"D13","name":"Secret Scanning","shortDescription":{"text":"Secret Scanning"},"helpUri":"https://codehealth.canine.dev/dimensions/D13","relationships":[{"target":{"id":"CWE-798","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-259","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"A07:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-798","CWE-259"],"owasp":"A07:2025"}},{"id":"D14","name":"License Compliance","shortDescription":{"text":"License Compliance"},"helpUri":"https://codehealth.canine.dev/dimensions/D14"},{"id":"D15","name":"Churn \u00D7 Complexity Hotspots","shortDescription":{"text":"Churn \u00D7 Complexity Hotspots"},"helpUri":"https://codehealth.canine.dev/dimensions/D15"},{"id":"D17","name":"Explicit Debt","shortDescription":{"text":"Explicit Debt"},"helpUri":"https://codehealth.canine.dev/dimensions/D17"},{"id":"D19","name":"Documentation Quality","shortDescription":{"text":"Documentation Quality"},"helpUri":"https://codehealth.canine.dev/dimensions/D19"},{"id":"D23","name":"Boundary Type-Coupling","shortDescription":{"text":"Boundary Type-Coupling"},"helpUri":"https://codehealth.canine.dev/dimensions/D23"},{"id":"D26","name":"Project Cohesion","shortDescription":{"text":"Project Cohesion"},"helpUri":"https://codehealth.canine.dev/dimensions/D26"},{"id":"D27","name":"Navigability","shortDescription":{"text":"Navigability"},"helpUri":"https://codehealth.canine.dev/dimensions/D27"},{"id":"D28","name":"Secrets (history)","shortDescription":{"text":"Secrets (history)"},"helpUri":"https://codehealth.canine.dev/dimensions/D28","relationships":[{"target":{"id":"CWE-798","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-259","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"A07:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-798","CWE-259"],"owasp":"A07:2025"}},{"id":"D29","name":"Static Analysis (SAST)","shortDescription":{"text":"Static Analysis (SAST)"},"helpUri":"https://codehealth.canine.dev/dimensions/D29","relationships":[{"target":{"id":"CWE-79","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-89","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-78","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-94","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-77","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"A05:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-79","CWE-89","CWE-78","CWE-94","CWE-77"],"owasp":"A05:2025"}},{"id":"D30","name":"Dependency Vulnerabilities","shortDescription":{"text":"Dependency Vulnerabilities"},"helpUri":"https://codehealth.canine.dev/dimensions/D30","relationships":[{"target":{"id":"CWE-1395","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-937","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"A03:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-1395","CWE-937"],"owasp":"A03:2025"}},{"id":"D31","name":"IaC \u0026 Container Security","shortDescription":{"text":"IaC \u0026 Container Security"},"helpUri":"https://codehealth.canine.dev/dimensions/D31","relationships":[{"target":{"id":"CWE-1032","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-732","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-16","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"A02:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-1032","CWE-732","CWE-16"],"owasp":"A02:2025"}},{"id":"D35","name":"Change Coupling","shortDescription":{"text":"Change Coupling"},"helpUri":"https://codehealth.canine.dev/dimensions/D35"},{"id":"D43","name":"Malicious Dependencies","shortDescription":{"text":"Malicious Dependencies"},"helpUri":"https://codehealth.canine.dev/dimensions/D43","relationships":[{"target":{"id":"CWE-506","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"A08:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-506"],"owasp":"A08:2025"}},{"id":"D44","name":"Platform End-of-Life","shortDescription":{"text":"Platform End-of-Life"},"helpUri":"https://codehealth.canine.dev/dimensions/D44"},{"id":"AX10","name":"Code composition","shortDescription":{"text":"Code composition"},"helpUri":"https://codehealth.canine.dev/dimensions/AX10"},{"id":"AX3","name":"Project dependency cycles","shortDescription":{"text":"Project dependency cycles"},"helpUri":"https://codehealth.canine.dev/dimensions/AX3"},{"id":"AX4","name":"Dependency direction","shortDescription":{"text":"Dependency direction"},"helpUri":"https://codehealth.canine.dev/dimensions/AX4"},{"id":"AX5","name":"Architecture \u0026 structure","shortDescription":{"text":"Architecture \u0026 structure"},"helpUri":"https://codehealth.canine.dev/dimensions/AX5"},{"id":"AXB2","name":"Runtime readiness","shortDescription":{"text":"Runtime readiness"},"helpUri":"https://codehealth.canine.dev/dimensions/AXB2"},{"id":"C2","name":"Access Controls","shortDescription":{"text":"Access Controls"},"helpUri":"https://codehealth.canine.dev/dimensions/C2"},{"id":"C3","name":"Audit Trail","shortDescription":{"text":"Audit Trail"},"helpUri":"https://codehealth.canine.dev/dimensions/C3"},{"id":"DM1","name":"Aggregate boundaries","shortDescription":{"text":"Aggregate boundaries"},"helpUri":"https://codehealth.canine.dev/dimensions/DM1"},{"id":"DM10","name":"One transaction, one aggregate","shortDescription":{"text":"One transaction, one aggregate"},"helpUri":"https://codehealth.canine.dev/dimensions/DM10"},{"id":"DM11","name":"Constructible invalid state","shortDescription":{"text":"Constructible invalid state"},"helpUri":"https://codehealth.canine.dev/dimensions/DM11"},{"id":"DM12","name":"Ambient inputs in the domain","shortDescription":{"text":"Ambient inputs in the domain"},"helpUri":"https://codehealth.canine.dev/dimensions/DM12"},{"id":"DM2","name":"Strongly-typed ids","shortDescription":{"text":"Strongly-typed ids"},"helpUri":"https://codehealth.canine.dev/dimensions/DM2"},{"id":"DM3","name":"Integration-event coupling","shortDescription":{"text":"Integration-event coupling"},"helpUri":"https://codehealth.canine.dev/dimensions/DM3"},{"id":"DM4","name":"Rich vs anemic model","shortDescription":{"text":"Rich vs anemic model"},"helpUri":"https://codehealth.canine.dev/dimensions/DM4"},{"id":"DM5","name":"Encapsulated state","shortDescription":{"text":"Encapsulated state"},"helpUri":"https://codehealth.canine.dev/dimensions/DM5"},{"id":"DM6","name":"Domain \u2194 infrastructure boundary","shortDescription":{"text":"Domain \u2194 infrastructure boundary"},"helpUri":"https://codehealth.canine.dev/dimensions/DM6"},{"id":"DM9","name":"Scattered domain decisions","shortDescription":{"text":"Scattered domain decisions"},"helpUri":"https://codehealth.canine.dev/dimensions/DM9"},{"id":"ED5","name":"Idempotency","shortDescription":{"text":"Idempotency"},"helpUri":"https://codehealth.canine.dev/dimensions/ED5"},{"id":"M1","name":"Documentation (README)","shortDescription":{"text":"Documentation (README)"},"helpUri":"https://codehealth.canine.dev/dimensions/M1"},{"id":"M2","name":"Architecture documentation","shortDescription":{"text":"Architecture documentation"},"helpUri":"https://codehealth.canine.dev/dimensions/M2"},{"id":"M3","name":"Folder \u0026 project structure","shortDescription":{"text":"Folder \u0026 project structure"},"helpUri":"https://codehealth.canine.dev/dimensions/M3"},{"id":"M4","name":"Documentation accuracy","shortDescription":{"text":"Documentation accuracy"},"helpUri":"https://codehealth.canine.dev/dimensions/M4"},{"id":"P1","name":"CI/CD gates","shortDescription":{"text":"CI/CD gates"},"helpUri":"https://codehealth.canine.dev/dimensions/P1"},{"id":"P3","name":"Security \u0026 performance tooling","shortDescription":{"text":"Security \u0026 performance tooling"},"helpUri":"https://codehealth.canine.dev/dimensions/P3"},{"id":"P4","name":"Deployment \u0026 Rollback","shortDescription":{"text":"Deployment \u0026 Rollback"},"helpUri":"https://codehealth.canine.dev/dimensions/P4"},{"id":"P6","name":"Release Hygiene","shortDescription":{"text":"Release Hygiene"},"helpUri":"https://codehealth.canine.dev/dimensions/P6"},{"id":"P7","name":"Outbound HTTP resilience","shortDescription":{"text":"Outbound HTTP resilience"},"helpUri":"https://codehealth.canine.dev/dimensions/P7"},{"id":"P8","name":"Schema migrations","shortDescription":{"text":"Schema migrations"},"helpUri":"https://codehealth.canine.dev/dimensions/P8"},{"id":"PF3","name":"Async \u0026 latency hygiene","shortDescription":{"text":"Async \u0026 latency hygiene"},"helpUri":"https://codehealth.canine.dev/dimensions/PF3"},{"id":"X1","name":"Async correctness","shortDescription":{"text":"Async correctness"},"helpUri":"https://codehealth.canine.dev/dimensions/X1"},{"id":"X10","name":"Duplicated predicate","shortDescription":{"text":"Duplicated predicate"},"helpUri":"https://codehealth.canine.dev/dimensions/X10"},{"id":"X12","name":"Unreachable branch","shortDescription":{"text":"Unreachable branch"},"helpUri":"https://codehealth.canine.dev/dimensions/X12"},{"id":"X13","name":"Undrained process stream","shortDescription":{"text":"Undrained process stream"},"helpUri":"https://codehealth.canine.dev/dimensions/X13"},{"id":"X14","name":"Bypassable address classification","shortDescription":{"text":"Bypassable address classification"},"helpUri":"https://codehealth.canine.dev/dimensions/X14"},{"id":"X15","name":"Unvalidated length from an untrusted reader","shortDescription":{"text":"Unvalidated length from an untrusted reader"},"helpUri":"https://codehealth.canine.dev/dimensions/X15"},{"id":"X17","name":"Uncapped recursion over a caller-supplied document","shortDescription":{"text":"Uncapped recursion over a caller-supplied document"},"helpUri":"https://codehealth.canine.dev/dimensions/X17"},{"id":"X19","name":"Unrestored process-global state","shortDescription":{"text":"Unrestored process-global state"},"helpUri":"https://codehealth.canine.dev/dimensions/X19"},{"id":"X20","name":"Mistyped argument guard","shortDescription":{"text":"Mistyped argument guard"},"helpUri":"https://codehealth.canine.dev/dimensions/X20"},{"id":"X21","name":"Side-effecting pattern guard","shortDescription":{"text":"Side-effecting pattern guard"},"helpUri":"https://codehealth.canine.dev/dimensions/X21"},{"id":"X22","name":"Contradicted release guard","shortDescription":{"text":"Contradicted release guard"},"helpUri":"https://codehealth.canine.dev/dimensions/X22"},{"id":"X23","name":"Unguarded diagnostic materialisation","shortDescription":{"text":"Unguarded diagnostic materialisation"},"helpUri":"https://codehealth.canine.dev/dimensions/X23"},{"id":"X24","name":"Document value interpolated into markup unescaped","shortDescription":{"text":"Document value interpolated into markup unescaped"},"helpUri":"https://codehealth.canine.dev/dimensions/X24"},{"id":"X25","name":"Inert configuration knob","shortDescription":{"text":"Inert configuration knob"},"helpUri":"https://codehealth.canine.dev/dimensions/X25"},{"id":"X26","name":"Unsynchronised callback handoff","shortDescription":{"text":"Unsynchronised callback handoff"},"helpUri":"https://codehealth.canine.dev/dimensions/X26"},{"id":"X27","name":"Collection changed while being enumerated","shortDescription":{"text":"Collection changed while being enumerated"},"helpUri":"https://codehealth.canine.dev/dimensions/X27"},{"id":"X28","name":"Index access outside its own emptiness guard","shortDescription":{"text":"Index access outside its own emptiness guard"},"helpUri":"https://codehealth.canine.dev/dimensions/X28"},{"id":"X3","name":"Exception handling","shortDescription":{"text":"Exception handling"},"helpUri":"https://codehealth.canine.dev/dimensions/X3"},{"id":"X30","name":"Support guard that admits what it rejects","shortDescription":{"text":"Support guard that admits what it rejects"},"helpUri":"https://codehealth.canine.dev/dimensions/X30"},{"id":"X32","name":"Type resolved by simple name across every loaded assembly","shortDescription":{"text":"Type resolved by simple name across every loaded assembly"},"helpUri":"https://codehealth.canine.dev/dimensions/X32"},{"id":"X4","name":"Structured logging","shortDescription":{"text":"Structured logging"},"helpUri":"https://codehealth.canine.dev/dimensions/X4"},{"id":"X6","name":"Hand-rolled structured-format parsing","shortDescription":{"text":"Hand-rolled structured-format parsing"},"helpUri":"https://codehealth.canine.dev/dimensions/X6"},{"id":"X7","name":"Silent fallback defaults","shortDescription":{"text":"Silent fallback defaults"},"helpUri":"https://codehealth.canine.dev/dimensions/X7"},{"id":"X9","name":"Subsumed condition operand","shortDescription":{"text":"Subsumed condition operand"},"helpUri":"https://codehealth.canine.dev/dimensions/X9"}]}},"results":[{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (18\u201320 lines \u00D7 2): src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:129-148 | src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:151-168 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:129\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py"},"region":{"startLine":129}}}],"partialFingerprints":{"codehealthFindingId/v1":"2f981e17af22441bbcf403d90bce81e7738f9f72873a914f314d51dda79e81b7"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (18\u201319 lines \u00D7 2): src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:105-122 | src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:178-196 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:178\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py"},"region":{"startLine":105}}}],"partialFingerprints":{"codehealthFindingId/v1":"4306ec62ea1b35c08bddb7a37467f629ef893ac8206e638f5a9667453215c599"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (18 lines \u00D7 2): src/application/cqrs/user/commands/register_oauth_user.py:59-76 | src/application/cqrs/user/commands/register_user.py:65-82 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from both call sites, so a change lands once. The \u0060return\u0060 at the foot of the matched lines is the enclosing body\u0027s own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that \u0060return\u0060 occupied \u2014 no decision has to be handed back and re-acted on. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060src/application/cqrs/user/commands/register_oauth_user.py:57\u0060 calls \u0060create_oauth_account\u0060 and \u0060src/application/cqrs/user/commands/register_user.py:64\u0060 does not \u2014 after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/cqrs/user/commands/register_oauth_user.py"},"region":{"startLine":59}}}],"partialFingerprints":{"codehealthFindingId/v1":"9c0ba664977b6e342500d960a9851a5d9084317ca486600dbec3e69e8c54e02d"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (16 lines \u00D7 2): src/infrastructure/repositories/converters.py:64-79 | src/infrastructure/repositories/converters.py:87-102 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060src/infrastructure/repositories/converters.py:81\u0060 calls \u0060add_role\u0060 and \u0060src/infrastructure/repositories/converters.py:104\u0060 does not \u2014 after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/repositories/converters.py"},"region":{"startLine":64}}}],"partialFingerprints":{"codehealthFindingId/v1":"b814443327003e7b4e1aac75f110a721f24f0ac00d6ecc180753e696768f86e6"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (14 lines \u00D7 2): src/application/services/tasks/email_templates.py:188-201 | src/application/services/tasks/email_templates.py:209-222 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/services/tasks/email_templates.py"},"region":{"startLine":188}}}],"partialFingerprints":{"codehealthFindingId/v1":"8800ff0df5fc742bba096d96b6af839a34b3f03f92471dedf08b9b58f50f4935"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12\u201313 lines \u00D7 5): src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:29-40 | src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:51-63 | src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:82-93 | src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:106-117 | src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:180-191 \u2014 all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites \u2014 resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:51\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:105\u0060 calls \u0060Column\u0060, \u0060Boolean\u0060 and \u0060src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:28\u0060 does not \u2014 after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py"},"region":{"startLine":29}}}],"partialFingerprints":{"codehealthFindingId/v1":"4820160a1d99d08304c327955360c1e75d071c1bf17796c707250a8488fe803f"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10\u201311 lines \u00D7 2): src/infrastructure/repositories/converters.py:204-214 | src/infrastructure/repositories/converters.py:241-250 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060src/infrastructure/repositories/converters.py:204\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/repositories/converters.py"},"region":{"startLine":204}}}],"partialFingerprints":{"codehealthFindingId/v1":"4f9ca47b82ab4c27b9f78251f3edc92408569f7cdc375ba572d03f0a49e18139"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7\u20139 lines \u00D7 2): src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:28-36 | src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:172-178 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:28\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names \u2014 the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py"},"region":{"startLine":28}}}],"partialFingerprints":{"codehealthFindingId/v1":"97f6ad58c6ed78b83a7e6d3802231c551526792dddd5547608d7fa24f091d58a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:42-46 | src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:66-70 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:42\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:65\u0060 calls \u0060UniqueConstraint\u0060, \u0060f\u0060 and \u0060src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:41\u0060 does not \u2014 after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py"},"region":{"startLine":42}}}],"partialFingerprints":{"codehealthFindingId/v1":"37f0dc5da646371c7b77d0c6df5d1b26c2d74cb64aabd6c0714f702267cdc1c5"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:98-102 | src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:166-170 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py:98\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/db/migrations/versions/20250515-154426_a5a0703734e0_database_initialization.py"},"region":{"startLine":98}}}],"partialFingerprints":{"codehealthFindingId/v1":"cc196ed924f3ca036a637a59385f6d05bfa7185095c7090cbde99f4143002ee1"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (19 lines \u00D7 2): src/application/exceptions/oauth.py:12-30 | src/infrastructure/exceptions/repository.py:17-80 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/exceptions/oauth.py"},"region":{"startLine":12}}}],"partialFingerprints":{"codehealthFindingId/v1":"1beb3eb850c8be13a5ac2ad429978ce051a71f661597087287b421b2668f016a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7 lines \u00D7 2): src/infrastructure/repositories/role/role_repo.py:25-33 | src/infrastructure/repositories/user/user_writer.py:19-25 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/repositories/role/role_repo.py"},"region":{"startLine":25}}}],"partialFingerprints":{"codehealthFindingId/v1":"ae8a0cb5ac0cebdc87eb7769bbbfd7e86a4b5c75d2febebeedb81b731334d8b6"}},{"ruleId":"D13","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"5c6011bf23689eb4410031b4f125466b624e3e2cf43c375007c0c280cb5e8224"},"taxa":[{"id":"CWE-259","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-798","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A07:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}}]},{"ruleId":"D13","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"21bed71e4d290e9feaa82714e8a31b27f32b355e628c95ebeab8b473973a2906"},"taxa":[{"id":"CWE-259","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-798","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A07:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}}]},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/presentation/api/v1/auth/auth_router.py: src/presentation/api/v1/auth/auth_router.py changed 10 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is AuthController.register at line 103), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201Cfix: prevent dataclass from overriding BaseEntity hash methods\u201D; \u201CDocumentation update: CQRS schema fix, Service\u0027s descritption, Mermaid schemas for Presentation layer explanation.\u201D; \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/presentation/api/v1/auth/auth_router.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/presentation/api/v1/auth/auth_router.py"},"region":{"startLine":103}}}],"partialFingerprints":{"codehealthFindingId/v1":"4fea463295eeed1a329a0cebed6167b8b444745e340b42acb8aec76193d8a629"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/application/cqrs/cqrs_di_setup.py: src/application/cqrs/cqrs_di_setup.py changed 12 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is MediatorProvider.get_command_mediator at line 106), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D; \u201CAdded OAuth Github support. New commands and queries for permissions. New query for role. Little fixes.\u201D; \u201CRebuild OAuth system in progress. Added new model schema OAuth Account to connect with Our User. Added domain model with new Repository. Some new methods in UserReader. Rebuilded OAuthManager, but not tested yet. New command for register OAuth users. Some fixes...\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/application/cqrs/cqrs_di_setup.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/cqrs/cqrs_di_setup.py"},"region":{"startLine":106}}}],"partialFingerprints":{"codehealthFindingId/v1":"80bdbda270d77b2e73452c18f10ba64313fb3bf6f0e4839e6061ca058740f4fe"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/settings/config.py: src/settings/config.py changed 10 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is OAuthProvider.get_auth_url at line 21), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201Cfix: prevent dataclass from overriding BaseEntity hash methods\u201D; \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded OAuth Github support. New commands and queries for permissions. New query for role. Little fixes.\u201D; \u201CRebuild OAuth system in progress. Added new model schema OAuth Account to connect with Our User. Added domain model with new Repository. Some new methods in UserReader. Rebuilded OAuthManager, but not tested yet. New command for register OAuth users. Some fixes...\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/settings/config.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/settings/config.py"},"region":{"startLine":21}}}],"partialFingerprints":{"codehealthFindingId/v1":"04936ef22283eee6b651f9a545c07d1c0fc25453827cf24762553ca28b3bba11"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/presentation/api/main.py: src/presentation/api/main.py changed 8 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is main.create_app at line 23), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201Cfix: prevent dataclass from overriding BaseEntity hash methods\u201D; \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D; \u201CAdded OAuth Github support. New commands and queries for permissions. New query for role. Little fixes.\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/presentation/api/main.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/presentation/api/main.py"},"region":{"startLine":23}}}],"partialFingerprints":{"codehealthFindingId/v1":"0a5ba1ae1fc39775a3bbb788dc422ff9b2fe2dd74f27a360844687245f9ca6f4"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/domain/user/entity/user.py: src/domain/user/entity/user.py changed 7 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 4 (its worst body is User._set_jwt_user_data at line 51), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201Cfix: prevent dataclass from overriding BaseEntity hash methods\u201D; \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CRebuild OAuth system in progress. Added new model schema OAuth Account to connect with Our User. Added domain model with new Repository. Some new methods in UserReader. Rebuilded OAuthManager, but not tested yet. New command for register OAuth users. Some fixes...\u201D; \u201CAdded OAuth support. Added password reset to auth with email notification. Some fixes.\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/domain/user/entity/user.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/domain/user/entity/user.py"},"region":{"startLine":51}}}],"partialFingerprints":{"codehealthFindingId/v1":"12f880c61376a3378c5f721d17a26d6fd1d7305fabdebcc0473d5a378d0e94a0"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/application/services/security/jwt_di_setup.py: src/application/services/security/jwt_di_setup.py changed 7 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is JWTProvider.get_jwt_encoder at line 26), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded OAuth Github support. New commands and queries for permissions. New query for role. Little fixes.\u201D; \u201CRebuild OAuth system in progress. Added new model schema OAuth Account to connect with Our User. Added domain model with new Repository. Some new methods in UserReader. Rebuilded OAuthManager, but not tested yet. New command for register OAuth users. Some fixes...\u201D; \u201CAdded OAuth support. Added password reset to auth with email notification. Some fixes.\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/application/services/security/jwt_di_setup.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/services/security/jwt_di_setup.py"},"region":{"startLine":26}}}],"partialFingerprints":{"codehealthFindingId/v1":"312f6bae7f8b66b0670a53ead78242b9536a1f2bd25f305a117abdd390852033"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/infrastructure/repositories/user/user_reader.py: src/infrastructure/repositories/user/user_reader.py changed 8 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 3 (its worst body is UserReader.get_active_user_by_id at line 39), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CRebuild OAuth system in progress. Added new model schema OAuth Account to connect with Our User. Added domain model with new Repository. Some new methods in UserReader. Rebuilded OAuthManager, but not tested yet. New command for register OAuth users. Some fixes...\u201D; \u201CAdded OAuth support. Added password reset to auth with email notification. Some fixes.\u201D; \u201Cfix\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/infrastructure/repositories/user/user_reader.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/repositories/user/user_reader.py"},"region":{"startLine":39}}}],"partialFingerprints":{"codehealthFindingId/v1":"02ac3201f6805f9bf43bfcd4c3efd27a905840f7ece5ba410960cd4ea433d33c"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/application/dependency_injector/di.py: src/application/dependency_injector/di.py changed 7 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is SchedulerProvider.get_scheduler_provider at line 65), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded OAuth Github support. New commands and queries for permissions. New query for role. Little fixes.\u201D; \u201CRebuild OAuth system in progress. Added new model schema OAuth Account to connect with Our User. Added domain model with new Repository. Some new methods in UserReader. Rebuilded OAuthManager, but not tested yet. New command for register OAuth users. Some fixes...\u201D; \u201Cfix\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/application/dependency_injector/di.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/dependency_injector/di.py"},"region":{"startLine":65}}}],"partialFingerprints":{"codehealthFindingId/v1":"cfbc5b4f901770cf803d7d96c299b3b4bfe8305a4c4502a32dcc6164776de944"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/presentation/api/lifespan.py: src/presentation/api/lifespan.py changed 6 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is lifespan.init_message_broker at line 23), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201Cfix: prevent dataclass from overriding BaseEntity hash methods\u201D; \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded OAuth support. Added password reset to auth with email notification. Some fixes.\u201D; \u201Cfix\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/presentation/api/lifespan.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/presentation/api/lifespan.py"},"region":{"startLine":23}}}],"partialFingerprints":{"codehealthFindingId/v1":"e2602903a556bd84d853f33f6d3af02a23e6cf10ea22274c0d1c330c83c7c10e"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/application/services/security/jwt_manager.py: src/application/services/security/jwt_manager.py changed 6 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 8 (its worst body is JWTManager.validate_token at line 101), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D; \u201CAdded OAuth support. Added password reset to auth with email notification. Some fixes.\u201D; \u201CAdded grafana with alloy, loki and prometheus for metrics. Added role interactions with some fix issues.\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/application/services/security/jwt_manager.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/services/security/jwt_manager.py"},"region":{"startLine":101}}}],"partialFingerprints":{"codehealthFindingId/v1":"609b2fac4d98aa03fbe0548a6463748a1b10038a74ae5497e788792e77edd60b"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/infrastructure/repositories/session/session_repo.py: src/infrastructure/repositories/session/session_repo.py changed 6 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 2 (its worst body is SessionRepository.get_session_by_id at line 33), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D; \u201CRebuild OAuth system in progress. Added new model schema OAuth Account to connect with Our User. Added domain model with new Repository. Some new methods in UserReader. Rebuilded OAuthManager, but not tested yet. New command for register OAuth users. Some fixes...\u201D; \u201CAdded OAuth support. Added password reset to auth with email notification. Some fixes.\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/infrastructure/repositories/session/session_repo.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/repositories/session/session_repo.py"},"region":{"startLine":33}}}],"partialFingerprints":{"codehealthFindingId/v1":"aa7f44bcf1637e354e52ab483edb115ac86dcfbe61e7d371dac6d31b6efec463"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/domain/permission/values/permission_name.py: src/domain/permission/values/permission_name.py changed 5 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 2 (its worst body is PermissionName._validate at line 14), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201Cfix: prevent dataclass from overriding BaseEntity hash methods\u201D; \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D; \u201CAdded OAuth Github support. New commands and queries for permissions. New query for role. Little fixes.\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/domain/permission/values/permission_name.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/domain/permission/values/permission_name.py"},"region":{"startLine":14}}}],"partialFingerprints":{"codehealthFindingId/v1":"af2f3ab7b7bf151a97d870655e25eef943019c70be1e1b311bd64198b40cce29"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/application/services/rbac/rbac_manager.py: src/application/services/rbac/rbac_manager.py changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 5 (its worst body is RBACManager._validate_role_name at line 444), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D; \u201CAdded grafana with alloy, loki and prometheus for metrics. Added role interactions with some fix issues.\u201D; \u201Cfix\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/application/services/rbac/rbac_manager.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/services/rbac/rbac_manager.py"},"region":{"startLine":444}}}],"partialFingerprints":{"codehealthFindingId/v1":"74bd4dcd9c030caf9d6e78333f47fd67e1853007ee837d8dc6b1976d4b0d2164"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/application/services/security/oauth_manager.py: src/application/services/security/oauth_manager.py changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 7 (its worst body is OAuthManager._parse_generic_user_info at line 614), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D; \u201CAdded OAuth Github support. New commands and queries for permissions. New query for role. Little fixes.\u201D; \u201CRebuild OAuth system in progress. Added new model schema OAuth Account to connect with Our User. Added domain model with new Repository. Some new methods in UserReader. Rebuilded OAuthManager, but not tested yet. New command for register OAuth users. Some fixes...\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/application/services/security/oauth_manager.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/services/security/oauth_manager.py"},"region":{"startLine":614}}}],"partialFingerprints":{"codehealthFindingId/v1":"f8804e7bb4c6fc0ae4d0ded8ae6d6c04483456c6e792b4495ea866da4764511f"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/presentation/api/v1/auth/request/user.py: src/presentation/api/v1/auth/request/user.py changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 4 (its worst body is UserCreate.validate_names at line 26), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D; \u201CAdded OAuth support. Added password reset to auth with email notification. Some fixes.\u201D; \u201CFixed some docker container issues, added external network for kafka. Added some inrernal and external events. Some fixes on kafka consumer impl. Now, app can produce some events to kafka, but still some issues to read them. TBD -\u003E\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/presentation/api/v1/auth/request/user.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/presentation/api/v1/auth/request/user.py"},"region":{"startLine":26}}}],"partialFingerprints":{"codehealthFindingId/v1":"0101149e6bae20ce6eb76211b3b8461f2833f8d05064481b2112b7798d88c263"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/domain/role/entity/role.py: src/domain/role/entity/role.py changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is Role.permission at line 16), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201Cfix: prevent dataclass from overriding BaseEntity hash methods\u201D; \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CRebuild OAuth system in progress. Added new model schema OAuth Account to connect with Our User. Added domain model with new Repository. Some new methods in UserReader. Rebuilded OAuthManager, but not tested yet. New command for register OAuth users. Some fixes...\u201D; \u201Cfix\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/domain/role/entity/role.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/domain/role/entity/role.py"},"region":{"startLine":16}}}],"partialFingerprints":{"codehealthFindingId/v1":"3486a1672326b2f582e006d0324958afcb80b820b620789a5e6b40f3dc993925"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/application/services/tasks/notification_manager.py: src/application/services/tasks/notification_manager.py changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 8 (its worst body is NotificationManager.send_notification at line 130), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CDocumentation update: CQRS schema fix, Service\u0027s descritption, Mermaid schemas for Presentation layer explanation.\u201D; \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D; \u201CAdded OAuth support. Added password reset to auth with email notification. Some fixes.\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/application/services/tasks/notification_manager.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/services/tasks/notification_manager.py"},"region":{"startLine":130}}}],"partialFingerprints":{"codehealthFindingId/v1":"693eca678385ed7aec1cda0404682e7e5ff64a26dc1068d2c07d6be172613c9b"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/application/exceptions/jwt.py: src/application/exceptions/jwt.py changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is AccessRejectedException.message at line 23), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CRebuild OAuth system in progress. Added new model schema OAuth Account to connect with Our User. Added domain model with new Repository. Some new methods in UserReader. Rebuilded OAuthManager, but not tested yet. New command for register OAuth users. Some fixes...\u201D; \u201CAdded grafana with alloy, loki and prometheus for metrics. Added role interactions with some fix issues.\u201D; \u201Cfix\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/application/exceptions/jwt.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/exceptions/jwt.py"},"region":{"startLine":23}}}],"partialFingerprints":{"codehealthFindingId/v1":"a4196d390e2751e5d2bbe25a1b188cf464770c2b212314969308d166e3137948"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/application/exceptions/rbac.py: src/application/exceptions/rbac.py changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is RoleAlreadyExistsException.message at line 22), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D; \u201CAdded grafana with alloy, loki and prometheus for metrics. Added role interactions with some fix issues.\u201D; \u201Cfix\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/application/exceptions/rbac.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/exceptions/rbac.py"},"region":{"startLine":22}}}],"partialFingerprints":{"codehealthFindingId/v1":"3e5e13de3fa75e9665a3b70cda69aee5e28901ef1f717ff4a7d791bbb290da37"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/application/services/session/session_manager.py: src/application/services/session/session_manager.py changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 2 (its worst body is SessionManager.get_or_create_session at line 29), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D; \u201CAdded OAuth support. Added password reset to auth with email notification. Some fixes.\u201D; \u201Cfix\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/application/services/session/session_manager.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/services/session/session_manager.py"},"region":{"startLine":29}}}],"partialFingerprints":{"codehealthFindingId/v1":"6c455e1edfc9e792bdfd0d667b882be9ff03599c037a04ca4753b59e846a5b60"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/infrastructure/repositories/role/role_repo.py: src/infrastructure/repositories/role/role_repo.py changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 2 (its worst body is RoleRepository.get_role_by_id at line 42), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded OAuth Github support. New commands and queries for permissions. New query for role. Little fixes.\u201D; \u201Cfix\u201D; \u201CFixed some docker container issues, added external network for kafka. Added some inrernal and external events. Some fixes on kafka consumer impl. Now, app can produce some events to kafka, but still some issues to read them. TBD -\u003E\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/infrastructure/repositories/role/role_repo.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/repositories/role/role_repo.py"},"region":{"startLine":42}}}],"partialFingerprints":{"codehealthFindingId/v1":"0964cbe3ec740b1053b5c4eecb9178372067f8ac0604d1b14716a80065cbc88a"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/infrastructure/repositories/token/redis_repo.py: src/infrastructure/repositories/token/redis_repo.py changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 2 (its worst body is RedisRepository.set at line 16), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded OAuth support. Added password reset to auth with email notification. Some fixes.\u201D; \u201CAdded grafana with alloy, loki and prometheus for metrics. Added role interactions with some fix issues.\u201D; \u201CFixed some docker container issues, added external network for kafka. Added some inrernal and external events. Some fixes on kafka consumer impl. Now, app can produce some events to kafka, but still some issues to read them. TBD -\u003E\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/infrastructure/repositories/token/redis_repo.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/repositories/token/redis_repo.py"},"region":{"startLine":16}}}],"partialFingerprints":{"codehealthFindingId/v1":"f65c81ae0b31c4f747a78ea50d1b9eb691aae0b4a819487f5beb746adde53a2c"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/presentation/api/v1/roles/rbac_router.py: src/presentation/api/v1/roles/rbac_router.py changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 4 (its worst body is RoleController.partial_update_role at line 232), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded OAuth Github support. New commands and queries for permissions. New query for role. Little fixes.\u201D; \u201CAdded grafana with alloy, loki and prometheus for metrics. Added role interactions with some fix issues.\u201D; \u201Cfix\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/presentation/api/v1/roles/rbac_router.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/presentation/api/v1/roles/rbac_router.py"},"region":{"startLine":232}}}],"partialFingerprints":{"codehealthFindingId/v1":"5047f940889e52f5948375e4d0bea1205dc18faf33f0cb8039368e1b9161fd3d"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/application/base/security/jwt_payload.py: src/application/base/security/jwt_payload.py changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is BaseJWTPayloadGenerator.generate at line 18), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201Cfix: prevent dataclass from overriding BaseEntity hash methods\u201D; \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D; \u201CFixed some docker container issues, added external network for kafka. Added some inrernal and external events. Some fixes on kafka consumer impl. Now, app can produce some events to kafka, but still some issues to read them. TBD -\u003E\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/application/base/security/jwt_payload.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/base/security/jwt_payload.py"},"region":{"startLine":18}}}],"partialFingerprints":{"codehealthFindingId/v1":"40c9957e21d1a772bbed697ce33c8ff4f5cf56128b6128c003576b1ff408ebaf"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/domain/session/entity/session.py: src/domain/session/entity/session.py changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 2 (its worst body is Session.terminate at line 21), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201Cfix: prevent dataclass from overriding BaseEntity hash methods\u201D; \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CRebuild OAuth system in progress. Added new model schema OAuth Account to connect with Our User. Added domain model with new Repository. Some new methods in UserReader. Rebuilded OAuthManager, but not tested yet. New command for register OAuth users. Some fixes...\u201D; \u201CFixed some docker container issues, added external network for kafka. Added some inrernal and external events. Some fixes on kafka consumer impl. Now, app can produce some events to kafka, but still some issues to read them. TBD -\u003E\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/domain/session/entity/session.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/domain/session/entity/session.py"},"region":{"startLine":21}}}],"partialFingerprints":{"codehealthFindingId/v1":"753d92a47740d8f6493f934a4158ce0d21d2412805c5305c3548e72cbd2c1470"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/application/base/security/jwt_user.py: src/application/base/security/jwt_user.py changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is JWTUserInterface.create_from_domain_user at line 16), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D; \u201Cfix\u201D; \u201CFixed some docker container issues, added external network for kafka. Added some inrernal and external events. Some fixes on kafka consumer impl. Now, app can produce some events to kafka, but still some issues to read them. TBD -\u003E\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/application/base/security/jwt_user.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/base/security/jwt_user.py"},"region":{"startLine":16}}}],"partialFingerprints":{"codehealthFindingId/v1":"578edcb9c55235bbbe7ee76dc55a27de2f71f07a666bedd00473bae17acb0402"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/application/services/rbac/rbac_di_setup.py: src/application/services/rbac/rbac_di_setup.py changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is RBACProvider.get_rbac_manager at line 14), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D; \u201CAdded grafana with alloy, loki and prometheus for metrics. Added role interactions with some fix issues.\u201D; \u201Cfix\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/application/services/rbac/rbac_di_setup.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/services/rbac/rbac_di_setup.py"},"region":{"startLine":14}}}],"partialFingerprints":{"codehealthFindingId/v1":"f77f8ab642e69670603f9b04d6198417d7e9801cde7d47b3bc2964607b0fac61"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/infrastructure/base/repository/role_repo.py: src/infrastructure/base/repository/role_repo.py changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is BaseRoleRepository.create_role at line 14), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded OAuth Github support. New commands and queries for permissions. New query for role. Little fixes.\u201D; \u201Cfix\u201D; \u201CFixed some docker container issues, added external network for kafka. Added some inrernal and external events. Some fixes on kafka consumer impl. Now, app can produce some events to kafka, but still some issues to read them. TBD -\u003E\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/infrastructure/base/repository/role_repo.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/base/repository/role_repo.py"},"region":{"startLine":14}}}],"partialFingerprints":{"codehealthFindingId/v1":"c19cebca183922537a7c8bbda591843f83928a1fb14e6258d00aa7bbffca617c"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/infrastructure/repositories/converters.py: src/infrastructure/repositories/converters.py changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 7 (its worst body is OrmToDomainConverter.user_to_domain at line 18), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CRebuild OAuth system in progress. Added new model schema OAuth Account to connect with Our User. Added domain model with new Repository. Some new methods in UserReader. Rebuilded OAuthManager, but not tested yet. New command for register OAuth users. Some fixes...\u201D; \u201Cfix\u201D; \u201CFixed some docker container issues, added external network for kafka. Added some inrernal and external events. Some fixes on kafka consumer impl. Now, app can produce some events to kafka, but still some issues to read them. TBD -\u003E\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/infrastructure/repositories/converters.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/repositories/converters.py"},"region":{"startLine":18}}}],"partialFingerprints":{"codehealthFindingId/v1":"be11a47ecb28ecab358c34bbebd17bc3435616ba55de5136a422f27f99daedb1"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/presentation/api/v1/roles/response/role.py: src/presentation/api/v1/roles/response/role.py changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is CreatedRoleResponseSchema.from_entity at line 16), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded OAuth Github support. New commands and queries for permissions. New query for role. Little fixes.\u201D; \u201CAdded grafana with alloy, loki and prometheus for metrics. Added role interactions with some fix issues.\u201D; \u201Cfix\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/presentation/api/v1/roles/response/role.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/presentation/api/v1/roles/response/role.py"},"region":{"startLine":16}}}],"partialFingerprints":{"codehealthFindingId/v1":"52b06c8832ea9459bae1069cddd4ae07d6ee87662969e1a7a011d07ac0228b42"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/application/cqrs/user/commands/login_user.py: src/application/cqrs/user/commands/login_user.py changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 2 (its worst body is LoginUserCommandHandler.handle at line 33), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded OAuth support. Added password reset to auth with email notification. Some fixes.\u201D; \u201Cfix\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/application/cqrs/user/commands/login_user.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/cqrs/user/commands/login_user.py"},"region":{"startLine":33}}}],"partialFingerprints":{"codehealthFindingId/v1":"8703e7477502711e9ac560121f6e0f508fa96d78e58c76fe03b9349b9c788d2d"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/application/exceptions/user.py: src/application/exceptions/user.py changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is UsernameAlreadyExistsException.message at line 12), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded OAuth support. Added password reset to auth with email notification. Some fixes.\u201D; \u201CFixed some docker container issues, added external network for kafka. Added some inrernal and external events. Some fixes on kafka consumer impl. Now, app can produce some events to kafka, but still some issues to read them. TBD -\u003E\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/application/exceptions/user.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/exceptions/user.py"},"region":{"startLine":12}}}],"partialFingerprints":{"codehealthFindingId/v1":"7d3c9a9688aeea8efc7e4540557b4ee21eabbf91e1e1477d56ebf09ab7bc93c2"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/application/services/security/jwt_payload_generator.py: src/application/services/security/jwt_payload_generator.py changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 3 (its worst body is JWTPayloadGenerator.generate at line 29), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D; \u201Cfix\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/application/services/security/jwt_payload_generator.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/services/security/jwt_payload_generator.py"},"region":{"startLine":29}}}],"partialFingerprints":{"codehealthFindingId/v1":"ded97b73d7b6228df45582b9d72141c8a89ced8d4a508cf739fc6aef49caf722"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/presentation/api/v1/auth/oauth_router.py: src/presentation/api/v1/auth/oauth_router.py changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 2 (its worst body is OAuthController.oauth_callback at line 228), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D; \u201CRebuild OAuth system in progress. Added new model schema OAuth Account to connect with Our User. Added domain model with new Repository. Some new methods in UserReader. Rebuilded OAuthManager, but not tested yet. New command for register OAuth users. Some fixes...\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/presentation/api/v1/auth/oauth_router.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/presentation/api/v1/auth/oauth_router.py"},"region":{"startLine":228}}}],"partialFingerprints":{"codehealthFindingId/v1":"05825401174b5605ae17fc15103235931e486cd9ca35d532fb96676a05e3a241"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/application/base/mediator/query.py: src/application/base/mediator/query.py changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is BaseQueryMediator.register_query at line 23), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201Cfix: prevent dataclass from overriding BaseEntity hash methods\u201D; \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CFixed some docker container issues, added external network for kafka. Added some inrernal and external events. Some fixes on kafka consumer impl. Now, app can produce some events to kafka, but still some issues to read them. TBD -\u003E\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/application/base/mediator/query.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/base/mediator/query.py"},"region":{"startLine":23}}}],"partialFingerprints":{"codehealthFindingId/v1":"018d23729286c96512af324f2ab04ef21de20bb7d52abe13e65957c544199f3e"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/application/cqrs/user/commands/add_oauth_account_request.py: src/application/cqrs/user/commands/add_oauth_account_request.py changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is AddOAuthAccountRequestCommandHandler.handle at line 28), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D; \u201CAdded OAuth Github support. New commands and queries for permissions. New query for role. Little fixes.\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/application/cqrs/user/commands/add_oauth_account_request.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/cqrs/user/commands/add_oauth_account_request.py"},"region":{"startLine":28}}}],"partialFingerprints":{"codehealthFindingId/v1":"256918929f2bb13fa2efead777ab1625a24a82c4ff000c1d5d2c811cf2fc4d47"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/application/services/security/security_user.py: src/application/services/security/security_user.py changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is SecurityUser.create_from_domain_user at line 35), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D; \u201Cfix\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/application/services/security/security_user.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/services/security/security_user.py"},"region":{"startLine":35}}}],"partialFingerprints":{"codehealthFindingId/v1":"13099e78771dd1cca54429633a9b986fcc3688fa6f412b938548c85561ee398c"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/application/services/tasks/celery.py: src/application/services/tasks/celery.py changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 2 (its worst body is celery.send_user_registration_notification at line 43), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D; \u201CAdded OAuth support. Added password reset to auth with email notification. Some fixes.\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/application/services/tasks/celery.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/services/tasks/celery.py"},"region":{"startLine":43}}}],"partialFingerprints":{"codehealthFindingId/v1":"0371b7cbd29377a69d2f3d682f76c38249c6cd38748dca71cd3dd53cfa9ac2f5"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/infrastructure/exceptions/repository.py: src/infrastructure/exceptions/repository.py changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is UserDoesNotExistException.message at line 16), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CRebuild OAuth system in progress. Added new model schema OAuth Account to connect with Our User. Added domain model with new Repository. Some new methods in UserReader. Rebuilded OAuthManager, but not tested yet. New command for register OAuth users. Some fixes...\u201D; \u201Cfix\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/infrastructure/exceptions/repository.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/exceptions/repository.py"},"region":{"startLine":16}}}],"partialFingerprints":{"codehealthFindingId/v1":"eb705a53c43f92142a0baaf382c6c65c56bc50628fce89fe6cc05eb561c22c21"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/infrastructure/message_broker/kafka_consumer.py: src/infrastructure/message_broker/kafka_consumer.py changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 6 (its worst body is AsyncKafkaConsumer.start_consuming at line 34), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201Cfix\u201D; \u201CFixed some docker container issues, added external network for kafka. Added some inrernal and external events. Some fixes on kafka consumer impl. Now, app can produce some events to kafka, but still some issues to read them. TBD -\u003E\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/infrastructure/message_broker/kafka_consumer.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/message_broker/kafka_consumer.py"},"region":{"startLine":34}}}],"partialFingerprints":{"codehealthFindingId/v1":"780e043f3fd408ae17f8f7ff5fffd8cb94e351edd13f616266ab40411fa862ec"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/infrastructure/repositories/permission/permission_repo.py: src/infrastructure/repositories/permission/permission_repo.py changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 2 (its worst body is PermissionRepository.get_permission_by_id at line 37), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded OAuth Github support. New commands and queries for permissions. New query for role. Little fixes.\u201D; \u201Cfix\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/infrastructure/repositories/permission/permission_repo.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/repositories/permission/permission_repo.py"},"region":{"startLine":37}}}],"partialFingerprints":{"codehealthFindingId/v1":"6a1f566b6e3a26fb37caa78eaf4ec3ceba754f808047446c915f45b8860a0b36"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/infrastructure/repositories/user/user_writer.py: src/infrastructure/repositories/user/user_writer.py changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 2 (its worst body is UserWriter.check_if_field_exists at line 35), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded grafana with alloy, loki and prometheus for metrics. Added role interactions with some fix issues.\u201D; \u201CFixed some docker container issues, added external network for kafka. Added some inrernal and external events. Some fixes on kafka consumer impl. Now, app can produce some events to kafka, but still some issues to read them. TBD -\u003E\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/infrastructure/repositories/user/user_writer.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/repositories/user/user_writer.py"},"region":{"startLine":35}}}],"partialFingerprints":{"codehealthFindingId/v1":"48c31a29e8ce201cefdfdce1f613a13bb47b050e6f9ff242add734d2415a72db"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/presentation/api/v1/users/user_router.py: src/presentation/api/v1/users/user_router.py changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is UserController.get_user_by_id at line 54), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D; \u201CAdded grafana with alloy, loki and prometheus for metrics. Added role interactions with some fix issues.\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/presentation/api/v1/users/user_router.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/presentation/api/v1/users/user_router.py"},"region":{"startLine":54}}}],"partialFingerprints":{"codehealthFindingId/v1":"01b2c400575d47ba562054095c8d5a4eab290956c2bed9e47983435f77f8e008"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/domain/role/values/role_name.py: src/domain/role/values/role_name.py changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 2 (its worst body is RoleName._validate at line 14), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201Cfix: prevent dataclass from overriding BaseEntity hash methods\u201D; \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/domain/role/values/role_name.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/domain/role/values/role_name.py"},"region":{"startLine":14}}}],"partialFingerprints":{"codehealthFindingId/v1":"d538fa72f850c3c4e993a4fb49bb2ed7bf7c0ae028cc0070a6d31c39f94a04f0"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/application/services/tasks/task_di_setup.py: src/application/services/tasks/task_di_setup.py changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is NotificationManagerProvider.get_notification_manager at line 9), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CDocumentation update: CQRS schema fix, Service\u0027s descritption, Mermaid schemas for Presentation layer explanation.\u201D; \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded OAuth support. Added password reset to auth with email notification. Some fixes.\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/application/services/tasks/task_di_setup.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/services/tasks/task_di_setup.py"},"region":{"startLine":9}}}],"partialFingerprints":{"codehealthFindingId/v1":"161dc7ab698be3ccff66c5d9e879799b24c5eea77c9cd5c578ff55fe5e9e32da"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/application/base/security/cookie_manager.py: src/application/base/security/cookie_manager.py changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is BaseCookieManager.set_cookie at line 18), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D; \u201CFixed some docker container issues, added external network for kafka. Added some inrernal and external events. Some fixes on kafka consumer impl. Now, app can produce some events to kafka, but still some issues to read them. TBD -\u003E\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/application/base/security/cookie_manager.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/base/security/cookie_manager.py"},"region":{"startLine":18}}}],"partialFingerprints":{"codehealthFindingId/v1":"931f072f91b59e83f7bb1a1e4a995ed0e8084c09dea9f58fbb94b7daa89defaa"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/application/base/security/jwt_encoder.py: src/application/base/security/jwt_encoder.py changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is BaseJWTEncoder.encode at line 16), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D; \u201CFixed some docker container issues, added external network for kafka. Added some inrernal and external events. Some fixes on kafka consumer impl. Now, app can produce some events to kafka, but still some issues to read them. TBD -\u003E\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/application/base/security/jwt_encoder.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/base/security/jwt_encoder.py"},"region":{"startLine":16}}}],"partialFingerprints":{"codehealthFindingId/v1":"005f58f22979485f5e7cb1e444d857ab6012db948e1ce8bd3f1bdfaa4e0706e1"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/application/base/session/session_manager.py: src/application/base/session/session_manager.py changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is BaseSessionManager.get_or_create_session at line 17), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded new queries for current user. Added documentation for currently existing services. Found and Fixed some bugs.\u201D; \u201CFixed some docker container issues, added external network for kafka. Added some inrernal and external events. Some fixes on kafka consumer impl. Now, app can produce some events to kafka, but still some issues to read them. TBD -\u003E\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/application/base/session/session_manager.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/application/base/session/session_manager.py"},"region":{"startLine":17}}}],"partialFingerprints":{"codehealthFindingId/v1":"3d56f9d45726321bc57cf43ff642104f24dee57ded4b65b25d6556e08f9a2da5"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/domain/base/entity/base.py: src/domain/base/entity/base.py changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 2 (its worst body is BaseEntity.__eq__ at line 19), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CRebuild OAuth system in progress. Added new model schema OAuth Account to connect with Our User. Added domain model with new Repository. Some new methods in UserReader. Rebuilded OAuthManager, but not tested yet. New command for register OAuth users. Some fixes...\u201D; \u201CFixed some docker container issues, added external network for kafka. Added some inrernal and external events. Some fixes on kafka consumer impl. Now, app can produce some events to kafka, but still some issues to read them. TBD -\u003E\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/domain/base/entity/base.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/domain/base/entity/base.py"},"region":{"startLine":19}}}],"partialFingerprints":{"codehealthFindingId/v1":"ffcae013d82655e91bd4ee656bbb78ada3ee624b1aaf2d3414d137cf0d36fb01"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/domain/permission/entity/permission_catalog.py: src/domain/permission/entity/permission_catalog.py changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is PermissionEnum.get_all_permissions at line 58), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded grafana with alloy, loki and prometheus for metrics. Added role interactions with some fix issues.\u201D; \u201Cfix\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/domain/permission/entity/permission_catalog.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/domain/permission/entity/permission_catalog.py"},"region":{"startLine":58}}}],"partialFingerprints":{"codehealthFindingId/v1":"329a57e55eb61530809b4b44eaf64620315229f1ccb868a860622fc8c73a4d4d"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/domain/role/entity/role_catalog.py: src/domain/role/entity/role_catalog.py changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is SystemRoles.get_all_roles at line 131), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded grafana with alloy, loki and prometheus for metrics. Added role interactions with some fix issues.\u201D; \u201Cfix\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/domain/role/entity/role_catalog.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/domain/role/entity/role_catalog.py"},"region":{"startLine":131}}}],"partialFingerprints":{"codehealthFindingId/v1":"65b1178be33d970669726ca04f2436a8ac647680dcfdb3cfd7b5c5f32090358b"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/domain/session/values/device_info.py: src/domain/session/values/device_info.py changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is DeviceInfo.create at line 18), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded OAuth support. Added password reset to auth with email notification. Some fixes.\u201D; \u201CFixed some docker container issues, added external network for kafka. Added some inrernal and external events. Some fixes on kafka consumer impl. Now, app can produce some events to kafka, but still some issues to read them. TBD -\u003E\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/domain/session/values/device_info.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/domain/session/values/device_info.py"},"region":{"startLine":18}}}],"partialFingerprints":{"codehealthFindingId/v1":"0d4d9c71dde493a82249d69c4f28c1dc9fb0edbaa1530861a735117e4748cb14"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/infrastructure/base/repository/permission_repo.py: src/infrastructure/base/repository/permission_repo.py changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 1 (its worst body is BasePermissionRepository.create_permission at line 14), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201CAdded OAuth Github support. New commands and queries for permissions. New query for role. Little fixes.\u201D; \u201Cfix\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/infrastructure/base/repository/permission_repo.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/base/repository/permission_repo.py"},"region":{"startLine":14}}}],"partialFingerprints":{"codehealthFindingId/v1":"63cdc551a07d072f43346e15464d586b1577227d9b935efd11101e89eea082c9"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/infrastructure/message_broker/kafka_producer.py: src/infrastructure/message_broker/kafka_producer.py changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 2 (its worst body is AsyncKafkaProducer.is_connected at line 28), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201Cfix\u201D; \u201CFixed some docker container issues, added external network for kafka. Added some inrernal and external events. Some fixes on kafka consumer impl. Now, app can produce some events to kafka, but still some issues to read them. TBD -\u003E\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/infrastructure/message_broker/kafka_producer.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/message_broker/kafka_producer.py"},"region":{"startLine":28}}}],"partialFingerprints":{"codehealthFindingId/v1":"b3decbd1dcfb127b499ef2b379c2085c6379a89d4ab80cda497826aca6fb4eb2"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: src/presentation/api/base_role_permissions_setup.py: src/presentation/api/base_role_permissions_setup.py changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 5 (its worst body is base_role_permissions_setup.seed_roles_and_permissions at line 15), UNDER the 15 threshold, so this is deliberately not filed as a churn \u00D7 complexity hotspot \u2014 the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: \u201CAdded ruff support. Naming fixes. Type fixes. Domain changes: ValueObject revorked, Entity changes. Application: now decorator authorization_required in helpers.py. Added README.md, but not finished.\u201D; \u201Cfix\u201D; \u201CFixed some docker container issues, added external network for kafka. Added some inrernal and external events. Some fixes on kafka consumer impl. Now, app can produce some events to kafka, but still some issues to read them. TBD -\u003E\u201D. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2025-02-14..2025-05-15, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-02-14 17:08:48 \u002B03:00\u0027 --until=\u00272025-05-15 17:08:48 \u002B03:00\u0027 --full-history --no-merges -- src/presentation/api/base_role_permissions_setup.py\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/presentation/api/base_role_permissions_setup.py"},"region":{"startLine":15}}}],"partialFingerprints":{"codehealthFindingId/v1":"34737d6b147160200a8a8cba43a2291c19697b21d86804f340f1fb652173e0ce"}},{"ruleId":"D26","level":"note","message":{"text":"Projects may be oversized for their cohesion: 1 of 2 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is \u0060(repository root)\u0060 (10827 LoC, 330 module-visible types across 75 directories). Review these for cohesion \u2014 draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"d5a94650dc74886a0f1f08eb9fb6775f1fc395279ef7e901c970c9d26f767a72"}},{"ruleId":"D29","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"193c8ffe44f72f65363b8500486c5fd2d2670faf59d822a2ce35e080398fdd46"},"taxa":[{"id":"CWE-502","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A08:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}}]},{"ruleId":"D29","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"eb3594cfb6dc5c174243073de9f20da9991fe9342b13f340e2a86a29dccd6112"},"taxa":[{"id":"CWE-502","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A08:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}}]},{"ruleId":"D29","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"06d2d21f27cffd417ec16e8f5f105d3fb5dd40884a66aa22484c6faac01a7596"},"taxa":[{"id":"CWE-502","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A08:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}}]},{"ruleId":"D29","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"416b0a3c2d23526ce99e441922ddbb398d30825ab88c75e3e6fdb6e107e0a043"},"taxa":[{"id":"CWE-502","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A08:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}}]},{"ruleId":"D29","level":"note","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"77b830ca43fc72d59bbde11864503a12dc2a7ecd9c90d0c66da3d833970a8a04"},"taxa":[{"id":"CWE-89","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A05:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}}]},{"ruleId":"D29","level":"note","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"25cc4ddb28490e022347d9d04f086bb16dabf2f234241567a4fe842f3c5a97b5"},"taxa":[{"id":"CWE-89","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A05:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}}]},{"ruleId":"D30","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"87ff0780b47113b696de6d40de76eec1019df78c8fc3e94f47ec747c2a467827"},"properties":{"dependency":{"package":"python-jose","version":"3.4.0","advisory":"[GHSA redacted]","aliases":["[CVE redacted]","[CVE redacted]","[GHSA redacted]","PYSEC-2024-232","PYSEC-2026-4298"],"reachability":{"kind":"production","file":"src/application/services/security/jwt_encoder.py","line":4}}}},{"ruleId":"D30","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"d546733b9ca45c1bd162da0b0b01ea42af530b6ed35676e28a14281b1424acd0"},"properties":{"dependency":{"package":"anyio","version":"4.9.0","advisory":"[GHSA redacted]","aliases":["[CVE redacted]","[CVE redacted]","[GHSA redacted]","PYSEC-2026-4024","PYSEC-2026-4025"],"reachability":{"kind":"not-imported"}}}},{"ruleId":"D30","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"8e57c8943213f2e598c35e19da95198d5c71d6429e194fad6ca964d78c444813"},"properties":{"dependency":{"package":"h11","version":"0.14.0","advisory":"[GHSA redacted]","aliases":["[CVE redacted]","PYSEC-2026-348"],"reachability":{"kind":"not-imported"}}}},{"ruleId":"D30","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"c39221e7a57c94c8668f293a52beb2217070a9b1a940bee5edd4b6b0b226af4b"},"properties":{"dependency":{"package":"certifi","version":"2025.1.31","advisory":"[GHSA redacted]","aliases":["PYSEC-2026-4320"],"reachability":{"kind":"not-imported"}}}},{"ruleId":"D30","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"e443c1e4129883bf08453ce21f8ad8383aa1bc20ef394ef57a6c82433508e37e"},"properties":{"dependency":{"package":"mako","version":"1.3.10","advisory":"[GHSA redacted]","aliases":["[CVE redacted]","[CVE redacted]","[CVE redacted]","[GHSA redacted]","[GHSA redacted]","PYSEC-2026-2617","PYSEC-2026-4243","PYSEC-2026-88"],"reachability":{"kind":"not-imported"}}}},{"ruleId":"D30","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"308f94f147b4ae554262cb31ebf3caf690a0cc1507dfa6a080fac00573a98e86"},"properties":{"dependency":{"package":"kafka-python","version":"2.1.5","advisory":"[GHSA redacted]","aliases":["[CVE redacted]","[CVE redacted]","[GHSA redacted]","PYSEC-2026-2190","PYSEC-2026-2191"],"reachability":{"kind":"unknown"}}}},{"ruleId":"D30","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"5102fe556f3399b622dcd81c118f7d1308c1374fbd00ede44c01babfc78c0a23"},"properties":{"dependency":{"package":"pyasn1","version":"0.4.8","advisory":"[GHSA redacted]","aliases":["[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","PYSEC-2026-2263","PYSEC-2026-3455","PYSEC-2026-3456","PYSEC-2026-3457"],"reachability":{"kind":"not-imported"}}}},{"ruleId":"D30","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"64c75a3299a9a190872f0b607fb5f4a2eec4880c08479c856652bbb6b93bd391"},"properties":{"dependency":{"package":"urllib3","version":"2.4.0","advisory":"[GHSA redacted]","aliases":["[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","PYSEC-2026-141","PYSEC-2026-1994","PYSEC-2026-1996","PYSEC-2026-1997","PYSEC-2026-1998","PYSEC-2026-1999","PYSEC-2026-4175","PYSEC-2026-4177"],"reachability":{"kind":"not-imported"}}}},{"ruleId":"D30","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"1bbb737d164fd8f211f53e1320e9ff1fc4666d40e3304fe466bba8607ec90ef3"},"properties":{"dependency":{"package":"black","version":"25.1.0","advisory":"[GHSA redacted]","aliases":["[CVE redacted]","[CVE redacted]","[CVE redacted]","[GHSA redacted]","[GHSA redacted]","PYSEC-2026-2120","PYSEC-2026-2121"],"reachability":{"kind":"unknown"}}}},{"ruleId":"D30","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"54b704e3373844688e7ce78b4ac7e30ce5b7e900fbe85efb3def08aafd17053b"},"properties":{"dependency":{"package":"tornado","version":"6.4.2","advisory":"[GHSA redacted]","aliases":["[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","PYSEC-2025-265","PYSEC-2025-266","PYSEC-2025-267","PYSEC-2026-140","PYSEC-2026-1974","PYSEC-2026-2287","PYSEC-2026-3387","PYSEC-2026-3388","PYSEC-2026-3389","PYSEC-2026-3928"],"reachability":{"kind":"not-imported"}}}},{"ruleId":"D30","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"4d55eb5e10fbe2eebac3cecc6f1c6c6c29fa6ca98a738924e23ab582305d2b6f"},"properties":{"dependency":{"package":"dnspython","version":"2.7.0","advisory":"[GHSA redacted]","aliases":["[CVE redacted]"],"reachability":{"kind":"not-imported"}}}},{"ruleId":"D30","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"41ad6f68cdf9ea113ce29dd2cd71ff041492ad89af71ef020b10c3cca836a50e"},"properties":{"dependency":{"package":"litestar","version":"2.15.1","advisory":"[GHSA redacted]","aliases":["[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","PYSEC-2026-2195","PYSEC-2026-2196","PYSEC-2026-2197","PYSEC-2026-2603","PYSEC-2026-2604"],"reachability":{"kind":"production","file":"src/presentation/api/exception_configuration.py","line":7}}}},{"ruleId":"D30","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"908c75fb62999ae42bccfe1163828c744ce3a0789ef67cdc74f0dbd5e7ceaa59"},"properties":{"dependency":{"package":"orjson","version":"3.10.15","advisory":"[GHSA redacted]","aliases":["[CVE redacted]","PYSEC-2026-107"],"reachability":{"kind":"production","file":"src/application/services/security/security_user.py","line":4}}}},{"ruleId":"D30","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"87d4db8c203b5e34f2b0fb9b4c3c87940bcbddcaf7defe76d0817a2235a5f8ac"},"properties":{"dependency":{"package":"multipart","version":"1.2.1","advisory":"[GHSA redacted]","aliases":["[CVE redacted]","PYSEC-2026-2670"],"reachability":{"kind":"unknown"}}}},{"ruleId":"D30","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"f6e4e3e7dfa2fced3008ddd64c93e5ac19634e1d95f3be6a06c516a7583bb258"},"properties":{"dependency":{"package":"ecdsa","version":"0.19.1","advisory":"[GHSA redacted]","aliases":["[CVE redacted]","[CVE redacted]","[GHSA redacted]","PYSEC-2026-1325","PYSEC-2026-2467"],"reachability":{"kind":"unknown"}}}},{"ruleId":"D30","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"27e162474dde2c9361a105b038933373cd874345b54fa8c92f26cb908472d9c6"},"properties":{"dependency":{"package":"cryptography","version":"44.0.2","advisory":"[GHSA redacted]","aliases":["[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[CVE redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","PYSEC-2026-2141","PYSEC-2026-35","PYSEC-2026-3552","PYSEC-2026-3553","PYSEC-2026-3554"],"reachability":{"kind":"not-imported"}}}},{"ruleId":"D30","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"0edbe0c20f21720d5285b2663177b2e3ab8c055b3130ca092c57460fd8d8174a"},"properties":{"dependency":{"package":"idna","version":"3.10","advisory":"[GHSA redacted]","aliases":["[CVE redacted]","PYSEC-2026-215"],"reachability":{"kind":"not-imported"}}}},{"ruleId":"D30","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"d0e6a57015dc23cfdd8374d0bc7df076eac4b337374fa23d10cb0ae918b0187d"},"properties":{"dependency":{"package":"pytest","version":"8.3.5","advisory":"[GHSA redacted]","aliases":["[CVE redacted]","PYSEC-2026-1845"],"reachability":{"kind":"test-or-tooling","file":"tests/conftest.py","line":3}}}},{"ruleId":"D30","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"9300387b7d5f3c552f43a162e198349c13ada8ea4ea972b22bbf175a9e015bfe"},"properties":{"dependency":{"package":"requests","version":"2.32.3","advisory":"[GHSA redacted]","aliases":["[CVE redacted]","[CVE redacted]","[GHSA redacted]","PYSEC-2026-1872","PYSEC-2026-2275"],"reachability":{"kind":"production","file":"src/application/services/security/oauth_manager.py","line":7}}}},{"ruleId":"D30","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"f35bcb5a3b582c92e6a7d51caec3ab2557cbdd9baaad1832ae7151bb7deb455e"},"properties":{"dependency":{"package":"python-dotenv","version":"1.0.1","advisory":"[GHSA redacted]","aliases":["[CVE redacted]","PYSEC-2026-2270"],"reachability":{"kind":"unknown"}}}},{"ruleId":"D30","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"854da5cef13784fde7cfff8a79eb2a7417bef798a376f1ff9e501c0d2a107a1d"},"properties":{"dependency":{"package":"pygments","version":"2.19.1","advisory":"PYSEC-2026-2987","aliases":["[CVE redacted]","[GHSA redacted]"],"reachability":{"kind":"not-imported"}}}},{"ruleId":"D31","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"fe2d688610b51e0a5a02c7c5dd1724a4986e40f2689fb84510e2ec0164c27d6a"}},{"ruleId":"D31","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"5cfed0ee4e80785ce23c7083cffdead9acc6c64f9dce56a00ca7178bd3d7bee5"},"taxa":[{"id":"CWE-1357","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-353","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A03:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}}]},{"ruleId":"D31","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"638d691cfbb8bb9270a989f2c25b0e77447f9b180801a2b3fbd915d54a0d3510"},"taxa":[{"id":"CWE-1357","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A03:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}},{"id":"CICD-SEC-3","toolComponent":{"name":"OWASP Top 10 CI/CD Security Risks","guid":"3c9b2a6e-5d14-4f7b-8e02-6a1d9c4b7f35"}}]},{"ruleId":"D31","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"d15df5171d54d9a3cfe919193b940b95eb1db599610449c8b68164e072da6651"},"taxa":[{"id":"CWE-1357","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-353","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A03:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}}]},{"ruleId":"D31","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"62ba3f391b97d680ac34e630794a6a7fc0f3b16bd44bab9e323085ff4fa2c944"}},{"ruleId":"D31","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"03400874d601518163011eed910f9aa5e00eb019cf0566ef4de3c1acc82a453a"},"taxa":[{"id":"CWE-1357","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A03:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}},{"id":"CICD-SEC-3","toolComponent":{"name":"OWASP Top 10 CI/CD Security Risks","guid":"3c9b2a6e-5d14-4f7b-8e02-6a1d9c4b7f35"}}]},{"ruleId":"D31","level":"note","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"1f51a163f26d94ce6b6f473117dde579d091c8cbf9e59810475c94d9fc921120"}},{"ruleId":"C2","level":"note","message":{"text":"No named authorization policies: Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) \u2014 this is NOT a claim that endpoints are unprotected. What\u0027s missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can\u0027t be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"b048fdf3fa524ac68c7874fdfcdb4c49d5f010013f2cb22a0bd84cb12ceb951f"}},{"ruleId":"C3","level":"note","message":{"text":"Partial audit-trail evidence: An audit mechanism is present, but the trail is not yet complete \u2014 missing: a write-side hook every change flows through (HistoricalRecords, auditlog.register, reversion.register, pghistory.track, SQLAlchemy-Continuum, a post_save / after_update listener recording each change, or an event-sourced store), per-model coverage (a change-history registration on each model that needs a who-changed-what trail, or an event-sourced aggregate)."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"274a04e524f3228d241c99316455563739cb06cfd10a01e446d00b8a14956083"}},{"ruleId":"DM4","level":"warning","message":{"text":"Anemic entity: Permission: \u0060Permission\u0060 is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) \u2014 the business logic lives in a service."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/domain/permission/entity/permission.py"},"region":{"startLine":8}}}],"partialFingerprints":{"codehealthFindingId/v1":"573fe7608acf879044abfcc6204cc31849cd5340a85989ec80afde2ef10eff0a"}},{"ruleId":"DM4","level":"warning","message":{"text":"Anemic entity: OAuthAccount: \u0060OAuthAccount\u0060 is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) \u2014 the business logic lives in a service."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/db/models/oauth_provider.py"},"region":{"startLine":8}}}],"partialFingerprints":{"codehealthFindingId/v1":"b05ac08b93cdbee57b4bf3d53d13d0b7d8500f1f9d80ae50b42085fd96805b3b"}},{"ruleId":"DM4","level":"warning","message":{"text":"Anemic entity: Permission: \u0060Permission\u0060 is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) \u2014 the business logic lives in a service."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/db/models/permission.py"},"region":{"startLine":28}}}],"partialFingerprints":{"codehealthFindingId/v1":"11b1e33ac4124214ba4f2404e1425cff8805dcc62736b7389c2a7f92a43a0802"}},{"ruleId":"DM4","level":"warning","message":{"text":"Anemic entity: Role: \u0060Role\u0060 is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) \u2014 the business logic lives in a service."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/db/models/role.py"},"region":{"startLine":28}}}],"partialFingerprints":{"codehealthFindingId/v1":"e07bf78eeb9f5b42c0add98edc1fd99a6d886b725ab31c498d2a043f4a5f3cd7"}},{"ruleId":"DM4","level":"warning","message":{"text":"Anemic entity: UserSession: \u0060UserSession\u0060 is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) \u2014 the business logic lives in a service."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/db/models/session.py"},"region":{"startLine":10}}}],"partialFingerprints":{"codehealthFindingId/v1":"c54ed6651f9c02ea2b6e09f99984ca80f019fc6126270351846fd68e09849006"}},{"ruleId":"DM4","level":"warning","message":{"text":"Anemic entity: User: \u0060User\u0060 is an aggregate/entity with 10 data propert(ies) but no state-changing behaviour (only data and queries) \u2014 the business logic lives in a service."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/infrastructure/db/models/user.py"},"region":{"startLine":19}}}],"partialFingerprints":{"codehealthFindingId/v1":"0c792c9e4de6718729fd80c4d72c509205a3db671238b647363f46bc22b64327"}},{"ruleId":"DM5","level":"warning","message":{"text":"Mutable entity: OAuthAccount: \u0060OAuthAccount\u0060 exposes publicly writable state (user_id, provider, provider_user_id, provider_email, is_active)."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/domain/oauth_account/entity/oauth_account.py"},"region":{"startLine":8}}}],"partialFingerprints":{"codehealthFindingId/v1":"840bc009ab7e721c366b4e17a2e171813bf94c03e6bd60bbbe8ba003f328300a"}},{"ruleId":"DM5","level":"warning","message":{"text":"Mutable entity: Permission: \u0060Permission\u0060 exposes publicly writable state (permission_name)."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/domain/permission/entity/permission.py"},"region":{"startLine":8}}}],"partialFingerprints":{"codehealthFindingId/v1":"296d9d78510e50f254d791f25f1b0f62c49ea049906505ede3dfd284e9ee94a9"}},{"ruleId":"DM5","level":"warning","message":{"text":"Mutable entity: Role: \u0060Role\u0060 exposes publicly writable state (name, description, security_level)."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/domain/role/entity/role.py"},"region":{"startLine":9}}}],"partialFingerprints":{"codehealthFindingId/v1":"f97fc91340c6e20c64534b717cd3ef937e633e9edac33b70c858b748045cc63e"}},{"ruleId":"DM5","level":"warning","message":{"text":"Mutable entity: Session: \u0060Session\u0060 exposes publicly writable state (user_id, user_agent, device_info, device_id, last_activity, is_active)."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/domain/session/entity/session.py"},"region":{"startLine":9}}}],"partialFingerprints":{"codehealthFindingId/v1":"a353e9d1e31b4360acad1e2a85678caa860ec8632bde3b29297fa72735ad8534"}},{"ruleId":"DM5","level":"warning","message":{"text":"Mutable entity: User: \u0060User\u0060 exposes publicly writable state (id, username, email, password, jwt_data, deleted_at, and 1 more)."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"src/domain/user/entity/user.py"},"region":{"startLine":19}}}],"partialFingerprints":{"codehealthFindingId/v1":"18869c252e9857bb35b834a1b445b4a680878b2dfa068a166f17a75f7d1faa36"}},{"ruleId":"M2","level":"note","message":{"text":"No ADRs: No Architecture Decision Records found \u2014 no conventional ADR directory, no numbered \u0060NNNN-title\u0060 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."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"670b3d6e36a756d63097d0dfbf90afd5fc761308800b9354894a07c3f4e4aa14"}},{"ruleId":"P1","level":"warning","message":{"text":"No CI pipeline: No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, \u2026) \u2014 changes aren\u0027t gated by an automated build/test."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"44f01af96e50474fba2df84d95ddf4f7e1d34c29c307830b9efc9057daa6b670"}},{"ruleId":"P3","level":"note","message":{"text":"No SAST: No static application security testing detected. For this repository\u0027s stack, add bandit, \u0060semgrep --config=p/python\u0060, or CodeQL\u0027s python pack \u2014 this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge\u0027s web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen \u2014 if that is your case the row is wrong, and saying so is more useful than adding a second scanner."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"6e54424179c892f03ef2fd003130ac4bd43f39bbf3b1ca0a0143e25acb80ec87"}},{"ruleId":"P6","level":"note","message":{"text":"No changelog: No CHANGELOG/HISTORY/RELEASES file \u2014 what shipped when isn\u0027t easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)"},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"dda5aa5aed8cbb292c3ef2b733bc138f614293ae6426c85e98bf31ef330d9415"}}],"taxonomies":[{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d","organization":"MITRE","informationUri":"https://cwe.mitre.org/","isComprehensive":false,"shortDescription":{"text":"The MITRE Common Weakness Enumeration (CWE)."},"taxa":[{"id":"CWE-1032","guid":"5f21e517-68aa-a650-9a25-5771ef024637","name":"OWASP Top Ten \u2014 Security Misconfiguration category","shortDescription":{"text":"OWASP Top Ten \u2014 Security Misconfiguration category"},"helpUri":"https://cwe.mitre.org/data/definitions/1032.html"},{"id":"CWE-1357","guid":"e4d2e772-757e-0a5c-bd7d-77052949d866","name":"Reliance on Insufficiently Trustworthy Component","shortDescription":{"text":"Reliance on Insufficiently Trustworthy Component"},"helpUri":"https://cwe.mitre.org/data/definitions/1357.html"},{"id":"CWE-1395","guid":"800e09e7-c11a-8654-9fa6-86f398995fed","name":"Dependency on Vulnerable Third-Party Component","shortDescription":{"text":"Dependency on Vulnerable Third-Party Component"},"helpUri":"https://cwe.mitre.org/data/definitions/1395.html"},{"id":"CWE-16","guid":"659db3ea-affc-8453-8add-c1218fbfcb92","name":"Configuration","shortDescription":{"text":"Configuration"},"helpUri":"https://cwe.mitre.org/data/definitions/16.html"},{"id":"CWE-259","guid":"ae9ad959-fbb6-9d5e-892d-3dca66da0b69","name":"Use of Hard-coded Password","shortDescription":{"text":"Use of Hard-coded Password"},"helpUri":"https://cwe.mitre.org/data/definitions/259.html"},{"id":"CWE-353","guid":"09d7e902-d4ee-f05d-ae6c-0a1554d0c18f","name":"Missing Support for Integrity Check","shortDescription":{"text":"Missing Support for Integrity Check"},"helpUri":"https://cwe.mitre.org/data/definitions/353.html"},{"id":"CWE-502","guid":"f7d3b296-aac0-5c5a-b706-e07faba26c36","name":"Deserialization of Untrusted Data","shortDescription":{"text":"Deserialization of Untrusted Data"},"helpUri":"https://cwe.mitre.org/data/definitions/502.html"},{"id":"CWE-506","guid":"401d6455-56e3-0552-9a39-f77461673e3f","name":"Embedded Malicious Code","shortDescription":{"text":"Embedded Malicious Code"},"helpUri":"https://cwe.mitre.org/data/definitions/506.html"},{"id":"CWE-732","guid":"1da27e8f-b330-7650-ab63-bd61953eae5d","name":"Incorrect Permission Assignment for Critical Resource","shortDescription":{"text":"Incorrect Permission Assignment for Critical Resource"},"helpUri":"https://cwe.mitre.org/data/definitions/732.html"},{"id":"CWE-77","guid":"332c8ade-6612-9f56-a06b-d8d90b1a8750","name":"Improper Neutralization of Special Elements used in a Command (\u0027Command Injection\u0027)","shortDescription":{"text":"Improper Neutralization of Special Elements used in a Command (\u0027Command Injection\u0027)"},"helpUri":"https://cwe.mitre.org/data/definitions/77.html"},{"id":"CWE-78","guid":"2e31ceaf-c7ae-2e5e-9661-cfb1362789cf","name":"Improper Neutralization of Special Elements used in an OS Command (\u0027OS Command Injection\u0027)","shortDescription":{"text":"Improper Neutralization of Special Elements used in an OS Command (\u0027OS Command Injection\u0027)"},"helpUri":"https://cwe.mitre.org/data/definitions/78.html"},{"id":"CWE-79","guid":"fd45580b-e8c4-fc5e-8c2f-aa8fab0b4dbf","name":"Improper Neutralization of Input During Web Page Generation (\u0027Cross-site Scripting\u0027)","shortDescription":{"text":"Improper Neutralization of Input During Web Page Generation (\u0027Cross-site Scripting\u0027)"},"helpUri":"https://cwe.mitre.org/data/definitions/79.html"},{"id":"CWE-798","guid":"5e8f057d-fee3-995a-a0cb-9fc5b0d174d1","name":"Use of Hard-coded Credentials","shortDescription":{"text":"Use of Hard-coded Credentials"},"helpUri":"https://cwe.mitre.org/data/definitions/798.html"},{"id":"CWE-89","guid":"6d08fdad-37eb-c150-bbf0-d7d946863407","name":"Improper Neutralization of Special Elements used in an SQL Command (\u0027SQL Injection\u0027)","shortDescription":{"text":"Improper Neutralization of Special Elements used in an SQL Command (\u0027SQL Injection\u0027)"},"helpUri":"https://cwe.mitre.org/data/definitions/89.html"},{"id":"CWE-937","guid":"16f316ae-415c-b354-a59b-1f7905f756e9","name":"Using Components with Known Vulnerabilities","shortDescription":{"text":"Using Components with Known Vulnerabilities"},"helpUri":"https://cwe.mitre.org/data/definitions/937.html"},{"id":"CWE-94","guid":"75e7f50c-6c2f-dd52-bf40-bf6c52b861fd","name":"Improper Control of Generation of Code (\u0027Code Injection\u0027)","shortDescription":{"text":"Improper Control of Generation of Code (\u0027Code Injection\u0027)"},"helpUri":"https://cwe.mitre.org/data/definitions/94.html"}]},{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61","version":"2025","organization":"OWASP Foundation","informationUri":"https://top10.owasp.org/2025/","isComprehensive":false,"shortDescription":{"text":"The OWASP Top 10:2025 web application security risks."},"taxa":[{"id":"A02:2025","guid":"668dee9e-41bc-6354-97d0-fdf8f40c50c1","name":"Security Misconfiguration","shortDescription":{"text":"Security Misconfiguration"},"helpUri":"https://top10.owasp.org/2025/A02_2025-Security_Misconfiguration/"},{"id":"A03:2025","guid":"168e227c-7735-2e57-bc6e-997affe644c5","name":"Software Supply Chain Failures","shortDescription":{"text":"Software Supply Chain Failures"},"helpUri":"https://top10.owasp.org/2025/A03_2025-Software_Supply_Chain_Failures/"},{"id":"A05:2025","guid":"87e86033-3231-8458-8e4a-5cb82743553a","name":"Injection","shortDescription":{"text":"Injection"},"helpUri":"https://top10.owasp.org/2025/A05_2025-Injection/"},{"id":"A07:2025","guid":"334ddd78-539d-d35c-83dd-253647eb7eaf","name":"Authentication Failures","shortDescription":{"text":"Authentication Failures"},"helpUri":"https://top10.owasp.org/2025/A07_2025-Authentication_Failures/"},{"id":"A08:2025","guid":"84b0c297-710e-9a5f-9335-936ecb260c36","name":"Software or Data Integrity Failures","shortDescription":{"text":"Software or Data Integrity Failures"},"helpUri":"https://top10.owasp.org/2025/A08_2025-Software_or_Data_Integrity_Failures/"}]},{"name":"OWASP Top 10 CI/CD Security Risks","guid":"3c9b2a6e-5d14-4f7b-8e02-6a1d9c4b7f35","organization":"OWASP Foundation","informationUri":"https://owasp.org/www-project-top-10-ci-cd-security-risks/","isComprehensive":false,"shortDescription":{"text":"The OWASP Top 10 CI/CD Security Risks."},"taxa":[{"id":"CICD-SEC-3","guid":"458c83a6-ebf7-cf55-8cc3-b4d949bbf271","name":"Dependency Chain Abuse","shortDescription":{"text":"Dependency Chain Abuse"},"helpUri":"https://owasp.github.io/www-project-top-10-ci-cd-security-risks/CICD-SEC-03-Dependency-Chain-Abuse"}]}],"properties":{"codehealthPublication":{"public":true,"notice":"This is the PUBLIC form of this artifact. Findings are listed in full, but the details of SECURITY findings \u2014 which rule fired, in which file, on which line, and how to fix it \u2014 are deliberately withheld, and any secret-scanner results are excluded entirely. Where detail is absent here it was REMOVED FOR PUBLICATION; it is not missing from the analysis. The complete artifact is available from the repository owner.","securityFindingsRedacted":36,"secretScannerRunsExcluded":0}},"redactionTokens":["A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."]}]}