Caveat verdict

aliyun-sls-openclaw-integration

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

SLS observability provisioning for OpenClaw using aliyun CLI; reads AK/SK from standard environment variables (ALIBABA_CLOUD_ACCESS_KEY_ID/SECRET) for the Alibaba Cloud CLI, which is the correct secure pattern.

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

0
security
40
transparency
70
maintenance

Permission integrity

Makes network requests but does not declare curl/wget in required binaries

network_out

Installs packages at runtime โ€” transitive dependencies are not auditable

package_install

Findings (4)

Pattern match critical

Possible hardcoded credential

references/cli-commands.md ยท code ยท SECRET="<your-sk>

Pattern match high

References sudo โ€” requests elevated privileges

SKILL.md ยท code ยท sudo

Pattern match high

apt-get install โ€” installs system packages

SKILL.md ยท code ยท apt-get install

Pattern match high

yum install โ€” installs system packages

SKILL.md ยท code ยท yum install

Why the tier is capped

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

network_outcredential_accesspackage_install

Is this flag fair?

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