Elevated 400 Bad Request errors when completing scans with Semgrep 1.181.0 — Semgrep Incident Timeline & Status

Try DevHelm Uptime

Semgrep Status

Elevated 400 Bad Request errors when completing scans with Semgrep 1.181.0

Started

Oct 19, 9:00 PM UTC

Resolved

Oct 19, 11:49 PM UTC

Duration

2 hrs 48 min

Resolvedminor impactVendor link

Affected:Scans and CI/CD

Update timeline

ResolvedOct 19, 11:49 PM

This issue has been resolved.

MonitoringOct 19, 11:05 PM

We have released a fix for this issue and are monitoring to confirm resolution.

IdentifiedOct 19, 9:20 PM

We have identified the issue and are working on a fix.

InvestigatingOct 19, 9:00 PM

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.