--- title: "A GitHub for maintainers" url: https://daily.dev/posts/a-github-for-maintainers-w8lqzjr3h source_url: https://nesbitt.io/2026/05/02/a-github-for-maintainers.html type: article source: "Andrew Nesbitt" published: 2026-05-02T17:15:47.945Z updated: 2026-05-02T17:16:12.189Z tags: ["security", "open-source", "github"] reading_time: 7 upvotes: 18 comments: 1 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # A GitHub for maintainers **[Andrew Nesbitt](https://daily.dev/sources/nesbitt-io)** · 7 min read · 18 upvotes · 1 comments ## Summary A wishlist for what a next-generation code forge should offer open source maintainers, focused on cross-project coordination rather than single-repo UX improvements. Key proposals include downstream testing (running dependents' test suites against a release candidate, similar to Rust's crater runs), a feed for dependents subscribed by lockfile to receive deprecation notices and CVE alerts, smarter fork network surfacing when upstream projects go quiet, package version distribution stats on repo pages, safer CI defaults with pinned actions and isolated caches, and a forge-run package caching proxy to reduce load on public registries. The author argues GitHub has modeled only the fork relationship while ignoring the dependency relationship, which is now the primary way code is reused. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community discussion Top comments from developers on daily.dev. **@kkurko** · 1 upvotes > A feed for dependents, downstream testing and and fork networks are really good ideas — coordination between projects is what's really missing. At my current company, we have a polyrepo setup with literally tens of thousands of repositories, and understanding the relationships between them is a mentally challenging task: even though you need to know about several dozen of them, coordinating everything at such a scale without the appropriate tools is still challenging ## Similar posts on daily.dev - [What would you want from a forge?](https://daily.dev/posts/what-would-you-want-from-a-forge--yplutdgql) · Lobsters · 0 upvotes · 0 comments - [Which GitHub features are needed in a code forge before you can migrate?](https://daily.dev/posts/which-github-features-are-needed-in-a-code-forge-before-you-can-migrate--mjprularq) · Lobsters · 0 upvotes · 0 comments --- Tags: [#security](https://daily.dev/tags/security), [#open-source](https://daily.dev/tags/open-source), [#github](https://daily.dev/tags/github) [View this post on daily.dev](https://daily.dev/posts/a-github-for-maintainers-w8lqzjr3h)