Source
Dependencies (SCA), licences & secrets — found from sitemap — Endor Labs
Checked for Endor Labs on 6 Nov 2026
- Page
- https://docs.endorlabs.com/scan/sca/reachability-analysis
- Checked
- 6 Nov 2026, 05:06 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:a188edd1fa6150a320d36a19727320db1a6a767f2160f8ef1b6babb0db4f0e91
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Reachability function level Report an error
“Endor Labs uses a static analysis technique called program analysis to perform function-level reachability analysis on direct and transitive dependencies. This is the most accurate way to determine exploitability in the context of your application”
-
Reachable function label Report an error
“Reachable Function: Endor Labs has determined that there is a path from the developer-written code to a vulnerable function, indicating that the finding is exploitable in your environment.”
-
Unreachable function label Report an error
“Unreachable Function: Endor Labs determines that no risk of exploitation exists, as no path exists from the source code to the vulnerable function.”
-
Potentially reachable function label Report an error
“Potentially Reachable Function: Endor Labs is unable to determine whether a finding is reachable or unreachable, typically because call graph analysis is unsupported for a given language or package manager.”
-
Dependency level reachability default Report an error
“Endor Labs supports dependency-level reachability by default for all supported languages.”
-
Dependency reachable label Report an error
“Reachable Dependency: Endor Labs established that an imported package is being used somewhere in the application.”
-
Dependency unreachable label Report an error
“Unreachable Dependency: Endor Labs determined that the imported dependency is not being used. The customer can use this information to remove the dependency, which is helpful for technical debt reduction initiatives.”
-
Dependency potentially reachable label Report an error
“Potentially Reachable Dependency: Endor Labs cannot definitively determine whether the application uses a dependency, generally because Endor Labs does not support the given language or package manager.”
-
Function level requirements Report an error
“Function-level Successful project build and client call graph generation”
-
Dependency level requirements Report an error
“Dependency-level Dependency resolution and import analysis only”
-
Precomputed reachability Report an error
“Pre-computed reachability: A pragmatic, manifest-based analysis technique that enables you to assess whether vulnerabilities in transitive dependencies could be reachable from your direct dependencies—all without requiring code compilation, builds, or full call graph generation.”
-
Precomputed transitive share Report an error
“With approximately 95% of vulnerabilities existing in transitive dependencies according to Endor Labs’ State of Dependency Management report”
-
Phantom dependencies detection Report an error
“Endor Labs’ reachability analysis conducts thorough scans of your codebase to identify functions and methods that both declared and undeclared dependencies invoke. By analyzing the actual usage of packages in your source code, the system identifies phantom dependencies—those that your code uses but does not explicitly declare.”
-
Dependency types Report an error
“Projects contain two types of dependencies, direct and transitive.”
Scores citing this record
- The Application Security Engineer Dependencies (SCA), licences & secrets
- The Engineering Manager Dependencies (SCA), licences & secrets
- The Lead Developer Dependencies (SCA), licences & secrets
- The Platform Engineer Dependencies (SCA), licences & secrets
- The Product Security Officer Dependencies (SCA), licences & secrets
- The Skeptic Dependencies (SCA), licences & secrets