Change-risk score
This change sits in the top third of this repository's own risk distribution, the band worth reviewing closely. It is riskier than 99% of this repository's own commits.
The largest health movement is in content_contract.rs, down 0.2. Nothing outside this PR depends on a contract it changed.
Every file in the repository, grouped into its own directories and sized by lines. The ones this PR changes are lit, and everything that imports them is marked.
Drawing 574 of 748 files at a readable size, grouped by directory and sized by lines of code. 10 changed here reach 11 more by import. 174 are too small to see at this width, which is what the frame below is for.
220 files, 7 changed by this PR and 11 that import one. Click any directory above to frame it instead.
Introduced findings are the ones inside the lines this PR added, not the file's existing ones. The resolved column is the only place in the product that lists them.
if condition combines 7 boolean operators
evaluate is 203 lines long
evaluate has cyclomatic complexity 32
if condition combines 4 boolean operators
if condition combines 4 boolean operators
if condition combines 4 boolean operators
validate_rendered_candidate has cyclomatic complexity 9
validate_provenance has cyclomatic complexity 10
validate_v2 has cyclomatic complexity 9
validate_authority_event_bytes has cyclomatic complexity 11
validate_catalog has cyclomatic complexity 11
detect_presence has cyclomatic complexity 14
render_candidate takes 7 parameters
if condition combines 3 boolean operators
if condition combines 3 boolean operators
unwrap/expect turns a recoverable error into a crash
evaluate has 3 nested blocks at the same level (bumpy road)
10% of file duplicated; worst clone shares 17 lines with crates/code-intel-cli/src/workflow_recommendation_contract.rs
unwrap/expect turns a recoverable error into a crash
unwrap/expect turns a recoverable error into a crash
unwrap/expect turns a recoverable error into a crash
validate_action is 67 lines long
validate_rendered_candidate is 67 lines long
validate_v2 is 77 lines long
validate_catalog is 63 lines long
unwrap/expect turns a recoverable error into a crash
unwrap/expect turns a recoverable error into a crash
unwrap/expect turns a recoverable error into a crash
unwrap/expect turns a recoverable error into a crash
unwrap/expect turns a recoverable error into a crash
unwrap/expect turns a recoverable error into a crash
unwrap/expect turns a recoverable error into a crash
unwrap/expect turns a recoverable error into a crash
unwrap/expect turns a recoverable error into a crash
unwrap/expect turns a recoverable error into a crash
unwrap/expect turns a recoverable error into a crash
unwrap/expect turns a recoverable error into a crash
unwrap/expect turns a recoverable error into a crash
unwrap/expect turns a recoverable error into a crash
unwrap/expect turns a recoverable error into a crash
a blocking filesystem call runs on a hot, request-reachable path; its latency is paid on every call through this function
a blocking filesystem call runs on a hot, request-reachable path; its latency is paid on every call through this function
a blocking filesystem call runs on a hot, request-reachable path; its latency is paid on every call through this function
a blocking filesystem call runs on a hot, request-reachable path; its latency is paid on every call through this function
a blocking filesystem call runs on a hot, request-reachable path; its latency is paid on every call through this function
a blocking filesystem call runs on a hot, request-reachable path; its latency is paid on every call through this function
a blocking filesystem call runs on a hot, request-reachable path; its latency is paid on every call through this function
a blocking filesystem call runs on a hot, request-reachable path; its latency is paid on every call through this function
a blocking filesystem call runs on a hot, request-reachable path; its latency is paid on every call through this function
a blocking filesystem call runs on a hot, request-reachable path; its latency is paid on every call through this function
a blocking filesystem call runs on a hot, request-reachable path; its latency is paid on every call through this function
The primary author of each changed file by share of its recent commits, mined from git history. Advisory: it says who has context, not who must review.
This page came from an index of 2233admin/code-intel-pipeline. No model calls, no configuration, and it refreshes on every push. Install the bot and every pull request gets one of these.