Harbor is an open-source, cloud-native container registry platform for managing OCI/Docker images, Helm charts, and other artifacts. It provides a full-stack solution with a Go backend, Angular web portal, PostgreSQL database, and Redis/ValKey job queue. The system supports artifact storage, vulnerability scanning (Trivy integration), SBOM generation, multi-registry replication (Docker Hub, Quay, JFrog, cloud CRs), tag retention policies, immutable tags, RBAC with LDAP/OIDC, robot accounts, webhook/notification pipelines, P2P preheat, and audit logging. The architecture follows a layered pattern: REST API handlers (v2.0) → controllers → managers → DAOs, with middleware chains for security, quota, and content trust. Key entry points include the core API server, job service for background tasks, registry controller for blob/manifest management, and the Angular portal for administration. External dependencies include PostgreSQL, Redis, Trivy scanner, and various cloud registry APIs. The codebase is well-structured with extensive unit and integration tests, though it exhibits some technical debt from generated mocks and legacy components.
Timoni is a Kubernetes package manager CLI tool powered by the CUE configuration language. It provides a workflow for defining, packaging, and deploying Kubernetes applications as OCI-distributed modules with typed schemas, health checks, and server-side apply. The architecture is a single binary CLI implemented in Go using Cobra for commands, with core logic in internal packages for module building (CUE compilation with overlay injection), OCI artifact management (push/pull/tag/sign), instance reconciliation (dry-run, diff, apply, wait, prune), and bundle composition for multi-instance multi-cluster deployments. The system relies on Flux CD's ssa package for Kubernetes server-side apply and inventory tracking via Secrets, and integrates with Cosign for signing and verification. The codebase is well-structured with a clear separation of concerns across engine, reconciler, runtime, and oci packages, and benefits from extensive integration tests using envtest and an in-memory OCI registry. While tightly coupled to the Kubernetes and CUE ecosystems, several internal components demonstrate high craftsmanship and potential for reuse.