[FEATURE]: Exclude bot accounts from contributor analytics and network graph

オープン
#428 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@Sandeepkg123 がすでに取り組んでいます。

2026年10月29日 から。

  • #431 @Sandeepkg123 による — オープン

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
55/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
github, javascript
領域
analytics

調査の方向性

Start by reading src/services/analytics.js, especially buildAnalyticalModel, and trace how its contributor data feeds repository and organization metrics. The issue proposes filtering accounts with type === "Bot" or a [bot] login suffix, with unit tests for filtering, connectors, bus-factor calculations, and unchanged results without bots. Done means those analytics consistently exclude identified bots while preserving human contributors; the open question about other automation accounts may need maintainer input.

索引モデルが issue の本文から書いたものです。

説明

enhancement
Feature and its Use Cases
Description

OrgExplorer uses GitHub's contributors API to build contributor analytics and visualize relationships between contributors and repositories. However, bot accounts such as dependabot[bot] may be processed alongside human contributors.

This can distort contributor counts, connector detection, bus-factor calculations, repository health diversity, and the contributor network graph, resulting in misleading insights about human collaboration and dependency on individual contributors.

Expected Behavior
  • Bot accounts should be excluded from human-focused contributor analytics by default.
  • Bots should not inflate human contributor counts or qualify as connectors merely because they contribute across multiple repositories.
  • Bot contributions should not distort repository-level or organization-level bus-factor calculations.
  • Bot accounts should not appear as nodes in the human contributor network graph.
  • Metrics should be computed over human contributors only; results for repositories without bots should remain unchanged.
Proposed Solution

Introduce a shared bot-detection helper that identifies accounts using GitHub's type === "Bot" field and, as a fallback, login names ending in [bot].

Apply the filtering at the beginning of buildAnalyticalModel in src/services/analytics.js, so contributor counts, connector detection, bus-factor calculations, health-diversity metrics, and the contributor network graph all consume the same filtered contributor data.

Add unit tests covering:

  • Exclusion of accounts with type: "Bot".
  • Exclusion of accounts with a [bot] login suffix when the type is missing.
  • Preservation of human contributors and existing analytics for repositories without bots.
  • Correct connector detection and bus-factor calculations when bot accounts are present.
  • Consistent filtering across repository-level and organization-level analytics.
Related Work

[PR #300](https://github.com/AOSSIE-Org/OrgExplorer/pull/300) handles anonymous contributor logins to prevent HTTP 422 errors in contributor intelligence. This proposal addresses a different concern: excluding identifiable bot accounts from human-focused analytics.

Open Question

Should bot accounts be excluded from all human-focused analytics by default, or should certain metrics retain automation activity for separate analysis?

Some automation accounts, such as renovate-bot, may use regular GitHub User accounts rather than the Bot type or a login ending in [bot]. Should these accounts be handled through a configurable allowlist or exclusion list in a future enhancement?

Checklist
  • I have searched existing issues and pull requests for duplicates.
  • I have reviewed related work, including PR #300.
  • I have joined the project's Discord community.

I'd like to work on this if the proposal is approved. I'm happy to clarify the intended bot-filtering behavior with the maintainers before starting implementation.

Additional Context

No response

Code of Conduct
  • I have joined the Discord server and will post updates there
  • I have searched existing issues to avoid duplicates
主要言語
JavaScript
スター
53
フォーク
182
平均マージ
18分
マージ済み PR(30日)
2

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

AOSSIE-Org/OrgExplorer のほかの issue

AOSSIE-Org/OrgExplorer の issue をすべて見る

似ている issue

JavaScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。