Skip to main content
Category: Developer Tools · Version: 1.0.0 · Author: OpenDirectory · Compatibility: All targets (claude, codex, opencode, gemini, anti-gravity, openclaw, hermes)
dependency-update-bot Weekly scan for outdated npm or pip packages. Fetches changelogs for each. Summarizes breaking changes with Gemini. Opens one PR per risk group.

Install

What It Does

  • Runs npm outdated --json or pip list --outdated to find outdated packages
  • Classifies each update as patch (low risk), minor (medium risk), or major (high risk) using semver
  • Fetches changelogs from GitHub Releases, CHANGELOG.md, or npm/PyPI registry as fallback
  • Uses Gemini to summarize what changed between old and new versions, flagging breaking changes
  • Creates a branch per risk group, updates the package file, and opens a PR with the changelog summary
  • Opens one PR per major update (since each major bump needs individual review)

Requirements

Setup

Fill in:
  • GEMINI_API_KEY (required)
  • GITHUB_TOKEN (optional, increases GitHub API rate limit from 60 to 5,000 requests/hour)

How to Use

Scan npm dependencies:
Scan pip dependencies:
Specific risk level only:

PR Structure

Each PR includes:
  • Risk level label (patch / minor / major)
  • For each package: version bump, changelog summary (3-5 bullets), breaking changes flagged with BREAKING prefix
  • How to verify section
One PR per risk group for patch and minor updates. One PR per package for major updates (since each breaking change needs individual review).

Risk Classification

If a patch or minor update’s changelog contains BREAKING CHANGE keywords, the bot escalates it to major automatically.

Changelog Sources

The bot tries these sources in order for each package:
  1. GitHub Releases API (best)
  2. Raw CHANGELOG.md from the repo
  3. npm registry README (fallback)
  4. PyPI project description (last resort)
If no changelog is found, the PR still includes the version bump with a note to review manually.

Project Structure

License

MIT