watchdep
Sign inSource

watchdep · a watch over every layer of your dependencies

Hear about the dependency that matters. Not the other four hundred.

watchdep watches every layer of your applications, from the packages you chose to the operating system under them, against the public sources of vulnerabilities and compromised releases. It tells the right person about what is exploited now in production code, and keeps every finding until a person has decided it.

$watchdep gatein any project: no account, no server
CI: the build fails on what is exploited now
$ watchdep gate

SEVERE  CVE-2021-44228  GHSA-jfh8-c2jp-5v3q  [fails the gate]
  Remote code injection in Log4j
  exploited now
  production, in CISA KEV since 2021-12-10, EPSS 100.0%, CVSS 10.0
  why: listed in CISA KEV: exploited now
  org.apache.logging.log4j:log4j-core 2.14.1  pom.xml  production
    fix: 2.15.0

HIGH  CVE-2021-44832  GHSA-8489-44mv-ggj8
  Improper Input Validation and Injection in Apache Log4j2
  production, EPSS 97.9%, CVSS 6.6
  why: medium (CVSS 6.6) raised by EPSS 97.9%
    fix: 2.17.1

2 severe, 2 high, 4 medium. Failing on: kev, malicious.
Failed: 2 finding(s) meet the threshold: CVE-2021-44228, CVE-2021-45046.
fig. 01 · real outputthe Log4Shell case of the known incidents corpus

reads

  • npm
  • Yarn
  • pnpm
  • Bun
  • RubyGems
  • PyPI
  • Poetry
  • uv
  • Pipenv
  • Composer
  • Go modules
  • Cargo
  • Maven
  • Gradle
  • NuGet
  • Pub
  • Hex
  • Swift
  • Debian
  • Ubuntu
  • Alpine

01 / What it does

Six things, as they look in watchdep.

Each with a piece of the product in the same words and colours it uses: colour only where it means something.

01

One view per application.

An API, a web client and a worker in three repositories are one application with three parts.

Storefront
apirails
webnode
workerpython

3 repositories · 1 application · 3 parts

02

Ranked by what is real.

Exploited now, in production code, comes first. A theoretical flaw in a test tool waits its turn.

Highlodash4.17.20 → 4.17.21
production · CVSS 7.2 · CVE-2021-23337

ranked by CISA KEV, EPSS, CVSS and where it runs

03

Never silently missing.

A source that stopped syncing or a file it could not read is itself an alert, never a clean result.

Not checked: the OSV mirror has not synced npm yet
Incomplete: some of what was found could not be read.

gate exits 2 when it could not look at everything

04

A record of decisions.

Who decided what about each finding and why, and whether production agrees it is fixed.

  1. Nov 02An admin acknowledged: moving to Spring 5.3.18 this sprint
  2. Nov 05A member accepted until 2027-01-31
  3. Nov 12An agent, for the person who connected it, acknowledged

append only: no entry is changed or deleted

05

A pull request per fix.

Opened in your own CI with your package manager, for the version that fixes it. A person merges.

#412watchdep/lodash-4.17.21
open, waiting for a person to merge

watchdep never merges, approves or auto-merges

06

A gate for every build.

The CLI alone fails a build on what is exploited now or a malicious release. No account, no server.

$ watchdep gate
Failed: 1 finding(s) meet the threshold: CVE-2021-44228.
$ echo $?
1

exit 0 clean · 1 a finding fails · 2 incomplete · 3 bad input

02 / The fix

One line in red. Then the same line in green.

A finding points at the line that brought the flaw in. It is fixed when production reports the new version, not when someone says so.

"node_modules/express": {  "version": "4.21.2",},"node_modules/lodash": {  "version": "4.17.20",  "license": "MIT"},
fig. 02 · beforepackage-lock.json · high · CVE-2021-23337
"node_modules/express": {  "version": "4.21.2",},"node_modules/lodash": {  "version": "4.17.21",  "license": "MIT"},
fig. 03 · afterfixed when production reports 4.17.21

03 / A finding

The finding, and the path it came in by.

Each finding names the part, the route through the dependency tree to the flawed package, why it has its level, and the version that fixes it. One finding per advisory per application, however many parts it appears in.

Your workspace / Storefront
1severe1high1medium0low
Severe
log4j-core remote code injection in Log4j
Exploited nowproductionCVE-2021-44228
search›log4j-core 2.14.1
Fix2.15.0
High
rack possible shell escape sequence injection
productionCVSS 10.0, EPSS 2.0%CVE-2022-30123
api›rails›actionpack›rack 2.2.3
Pull requestopen, waiting for a person
Medium
vm2 sandbox escape
development only: dropped from highCVE-2023-37466
web›vm2 3.9.17
Decidedaccepted until 2027-01-31

04 / How it works

From the inventory to the fix.

  1. Inventory

    The CLI lists every package at every depth, the runtimes, and the operating system packages of your images, with the path each came in by.

  2. Sources

    OSV, the GitHub Advisory Database, NVD, CISA KEV, EPSS and endoflife.date, mirrored and watched for silence.

    OSV and GitHub every hour · CISA KEV every 6 hours · NVD 04:00 and EPSS 15:10 UTC daily

  3. Ranking

    Exploited now and production first. When data is missing it errs louder, labelled provisional.

  4. Alerts

    Each person chooses how they hear: severe at once, high in a daily digest, the rest weekly or on screen.

  5. Fixes

    A pull request per finding, opened in your own CI with your package manager. A person merges every one.

The whole story

05 / Limits

What it never does.

The server never reads your source code. Code checks and fixes run in the CLI, where the code already is.
It never holds write access to a repository.
It never runs a package manager on the server.
It never merges, approves or auto-merges a pull request.
It never reads "could not look" as "no findings".

What it reads and stores

06 / Get started

Two pieces you run. One we run.

The CLI and the Action run where your code already is, and are MIT licensed. The hosted service keeps the findings, the alerts and the decision log.

The CLI

One static binary. watchdep gate needs nothing else; watchdep scan sends the inventory to the hosted service.

The hosted service

The screens, the OSV mirror, the sources, alerts and the decision log, for you and the people you invite.

The Action

Runs the CLI in GitHub Actions from a pinned release whose checksum it verifies first.

InstallSign up

07 / Questions

Asked before installing.

01Do I need a server to try it?

No. watchdep gate runs in any project with no account and no server. It checks the inventory against OSV, CISA KEV and EPSS directly and exits with a code a CI build can stop on.

02Does the server read my source code?

No. What leaves your machine is an inventory: package names, versions, file paths and the commit, never file contents. The code check and fixes run in the CLI, where the code already is.

03What happens when a source stops answering?

A sync that fails keeps the previous data. A source with no good sync in 24 hours is stalled: it shows in deep orange and owners and admins are alerted. Nothing it would have said is read as clean.

04Will it merge fixes for me?

No. It opens a pull request per finding from your own CI with your own package manager, and a person merges every one. watchdep never merges, approves or auto-merges.

05Can I run the server myself?

Not for now: watchdep is offered as a hosted service. The CLI and the GitHub Action are MIT licensed, and the CLI's gate needs no account at all.

06Is there a release to download?

Yes. The CLI's first release is 0.1.0: one static binary per platform with a checksums file, and the GitHub Action installs it checked against those checksums. Install shows how.