Find and fix the issues that matter in your code (SAST)
Fix vulnerabilities in open source dependencies and block malware
Find and fix hardcoded secrets with semantic analysis
Scan and fix AI-generated code the moment it's written
Combine AI reasoning with rule-based analysis for detection, triage, and remediation
Automate, manage, and enforce security across your organization
Build and deploy security pipelines that combine static analysis with AI at scale
Stay up to date on changes to the Semgrep platform, big and small
Protect against software supply chain attacks
Increase security while accelerating development
Prevent the most critical web application security risks
Protect Your Code with Secure Guardrails
Mitigate software supply chain risks
Increase security while accelerating development
Want to read all the docs? Start here
Get the latest news about Semgrep
See how Semgrep can save you time and money
Join the friendly Slack group to ask questions or share feedback
Join us at a Semgrep Event!
See why users love Semgrep
View our library of on-demand webinars
Dependency path shows how a vulnerable package reached your project, tracing the chain from your app to the direct dependency to the transitive one, so teams can prioritize and remediate faster. That view has been available in the app and the API, but teams that consume Supply Chain results directly from the CLI had no way to see it there. Semgrep 1.168 adds the --x-dependency-paths flag, so CLI users now get dependency paths alongside any reported vulnerabilities.