request_impact
Read-onlyIdempotent
Identify the impact of code findings by mapping them to entry points such as HTTP routes, Celery tasks, and signals, enabling prioritized fixes based on actual reachability.
Instructions
Every finding, grouped by the entry points that actually reach it.
The other checks answer "where is this defect". A few hundred correct
entries sorted by severity still does not say where to start, because risk
is severity times how often the code runs and nothing in the list says
whether a line is on the path of an endpoint served ten thousand times an
hour or of a command last run in 2023.
This runs the checks, maps each finding to the function containing it, and
walks the call graph backwards to the HTTP routes, Celery tasks, signal
receivers and management commands that reach it. Each finding carries the
path taken to it.
`unattributed` means no entry point this can see reaches the finding. It
does not mean unreachable and it does not mean safe - a plain Django
function view carries no decorator and belongs to no view class.
Args:
search_path: directory to scan. Defaults to the configured project.
max_depth: how many callers to walk back through.
tenant_root: passed to the ownership check when this runs the checks.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| max_depth | No | ||
| search_path | No | ||
| tenant_root | No | auth.User |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||