What it is
An auto-merge gate for dependency update pull requests.
What it does: For each Dependabot or Renovate pull request, depgate collects the release notes, the places in your code that use the package, the semver jump, security advisories and the CI status. One Jev call answers six typed questions. A policy then labels the pull request auto-merge, review or hold, and posts one comment that quotes the release-note lines and code locations that matter.
Why it belongs in the showcase: It puts a calibrated gate in front of an action that changes the main branch, and it reports wrong merges as the key metric.
Caveats: Partly invented and simulated evaluation inputs; author-written labels.
Evidence
Public MIT repo; the author labelled 199 real npm and PyPI version bumps of 50 packages by written rules (each paired with short invented source files, CI results simulated); on the 146 updates all three backends answered, Jev wrongly auto-merged 0 (semver rules: 10), decision accuracy 91.1% (Gemini Flash-Lite 89.0%, semver rules 57.5%), typical time 0.49 s, cost $0.061 per 1,000 updates (LLM $0.196); on all 199, Jev auto-merged 50 safe updates and no wrong ones.
Caveats
- The code that uses each package and the CI results in the evaluation are invented or simulated
- Labels follow the author's own written rules
- Auto-merge still depends on your required checks; the tool approves and enables auto-merge on your repository
Unofficial case page. Stars / list position observed for heat; do not treat heat as a quality SLA. Review the upstream README before you depend on it.