[FEATURE]: Exclude bot accounts from contributor analytics and network graph
Los mantenedores suelen responder en 1 día
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 55/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- github, javascript
- Área
- analytics
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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
- Lenguaje dominante
- JavaScript
- Estrellas
- 53
- Forks
- 182
- Merge medio
- 18 min
- PR fusionados (30 d)
- 2
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de AOSSIE-Org/OrgExplorer
-
[BUG]: PAT popup input lacks label association and visibility button lacks an accessible namePosiblemente ocupada @prasanm1423 la tomó hace 3 días. Abiertobug enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
AOSSIE-Org/OrgExplorer#466 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
[FEATURE]: Set dynamic document.title based on active page routePosiblemente ocupada @23241a6749 la tomó hace 1 día. Abiertoenhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
AOSSIE-Org/OrgExplorer#462 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
[BUG]: SocialShareButton logs unconditional console.warn when script is not loadedPosiblemente ocupada @vivekrajputofficial29-afk la tomó hace 1 día. Abiertobug enhancement
Dificultad 1/5 Menos de una hora Aptitud para principiantes 89/100
AOSSIE-Org/OrgExplorer#461 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
[BUG]: governance page shows "No dead issues" before the audit has runQuizá libre de nuevo @SYED-IRTEZA-HUSSAIN-RIZVI la tomó hace 8 días y no hay ningún pull request abierto. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
AOSSIE-Org/OrgExplorer#453 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
[BUG]: User-controlled org/repo names are interpolated into API URLs unencodedPosiblemente ocupada @AbhishekKumar-cse la tomó hace 10 días. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
AOSSIE-Org/OrgExplorer#449 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de AOSSIE-Org/OrgExplorer
Issues similares
-
enhancement frontend good first issue help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
Los mantenedores suelen responder en 2 días
-
marketing
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
[bug]: Maximizing the Windows dashboard covers the taskbarPosiblemente ocupada @xiufengsun la tomó hoy. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 63/100
xiufengsun/TokenTracker#1152 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
parity: scripting.net's net-http row fails on macOS with errno 61 where the BDS golden has 111AbiertoBug Tests
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
JSPrismarine/JSPrismarine#3384 ·
Los mantenedores suelen responder en 1 día
-
cat:test dx effort:xs sev:low
Dificultad 1/5 1-3 horas Aptitud para principiantes 82/100
LucasSantana-Dev/Lucky#3251 ·
Los mantenedores suelen responder en 1 día