ChangesSemgrepDelay in findings being updated
Semgrep: Incident updated: Delay in findings being updated
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.
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.
Before captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
be0f56bb3ece8326…After captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
3a4941425458ba92…
History of this incident
Tuesday, October 27
1 incident change
- Normal progressIncident
Incident updateDelay in findings being updatedthis change
Cite this
Incident updated: Delay in findings being updated on Semgrep’s status page, changed 2026-10-27 18:13 UTC (change 1 of 1).
- Title
- Incident updated: Delay in findings being updated
- Vendor
- Semgrep
- Date
- URL
- https://rewindex.com/change/r10a2ec8b71dda7