How jonathanchaveztamales/llm-leaderboard works
Project type and purpose
• This is a “static data + schema repository” that feeds an interactive dashboard (llm-stats.com).
• No traditional MVC backend: data lives as JSON, validated via JSON Schema and Node.js scripts; front-end is a static site (hosted on a CDN).
File structure
• Top-level:
• data/ – JSON files (models, providers, benchmarks, organizations, licenses)
• schemas/ – JSON Schema files + validator scripts
• results-validator/ – CLI or helper code for validating result sets
• package.json – Node.js tooling for validation and build
• .github/workflows/schema-validation.yml – CI workflow for running validators
• No src/frontend folder here: the site itself likely lives elsewhere or is built via another pipeline reading these files.
Main components
a. Contributors & Maintainers
b. GitHub Repository (Data + Schemas + Validation scripts)
c. CI/CD (GitHub Actions)
d. Validator Service (Node.js JSON-Schema checks)
e. Deployment Target (Static-site hosting or CDN)
f. End-User Client (Browser running the dashboard)
Relationships and interactions
• Contributor opens a Pull Request → GitHub Actions triggers schema and integrity validation → Validator scripts run against data/ JSON using schemas/ → If validation passes, PR can merge.
• On merge (main branch): GitHub Actions or another workflow builds/deploys the static site (pulls data folder, bundles it, publishes to hosting).
• End-user’s browser fetches static assets (HTML/CSS/JS) + JSON data from the CDN, then renders the interactive dashboard.
Architectural patterns & design principles
• Static-Site Generation pattern: treat JSON files as data source, build artifacts served on CDN.
• CI/CD pipeline ensures data integrity before merge or deploy.
• Schema-first design: all JSON must conform to schemas/ via automated validation.
• Separation of concerns:
• Data storage (data/)
• Data validation (schemas/, results-validator/)
• Build & deploy (GitHub Actions)
• Consumption (static site + client)
Technologies & frameworks
• GitHub Actions (.github/workflows/schema-validation.yml) for CI.
• Node.js (package.json) & JSON-Schema (schemas/*.schema.json + validator.js).
• JSON files served over HTTP from a CDN or GitHub Pages/custom domain.
• Front-end (not in this repo) likely a JS framework fetching these JSON endpoints.