Dynamic Maven & Gradle dependency resolution impaired

Incident Report for Semgrep

Resolved

Dynamic maven & gradle scans are now operating as normal.
Posted Sep 03, 2026 - 00:10 UTC

Monitoring

The third party registry's rate limits have been lifted, and impact to scans appears mitigated.
Posted Sep 02, 2026 - 16:25 UTC

Update

Under one percent of supply chain scans that dynamically resolve dependencies for gradle and maven projects have been failing, due to rate limiting applied by a third-party package registry.

Affected projects may show incomplete or missing Supply Chain findings. We are rolling out a caching mirror to reduce the impact of these rate limits. Subsequent scheduled scans should resolve any impacted findings. No further action from customers is required at this time
Posted Sep 01, 2026 - 22:55 UTC

Identified

A small number (

Affected projects may show incomplete or missing Supply Chain findings. We are rolling out a caching mirror to reduce the impact of these rate limits. Subsequent scheduled scans should resolve any impacted findings. No further action from customers is required at this time.
Posted Sep 01, 2026 - 22:50 UTC
This incident affected: semgrep.dev (Managed Scans).