Package managers keep using git as a database, it never works out

Git repositories initially seem ideal for package registries with built-in version control and distributed architecture, but major package managers like Cargo, Homebrew, CocoaPods, and Go modules all eventually abandoned git-based indexes due to performance problems. As registries grow, git's filesystem limitations cause slow clones, expensive delta resolution, and CI bottlenecks. The pattern is consistent: start with git, hit scaling issues around directory limits and cross-platform compatibility, implement workarounds like sharding, then migrate to HTTP-based protocols or CDNs. Git lacks database features like constraints, indexes, and efficient point queries that package registries actually need.