depup

Check dependency versions across multiple ecosystems.

depup auto-detects project ecosystems in a directory tree and checks all dependencies for newer versions. It supports Maven and npm (with npm, pnpm, yarn classic, and bun package managers).

Installation

Precompiled binaries are available for macOS (Intel & Apple Silicon), Linux, and Windows.

Brew

brew tap hpehl/tap
brew install depup

Cargo

cargo install depup-cli

Build from source

1. Install Rust and Cargo
2. git clone git@github.com:hpehl/depup.git
3. cd depup
4. cargo build --release && cargo install --path .

This installs the depup binary to ~/.cargo/bin/ which should be in your $PATH.

Usage

Check

# Check current directory (auto-detects ecosystems)
depup check

# Check a specific project
depup check /path/to/project

# JSON output (for scripting)
depup check --json

# Only show outdated versions
depup check --outdated

# Exclude pre-release versions (alpha, beta, RC, milestone)
depup check --stable

# Filter by ecosystem
depup check --maven
depup check --npm

# Filter by kind
depup check --dependencies
depup check --plugins
depup check --dev-deps
depup check --tools

# Filter by version property (Maven only)
depup check --managed          # only dependencies using a version property
depup check --unmanaged        # only dependencies with plain inline versions

# Filter by artifact name (glob wildcards)
depup check --include 'org.junit:*'           # only org.junit artifacts
depup check --exclude '*:guava'               # exclude guava
depup check --include 'org.wildfly:*' --exclude '*:core'  # combine filters

Update

# Update all outdated dependencies
depup update

# Update a specific project
depup update /path/to/project

# Preview what would be updated (no changes made)
depup update --dry-run

# Only update to stable releases (exclude pre-release versions)
depup update --stable

# Filter by ecosystem
depup update --maven
depup update --npm

# Filter by kind
depup update --dependencies
depup update --plugins
depup update --dev-deps
depup update --tools

# Filter by version property (Maven only)
depup update --managed          # only update managed version properties
depup update --unmanaged        # only update inline versions

# Filter by artifact name (glob wildcards)
depup update --include 'org.junit:*'           # only update org.junit artifacts
depup update --exclude '*:guava'               # skip guava
depup update --include 'react*'                # only update react packages (npm)

# JSON output
depup update --json

For Maven, depup update rewrites version numbers in POM files while preserving all formatting, comments, and indentation. Both managed properties (${...} references in <properties> blocks) and plain inline versions (<version>5.10.0</version> inside dependency/plugin blocks) are updated.

For npm, depup update delegates to the detected package manager's native update command (npm update, pnpm update, yarn upgrade, bun update).

The exit code is 0 when all updates succeed, 1 when any update fails.

Audit

# Audit all dependencies for known vulnerabilities
depup audit

# Audit a specific project
depup audit /path/to/project

# JSON output
depup audit --json

# Filter by minimum severity level
depup audit --severity critical      # only critical vulnerabilities
depup audit --severity high          # critical + high

# Filter by ecosystem
depup audit --maven
depup audit --npm

# Filter by kind
depup audit --dependencies
depup audit --plugins
depup audit --dev-deps

# Filter by version property (Maven only)
depup audit --managed
depup audit --unmanaged

# Filter by artifact name (glob wildcards)
depup audit --include 'org.wildfly:*'
depup audit --exclude '*:guava'

The audit subcommand queries OSV.dev for known vulnerabilities in all discovered dependencies. It works for both Maven and npm ecosystems using the same unified API. Tool versions (Node.js, package manager versions) are skipped.

The exit code is 0 when no vulnerabilities are found, 1 when any are detected.

Completions

# Generate shell completions (auto-detects shell)
depup completions

# Install shell completions
depup completions --install

# Generate completions for a specific shell
depup completions fish

If both Maven and npm ecosystem projects are found in the target path, both are checked and results are combined.

Subcommands

Command	Description
check	Check dependencies for newer versions
update	Update outdated dependencies in place
audit	Audit dependencies for known vulnerabilities via OSV.dev
completions	Generate and install shell completions

Ecosystems

Maven

Scans multi-module Maven projects and checks dependency versions against upstream Maven repositories. Discovers:

• Property references — any ${...} property used as a version (e.g., ${junit.version}, ${version.wildfly}, ${my.lib.version}). The only exclusion is ${project.*} properties which are Maven built-ins.
• Plain inline versions — artifacts with hardcoded version numbers (e.g., <version>5.10.0</version>) are also checked.
• Tool versions — Node.js and package manager version properties in Maven POMs (e.g., version.node, version.npm, version.pnpm, version.yarn).

Works where Maven's versions:display-property-updates fails — when properties are defined in a parent POM but referenced in child POMs.

npm

Discovers npm ecosystem projects in the directory tree by detecting the package manager via lock file (pnpm-lock.yaml, package-lock.json, yarn.lock, bun.lock/bun.lockb) or the packageManager field in package.json. Runs the appropriate package manager's outdated command on each discovered project and aggregates results. Workspace members are skipped — only root projects are checked.

Supported package managers: npm, pnpm, yarn (classic), bun.

Example Output

  [2/4] ████████████████████████████▓░ org.junit.jupiter:junit-jupiter

  Dependencies
  ✓ org.apache.maven.plugins:maven-compiler-plugin  3.13.0    up-to-date
  → org.junit.jupiter:junit-jupiter                 5.10.0    → 5.12.2
  Plugins
  ✓ org.apache.maven.plugins:maven-javadoc-plugin   3.12.0    up-to-date
  ✓ org.mockito:mockito-core                        5.18.0    up-to-date

4 checked: 3 current, 1 outdated  (● Dependency, ■ Plugin)

Done in 1s

The exit code is 0 when all versions are current, 1 when any are outdated.

Update Output

  [1/1] ████████████████████████████████ pom.xml

  ✓ org.junit.jupiter:junit-jupiter                 5.10.0 → 5.12.2   pom.xml    updated
  ✓ org.mockito:mockito-core                         5.14.0 → 5.18.0   pom.xml    updated

2 updated  (● Dependency)

Done in 2s

Dry-run preview (depup update --dry-run):

Dry run — no changes made:
  ✓ org.junit.jupiter:junit-jupiter                 5.10.0 → 5.12.2   pom.xml    updated
  ✓ org.mockito:mockito-core                         5.14.0 → 5.18.0   pom.xml    updated

2 updated  (● Dependency)

Done in 1s

The exit code is 0 when all updates succeed, 1 when any update fails.

Audit Output

  [2/2] ████████████████████████████████ Fetching vulnerability details...

  ✓ org.wildfly:wildfly-ee                         35.0.0    pom.xml    no vulnerabilities
  ✗ com.fasterxml.jackson.core:jackson-databind     2.15.0    pom.xml    2 vulnerabilities
      [CRITICAL] GHSA-xxxx-yyyy (CVE-2024-1234)    Deserialization of untrusted data
      [HIGH]     GHSA-aaaa-bbbb (CVE-2024-5678)    Server-side request forgery

2 audited: 1 clean, 1 vulnerable (1 critical, 1 high)  (● Dependency)

Done in 3s

The exit code is 0 when no vulnerabilities are found, 1 when any are detected.

JSON Mode

Use --json for machine-readable output. Progress bars are suppressed, and errors produce structured JSON:

{"error": {"code": "POM_NOT_FOUND", "message": "No pom.xml found in /nonexistent"}}

Error codes: POM_NOT_FOUND, POM_PARSE_FAILED, HTTP_REQUEST_FAILED, CLAP_PARSE_ERROR, INTERNAL.

How It Works

Maven

1. Parses the root pom.xml and recursively follows <modules> declarations
2. For every <dependency> and <plugin>, extracts the version — either a ${...} property reference (any name, not just version.*) or a plain inline version number
3. Resolves property values from the root POM's <properties> block (supports chained references up to 10 levels)
4. Queries Maven Central for the latest version of each artifact (via maven-metadata.xml)
5. If not found on Maven Central, queries all <repositories> and <pluginRepositories> defined in the POMs in parallel
6. Compares versions using Maven-aware ordering (handles .Final, -SP1, and other qualifiers)

npm

1. Walks the directory tree finding directories with a recognized lock file or packageManager field in package.json
2. Auto-detects the package manager (npm, pnpm, yarn, or bun) from the lock file type or packageManager field
3. Skips node_modules/ and workspace members
4. Runs each package manager's list and outdated commands in JSON mode
5. Parses and aggregates results across all discovered projects

Version Filtering

By default, depup includes pre-release versions but always excludes SNAPSHOTs (Maven). Use --stable (alias --releases-only) to also exclude pre-release versions matching these patterns:

• *-alpha*, *-beta*
• *-RC*, *-CR*
• *-M* (milestones)
• *-preview*, *-dev*, *-incubating*

SNAPSHOTs are always excluded regardless of flags.

Shell Completions

Generate and install shell completions for tab-completion of subcommands and flags:

depup completions --install       # auto-detect shell, install to standard path
depup completions fish            # print fish completions to stdout
depup completions --install zsh   # install zsh completions

Supported shells: bash, zsh, fish, elvish, powershell.

Requirements

• Rust 1.85+ (edition 2024)
• Network access to Maven Central (repo1.maven.org) and any custom repositories defined in the project's POMs
• For npm ecosystem checks: the respective package manager (npm, pnpm, yarn, or bun) must be installed and on PATH

License

Apache License 2.0