octoscope 0.27.0 the integrity scan stops describing a repo and starts noticing things about it.
Before this release the supply-chain scan could only talk in the present tense: here is what auto-executes right now, here is a commit tip that looks forged. Useful if you happen to scan while the implant is sitting there. Useless for the two questions you actually have when a worm is circulating did something change, and what could whoever got in reach?
octoscope 0.28.0 is out, and the integrity scan can now see an attack that lives in two files instead of one.
Here's the shape it used to miss. You read a workflow, it triggers on pull_request_target so anyone can start it, and it holds nothing worth stealing. Fine. Except the last line is uses: ./.github/workflows/build.yml with secrets: inherit and that file reads your deploy token. Neither file is a finding on its own. Together they're a stranger's pull request opening a path to your secrets.
The big one first: octoscope has a real guide now. Ten pages at its own address Getting started, Authentication, The tabs, Drill-ins & scan, Live & reliable, Themes, Configuration, Scripting, plus a reference pair for every CLI flag and every keybind. https://gfazioli.github.io/octos...
The Repos tab has shown a CI rollup dot per repository for a while, and it always stopped there. Red meant something was wrong, and then you went to the browser to find out what. That last step was the annoying one.
Now you open the repo and the drill-in answers it: a Checks section listing the individual checks on the default branch, with failures floated to the top. That ordering matters more than it sounds the list is capped at eight rows, so a red job in a forty-job matrix would otherwise hide behind all the passing ones.
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.
octoscope's Repos tab has had pinned repos for a while now a sticky section up top for the handful you actually live in. This release gives the Issues tab the same treatment.
Press P on any issue (or pick Pin from the space action menu) and it sticks to the top, in the order you pinned it, across refreshes and restarts. It composes with everything else you already do: the sort cycle (s) reorders only the rest, and the / filter narrows both sections at once. The set is saved to your config under pinned_issues, so the next launch brings them right back press P again to unpin, and a pinned issue that gets closed just stops showing.
Two additions that close the loop between watching (what v0.14.0 widened) and noticing (what's actually waiting for your attention). One feature lands on screen, one in your macOS notification center; both keep octoscope read-only.
Following up on what @sk_uxpin asked for on the v0.11.0 launch thread: you can now read pull-request diffs inside octoscope.
Press Enter on any PR for the drill-in. Press f for a full-screen list of the changed files. Enter on a file row opens its unified diff with syntax highlighting chroma's diff lexer, monokai palette, the universally recognised red/green for - / + lines and a scrollable viewport so a 400-line patch fits without pushing anything off-screen.
