{"$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":"D5","name":"Coupling","shortDescription":{"text":"Coupling"},"helpUri":"https://codehealth.canine.dev/dimensions/D5"},{"id":"D6","name":"Cohesion (LCOM4)","shortDescription":{"text":"Cohesion (LCOM4)"},"helpUri":"https://codehealth.canine.dev/dimensions/D6"},{"id":"D11","name":"Test Reliability","shortDescription":{"text":"Test Reliability"},"helpUri":"https://codehealth.canine.dev/dimensions/D11"},{"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":"D15","name":"Churn \u00D7 Complexity Hotspots","shortDescription":{"text":"Churn \u00D7 Complexity Hotspots"},"helpUri":"https://codehealth.canine.dev/dimensions/D15"},{"id":"D16","name":"Bus Factor","shortDescription":{"text":"Bus Factor"},"helpUri":"https://codehealth.canine.dev/dimensions/D16"},{"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":"D20","name":"ADR Quality","shortDescription":{"text":"ADR Quality"},"helpUri":"https://codehealth.canine.dev/dimensions/D20"},{"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":"D32","name":"Data Compliance (PII/GDPR)","shortDescription":{"text":"Data Compliance (PII/GDPR)"},"helpUri":"https://codehealth.canine.dev/dimensions/D32","relationships":[{"target":{"id":"CWE-359","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-312","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-200","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"A01:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-359","CWE-312","CWE-200"],"owasp":"A01:2025"}},{"id":"D34","name":"Knowledge Freshness","shortDescription":{"text":"Knowledge Freshness"},"helpUri":"https://codehealth.canine.dev/dimensions/D34"},{"id":"D35","name":"Change Coupling","shortDescription":{"text":"Change Coupling"},"helpUri":"https://codehealth.canine.dev/dimensions/D35"},{"id":"D36","name":"Supply-chain Provenance \u0026 Signing","shortDescription":{"text":"Supply-chain Provenance \u0026 Signing"},"helpUri":"https://codehealth.canine.dev/dimensions/D36","relationships":[{"target":{"id":"CWE-1357","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-494","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-1357","CWE-494"],"owasp":"A03:2025"}},{"id":"D37","name":"Vulnerability-disclosure Policy","shortDescription":{"text":"Vulnerability-disclosure Policy"},"helpUri":"https://codehealth.canine.dev/dimensions/D37","relationships":[{"target":{"id":"CWE-1059","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-1059"],"owasp":"A02:2025"}},{"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":"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":"AX8","name":"Test isolation","shortDescription":{"text":"Test isolation"},"helpUri":"https://codehealth.canine.dev/dimensions/AX8"},{"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":"P12","name":"CI test-gate honesty","shortDescription":{"text":"CI test-gate honesty"},"helpUri":"https://codehealth.canine.dev/dimensions/P12"},{"id":"P2","name":"Observability","shortDescription":{"text":"Observability"},"helpUri":"https://codehealth.canine.dev/dimensions/P2"},{"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":"SC1","name":"Supply-chain hygiene","shortDescription":{"text":"Supply-chain hygiene"},"helpUri":"https://codehealth.canine.dev/dimensions/SC1"},{"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":"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":"D1","level":"warning","message":{"text":"salary_lookup.collect_validation_issues (cyclomatic 26): salary_lookup.collect_validation_issues has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"salary_lookup.py"},"region":{"startLine":56}}}],"partialFingerprints":{"codehealthFindingId/v1":"be8f2690cab1aa2f72be657c5f994de6957e6533368af85e6490a093db693cbd"}},{"ruleId":"D1","level":"warning","message":{"text":"salary_lookup.match_score_optimized (cyclomatic 24): salary_lookup.match_score_optimized has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"salary_lookup.py"},"region":{"startLine":213}}}],"partialFingerprints":{"codehealthFindingId/v1":"4ad79d8997ef88a34c608c1f6c92dff7ab24f67ee84bf744875a66f6182ad4e1"}},{"ruleId":"D1","level":"warning","message":{"text":"salary_lookup.format_entry (cyclomatic 22): salary_lookup.format_entry has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"salary_lookup.py"},"region":{"startLine":315}}}],"partialFingerprints":{"codehealthFindingId/v1":"fdefaff5addff139c9250fb18f39a9badf128221d2a6596ee0e17f6c9f776acb"}},{"ruleId":"D2","level":"warning","message":{"text":"salary_lookup.format_entry (cognitive 49): salary_lookup.format_entry has cognitive complexity 49 (threshold 15). Drivers by points: if/else 14 (29 pts), ternaries 2 (10 pts), loops 3 (6 pts), boolean chains 4 (nesting depth added 26). To reduce it, flatten the nesting: this score is depth rather than breadth \u2014 most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language\u0027s equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"salary_lookup.py"},"region":{"startLine":315}}}],"partialFingerprints":{"codehealthFindingId/v1":"edf424755430a6b582abb5f33a53fe0ab71881c179bc79ab85239b456057de55"}},{"ruleId":"D2","level":"warning","message":{"text":"salary_lookup.collect_validation_issues (cognitive 45): salary_lookup.collect_validation_issues has cognitive complexity 45 (threshold 15). Drivers by points: if/else 15 (32 pts), boolean chains 7, loops 2 (4 pts), error handling 1 (2 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"salary_lookup.py"},"region":{"startLine":56}}}],"partialFingerprints":{"codehealthFindingId/v1":"0d6ba51518bb0e464a44c923981de637566696079b98fe858deec502b23ef5cf"}},{"ruleId":"D2","level":"warning","message":{"text":"salary_lookup.match_score_optimized (cognitive 38): salary_lookup.match_score_optimized has cognitive complexity 38 (threshold 15). Drivers by points: if/else 21 (31 pts), boolean chains 7 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"salary_lookup.py"},"region":{"startLine":213}}}],"partialFingerprints":{"codehealthFindingId/v1":"f4d72c0a925bb0ac89b9f9951ddb6e98a1e16ab8dc9fb70a25f980c89418114e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 11): salary_lookup.py:415-424 | tools/check_upstream_updates.py:72-76 | tools/convert_salary_excel.py:407-416 | tools/fetch_page.py:235-244 | tools/install_portal_clis.py:125-129 | tools/job_key.py:361-370 | tools/rank_state.py:521-530 | tools/robots_check.py:215-224 | tools/upstream_triage.py:46-55 | tools/verify_layout.py:430-439 | tools/verify_pdf.py:359-368 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 11 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 11 times."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"salary_lookup.py"},"region":{"startLine":415}}}],"partialFingerprints":{"codehealthFindingId/v1":"5b256c3a9dc42e355a91be375ffb6648c02a7b3160c362549e71ac6724c85aa6"}},{"ruleId":"D4","level":"warning","message":{"text":"Edited copy of a member (16 corresponding lines): tools/fetch_page.py:216-231 | tools/posting_guard.py:76-100 \u2014 These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below \u2014 the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members\u0027 grain \u2014 factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"tools/fetch_page.py"},"region":{"startLine":216}}}],"partialFingerprints":{"codehealthFindingId/v1":"d61e0153ba48d7cf3137e39f54dfa06b5a65aeae25d0b72c332960330d6b2ef6"}},{"ruleId":"D4","level":"warning","message":{"text":"Edited copy of a member (11 corresponding lines): tools/check_framework_version.py:68-80 | tools/check_upstream_updates.py:52-62 \u2014 These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below \u2014 the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members\u0027 grain \u2014 factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"tools/check_framework_version.py"},"region":{"startLine":68}}}],"partialFingerprints":{"codehealthFindingId/v1":"8de8de404d3bb2866cce573b3cdbc0efaac992908780ce63eb7dc4024c73be55"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (16\u201318 lines \u00D7 2): tools/fetch_page.py:216-231 | tools/posting_guard.py:83-100 \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 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":"tools/fetch_page.py"},"region":{"startLine":216}}}],"partialFingerprints":{"codehealthFindingId/v1":"25e80b8f6bc5f90f3ac32dcdeb53f81f664805d3352c1ef50f686d1ee9534ac9"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): tools/lint_skills.py:81-89 | tools/security_guards.py:493-501 \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 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":"tools/lint_skills.py"},"region":{"startLine":81}}}],"partialFingerprints":{"codehealthFindingId/v1":"b3003132cfd9f2c4f176d83b80d32be4e00eaf01d8916a64d75d0471940f5212"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): tools/job_key.py:311-318 | tools/rank_state.py:104-111 \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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"tools/job_key.py"},"region":{"startLine":311}}}],"partialFingerprints":{"codehealthFindingId/v1":"dd7c8f4caee5986d7f81e24b765ae8c18874bf9e6cd9f98cef186c6ddebd3d01"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7 lines \u00D7 2): tools/rank_state.py:355-361 | tools/rank_state.py:393-399 \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. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060tools/rank_state.py:353\u0060 calls \u0060parse_iso\u0060, \u0060get\u0060 and \u0060tools/rank_state.py:392\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":"tools/rank_state.py"},"region":{"startLine":355}}}],"partialFingerprints":{"codehealthFindingId/v1":"167c630795c234646f3a8a5f8a46dc925cab58a6aa684b4cf806346319fd6b95"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): tools/check_framework_version.py:26-34 | tools/check_upstream_updates.py:41-45 \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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"tools/check_framework_version.py"},"region":{"startLine":26}}}],"partialFingerprints":{"codehealthFindingId/v1":"920de6a70321e72891e2392e9630bad957239c15e95833a98f5b267c66796713"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: tools/convert_salary_excel.py: tools/convert_salary_excel.py changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 59 in convert_salary_excel.parse_sheet at line 167. 15 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one \u2014 a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- tools/convert_salary_excel.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":"tools/convert_salary_excel.py"},"region":{"startLine":167}}}],"partialFingerprints":{"codehealthFindingId/v1":"29fe0da9979e76764d4a7cfb6e71fdd39c80b058894e924891d81866766f4485"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: tools/rank_state.py: tools/rank_state.py changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 49 in rank_state.cmd_apply at line 315. 13 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one \u2014 a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- tools/rank_state.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":"tools/rank_state.py"},"region":{"startLine":315}}}],"partialFingerprints":{"codehealthFindingId/v1":"bc506b4931a289fbbf46545b1be1b95de3e74ec473f276adc07721046315dbde"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: tools/security_guards.py: tools/security_guards.py changed 22 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in security_guards.check_permissions at line 492. 11 of those changes were fix/bug commits, and the other 11 changed it for other reasons \u2014 this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one \u2014 a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- tools/security_guards.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":"tools/security_guards.py"},"region":{"startLine":492}}}],"partialFingerprints":{"codehealthFindingId/v1":"bbf6465fa7c55e7c1cddfde0ed087dfacd337645a6ef1bb9926cd7c494dc243c"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: .agents/skills/freehire-search/cli/src/cli.ts: .agents/skills/freehire-search/cli/src/cli.ts changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in main at line 186. 7 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one \u2014 a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- .agents/skills/freehire-search/cli/src/cli.ts\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":".agents/skills/freehire-search/cli/src/cli.ts"},"region":{"startLine":186}}}],"partialFingerprints":{"codehealthFindingId/v1":"3e8bc882914f0ebbf3a91fd7357f783c04906df14e781fd113573d9a96d72f39"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: tools/posting_guard.py: tools/posting_guard.py changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in posting_guard.clean_text at line 201. 11 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one \u2014 a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- tools/posting_guard.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":"tools/posting_guard.py"},"region":{"startLine":201}}}],"partialFingerprints":{"codehealthFindingId/v1":"09a21ded83a9c6ac1ae0bb661193327f7fee3ae0fe6ef87aeb5d01c139994449"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: .agents/skills/linkedin-search/cli/src/cli.ts: .agents/skills/linkedin-search/cli/src/cli.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in main at line 77. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one \u2014 a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- .agents/skills/linkedin-search/cli/src/cli.ts\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":".agents/skills/linkedin-search/cli/src/cli.ts"},"region":{"startLine":77}}}],"partialFingerprints":{"codehealthFindingId/v1":"9f45bbdc14ecdb5cdac877066efcd21f4d1a28b70dba8213b8517f454fbe16f4"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: salary_lookup.py: salary_lookup.py changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in salary_lookup.format_entry at line 315. 9 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one \u2014 a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- salary_lookup.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":"salary_lookup.py"},"region":{"startLine":315}}}],"partialFingerprints":{"codehealthFindingId/v1":"4350cdf01fc90180343e11d4e241545c68f355018afe9d0a5eeeebb2a79cb7e3"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: tools/upstream_triage.py: tools/upstream_triage.py changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in upstream_triage.main at line 150. 6 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one \u2014 a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- tools/upstream_triage.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":"tools/upstream_triage.py"},"region":{"startLine":150}}}],"partialFingerprints":{"codehealthFindingId/v1":"d871fcdecf2ba5b49c8e826a5506226437301fcf8e0582f23eeb9a4e0b47813e"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: .agents/skills/jobnet-search/cli/src/commands/detail.ts: .agents/skills/jobnet-search/cli/src/commands/detail.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in mapSearchAdToDetail at line 69. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one \u2014 a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- .agents/skills/jobnet-search/cli/src/commands/detail.ts\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":".agents/skills/jobnet-search/cli/src/commands/detail.ts"},"region":{"startLine":69}}}],"partialFingerprints":{"codehealthFindingId/v1":"e620fb25e2da42e615a1e84e3ae75646afdb593045d6a468c37a2f2b3d8fbd02"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: tools/check_upstream_updates.py: tools/check_upstream_updates.py changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in check_upstream_updates.main at line 79. 4 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one \u2014 a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- tools/check_upstream_updates.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":"tools/check_upstream_updates.py"},"region":{"startLine":79}}}],"partialFingerprints":{"codehealthFindingId/v1":"97e573d2cb49c5c0bbc104701a55b89b53268b3f0561fd5ef7b7b06e929c0cc1"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: .agents/skills/jobindex-search/cli/src/commands/detail.ts: .agents/skills/jobindex-search/cli/src/commands/detail.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in parseDetailPage at line 168. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- .agents/skills/jobindex-search/cli/src/commands/detail.ts\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":".agents/skills/jobindex-search/cli/src/commands/detail.ts"},"region":{"startLine":168}}}],"partialFingerprints":{"codehealthFindingId/v1":"654dbb2f4f75139f26428025203da8768fc8efcdd156b3a86f5d5357e04c67f9"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: .agents/skills/linkedin-search/cli/src/helpers.ts: .agents/skills/linkedin-search/cli/src/helpers.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in parseJobDetail at line 279. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- .agents/skills/linkedin-search/cli/src/helpers.ts\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":".agents/skills/linkedin-search/cli/src/helpers.ts"},"region":{"startLine":279}}}],"partialFingerprints":{"codehealthFindingId/v1":"a3e1f0681a4f82f0b77f6c5684fee86f7f4d62241c5fccee4f4660990bff8fb7"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: tools/job_key.py: tools/job_key.py changed 9 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file\u0027s churn. Its max cyclomatic complexity is 15 (its worst body is job_key.make_key at line 149), AT OR 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(scrape): keep C\u002B\u002B, C# and C job titles distinct in dedup and keys (#830)\u201D; \u201Cfix(job-key): fold Latin letters without an NFKD decomposition and add --audit --migrate (#637)\u201D; \u201Cfix(job-key): report a non-string url in --audit instead of a traceback (#634)\u201D; \u201Cfix(job-key): report a non-object state file in --audit instead of a traceback (#626)\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 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- tools/job_key.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":"tools/job_key.py"},"region":{"startLine":149}}}],"partialFingerprints":{"codehealthFindingId/v1":"cfd84ff5460e0321e55020d1bea853a0e261451bdb5320fb7f00d5094af1ecf0"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: tools/verify_pdf.py: tools/verify_pdf.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 13 (its worst body is verify_pdf._quantity_range at line 173), AT OR 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(verify_pdf): exclude currency amounts from ASCII date checks (#724)\u201D; \u201Cfix(tools): confine verify_pdf --dump-text and drop the bare pdftotext allowance\u201D; \u201Cfix(verify_pdf): --ascii-dates catches the 2016\u201317 form again (regression in #533) (#698)\u201D; \u201Cfix(verify_pdf): --ascii-dates treats a numeric range as a date only when both ends are bare years (#533)\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 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- tools/verify_pdf.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":"tools/verify_pdf.py"},"region":{"startLine":173}}}],"partialFingerprints":{"codehealthFindingId/v1":"b86d8ef363c988cdf4d47018e1f3777db4e342c3a620f1c26bbc83ae883e4121"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: tools/fetch_page.py: tools/fetch_page.py changed 7 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 15 (its worst body is fetch_page.main at line 247), AT OR 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(fetch): compare --out against the repo by identity, not spelling (#742)\u201D; \u201Cfix(fetch-page): drop unclosed script and template blocks from --text (#764)\u201D; \u201Cfix(fetch-page): decode standard zlib-wrapped HTTP deflate (#711)\u201D; \u201Cfix(fetch-page): pass --compressed only when curl supports it (#759)\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 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- tools/fetch_page.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":"tools/fetch_page.py"},"region":{"startLine":247}}}],"partialFingerprints":{"codehealthFindingId/v1":"45885796f89f5855a26fbe5bb87b533068a91f9567ce5bfbb295e51e2e590484"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: .agents/skills/jobnet-search/cli/src/commands/search.ts: .agents/skills/jobnet-search/cli/src/commands/search.ts changed 7 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 15 (its worst body is (anonymous) at line 118), AT OR 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(portals): keep hidden markup and invisible characters out of CLI output\u201D; \u201Cfix(jobnet-search): keep canonical portal url and emit destination in applyUrl (closes #701) (#706)\u201D; \u201Cfix(jobnet-search): filter search by the ESCO occupation that occupations prints (#649)\u201D; \u201Cfix(jobnet-search): route external ads to jobAdUrl with http(s) validation and fallback (#538) (#557)\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 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- .agents/skills/jobnet-search/cli/src/commands/search.ts\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":".agents/skills/jobnet-search/cli/src/commands/search.ts"},"region":{"startLine":118}}}],"partialFingerprints":{"codehealthFindingId/v1":"d9c4e74a2d4972be3c70018c52f6c417557a2ea50df9ad892c855beb781478af"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: .agents/skills/freehire-search/cli/src/helpers.ts: .agents/skills/freehire-search/cli/src/helpers.ts changed 9 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 14 (its worst body is apiGet at line 61), AT OR 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(portals): keep hidden markup and invisible characters out of CLI output\u201D; \u201Cfix(freehire-search): drop the github.com URL from the User-Agent (#689)\u201D; \u201Cfix(freehire-search): reject detail URLs on other hosts instead of asking the API for their last segment (#622) (#623)\u201D; \u201Cfix(freehire-search): emit the contract\u0027s YYYY-MM-DD date instead of the API\u0027s ISO timestamp (#621)\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 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- .agents/skills/freehire-search/cli/src/helpers.ts\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":".agents/skills/freehire-search/cli/src/helpers.ts"},"region":{"startLine":61}}}],"partialFingerprints":{"codehealthFindingId/v1":"019c784d071a9919c5de83323ee996555e999738cc18a7a4a05c5e2c8d5a6c57"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: tools/robots_check.py: tools/robots_check.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 15 (its worst body is robots_check._match at line 126), AT OR 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(robots_check): match wildcard rules in linear time and hand curl only http(s) URLs (#779)\u201D; \u201Cfix(tools): force UTF-8 output on fetch_page \u0026 robots_check (closes #685) (#686)\u201D; \u201Cfix(robots-check): unquote query strings and restrict \u0027$\u0027 anchor to pattern end (#543) (#546)\u201D; \u201Cfix(robots-check): stop a leading BOM or an undecodable rule from reading as allowed (#509)\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 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- tools/robots_check.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":"tools/robots_check.py"},"region":{"startLine":126}}}],"partialFingerprints":{"codehealthFindingId/v1":"723129ab1acd9d151f92178fc51ca6de208e58a59c262e697937d306d40c8786"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: .agents/skills/linkedin-search/cli/src/commands/detail.ts: .agents/skills/linkedin-search/cli/src/commands/detail.ts 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 14 (its worst body is runDetail at line 46), AT OR 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(portals): keep hidden markup and invisible characters out of CLI output\u201D; \u201Cfix(linkedin-search): reject detail URLs on other hosts instead of fetching the posting with that number (#500)\u201D; \u201Cfix(linkedin-search): accept LinkedIn job URLs with trailing slashes in detail command (#411) (#412)\u201D; \u201Cfix(linkedin-search): drop the never-delivered applyUrl detail field\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 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- .agents/skills/linkedin-search/cli/src/commands/detail.ts\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":".agents/skills/linkedin-search/cli/src/commands/detail.ts"},"region":{"startLine":46}}}],"partialFingerprints":{"codehealthFindingId/v1":"319b9d5dc2923a08ac0462b924190c1d86223db19a7408736edc6317aba27098"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: tools/install_portal_clis.py: tools/install_portal_clis.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 9 (its worst body is install_portal_clis.unsafe_reason at line 50), AT OR 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(install): find bun at standard install locations when PATH misses it (#762)\u201D; \u201Cfix(guards): refuse a .npmrc beside a portal manifest, like bunfig.toml\u201D; \u201Cfix(guards): read .gitignore like git, allowlist settings.json keys, refuse workspaces and bunfig.toml\u201D; \u201Cfix(installer): disable dependency hooks explicitly across Bun versions\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 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- tools/install_portal_clis.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":"tools/install_portal_clis.py"},"region":{"startLine":50}}}],"partialFingerprints":{"codehealthFindingId/v1":"17c5466dcd832a709d3ace6f52396b15de7f3b223d8e28261f03516350514843"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: .agents/skills/jobbank-search/cli/src/helpers.ts: .agents/skills/jobbank-search/cli/src/helpers.ts 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 10 (its worst body is visibleHtml at line 229), AT OR 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(portals): keep hidden markup and invisible characters out of CLI output\u201D; \u201Cfix(portal-clis): reject foreign detail URLs in Jobbank and Jobnet (#672)\u201D; \u201Cfix(portal-clis): accept full posting URLs in jobbank, jobdanmark, and jobnet detail commands (#430)\u201D; \u201Cfix(jobbank-search)!: emit deadline as YYYY-MM-DD in search output\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 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- .agents/skills/jobbank-search/cli/src/helpers.ts\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":".agents/skills/jobbank-search/cli/src/helpers.ts"},"region":{"startLine":229}}}],"partialFingerprints":{"codehealthFindingId/v1":"4c7d9fd4bf6e5a6fda5f3542507955ab50fcdad2bf20c625b4b70305bdd017b1"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: .agents/skills/jobdanmark-search/cli/src/helpers.ts: .agents/skills/jobdanmark-search/cli/src/helpers.ts 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 10 (its worst body is visibleHtml at line 154), AT OR 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(portals): keep hidden markup and invisible characters out of CLI output\u201D; \u201Cfix(jobdanmark-search): back off on 429/5xx in detail instead of failing on the first attempt (#460)\u201D; \u201Cfix(portal-clis): accept full posting URLs in jobbank, jobdanmark, and jobnet detail commands (#430)\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 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- .agents/skills/jobdanmark-search/cli/src/helpers.ts\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":".agents/skills/jobdanmark-search/cli/src/helpers.ts"},"region":{"startLine":154}}}],"partialFingerprints":{"codehealthFindingId/v1":"ebac90350cc42ab5faee7c4e11dcf7b486f52a4c431dff98115743521b2467a5"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: .agents/skills/jobnet-search/cli/src/helpers.ts: .agents/skills/jobnet-search/cli/src/helpers.ts 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 10 (its worst body is visibleHtml at line 90), AT OR 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(portals): keep hidden markup and invisible characters out of CLI output\u201D; \u201Cfix(portal-clis): reject foreign detail URLs in Jobbank and Jobnet (#672)\u201D; \u201Cfix(portal-clis): accept full posting URLs in jobbank, jobdanmark, and jobnet detail commands (#430)\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 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- .agents/skills/jobnet-search/cli/src/helpers.ts\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":".agents/skills/jobnet-search/cli/src/helpers.ts"},"region":{"startLine":90}}}],"partialFingerprints":{"codehealthFindingId/v1":"456a480d782a897c29b819186743d25cccd717001745bdef66c3123a40508897"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: .agents/skills/jobbank-search/cli/src/cli.ts: .agents/skills/jobbank-search/cli/src/cli.ts 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 (anonymous) at line 34), AT OR 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(portal-clis): reject missing Danish option values before dispatch (#573)\u201D; \u201Cfix(portal-clis): reject undefined single-dash flags in the unknown-flag guard (#428)\u201D; \u201Cfix(portals)!: reject unknown flags in all six CLIs\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 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- .agents/skills/jobbank-search/cli/src/cli.ts\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":".agents/skills/jobbank-search/cli/src/cli.ts"},"region":{"startLine":34}}}],"partialFingerprints":{"codehealthFindingId/v1":"cdc57eab9279e635d70b1273421236fc17c7f474598a1fb96e8c3a5bf1a59f74"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: .agents/skills/jobdanmark-search/cli/src/cli.ts: .agents/skills/jobdanmark-search/cli/src/cli.ts 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 (anonymous) at line 37), AT OR 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(portal-clis): reject missing Danish option values before dispatch (#573)\u201D; \u201Cfix(portal-clis): reject undefined single-dash flags in the unknown-flag guard (#428)\u201D; \u201Cfix(portals)!: reject unknown flags in all six CLIs\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 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- .agents/skills/jobdanmark-search/cli/src/cli.ts\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":".agents/skills/jobdanmark-search/cli/src/cli.ts"},"region":{"startLine":37}}}],"partialFingerprints":{"codehealthFindingId/v1":"fb148040013896d7106fccf64c2b1650dd0b17b95fa2f54f39f09d7109fe77c9"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: .agents/skills/jobindex-search/cli/src/cli.ts: .agents/skills/jobindex-search/cli/src/cli.ts 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 (anonymous) at line 34), AT OR 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(portal-clis): reject missing Danish option values before dispatch (#573)\u201D; \u201Cfix(portal-clis): reject undefined single-dash flags in the unknown-flag guard (#428)\u201D; \u201Cfix(portals)!: reject unknown flags in all six CLIs\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 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- .agents/skills/jobindex-search/cli/src/cli.ts\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":".agents/skills/jobindex-search/cli/src/cli.ts"},"region":{"startLine":34}}}],"partialFingerprints":{"codehealthFindingId/v1":"4bd97737d46dd489ff104c0ed12de9d7178b11f0b6c4483f26bc829442875878"}},{"ruleId":"D15","level":"warning","message":{"text":"Repeated repair: .agents/skills/jobnet-search/cli/src/cli.ts: .agents/skills/jobnet-search/cli/src/cli.ts 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 (anonymous) at line 36), AT OR 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(portal-clis): reject missing Danish option values before dispatch (#573)\u201D; \u201Cfix(portal-clis): reject undefined single-dash flags in the unknown-flag guard (#428)\u201D; \u201Cfix(portals)!: reject unknown flags in all six CLIs\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 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-08-14 21:37:19 \u002B01:00\u0027 --until=\u00272026-11-12 21:37:19 \u002B01:00\u0027 --full-history --no-merges -- .agents/skills/jobnet-search/cli/src/cli.ts\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":".agents/skills/jobnet-search/cli/src/cli.ts"},"region":{"startLine":36}}}],"partialFingerprints":{"codehealthFindingId/v1":"532c34c57b935c3a3a665fbfa51bae6ea13208d18b9d3af50450d7ca2bc40357"}},{"ruleId":"D20","level":"note","message":{"text":"No ADRs found: No ADRs found. No recognised ADR directory (\u0060docs/adr/\u0060, \u0060docs/decisions/\u0060, \u0060adr/\u0060, \u0060docs/rfcs/\u0060, an \u0060ADR0001/\u0060 folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (\u0060docs/adr/use-postgres.md\u0060, \u0060docs/adr/2024/0001-x.md\u0060); or a file anywhere whose name is ADR-shaped (\u00600001-use-postgres.md\u0060, \u0060adr-012-caching.md\u0060); or, when neither turned anything up, a document carrying the decision-record signature (an \u0022Architecture Decision Record\u0022 heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these \u2014 unnumbered files outside any recognised directory, without those headings \u2014 is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in \u0060docs/adr/\u0060. ADRs are expected here because \u0060.agents/skills/linkedin-search/cli/package.json\u0060 makes this repository a deployable product (line 7)."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":".agents/skills/linkedin-search/cli/package.json"},"region":{"startLine":7}}}],"partialFingerprints":{"codehealthFindingId/v1":"af31c404b7be08c8c08ade48554a5ef978f1061e39e5a6e96dd253a1232e887d"}},{"ruleId":"D29","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":"482e3b19efd040fb2215efbc5e65f5b9996234817368c5a9198eb89910e46231"},"taxa":[{"id":"CWE-1357","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-829","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A03:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}}]},{"ruleId":"D29","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":"19f2b0f7f0fdbd4ec620a17b9b98906a0eed2dc29f5e89caafa9794981bd25c9"},"taxa":[{"id":"CWE-214","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-532","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A09:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}}]},{"ruleId":"D29","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":"30d183a390d6a88d22e1a75fc40dd7a154a1e43c70d2d22da87f5b8f670e2179"},"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":"D29","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":"3c78cd14d33035944d252aea9570e8e65233a8fb8de6936e2b2b67929de5ba6d"},"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":"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":"1edffb07376416d1b25d80bc8e2620d7ff4d3528eab1e709cfd3108821527a1e"},"taxa":[{"id":"CWE-1333","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A02: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":"adc78344231037a86c853d1366fa001fb292f1e44c17d5af9b0d1b8bcc0b73b6"},"taxa":[{"id":"CWE-1333","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A02: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":"91217041ec18e371e811666b1dd74b60d301bc0a27fa9b07984a72390187d374"},"taxa":[{"id":"CWE-1333","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A02: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":"18ab57346779e979752278e6907b1cd179160b6990747fa4f9cef32d8d9c6485"},"taxa":[{"id":"CWE-1333","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A02: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":"1b6c440c5155fced13b9face1481ebbaf0a95207149789d2e43e12681d1484bf"},"taxa":[{"id":"CWE-1333","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A02: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":"c4826d7dd12a3687b526a75edb5ef58edfcc9a184066b181b7c6dfa3364688d8"},"taxa":[{"id":"CWE-1333","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A02: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":"89d98bd5f0ec05e3242ce48cf75b4a4ccf08d5bbbf9950d663cbc61452063210"},"taxa":[{"id":"CWE-1333","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A02: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":"c4ed6fe1f8a1d8f90edbb9f04147a8c890fc42cc23d5b6480f1b9dc62b14e79b"},"taxa":[{"id":"CWE-125","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A06: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":"8574b9378d4b546d133044e87db130c3e552229bc42b230919bea7e0d0f176e4"},"taxa":[{"id":"CWE-125","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A06: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":"9862df105ee37e368b5c51178f0209e28c06627c469f5a6456b8ad0f11389598"},"taxa":[{"id":"CWE-1333","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A02: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":"e983c7667d82613f8d2644f0648bc871ddc50ead7bc7d2879b5cc0cc8850d1a2"},"taxa":[{"id":"CWE-1333","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A02: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":"ababaf497a4ba59a7356d1a9a7973c9e4d49f080b410153168ab70c2abf2ca78"},"taxa":[{"id":"CWE-1333","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A02: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":"17a1c1b9f19baaabce4de64903458f91cf534036fbf9bf04caa0f087c990c84c"},"taxa":[{"id":"CWE-125","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A06: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":"dfda632b59171da88eb6bb1ec4310f5f2680520830c4f66fd2fd99eb5e3abbc5"},"taxa":[{"id":"CWE-125","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A06: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":"7d100b80f8ffdfd45cb5c17cb1c003cef584f268e5d63576b7421a807dfcc500"},"taxa":[{"id":"CWE-125","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A06:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}}]},{"ruleId":"D32","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":"a27fc7d0cef0c0b00110da7a406ed969893d713bac81b2d64d3daf637ecd0e66"}},{"ruleId":"D32","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":"523fa908c33127feaedbb4a0b81a33ca027b269d3079b9904d79a77a6200c0e8"}},{"ruleId":"D36","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":"1b213f6eedd4b140d0bc37bdf1496f72811a643f34064f12518b32e9e83bcfc7"},"taxa":[{"id":"CICD-SEC-9","toolComponent":{"name":"OWASP Top 10 CI/CD Security Risks","guid":"3c9b2a6e-5d14-4f7b-8e02-6a1d9c4b7f35"}}]},{"ruleId":"D36","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":"0e17f71490e4d120a48b2b2881ab866c93b272bef2febb673a3e8e42b2c288ab"},"taxa":[{"id":"CICD-SEC-9","toolComponent":{"name":"OWASP Top 10 CI/CD Security Risks","guid":"3c9b2a6e-5d14-4f7b-8e02-6a1d9c4b7f35"}}]},{"ruleId":"D36","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":"d657599f6f99da1927d3377533dfc0888b34c4d84aa7d5579841fd72d0e39bce"},"taxa":[{"id":"CICD-SEC-6","toolComponent":{"name":"OWASP Top 10 CI/CD Security Risks","guid":"3c9b2a6e-5d14-4f7b-8e02-6a1d9c4b7f35"}}]},{"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":"M3","level":"note","message":{"text":"No src/ separation: Most of the production code is in directories of its own, but 1 application file(s) sit at the repository root beside the build and tooling files (\u0060salary_lookup.py\u0060)."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"fdf7f5b24e313364d10170a5c2542959902fe0d26ed70edef3eaa10ec5bcdb1d"}},{"ruleId":"P2","level":"warning","message":{"text":"No structured logging: No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page \u2014 but when a run fails on a user\u0027s machine, neither they nor you have anything to read."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"9f10d71351c6778ebe84e761f82a90d4f9ed6c64f5e01975ede8fda7e4e2ebc5"}},{"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 as a CI step. What was searched, so you can tell an absence from a miss: the 3 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":[{"physicalLocation":{"artifactLocation":{"uri":".github/workflows/ci.yml"},"region":{"startLine":32}}}],"partialFingerprints":{"codehealthFindingId/v1":"6e54424179c892f03ef2fd003130ac4bd43f39bbf3b1ca0a0143e25acb80ec87"}},{"ruleId":"P4","level":"note","message":{"text":"No release approval gate: The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY\u0027S PIPELINE FILES. What was read: every file under \u0060.github/workflows/\u0060, \u0060.forgejo/workflows/\u0060, \u0060.gitea/workflows/\u0060, \u0060.azuredevops/\u0060 and \u0060.azure-pipelines/\u0060, plus \u0060.gitlab-ci*\u0060 and \u0060azure-pipelines*\u0060 \u2014 with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab\u0027s \u0060when: manual\u0060, CircleCI\u0027s \u0060type: approval\u0060, an Azure \u0060ManualValidation@\u0060 task or an \u0060approvals:\u0060 block, a Jenkins \u0060input\u0060 step, a \u0060uses:\u0060 step naming an approval action, an \u0060environment:\u0060 paired with \u0060reviewers\u0060 / \u0060required_reviewers\u0060 / \u0060protection\u0060 / \u0060wait-timer\u0060 / \u0060deployment_branch_policy\u0060, a draft-release step, a \u0060workflow_dispatch\u0060 promotion, or a release-event gate. \u2605 What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy \u2014 all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":".github/workflows/release.yml"},"region":{"startLine":88}}}],"partialFingerprints":{"codehealthFindingId/v1":"6c11e2dbd483b4b423b95ac61bfcc7af1d55351b28a20d2b1105b31cfe38cc60"}},{"ruleId":"SC1","level":"warning","message":{"text":"JavaScript dependencies are not locked: .agents/skills/freehire-search/cli/package.json declares dependencies that no committed lockfile resolves \u2014 there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it \u2014 so its installs aren\u0027t reproducible (SSDF PW.4.4). Commit its package manager\u0027s lockfile (or add it to the locked workspace) and install from it (\u0060npm ci\u0060, \u0060yarn --immutable\u0060, \u0060pnpm i --frozen-lockfile\u0060 or \u0060bun i --frozen-lockfile\u0060). Advisory \u2014 never scored."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":".agents/skills/freehire-search/cli/package.json"},"region":{"startLine":16}}}],"partialFingerprints":{"codehealthFindingId/v1":"fd525081d01968b8dda8da7dfa591c1800976fc0deefc731e5f3c135c414db43"}},{"ruleId":"SC1","level":"warning","message":{"text":"JavaScript dependencies are not locked: .agents/skills/jobbank-search/cli/package.json declares dependencies that no committed lockfile resolves \u2014 there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it \u2014 so its installs aren\u0027t reproducible (SSDF PW.4.4). Commit its package manager\u0027s lockfile (or add it to the locked workspace) and install from it (\u0060npm ci\u0060, \u0060yarn --immutable\u0060, \u0060pnpm i --frozen-lockfile\u0060 or \u0060bun i --frozen-lockfile\u0060). Advisory \u2014 never scored."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":".agents/skills/jobbank-search/cli/package.json"},"region":{"startLine":15}}}],"partialFingerprints":{"codehealthFindingId/v1":"1e49fe6a8d569e0e106577dbe56b41bed8aa349d6cef260df6b4b9ccc150d1e6"}},{"ruleId":"SC1","level":"warning","message":{"text":"JavaScript dependencies are not locked: .agents/skills/jobdanmark-search/cli/package.json declares dependencies that no committed lockfile resolves \u2014 there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it \u2014 so its installs aren\u0027t reproducible (SSDF PW.4.4). Commit its package manager\u0027s lockfile (or add it to the locked workspace) and install from it (\u0060npm ci\u0060, \u0060yarn --immutable\u0060, \u0060pnpm i --frozen-lockfile\u0060 or \u0060bun i --frozen-lockfile\u0060). Advisory \u2014 never scored."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":".agents/skills/jobdanmark-search/cli/package.json"},"region":{"startLine":15}}}],"partialFingerprints":{"codehealthFindingId/v1":"ef7b9e22f3dfb4d8f1849e4aba50fbdaf4cb277960d3279998d4f9de7e314701"}},{"ruleId":"SC1","level":"warning","message":{"text":"JavaScript dependencies are not locked: .agents/skills/jobindex-search/cli/package.json declares dependencies that no committed lockfile resolves \u2014 there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it \u2014 so its installs aren\u0027t reproducible (SSDF PW.4.4). Commit its package manager\u0027s lockfile (or add it to the locked workspace) and install from it (\u0060npm ci\u0060, \u0060yarn --immutable\u0060, \u0060pnpm i --frozen-lockfile\u0060 or \u0060bun i --frozen-lockfile\u0060). Advisory \u2014 never scored."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":".agents/skills/jobindex-search/cli/package.json"},"region":{"startLine":15}}}],"partialFingerprints":{"codehealthFindingId/v1":"99d1d00d9fb69dacdea47965ee513d5452ca5f8dcfe0dd5ef07bee3c7061a05b"}},{"ruleId":"SC1","level":"warning","message":{"text":"JavaScript dependencies are not locked: .agents/skills/jobnet-search/cli/package.json declares dependencies that no committed lockfile resolves \u2014 there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it \u2014 so its installs aren\u0027t reproducible (SSDF PW.4.4). Commit its package manager\u0027s lockfile (or add it to the locked workspace) and install from it (\u0060npm ci\u0060, \u0060yarn --immutable\u0060, \u0060pnpm i --frozen-lockfile\u0060 or \u0060bun i --frozen-lockfile\u0060). Advisory \u2014 never scored."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":".agents/skills/jobnet-search/cli/package.json"},"region":{"startLine":15}}}],"partialFingerprints":{"codehealthFindingId/v1":"7840385687de6d46c640f568beda9761479bed709011760bcf8853e62db77471"}},{"ruleId":"SC1","level":"warning","message":{"text":"JavaScript dependencies are not locked: .agents/skills/linkedin-search/cli/package.json declares dependencies that no committed lockfile resolves \u2014 there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it \u2014 so its installs aren\u0027t reproducible (SSDF PW.4.4). Commit its package manager\u0027s lockfile (or add it to the locked workspace) and install from it (\u0060npm ci\u0060, \u0060yarn --immutable\u0060, \u0060pnpm i --frozen-lockfile\u0060 or \u0060bun i --frozen-lockfile\u0060). Advisory \u2014 never scored."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":".agents/skills/linkedin-search/cli/package.json"},"region":{"startLine":16}}}],"partialFingerprints":{"codehealthFindingId/v1":"e9171c94805fc807ee563d55afc393e16426b94f3b6b3b987c35d9eaa40575c6"}},{"ruleId":"X10","level":"note","message":{"text":"Duplicated predicate: \u0060!VOID_TAGS.has(tag) \u0026\u0026 !m[0].endsWith(\u0022/\u003E\u0022)\u0060 appears character-identically in 6 files \u2014 .agents/skills/freehire-search/cli/src/helpers.ts, .agents/skills/jobbank-search/cli/src/helpers.ts, .agents/skills/jobdanmark-search/cli/src/helpers.ts, .agents/skills/jobindex-search/cli/src/helpers.ts. It is one line, so the duplication detector\u0027s token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":".agents/skills/freehire-search/cli/src/helpers.ts"},"region":{"startLine":324}}}],"partialFingerprints":{"codehealthFindingId/v1":"3693c80425584bfa2ef00ecbdf4c4e495518553d1d8c90e524ce81f45fa68fd1"}},{"ruleId":"X10","level":"note","message":{"text":"Duplicated predicate: \u0060!token.startsWith(\u0022-\u0022) || token.includes(\u0022=\u0022)\u0060 appears character-identically in 4 files \u2014 .agents/skills/jobbank-search/cli/src/cli.ts, .agents/skills/jobdanmark-search/cli/src/cli.ts, .agents/skills/jobindex-search/cli/src/cli.ts, .agents/skills/jobnet-search/cli/src/cli.ts. It is one line, so the duplication detector\u0027s token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":".agents/skills/jobbank-search/cli/src/cli.ts"},"region":{"startLine":69}}}],"partialFingerprints":{"codehealthFindingId/v1":"2be3be2fb0a5a620dd1972572987d1c2411c5b4fb30bcc62afadf7d007df555c"}},{"ruleId":"X10","level":"note","message":{"text":"Duplicated predicate: \u0060err instanceof Error \u0026\u0026 err.message.includes(\u0022NOT_FOUND\u0022)\u0060 appears character-identically in 2 files \u2014 .agents/skills/jobbank-search/cli/src/commands/detail.ts, .agents/skills/jobdanmark-search/cli/src/commands/detail.ts. It is one line, so the duplication detector\u0027s token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":".agents/skills/jobbank-search/cli/src/commands/detail.ts"},"region":{"startLine":111}}}],"partialFingerprints":{"codehealthFindingId/v1":"fb4d1f2a99091fc2424341b9f33fd35db5d1947c7610a2d68b609c3b8ad2356c"}},{"ruleId":"X10","level":"note","message":{"text":"Duplicated predicate: \u0060hasScheme || /^[a-z0-9.-]\u002B\\.[a-z]{2,}(\\/|$)/i.test(trimmed)\u0060 appears character-identically in 2 files \u2014 .agents/skills/freehire-search/cli/src/helpers.ts, .agents/skills/linkedin-search/cli/src/commands/detail.ts. It is one line, so the duplication detector\u0027s token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":".agents/skills/freehire-search/cli/src/helpers.ts"},"region":{"startLine":396}}}],"partialFingerprints":{"codehealthFindingId/v1":"eae96e18db80102128b1f5bd2bc2ab61f1fc1140e779b72fc47a608d23fc9f80"}},{"ruleId":"X10","level":"note","message":{"text":"Duplicated predicate: \u0060name === \u0022style\u0022 \u0026\u0026 /(?:^|;)\\s*(?:display\\s*:\\s*none|visibility\\s*:\\s*hidden|mso-hide\\s*:\\s*all)\\b/i.test(value)\u0060 appears character-identically in 6 files \u2014 .agents/skills/freehire-search/cli/src/helpers.ts, .agents/skills/jobbank-search/cli/src/helpers.ts, .agents/skills/jobdanmark-search/cli/src/helpers.ts, .agents/skills/jobindex-search/cli/src/helpers.ts. It is one line, so the duplication detector\u0027s token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":".agents/skills/freehire-search/cli/src/helpers.ts"},"region":{"startLine":296}}}],"partialFingerprints":{"codehealthFindingId/v1":"83a2738352e5738e612385a3afba414c15053a908d1e013b33b8476e61890d71"}},{"ruleId":"X10","level":"note","message":{"text":"Duplicated predicate: \u0060next === undefined || next.startsWith(\u0022-\u0022)\u0060 appears character-identically in 5 files \u2014 .agents/skills/jobbank-search/cli/src/cli.ts, .agents/skills/jobdanmark-search/cli/src/cli.ts, .agents/skills/jobindex-search/cli/src/cli.ts, .agents/skills/jobnet-search/cli/src/cli.ts. It is one line, so the duplication detector\u0027s token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":".agents/skills/jobbank-search/cli/src/cli.ts"},"region":{"startLine":76}}}],"partialFingerprints":{"codehealthFindingId/v1":"f81b7fb3717a7f19a6b8df381f7ac30b153f543fc9c4f594c16a9025875ae784"}},{"ruleId":"X10","level":"note","message":{"text":"Duplicated predicate: \u0060params \u0026\u0026 Object.keys(params).length \u003E 0\u0060 appears character-identically in 3 files \u2014 .agents/skills/jobdanmark-search/cli/src/helpers.ts, .agents/skills/jobindex-search/cli/src/helpers.ts, .agents/skills/jobnet-search/cli/src/helpers.ts. It is one line, so the duplication detector\u0027s token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":".agents/skills/jobdanmark-search/cli/src/helpers.ts"},"region":{"startLine":6}}}],"partialFingerprints":{"codehealthFindingId/v1":"312aa3db4750ad57b8ec8c8b0af51b43c1ec91ffa435302002dffea6fe81d0ef"}},{"ruleId":"X10","level":"note","message":{"text":"Duplicated predicate: \u0060response.status === 429 || response.status \u003E= 500\u0060 appears character-identically in 6 files \u2014 .agents/skills/freehire-search/cli/src/helpers.ts, .agents/skills/jobbank-search/cli/src/helpers.ts, .agents/skills/jobdanmark-search/cli/src/helpers.ts, .agents/skills/jobindex-search/cli/src/helpers.ts. It is one line, so the duplication detector\u0027s token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":".agents/skills/freehire-search/cli/src/helpers.ts"},"region":{"startLine":82}}}],"partialFingerprints":{"codehealthFindingId/v1":"5e9a03a7c7060bf0fb128d8cb626f0073486b8b149c0fa2a9db74f773aba050d"}},{"ruleId":"X10","level":"note","message":{"text":"Duplicated predicate: \u0060url.protocol !== \u0022http:\u0022 \u0026\u0026 url.protocol !== \u0022https:\u0022\u0060 appears character-identically in 2 files \u2014 .agents/skills/jobbank-search/cli/src/helpers.ts, .agents/skills/jobnet-search/cli/src/helpers.ts. It is one line, so the duplication detector\u0027s token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":".agents/skills/jobbank-search/cli/src/helpers.ts"},"region":{"startLine":172}}}],"partialFingerprints":{"codehealthFindingId/v1":"c82e1841c62a9626af66d51296fd31e0c55e79ae5bc939bbc62010d37e9a68a7"}},{"ruleId":"X10","level":"note","message":{"text":"Duplicated predicate: \u0060value !== null \u0026\u0026 typeof value === \u0022object\u0022 \u0026\u0026 Object.getPrototypeOf(value) === Object.prototype\u0060 appears character-identically in 6 files \u2014 .agents/skills/freehire-search/cli/src/helpers.ts, .agents/skills/jobbank-search/cli/src/helpers.ts, .agents/skills/jobdanmark-search/cli/src/helpers.ts, .agents/skills/jobindex-search/cli/src/helpers.ts. It is one line, so the duplication detector\u0027s token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":".agents/skills/freehire-search/cli/src/helpers.ts"},"region":{"startLine":282}}}],"partialFingerprints":{"codehealthFindingId/v1":"29b6c38bfe85ba48d167c3816c2b1939575a8f9629add032cc00a88d04bcdc94"}},{"ruleId":"X7","level":"note","message":{"text":"Silent fallback default on parse failure: \u0060_own_cli_grant\u0060 returns \u0060set()\u0060 when \u0060ValueError\u0060 is raised, with no log or raise \u2014 a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"tools/security_guards.py"},"region":{"startLine":399}}}],"partialFingerprints":{"codehealthFindingId/v1":"8913a8dcbfcb12b464f37ce27c1d1830f64fd297ec04ae3c57e19aa66e0fc967"}},{"ruleId":"X9","level":"note","message":{"text":"Subsumed condition operand: \u0060a.startsWith(\u0022--\u0022)\u0060 can never decide this \u0060||\u0060 \u2014 every value satisfying \u0060a.startsWith(\u0022--\u0022)\u0060 also satisfies \u0060a.startsWith(\u0022-\u0022)\u0060, so the \u0060||\u0060 chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":".agents/skills/linkedin-search/cli/src/cli.ts"},"region":{"startLine":24}}}],"partialFingerprints":{"codehealthFindingId/v1":"8daf7b67fa16181e5ce1232c1923e073d20afc32313dfd4c61befe568ed4ebb0"}}],"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-1059","guid":"a2381a08-60f6-9554-a8b8-f3018cfaaca5","name":"Insufficient Technical Documentation","shortDescription":{"text":"Insufficient Technical Documentation"},"helpUri":"https://cwe.mitre.org/data/definitions/1059.html"},{"id":"CWE-125","guid":"98717707-96bf-ca5b-9568-8d1d257574c1","name":"CWE-125","shortDescription":{"text":"CWE-125"},"helpUri":"https://cwe.mitre.org/data/definitions/125.html"},{"id":"CWE-1333","guid":"11a336ce-63de-c45c-845e-29ca1e8df13d","name":"CWE-1333","shortDescription":{"text":"CWE-1333"},"helpUri":"https://cwe.mitre.org/data/definitions/1333.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-200","guid":"b0ce3b1d-7a29-fe50-8aab-9aba899d2988","name":"Exposure of Sensitive Information to an Unauthorized Actor","shortDescription":{"text":"Exposure of Sensitive Information to an Unauthorized Actor"},"helpUri":"https://cwe.mitre.org/data/definitions/200.html"},{"id":"CWE-214","guid":"b10ad120-fb22-1351-9348-aa23b453e815","name":"CWE-214","shortDescription":{"text":"CWE-214"},"helpUri":"https://cwe.mitre.org/data/definitions/214.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-312","guid":"96724ece-b0b2-a45c-83f9-0869fa3f6bea","name":"Cleartext Storage of Sensitive Information","shortDescription":{"text":"Cleartext Storage of Sensitive Information"},"helpUri":"https://cwe.mitre.org/data/definitions/312.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-359","guid":"b7dfe5b0-0351-645b-a311-b936102c2929","name":"Exposure of Private Personal Information to an Unauthorized Actor","shortDescription":{"text":"Exposure of Private Personal Information to an Unauthorized Actor"},"helpUri":"https://cwe.mitre.org/data/definitions/359.html"},{"id":"CWE-494","guid":"b8a65e0d-e459-4a55-a931-fc1136482375","name":"Download of Code Without Integrity Check","shortDescription":{"text":"Download of Code Without Integrity Check"},"helpUri":"https://cwe.mitre.org/data/definitions/494.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-532","guid":"1cd8877a-76e8-ce54-b40b-779af23364a0","name":"Insertion of Sensitive Information into Log File","shortDescription":{"text":"Insertion of Sensitive Information into Log File"},"helpUri":"https://cwe.mitre.org/data/definitions/532.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-829","guid":"13c33925-97fb-5a5e-b40c-56d328b8a4d7","name":"Inclusion of Functionality from Untrusted Control Sphere","shortDescription":{"text":"Inclusion of Functionality from Untrusted Control Sphere"},"helpUri":"https://cwe.mitre.org/data/definitions/829.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":"A01:2025","guid":"df693558-c822-0452-8f7b-4d53cb6bcc59","name":"Broken Access Control","shortDescription":{"text":"Broken Access Control"},"helpUri":"https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/"},{"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":"A06:2025","guid":"491554d7-b8e4-9652-91a9-53700dc92ece","name":"Insecure Design","shortDescription":{"text":"Insecure Design"},"helpUri":"https://top10.owasp.org/2025/A06_2025-Insecure_Design/"},{"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/"},{"id":"A09:2025","guid":"78892bc9-3c98-495d-881c-8af1390d643c","name":"Security Logging \u0026 Alerting Failures","shortDescription":{"text":"Security Logging \u0026 Alerting Failures"},"helpUri":"https://top10.owasp.org/2025/A09_2025-Security_Logging_and_Alerting_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-6","guid":"f2ee2486-b260-2952-a41f-6b67fa713940","name":"Insufficient Credential Hygiene","shortDescription":{"text":"Insufficient Credential Hygiene"},"helpUri":"https://owasp.github.io/www-project-top-10-ci-cd-security-risks/CICD-SEC-06-Insufficient-Credential-Hygiene"},{"id":"CICD-SEC-9","guid":"b3d36727-0395-5b51-94c4-5e173d62eab3","name":"Improper Artifact Integrity Validation","shortDescription":{"text":"Improper Artifact Integrity Validation"},"helpUri":"https://owasp.github.io/www-project-top-10-ci-cd-security-risks/CICD-SEC-09-Improper-Artifact-Integrity-Validation"}]}],"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":24,"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."]}]}