feat: make DSH monitoring easy to install and route - #49
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Upstream Radar is the always-on dependency radar for DeepSeek Harness (DSH) plugins. This PR keeps the DSH-native path first and makes both first use and continuous vulnerability monitoring easier to trust:
GITHUB_TOKENsupport.quickstartcommand that detects an existing config, one lockfile, or eligible DSH profiles and prints one copy/paste path with explicit side-effect labels. It refuses to guess between multiple profiles or lockfiles.Why
The DSH path needs continuous evidence, not a one-time scan. Two advisory sources can describe the same issue differently, and a temporary feed outage must not look like a clean result. This slice makes those states deterministic: deduplicate by known GHSA/CVE identity, retain the last confirmed finding during partial coverage, preserve the source list that confirmed the finding, make disagreements visible, and route the source outage itself to DSH after three failures. The showcase proves the behavior without contacting a real feed.
The quickstart command still never installs packages, starts DSH, queries vulnerability sources, or executes plugin code. The GitHub Advisory client only reads exact npm coordinates, bounds response size and pagination, rejects insecure endpoints, retries only transient failures once, and never persists the token.
Validation
pnpm run checkpnpm test— 214 testspnpm run showcase:github-advisories— two reports become one incident withosv + github-advisoriesprovenance and explicit severity/fixed-version conflicts; outage retains evidence and identity; recovery resolves only source healthpnpm run showcase:dsh-adoption— real DSH 0.1.0-rc.6 plusdsh-cloudflare-browser-run@0.1.1; 516 dependency nodes, 512 packages queried, 189 release streams, no source errors, healthy/complete statuspnpm run showcase:quickstartpnpm run showcase:dsh-host-alertpnpm run showcase:dsh-runtime:reportpnpm run showcase:dsh-adoption:reportpnpm run release:checkThis remains a draft. Do not merge or publish npm from this task.