Rewindex

ChangesSemgrepElevated 400 Bad Request errors when completing scans with Semgrep 1.181.0

Semgrep: Incident updated: Elevated 400 Bad Request errors when completing scans with Semgrep 1.181.0

Incident updateNot classified yetChanged stspg.io (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Semgrep removed; blue is what they added. Muted text is unchanged context.

ChangedStatus#1
Before: monitoring
After: resolved
AddedResolved time#2
Before: not present
After: 2026-10-19 23:49 UTC
AddedUpdateresolved#3
Before: not present
After: This issue has been resolved.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

YesterdayMonday, October 19Mon, Oct 19

3 incident changes

All Semgrep changesSemgrep profileMarkdownJSON