Related to useblacksmith/bazel-remote

View on GitHub ↗

Repositories that share contributors with useblacksmith/bazel-remote, which has 1 in the loaded window. A contributor is someone who pushed, opened a pull request or issue, reviewed, or commented — stars and forks do not count, or a repository would be related to everything its stargazers ever starred.

Partial coverage11,441 / 12,380 hourly files (92%) · 2 absent upstream · 937 failed, retryable2025-03-13 → 2026-08-10 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.

Automation is excluded, and that is what makes this useful. CI accounts, dependency updaters and mirroring jobs touch millions of repositories. Counted, every repository shares contributors with every other one and this becomes a list of whatever is busiest. Accounts matching the bot conventions are left out on both sides of the comparison.

None of useblacksmith/bazel-remote's 1 contributors has worked on another repository in the loaded window. That is common early in a backfill — overlap needs both projects to be active in the same dates, so this fills in as more of the window loads.

Overlap is computed over the loaded window only, so two projects that share a team but were active in different months will not appear related. Forks show up here by design — they genuinely share contributors — and are usually recognisable by carrying the same repository name under a different owner. Data health covers what the window does and does not capture.