Skills/ClawHub/alibabacloud-waf-domain-cert-status-check

alibabacloud-waf-domain-cert-status-check@0.0.1

CAUTION

Publisher claims: "Read-only inventory of SSL certificates bound to domains onboarded to Alibaba Cloud WAF (CNAME access, WAF 3.0 and 2.0): collects each domain's certificate, resolves its validity, classifies it as expired / expiring / healthy, and returns a summary table with renewal guidance so HTTPS is not interrupted by a silently expiring certificate. Use when a customer asks which WAF certificates are about to expire, wants an expiry audit across onboarded domains, worries about HTTPS breaking after expiry, or needs a periodic certificate health check. Not for: why one request was blocked, protection rule effectiveness, certificate-chain / TLS handshake troubleshooting, cloud-product-access domains (CLB / ALB / ECS), or performing the renewal itself. Triggers: "WAF证书到期", "证书快过期了吗", "证书有效期", "证书过期检查", "证书到期提醒", "证书巡检", "证书续期", "域名证书状态", "HTTPS证书会不会断", "cert expiry check", "certificate about to expire", "WAF certificate status", "certificate validity audit", "renew certificate before expiry"" Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher sdk-team · joined 13 days agoInstalls 203Last detonated 2 h ago
What would fix thisWatchDispute verdict

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-04 and scored it 62/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Authorization escalation language; Privileged sudo command. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.

Static findings

HIGH
Authorization escalation languagereferences/cli-installation-guide.md:70 · Authorization escalation languageFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01
HIGH
Privileged sudo commandSKILL.md:128 · Privileged sudo command — agent may execute with elevated privilegesFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
Python subprocess execution detectedscripts/check_cert_status.py:148 · Python subprocess execution detectedFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05

What would make this Verified

18 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim sdk-team: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Privileged sudo command≈ +4 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
  3. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
  4. Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim sdk-team