joern-slice

To extract a program slice, you provide the target function name and the relative file path to the joern-slice tool. It uses static analysis to identify the specific file paths and line numbers influencing that function.

Yes, you need a pre-generated CPG binary to perform data flow analysis. The joern-slice command-line utility requires this pre-existing Code Property Graph to function within its sandboxed environment.

Static code slicing isolates the specific lines of code that influence a sensitive function during a security audit. This allows you to focus your analysis on relevant logic and data flow rather than reviewing the entire project.

Automated code slicing helps with debugging by tracing data flow and dependencies within complex codebases. It automatically identifies the relevant code nodes and line numbers for a given function, reducing manual tracing effort.

No, you cannot use this tool without its dependencies. It requires both the joern-slice command-line utility and python3 to execute static analysis and extract program slices in the sandboxed environment.

A limitation is that Joern-based dependency tracking requires a pre-generated CPG binary before execution. Additionally, the tool operates within a sandboxed environment, which may restrict direct file system interactions.