Telemetry Categories#
The 47+ telemetry engines are organized into 5 functional categories:
- GitHub Activity: Readme stats, streak counters, contribution activity graphs, ISO calendars.
- Coding Metrics: WakaTime language distributions, daily coding time, commit velocity radars.
- Achievements & Gamification: GitHub profile trophies, LeetCode stats, Codeforces ratings.
- Visual Banners & Caps: Capsule renderers, dynamic profile views counters, header borders.
- Tech Stack & Badges: Shields.io flat-square badges, SkillIcons grids, Devicons stacks.
Top Engines Reference#
1. 3D Isometric Commit Skyline (`isometric-calendar`)#
- Source:
https://github-profile-3d-contrib.vercel.app/api - Parameters:
username,theme(default:dark). - Output: 3D extruded voxel representation of yearly contribution counts.
2. GitHub Readme Stats (`github-stats`)#
- Source:
https://github-readme-stats.vercel.app/api - Parameters:
username,show_icons=true,theme=tokyonight,rank_icon=github. - Output: Total stars, commits, PRs, issues, and contribution grade (A+ to F).
3. WakaTime Programming Metrics (`wakatime-stats`)#
- Source:
https://github-readme-stats.vercel.app/api/wakatime - Parameters:
username,layout=compact,theme=radical. - Output: Verified language percentages over the last 30 days.
Camo CDN Caching Considerations#
GitHub Camo caches external images based on the Cache-Control header sent by the telemetry server. If a telemetry engine sets:
HTTP
GitHub Camo will re-fetch the image every 4 hours. All MonoForge telemetry engines configure optimal cache headers balancing freshness with API rate limit conservation.