look at the artifact before it touches your machine.

the verdict has to be trustworthy before anything else matters.

• ✓fix the inverted socket score (flag low safety scores, not high)
• ✓migrate off the deprecated socket endpoint
• ✓block only on hard signals; everything else is a warning
• ✓demote noisy patterns outside lifecycle scripts
• ✓agent error ≠ agent rejection, with a 120s timeout
• ✓loud warnings on config parse failures
• ✓green test suite

delete everything that distracts from the one-sentence product.

• ✓presets collapsed to default and strict
• ✓active-incident advisory mode deleted
• ✓npm staged-publish flow deleted
• ✓sbom output deleted
• ✓safe-resolver suggestions deleted
• ✓scguard install passes original args through the gate
• ✓reduce SCGUARD_* env vars to four public controls
• ✓shrink commands.ts under 700 lines; help fits one screen

the test that defines what "correct" means for this product.

• ✓benign corpus: top 50 npm packages must pass under default policy (offline fixtures)
• ✓malicious corpus: real-world attack shapes must block
• ✓both wired into bun run check and ci

the v0.2 headline: replace command-line interception with protocol interception at the registry level.

• ○spike: bun http proxy for registry.npmjs.org gating tarball fetches
• ○decision gate on install-time latency
• ○scguard proxy start|stop|status|setup
• ○verdict cache keyed by tarball sha256
• ○auth / scoped-registry passthrough
• ○readable 403 block pages pointing at the report

proxy-first docs, honest changelog, tag v0.2.0 once phases 0–3 hold.

• ○readme, site, and demos updated to the proxy-first story
• ○scguard doctor verifies proxy + agent auth for real
• ○changelog + v0.2.0 tag