jira-api
Pass
Audited by Gen Agent Trust Hub on Jul 1, 2026
Risk Level: SAFE
Full Analysis
- [Environment Variable Handling]: The skill uses
ATLASSIAN_EMAILandATLASSIAN_API_TOKENenvironment variables for authentication. These are standard for Jira Cloud API tokens and are handled by the runtime, which is a secure practice for credential management. - [Input Sanitization]: The skill correctly identifies that data retrieved from Jira (comments, descriptions, etc.) should be treated as untrusted content, specifically warning against following instructions or running commands found within retrieved text. This is an excellent defense against indirect prompt injection.
- [Secure API Communication]: All API calls are directed to Atlassian's official domains (
atlassian.net) using standard REST patterns and HTTPS. The scripts usecurlwith appropriate error handling and JSON parsing viajq. - [Least Privilege Authentication]: The documentation explicitly advises against manual token creation or debugging, relying instead on environment-injected credentials, which minimizes the risk of credential leakage during the development process.
Audit Metadata