checking-merge-readiness

Warn

Audited by Snyk on Oct 9, 2026

Risk Level: MEDIUM
Full Analysis

MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).

  • Third-party content exposure detected (medium risk: 0.30). The workflow requires fetching and ingesting external GitHub pull request data, including descriptions, diffs, review threads, commit comments, and linked issues authored by pull request submitters and outside contributors.

MEDIUM W009: Direct money access capability detected (payment gateways, crypto, banking).

  • Direct money access detected (medium risk: 0.30). The skill reviews pull requests and provides an option to merge them using gh pr merge. This is a direct financial or operational execution (executing a pull request merge operation via GitHub CLI). However, this direct operation is gated by the invoking user's existing GitHub CLI (gh) credentials and explicit interactive user selection from a menu ("Option 1 is Proceed to merge... waits for a numbered reply"), satisfying independent access control (external service authentication/session gating via gh). Therefore, it qualifies for medium severity.

Issues (2)

W011
MEDIUM

Third-party content exposure detected (indirect prompt injection risk).

W009
MEDIUM

Direct money access capability detected (payment gateways, crypto, banking).

Audit Metadata
Risk Level
MEDIUM
Analyzed
Oct 9, 2026, 12:52 PM
Issues
2