goharbor/harbor

This system is a container image registry and security platform that manages the lifecycle of container images, Helm charts, and other artifacts. It provides comprehensive features for artifact storage, replication, and scanning, alongside robust access control and audit logging capabilities. The codebase has been significantly refactored to modernize its architecture, replacing legacy frameworks with modular Go controllers and a new templating system for configuration management.

This period focused on a comprehensive architectural overhaul, replacing the legacy Beego framework with a modern Go-based API and service layer. The work involved removing obsolete authentication plugins, legacy deployment scripts, and outdated static assets, while introducing pluggable authentication providers and a new job service v2. Security was strengthened by enforcing non-root container users, implementing header-based secret validation, and centralizing configuration and role constants.

79 changes

This period focused on refactoring the codebase's core architecture, introducing a new modular controller pattern for managing artifacts, projects, and repositories. It also involved rebuilding the jobservice with a Redis-backed worker model and establishing a new, Python-based configuration and migration framework for deployment and upgrades.

97 changes

This period focused on modernizing the codebase by introducing a new controller-based architecture for managing system resources, users, and jobs. It also involved centralizing configuration management with a templated, type-safe approach and migrating the cache backend from Redis to Valkey.

57 changes

goharbor/harbor was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.