[BUG]: Standard analysis silently truncates organizations with over 500 repositories

Abierto
#357 5 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@Roshnicoderr ya está trabajando en esto.

Desde el 18/10/2026.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
52/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github, javascript
Área
data, frontend

Línea de trabajo

The payload names no source files. Start by finding where OrgExplorer requests an organization's repository list without a PAT and where the 500-repository cap is applied, then check how the Overview Total Repos value and the Repositories page read that list. Reproduce with an organization over 500 public repos such as microsoft. Done means the full repository count is fetched or the Overview clearly labels the figure as partial. The four comments may hold the chosen approach, so read them first.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug
Bug Description

When exploring an organization without a GitHub PAT, OrgExplorer fetches at most 500 repositories. The Overview displays the number fetched as Total Repos, which can make this partial result look like the organization’s full repository count. Organizations with more than 500 public repositories are therefore undercounted, and their remaining repositories are missing from the Repositories page.

Steps to Reproduce
  1. Make sure no PAT is configured.
  2. Explore an organization with more than 500 public repositories, such as microsoft.
  3. Check the Overview’s Total Repos count and the Repositories page.
  4. Observe that at most 500 repositories are fetched and shown, rather than the organization’s full public repository count.
Logs and Screenshots
Image
Environment Details

OS - Windows 11

Impact

Medium - Feature works but has issues

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

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de AOSSIE-Org/OrgExplorer

Todos los issues de AOSSIE-Org/OrgExplorer

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.