From the Inside Claude Code - The Claude Code Ecosystem architecture map
External-PR workflows never execute contributor code
strength · low · verified
Both pull_request_target workflows check out only the base repository and read the head marketplace.json as data through the GitHub API. External-pr-scope.js trusts the source repo rather than the submitter: a PR is in scope only if it adds entries pinned to a commit in a repo that already backs a live entry.
This avoids the classic pull_request_target pitfall of checking out and running head code with a write token. Keep that invariant explicit in review, since one added checkout of the PR ref would undo it.
The trail
Open on the mapMore from this board
- Optional SessionStore methods raise instead of being absent, so a change in Types reaches 13 modules
- The Lowerer is one struct spread over 38 files and 29,700 lines with no unit tests
- Day 1: start with marketplace.json, the contract everything else serves
- Every SDK module imports its exceptions from one file, _errors.py
- Partner MCP plugins launch unpinned packages on every user's machine
- PR-controlled agent config is restored from the base branch before Claude starts
- Control-protocol failures escape the SDK exception hierarchy
- Both public entry points share one control-protocol engine
- The triage and dedupe agents are boxed in identity, tools and network
- Label decisions by the triage agent leave no reason a maintainer can see
- Spend and run length are bounded at the transport
- The subprocess transport carries five responsibilities in one file
- Command-line construction is hardened against argument injection
- Every agent-driven closure has a human override before it happens
- Skip for now: config-only integrations, CI plumbing and single-file plugins
- Channel servers keep bot tokens owner-only and refuse injected pairing requests