Add Agentic Workflow vulnerability triage - #4
Draft
jeffreyolio wants to merge 1 commit into
Draft
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's in this PR?
Alternative B: adds an organization-owned GitHub Agentic Workflow for Barnacle dependency-vulnerability triage, using the Codex engine.
Codex runs with read-only GitHub permissions inside the Agent Workflow Firewall. GitHub writes are available only through a path-restricted
create-pull-requestsafe output that enforces draft status and never merges. The workflow adds threat detection, turn and cost limits, SHA-pinned actions and containers, and a pinned triage skill. A deterministic final job translates the safe-output result into Barnacle's versioned artifact contract.This PR is mutually exclusive with the direct
openai/codex-actionworkflow in #3; reviewers should choose one execution model.Before
Repositories would need to build their own agent execution, sandbox, write controls, and result normalization.
After
Repositories can call one compiled reusable Agentic Workflow while Barnacle remains responsible for dispatch, Slack review, and lifecycle tracking.
QA Instructions
barnacle-triage-<attempt_id>without opening a pull request.References