Caveat verdict
jira-m
88
🟢 Trusted
No high-risk patterns surfaced by the deep scan — automated capability review, not behavioral proof.
Standard Jira Cloud REST API client using user-supplied env vars (JIRA_URL, JIRA_EMAIL, JIRA_API_TOKEN) to perform documented project management operations; network access and credential use match the stated purpose.
⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.
Automated static analysis — not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.
55
security
30
transparency
70
maintenance
Permission integrity
Code accesses API keys/tokens but declares no environment variables
credential_access
Findings (1)
Pattern match critical
Possible hardcoded credential
SKILL.md · code · TOKEN="your-api-token
Permissions & capabilities
No declared permissions — minimal attack surface.
network_incredential_access Is this flag fair?
Thanks — recorded.