Run whatsdiff inside any git repository holding a composer.lock or a package-lock.json. The usual entry point is analyse, straight after a dependency update:
bash
whatsdiff analyse
Commands
| Command | Description |
|---|---|
analyse |
Show what changed in composer.lock and package-lock.json |
between |
Compare dependencies between two commits, branches, or tags |
check |
Answer whether one package changed, for scripts and CI |
audit |
List known security advisories affecting installed packages |
changelog |
Read release notes for updated packages |
tui |
Browse changes and changelogs in an interactive terminal interface |
config |
Get or set configuration values |
Global options
Every command accepts these:
| Option | Description |
|---|---|
-h, --help |
Display help for the command |
-V, --version |
Display the application version |
-q, --quiet |
Only display errors |
--silent |
Output nothing at all |
--ansi, --no-ansi |
Force or disable ANSI output |
-n, --no-interaction |
Never ask an interactive question |
-v, -vv, -vvv |
Increase verbosity: normal, verbose, debug |