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

Aperta
#428 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@Sandeepkg123 ci sta già lavorando.

Dal 29/10/2026.

  • #431 di @Sandeepkg123 — aperta

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
55/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github, javascript
Ambito
analytics

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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
Lingua principale
JavaScript
Stelle
53
Fork
182
Merge medio
18m
PR unite (30g)
2

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di AOSSIE-Org/OrgExplorer

Tutte le issue di AOSSIE-Org/OrgExplorer

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.