huawei-cloud-waf-list@1.0.1
CAUTIONPublisher claims: "1. Query the list of Huawei Cloud WAF (Web Application Firewall, Web应用防火墙) protected websites / domain names under the current account through KooCLI (hcloud waf ListHost / ListCompositeHosts — read-only GET /v1/{project_id}/waf/instance and /v1/{project_id}/composite-waf/host). 2. Output modes: a compact table (default) with 防护域名 | 防护状态 | 接入方式 | 保活方式 | 独享IP | Domain ID key fields, --json (the raw host array)[, and --names-only (unique sorted domain list). 3. Supports --region to pick the region, --all-modes / --mode cloud|premium to select cloud-mode or dedicated/premium-mode protected domains, --hostname filtering, --protect-status (-1 bypass / 0 suspended / 1 enabled), --enterprise-project-id and --policyname filters, and automatic pagination (--pagesize, -1 = fetch all). Access mode (接入方式 cloud/premium) is surfaced from waf_type, keep-alive mode (保活方式) from proxy. 4. Explicit error hints for an empty protected-site list (「当前区域无 WAF 防护网站」), 403 / insufficient IAM permission (「无权限访问 WAF 防护网站列表」, WAF.00012006), disabled region (APIGW.0802), and hcloud not installed. 5. Built-in write-intent guard: any mutating intent (create / delete / update / migrate / rename / batch ...) is rejected before execution — this skill is strictly read-only. 6. Triggers include: "list WAF sites", "WAF 防护网站列表", "查询WAF防护域名", "WAF 域名列表", "WAF 防护状态查询", "WAF 网站盘点", "WAF 巡检", "list waf hosts", "waf protected domains", "华为云WAF列表". 7. Offline unit tests (mocked hcloud subprocess) cover routing, output modes, filters, error scenarios and the write-intent guard." Observed in sandbox: static analysis only — behavior not yet observed.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-05 and scored it 63/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis 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
What would make this Verified
17 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim wlc-dev: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- 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.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.