Semgrep: Some scans failing with exit code 7
Timeline of updates
- resolved
This issue has been resolved. No new Managed Scans since the fix have encountered an unexpected exit code 7. If you are not using Managed Scans and encounter an unexpected scan exit code 7, please re-attempt the scan with Semgrep version 1.142.3 or earlier. If you continue to encounter issues, contact Semgrep Support.
From Semgrep’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.semgrep.dev (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Semgrep, started 2025-11-24 18:52 UTC, resolved after 4.6 h, 1 update(s).
- Title
- Some scans failing with exit code 7
- Vendor
- Semgrep
- Date
- URL
- https://rewindex.com/company/semgrep/incidents/7tqx8lryhkz8
Semgrep profileRecent Semgrep incidentsAll outages on November 24, 2025Semgrep in November 2025MarkdownJSON