octoscope v0.19.0 — freshness & correctness 🔭
Two honesty fixes this round: octoscope now tells you when a newer version is out, and it counts your whole account instead of just the first 100 repositories.
The update notice
On launch — and hourly after that, on its own timer separate from the dashboard refresh — octoscope checks the public Releases API and, if there's something newer, drops a quiet one-line notice under the banner. The upgrade command is context-aware: it detects how you installed octoscope and suggests the right one — brew upgrade, go install, gh extension upgrade, or a download link.
It never self-updates. The package manager owns the binary, and auto-overwriting it would fight brew/gh/go and break octoscope's read-only model. The check is cheap — one free request, cached on disk so short repeated sessions don't re-poll — and silent on failure, because a flaky check shouldn't nag you. Turn it off with check_for_updates = false; it's also suppressed under --public-only.
Accurate totals past 100 repos
The dashboard used to read only your first 100 owned repositories. On prolific accounts that meant stars, forks, open issues/PRs and language totals were quietly undercounting — and the Repos list stopped at 100. Both the repo and CI queries now paginate through the whole set (up to 500), so the numbers and the list are finally complete. With 100 or fewer repos nothing changes — it's still a single page.
Upgrade
brew upgrade gfazioli/tap/octoscopehttps://github.com/gfazioli/octoscope/releases/tag/v0.19.0
As always: read-only, free, MIT, on Linux / macOS / Windows.
Source: https://github.com/gfazioli/octoscope
What's the most repos anyone here keeps on one account? Curious how far past 100 the undercount was actually biting.


Replies