Skip to content

bugs: verification gate runs the scanned repository's tests on an untrusted checkout #7787

Open

Description

@kyle-sexton

plugins/bugs/skills/scan/context/verification-gate.md lets a gate run the scanned repository's tests to label a finding reproduced. That executes scanned code on an unattended run over an untrusted checkout.

Decide whether the gate should keep running the scanned repository's tests, and if so under what containment.

Split from #7394, where it was noted but not graded.

Refs: #7394

Activity

  1. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 17, 2026
  2. github-actions commented on Oct 17, 2026

    @github-actions
    Contributor

    Thanks for the report. Automated triage handed this issue to a maintainer.

    Proposed work class: work-class: structural
    Basis: automated intake triage; a maintainer confirms or changes it.

    Automated triage. A maintainer reviews it.

  3. added
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    and removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 17, 2026
  4. kyle-sexton commented on Oct 18, 2026

    @kyle-sexton
    MemberAuthor

    Decision recorded.

    Question: The /bugs:scan verification gate runs the scanned repository's tests to mark a finding "reproduced". On an unattended run over an untrusted checkout, that executes untrusted code. Options: (a) unattended runs never execute scanned code, and attended runs do only after the person agrees; (b) run tests only in a sandbox with no network and no credentials; (c) keep current behavior.

    Owner's answer: (a) Unattended runs fall back to the existing verified-by-reading label. No CI workflow calls bugs:scan today, so the exposure is local loops and routines. Basis: plugins/bugs/skills/scan/context/verification-gate.md:78-84; scan SKILL.md:2, :64-65.

    The owner accepted this recommendation as item D32 of a 32-decision batch in an attended backlog-shaping session on 2026-10-18. The batch question: "Accept all 32 recommendations, including the four flagged above (D2 close the relearn, D26 cross-repo sync without per-repo confirm, D10 narrow hook, D23 delete guard only)?" The owner answered: "Accept all 32 (Recommended)".

    Posted by AI from the owner's answer in that session.

  5. added
    status: confirmedA maintainer confirmed the item is real and in scope; ready to be worked.
    and removed
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Oct 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    status: confirmedA maintainer confirmed the item is real and in scope; ready to be worked.

    Type

    Fields

    No fields configured for Task.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions