[FEATURE]: Exclude bot accounts from contributor analytics and network graph
Maintainer antworten meist innerhalb von 1 Tag
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 55/100
- Issue-Typ
- Feature
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- github, javascript
- Bereich
- analytics
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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
- Vorherrschende Sprache
- JavaScript
- Sterne
- 53
- Forks
- 182
- Ø Merge
- 18 Min.
- Gemergte PRs (30 T.)
- 2
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus AOSSIE-Org/OrgExplorer
-
[BUG]: PAT popup input lacks label association and visibility button lacks an accessible nameEvtl. vergeben @prasanm1423 hat das vor 3 Tagen übernommen. Offenbug enhancement
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
AOSSIE-Org/OrgExplorer#466 · 2 Kommentare ·
Maintainer antworten meist innerhalb von 1 Tag
-
[FEATURE]: Set dynamic document.title based on active page routeEvtl. vergeben @23241a6749 hat das vor 1 Tag übernommen. Offenenhancement
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
AOSSIE-Org/OrgExplorer#462 · 2 Kommentare ·
Maintainer antworten meist innerhalb von 1 Tag
-
[BUG]: SocialShareButton logs unconditional console.warn when script is not loadedEvtl. vergeben @vivekrajputofficial29-afk hat das vor 1 Tag übernommen. Offenbug enhancement
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 89/100
AOSSIE-Org/OrgExplorer#461 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
[BUG]: governance page shows "No dead issues" before the audit has runEvtl. wieder frei @SYED-IRTEZA-HUSSAIN-RIZVI hat das vor 8 Tagen übernommen, und es ist kein Pull Request offen. Offenbug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 83/100
AOSSIE-Org/OrgExplorer#453 · 3 Kommentare ·
Maintainer antworten meist innerhalb von 1 Tag
-
[BUG]: User-controlled org/repo names are interpolated into API URLs unencodedEvtl. vergeben @AbhishekKumar-cse hat das vor 10 Tagen übernommen. Offenbug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 66/100
AOSSIE-Org/OrgExplorer#449 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in AOSSIE-Org/OrgExplorer
Ähnliche Issues
-
good first issue help wanted
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 88/100
-
tech-debt
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement frontend good first issue help wanted
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 85/100
Maintainer antworten meist innerhalb von 2 Tagen
-
marketing
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
Maintainer antworten meist innerhalb von 1 Tag
-
[功能优化] 优化首页 排行 标签页的显示Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
Maintainer antworten meist innerhalb von 1 Tag