CodesWhat/drydock — Open source container update monitoring — 23 registries, 20 notification triggers, audit log, OIDC a…

Description and use

**Brief Summary**
CodesWhat /drydock is an open‑source observability platform that monitors container image updates across 23 registries, fires up to 20 different notification triggers, and records every change in an audit log. It ships with OIDC authentication, Prometheus metrics, and a modern dashboard, all built in TypeScript.

**Value**
Drydock gives teams a turnkey way to keep their container fleets secure and compliant without writing custom polling scripts or stitching together disparate tools. By surfacing real‑time update signals, it enables rapid prototyping of AI‑driven workflows (e.g., RAG pipelines or autonomous agents) that react to new images, while the built‑in metrics and audit trail satisfy DevOps, security, and compliance requirements.

**Practical Adoption Path**

1. **Evaluate** – Clone the repo, run the Docker‑compose demo, and verify that the registries and notification channels you need are supported.
2. **Integrate** – Use the provided REST API/SDK or CLI to embed update events into your CI/CD or AI orchestration pipelines.
3. **Secure** – Configure OIDC for single‑sign‑on and set up Prometheus scraping for observability.
4. **Deploy** – Scale the service with Helm/Kustomize in a Kubernetes cluster, and point your existing alerting (PagerDuty, Slack, etc.) to the chosen triggers.

**Production Readiness**
The project scores 78/100, shows recent activity (last commit 2026‑06‑22), has 203 GitHub stars, and is actively used in several OSS pilots. Its core features (registry polling, audit logging, auth, metrics) are mature, and the TypeScript codebase is well‑structured. While the license and long‑term maintainer commitment still need a final check, the overall signal set (high adoption, robust feature set, clear documentation) makes Drydock a solid candidate for a production pilot in container‑centric environments.

Problem

CodesWhat/drydock helps add AI capability without starting from a blank model stack.

Outcome

High for an OSS candidate: recent activity, adoption, and ecosystem signals are strong enough for a serious pilot.

Workflow

• prototype AI features
• build RAG or agent workflows
• evaluate model tooling

Evidence

Open source container update monitoring — 23 registries, 20 notification triggers, audit log, OIDC auth, Prometheus metrics, and a modern dashboard.

Source