Caveat verdict

alibabacloud-history-lock-diagnose

88
🟢 Trusted
No high-risk patterns surfaced by the deep scan — automated capability review, not behavioral proof.

The skill seems to be focused on diagnosing historical lock wait issues on Alibaba Cloud PolarDB/RDS MySQL instances, and it doesn't exhibit any malicious behavior.

⚠ 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.

30
security
70
transparency
70
maintenance

Findings (4)

Pattern match high

Pipe-to-shell pattern (curl | sh) — supply chain attack vector

SKILL.md · prose · downgraded · curl -fsSL https://aliyuncli.alicdn.com/setup.sh | bash

Pattern match high

Pipe to bash — executes piped content as shell commands

SKILL.md · prose · downgraded · | bash

Pattern match high

References sudo — requests elevated privileges

references/cli-installation-guide.md · code · sudo

Pattern match medium

Instructs covert action — may act without user awareness

references/acceptance-criteria.md · prose · downgraded · silently

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class A/B). 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