global-bug@1.0.0
CAUTION· static onlyPublisher claims: "Bug问题上报技能。当用户说"有xxx问题"、"xxxBug"、"发现xxx问题"时触发,自动将Bug信息添加到企业微信智能表格中。参数映射:问题描述为用户问题,发现问题人员留空,处理进度默认"处理中",严重程度留空,处理人固定"姜春波",发现日期留空,解决时间留空。" Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-19 and scored it 66/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: Destructive file system command detected. 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
rm -f /tmp/bug_request.jsonFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.No other findings across 263 lines in 3 files.
Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
14 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim wearflatshoestowalktheworld: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Destructive file system command detected≈ +4 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.