Live  /  Semgrep  /  Incident

Semgrep: Incomplete Semgrep 1.176.1 release: PyPI installs cannot use Pro Engine

Semgrep · semgrep.devMajor incidentResolved2026-09-04 23:15 UTC
Public — what happened

Summary

Semgrep said that its 1.176.1 patch release went out incomplete, so anyone who installed that version through PyPI could not use the Pro Engine. The company labeled the problem major and first reported it on September 4, 2026 at 23:13 UTC. While working on a fix, Semgrep advised users to install version 1.175.1 or 1.176.0 instead. The status was still listed as investigating, though a resolution time of 23:51 the same day was also recorded.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Semgrep against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Semgrep: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Semgrep report →

More from Semgrep

Covered in The Squid’s Ink, Week 37, 2026, our weekly internet health report.

The full archive is on the Semgrep status & history page.

Related: Semgrep status & history. SquidGrid is not affiliated with Semgrep.