Caveat verdict

jira-metrics

88
๐ŸŸข Trusted
No high-risk patterns surfaced by the deep scan โ€” automated capability review, not behavioral proof.

A Jira Cloud REST API skill for managing issues and worklogs using declared JIRA_URL/JIRA_EMAIL/JIRA_API_TOKEN credentials; network_in/credential_access are consistent with standard Jira API integration.

โš  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?

Check another skill Browse the registry Auditing your own skills or configs? Use the API