ClawAudit verdict

jira-auto-analyze

45
🟠 Risky
Significant concerns — only install if you understand the risks

The config section shows a hardcoded username ('liuwei1') and password ('Lw@123456') in plaintext within the skill document, which is a credential hygiene risk; however the skill automates legitimate JIRA ticket triage and there is no evidence of exfiltration.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis — not a human review. ClawAudit flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

20
security
90
transparency
70
maintenance

Findings (4)

Pattern match critical

Possible hardcoded credential

INSTALL.md · code · PASSWORD="Lw@123456

Pattern match critical

Recursive delete from root or home — destructive command

INSTALL.md · code · rm -rf ~

Pattern match medium

Python os.environ.get — reads environment variable

INSTALL.md · code · os.environ.get(

Pattern match medium

subprocess execution — runs system commands from Python

scripts/setup.py · prose · downgraded · subprocess.run(

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class D). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.

Permissions & capabilities

No declared permissions — minimal attack surface.

Is this flag fair?

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