Ctrl K
ComunidadGuías…
GITHUB · ANALIZADO

repo-growth-monitor

Self-hosted GitHub repository growth analytics tool with traffic, search ranking, and star tracking. Docker Compose deployment with Java 21 + Node.js frontend.

Ficha actualizada 22 sept 2026, 19:51 · upstream 22 sept 2026, 19:39 · release v0.8.0

Ver códigoProblemas y ayudaRepositorio ↗Sitio oficial
00

Qué es repo-growth-monitor

Descripción editorial construida a partir del repositorio, su documentación y sus señales de mantenimiento.

Repo Growth Monitor provides self-hosted GitHub analytics including visitor counts, clone metrics, referrer data, search rankings, and star growth over time. Built on Spring Boot and Node.js with PostgreSQL persistence. Requires a Fine-grained Personal Access Token for repository-level access control. Ideal for developers who need to understand their own repo's performance without relying on third-party services.

CASOS DE USO
  • Track your GitHub repository's traffic growth over time
  • Monitor visitor and clone counts to gauge community interest
  • Analyze referrer sources to identify key contributors or communities
  • Measure search ranking changes relative to competitors
  • Observe star growth patterns for project visibility trends
  • Build a foundation for competitor discovery through shared metrics
PUNTOS DESTACADOS
  • Self-hosted with Docker Compose - no need to sign up for GitHub Analytics
  • Fine-grained token authentication allows selective repository tracking
  • Supports both Java backend and Node.js frontend in a single deployment
  • Planner window restricts data collection to business hours (10:00–18:00 UTC)
  • Data persists in PostgreSQL volume, allowing incremental updates without full restart
PRECAUCIONES
  • Requires GitHub Fine-grained Personal Access Token with specific permissions
  • No support for Python or other languages - only Java and Node.js
  • Search ranking data is limited to GitHub's own metrics (no external indexing)
  • Star growth tracking may be delayed by GitHub's API response times
  • Traffic data is aggregated at the repository level, not per-user
01

Perfil de infraestructura

Estimación inicial derivada del repositorio y de los servicios detectados.

CPU2 vCPUrecomendación inicial
MEMORIA2 GBRAM estimada
DISCO20 GBalmacenamiento base
COMPLEJIDADmediumnivel de operación
02

Despliegue detectado

Qué señales reales de instalación hemos encontrado.

Listo para automatizar

Deploy via Docker Compose using a Fine-grained PAT. Set POSTGRES_PASSWORD in .env. For production, use separate volumes for data persistence. The tool requires Java 21 and Node.js 18+. No Python or other languages are supported. Always set the token from environment variables - it is never stored in PostgreSQL or returned by the API.

✓Dockerfile
✓Compose
✓One-click
03

Stack y dependencias

Componentes inferidos a partir de manifests, configuración y documentación.

FRAMEWORKS
ReactNode.js
SERVICIOS
PostgreSQL
BASES DE DATOS
PostgreSQL
PUERTOS
80808082808154335432
05

Puede sustituir a

Relaciones detectadas por el análisis del repositorio y su categoría.

06

Experiencia real de la comunidad

Ayuda a contrastar la estimación automática con instalaciones reales.

Todavía no hay datos comunitarios para este proyecto.