[FEATURE]: Exclude bot accounts from contributor analytics and network graph
维护者通常 1 天内回复
评估
- 难度
- 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 内容生成。
描述
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 分钟
- 30 天内合并 PR
- 2
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
AOSSIE-Org/OrgExplorer 的其他 Issue
-
[BUG]: PAT popup input lacks label association and visibility button lacks an accessible name可能已有人在做 @prasanm1423 于 3 天前认领。 未关闭bug enhancement
难度 2/5 1-3 小时 新手友好度 78/100
AOSSIE-Org/OrgExplorer#466 · 2 条评论 ·
维护者通常 1 天内回复
-
[FEATURE]: Set dynamic document.title based on active page route可能已有人在做 @23241a6749 于 1 天前认领。 未关闭enhancement
难度 2/5 1-3 小时 新手友好度 78/100
AOSSIE-Org/OrgExplorer#462 · 2 条评论 ·
维护者通常 1 天内回复
-
[BUG]: SocialShareButton logs unconditional console.warn when script is not loaded可能已有人在做 @vivekrajputofficial29-afk 于 1 天前认领。 未关闭bug enhancement
难度 1/5 1 小时以内 新手友好度 89/100
AOSSIE-Org/OrgExplorer#461 · 1 条评论 ·
维护者通常 1 天内回复
-
[BUG]: governance page shows "No dead issues" before the audit has run可能重新可做 @SYED-IRTEZA-HUSSAIN-RIZVI 于 8 天前认领,目前没有进行中的 PR。 未关闭bug
难度 2/5 1-3 小时 新手友好度 83/100
AOSSIE-Org/OrgExplorer#453 · 3 条评论 ·
维护者通常 1 天内回复
-
[BUG]: User-controlled org/repo names are interpolated into API URLs unencoded可能已有人在做 @AbhishekKumar-cse 于 10 天前认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 66/100
AOSSIE-Org/OrgExplorer#449 · 1 条评论 ·
维护者通常 1 天内回复
查看 AOSSIE-Org/OrgExplorer 的全部 Issue
相似的 Issue
-
enhancement frontend good first issue help wanted
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 2 天内回复
-
marketing
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
[bug]: Maximizing the Windows dashboard covers the taskbar可能已有人在做 @xiufengsun 今天认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 63/100
xiufengsun/TokenTracker#1152 · 1 条评论 ·
维护者通常 1 天内回复
-
Bug Tests
难度 2/5 1-3 小时 新手友好度 78/100
JSPrismarine/JSPrismarine#3384 ·
维护者通常 1 天内回复
-
cat:test dx effort:xs sev:low
难度 1/5 1-3 小时 新手友好度 82/100
LucasSantana-Dev/Lucky#3251 ·
维护者通常 1 天内回复