> ## Documentation Index
> Fetch the complete documentation index at: https://docs.endorlabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Call graphs

> Mitigate open source vulnerabilities with call graph visualizations, pinpointing and understanding the invocation of vulnerable methods for actionable developer insights.

Endor Labs has developed a systematic approach to conduct call graph analysis. Here is a structured overview:

* **Scope Expansion**: Traditional methods of static analysis typically analyze a single project at a time. Endor Labs, however, expands its scope to include not only the client projects but also their dependencies, often comprising over 100 packages.

* **Enhanced Dependency Analysis**: Endor Labs employs static call graphs to conduct detailed dependency analysis, enabling a comprehensive understanding of how different external components interact within client projects. By leveraging these call graphs, Endor Labs aims to minimize false positives and more accurately identify the specific locations of problems in dependencies.

* **Multiple Data Sources**: Endor Labs uses both source code and binary artifacts to enrich the analysis. This approach returns results quickly and doesn't rely on test coverage. For languages other than Java and .NET, methods without a definition in the call graph are treated as public entry points during reachability stitching.

* **Benchmarking for Continuous Improvement**: Endor Labs maintains accuracy and relevance by using dynamic call graphs internally to benchmark and refine static call graphs, thereby actively identifying and addressing gaps.

* **Scalability**: Endor Labs addresses the challenge of scalability and generates call graphs not only for each project release but also for all its dependencies. This approach effectively manages large projects with multiple versions, ensuring that the analysis remains both relevant and applicable across the entire spectrum of client dependency sets.

For more information, see [Visualizing the impact of call graphs on open source security](https://www.endorlabs.com/learn/securing-code-with-beautiful-call-graph-visualizations).

Endor Labs uses static call graphs to perform dependency analysis at a fine-grained level. It is minimally intrusive to the developer workflow and provides results during development.

The Endor Labs user interface provides visualizations of call graphs that annotate vulnerability data and simplify it into informative call paths. This helps developers identify and address problematic invocations of vulnerable methods efficiently.

Endor Labs supports call paths for `Java`, `Python`, `Rust`, `JavaScript`, `Go`, `.NET (C#)`, `Kotlin`, `Scala`, and `Ruby`.

### View call paths

A call path is the sequence of function calls that connects your code to a specific function in a dependency. It shows how a vulnerable method gets invoked, so you can pinpoint where and how a vulnerability is reachable in your project.

To view call paths for a specific finding:

1. Select **Projects** from the left sidebar.
2. Select the project for which you want to view the call path.
3. Select **FINDINGS** and select the finding from the list view.
4. Expand a specific finding to view more details.
5. In the details section, select **CALL PATHS**.

   A finding may have multiple call paths.

   ![Call Paths](https://mintcdn.com/endorlabs-b4795f4f/Uc3T4mPoaFbRUPbf/images/scan/sca/call-path.webp?fit=max\&auto=format\&n=Uc3T4mPoaFbRUPbf\&q=85\&s=9e26b0e55b175a7dbf025090725753b0)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.