ai-governance-audit-chain@1.1.3
CAUTIONPublisher claims: "「AI 改了我的文件,怎么查是谁改的?」「AI 自动帮我发邮件、发帖,怎么拦住?」「让 AI 干活,怎么留痕?」 装上它,AI 会先给自己立三条规矩:每个任务建籍(谁在干、干什么、依据什么)、每步操作留证(改了什么、证据在哪、怎么复算)、 关键动作设门禁(对外发送、删除覆盖、付款下单之前先过闸)。适用于 AI 越权操作、智能体乱来、AI 结论没标来源、 自动化流程要人工审批、合规审计要留痕、事后追责要证据链、提示词注入防范、AI 可靠性提升。" 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-06 and scored it 67/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
No findings across 1,158 lines in 10 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
13 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim zhaoxinghua09-cell: 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.