jira-to-local

Warn

Audited by Snyk on Aug 24, 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 required runtime workflow for jira-to-local (workflows/pull.md Step 3 + loop) fetches and formats Jira issue content (including description, comments, subtasks, worklogs, linked Confluence pages) via fetch-issue.mjs/fetch-confluence.mjs, so outsider-authored free text in those Jira/Confluence fields is ingested at runtime.

Issues (1)

W011
MEDIUM

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

Audit Metadata
Risk Level
MEDIUM
Analyzed
Aug 24, 2026, 05:42 PM
Issues
1
Security Audit — snyk — jira-to-local