🔭 octoscope v0.24.1 is out — a small reliability & security patch
Quick backstory on the "why": octoscope's repo drill-in shows a 12-month star-history sparkline, and that reads GitHub's stargazers endpoint — which GitHub has been tightening (a scoped token is now required) and which throws the odd 5xx. The catch: one failed star-history call used to abort the whole detail view. Not great.
✅ Now it's best-effort. If star history can't load, octoscope just drops the sparkline and still shows the description, license, latest release, recent commits and open issues/PRs. The star count itself was never affected — that's a public number, not the restricted list.
🔒 This build also picks up a Go standard-library security fix (crypto/tls, GO-2026-5856), so it's worth grabbing even if you never open a drill-in.
💡 Tip: press Enter on any Repos / PRs / Issues row to open the drill-in — and inside a repo, v toggles the star sparkline between density and a cumulative curve.
Upgrade:
brew upgrade gfazioli/tap/octoscopeMore: https://gfazioli.github.io/octoscope · https://octoscope.substack.com
How do you keep an eye on your GitHub activity without leaving the terminal? Curious what you'd want octoscope to surface next.
Replies
WebCurate.co
Nice update. I like the change to make the star history optional instead of letting one failed request break the whole view.
Those small reliability improvements usually make a bigger difference than adding new features.
Netfox
@hosseinyazdi hey Hossein, appreciate that — you nailed it honestly. that star-history call was the perfect example: one flaky endpoint used to kill the whole drill-in, which felt way worse than just dropping the sparkline. now it degrades gracefully and you still get everything else.
these little fixes take 80% of the effort and get 0 glory 😅 but they’re what make a tool feel trustworthy. thanks for taking the time — lmk what you’d want octoscope to surface next 🔭