01
One view per application.
An API, a web client and a worker in three repositories are one application with three parts.
3 repositories · 1 application · 3 parts
watchdep · a watch over every layer of your dependencies
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 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.
no analytics here or in the hosted service
the theme you pick stays in your browser
fonts and icons are served from this site
plain HTML and two small scripts, for the theme
the server gets names, versions, paths and the commit
reads
01 / What it does
Each with a piece of the product in the same words and colours it uses: colour only where it means something.
01
An API, a web client and a worker in three repositories are one application with three parts.
3 repositories · 1 application · 3 parts
02
Exploited now, in production code, comes first. A theoretical flaw in a test tool waits its turn.
ranked by CISA KEV, EPSS, CVSS and where it runs
03
A source that stopped syncing or a file it could not read is itself an alert, never a clean result.
gate exits 2 when it could not look at everything
04
Who decided what about each finding and why, and whether production agrees it is fixed.
append only: no entry is changed or deleted
05
Opened in your own CI with your package manager, for the version that fixes it. A person merges.
watchdep never merges, approves or auto-merges
06
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
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"},
"node_modules/express": { "version": "4.21.2",},"node_modules/lodash": { "version": "4.17.21", "license": "MIT"},
03 / A finding
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.
04 / How it works
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.
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
Exploited now and production first. When data is missing it errs louder, labelled provisional.
Each person chooses how they hear: severe at once, high in a daily digest, the rest weekly or on screen.
A pull request per finding, opened in your own CI with your package manager. A person merges every one.
05 / Limits
06 / Get started
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.
One static binary. watchdep gate needs nothing else; watchdep scan sends the inventory to the hosted service.
The screens, the OSV mirror, the sources, alerts and the decision log, for you and the people you invite.
Runs the CLI in GitHub Actions from a pinned release whose checksum it verifies first.
07 / Questions
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.
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.
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.
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.
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.
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.