A terminal dashboard for your dev.to portfolio, built on top of devdash. It shows an overview of your published articles plus three live leaderboards: Most Liked, Most Viewed, and Most Commented.
devdash is a config-driven terminal dashboard with widgets for services like GitHub,
Google Analytics, Travis CI, etc. — but no dev.to/Forem support out of the box, and
the upstream project has been archived since 2023. Instead of forking it, this repo
uses devdash's local host command widget (lh.table), which runs an arbitrary
shell command and renders its stdout as a real bordered table.
devto-stats/— a small Go program that calls the dev.to API (GET /api/articles/me), paginates through all of your articles, and prints sorted, table-ready rows.devdash.yml— the dashboard layout: one summary row plus three side-by-side leaderboard tables, each backed by adevto-statsinvocation.devdash/— a local clone of upstream devdash, built from source (fetched bymake setup, not vendored into this repo).
Two things worth knowing if you poke at the code:
- devdash refreshes all widgets concurrently on every cycle, which is enough
concurrent load to trip dev.to's API rate limit (
429).devto-statsretries with backoff + jitter to absorb that. - devdash's table widget rejoins each row with commas internally and re-splits the
whole batch on commas to build cells — so a literal comma in an article title
would silently shift every row after it by one column.
devto-statsstrips commas (and slugifies whitespace) out of titles before printing them.
Requires Go (to build both binaries) and Git.
git clone https://github.com/lovestaco/devto_devdash.git
cd devto_devdash
make setup # clones + builds devdash, builds devto-stats, creates .envEdit .env and set your dev.to API key (generate one at
https://dev.to/settings/extensions):
DEVTO_API_KEY=your_dev_to_api_key_here
make runCtrl+R— force refreshCtrl+C— quit- Auto-refreshes every 5 minutes (
general.refreshindevdash.yml)
Other targets: make build (rebuild binaries), make clean (remove ./bin).
.env,./bin, and the cloneddevdash/source are all gitignored — the API key never gets committed, and devdash is treated as a build dependency rather than vendored code.devto-statsonly countspublishedarticles, and reads reactions, views, and comments straight from the Forem API's own fields (positive_reactions_count,page_views_count,comments_count).
I'm Maneshwar, and alongside peektea I'm building git-lrc — a micro AI code reviewer that runs on every commit.
It hooks into git commit, reviews every diff before it lands, and catches the bugs AI agents introduce silently. 60-second setup.
AI agents write code fast.
They also silently remove logic, change behavior, and introduce bugs — without telling you.
You often find out in production.
git-lrc fixes this.
Any feedback or contributors are welcome.
⭐ Star git-lrc on GitHub to help other devs discover it.