Public: anyone can read this; the crew can change it.
See and steer the flows upstream and downstream: dependencies, sources, forks, followers and code scanning #9434
4 earlier comments
Owner, 2026-11-05: as much as possible should work without the crew, so tokens are not a dependency. Reading upstream releases, comparing versions, advisories, code scanning, the view and the actions are deterministic and run with the crew off. The crew only adds judgment on top: writing the issue, adopting a feature. Each part has a test with the crew disabled and no model credential.
From reviewing Absorb (now on trunk): the radar app runs its own timer from its feature settings and needs no crew. Its core can be fully deterministic: read GitHub release tags and npm dist-tags, compare semver with what the repository pins, and pull the CHANGELOG sections between the pinned and new versions into a JSON report. The model is optional on top, writing an issue only when its scout setting is on and a credential exists.
Reviewed pull #9537 at its head: left open: One view per repository shows what flows in (dependencies with their latest releases and advisories, followed sources, origins) and what flows out (forks, followers, mirrors such as GitHub, forges that follow it), each with its state and when it last moved. — Advisories, followers and forge followers are not shown yet.; Each line can be acted on where it stands: update this dependency, follow or stop following, pull this change in, send this back. Actions go through the existing gates and walls. — Only the read-upstream action exists.; A dependency watcher, Radar or its successor, reads upstream releases and changelogs on a schedule, and files an issue for the crew when an update is useful or a feature is worth adopting, with the reason and the risk in plain words. On autonomous repositories the crew does the work and its normal checks decide. — No schedule, no changelogs, no issue filing.; Code scanning runs on every push and nightly: secrets, dependency advisories and static analysis. Findings show on the repository and in this view, and a new high finding blocks a release until a person accepts it. — Code scanning is not implemented.; The view is a picture first, sources on one side and followers on the other, in the home page's design language (#9433), and fast under load. — A two-column list view exists, but followers are missing and it is not yet a picture.; An admin sees the same across all repositories. — No all-repositories view..
Left open after pull #9537 landed: 6 unticked items remain (One view per repository shows what flows in (dependencies with their latest releases and advisories, followed sources, origins) and what flows out (forks, followers, mirrors such as GitHub, forges that follow it), each with its state and when it last moved.; Each line can be acted on where it stands: update this dependency, follow or stop following, pull this change in, send this back. Actions go through the existing gates and walls.; A dependency watcher, Radar or its successor, reads upstream releases and changelogs on a schedule, and files an issue for the crew when an update is useful or a feature is worth adopting, with the reason and the risk in plain words. On autonomous repositories the crew does the work and its normal checks decide.; …). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Split: #9590 (every line in and out), #9591 (act on a line), #9592 (scheduled radar files issues), #9593 (code scanning that holds a release), #9595 (picture first), #9594 (admin view across repositories).
The owner, 2026-11-05: "he had a very interesting radar app where he listens upstream on our dependencies and the crew automatically leverages new features and keeps things up to date. code scanning here would be amazing as well. this makes me think of the upstream and downstream flows as something i want to look at and interact with."
Related: Ben's Absorb pull (being brought onto trunk) and his
radarapp; followed and trusted sources; the nightly security check (secrets, Trivy, Nuclei); #9406; #9427.Done when: