Elevated 400 Bad Request errors when completing scans with Semgrep 1.181.0

Incident Report for Semgrep

Resolved

This issue has been resolved.
Posted Oct 19, 2026 - 23:49 UTC

Monitoring

We have released a fix for this issue and are monitoring to confirm resolution.
Posted Oct 19, 2026 - 23:05 UTC

Identified

We have identified the issue and are working on a fix.
Posted Oct 19, 2026 - 21:20 UTC

Investigating

Some scans with Semgrep 1.181.0 are unable to be successfully reported to the Semgrep AppSec Platform due to a 400 error. The issue may be related to dynamic dependency resolution.
Posted Oct 19, 2026 - 21:00 UTC
This incident affected: semgrep.dev (Scans and CI/CD).
← Current Status Powered by Atlassian Statuspage