leafather-report-audit@3.6.0
CAUTION· static onlyPublisher claims: "数鉴-报告审计技能。做报告时就用:算数即记账,交付前对账。两条路产同一本账本——①有指标定义(ledger.yaml + indicators.yaml)→ rla_ledger 生成账本,模板里写 [[id]] 渲染,数字天生带出处、数据变了拒绝渲染;②有脚本跑数 → rla_report 录像自动记账。审计时把报告数字逐个追溯回账本,追不到即拦;覆盖率不足不许判定通过。适用三时机:出报告(算数记账)、改报告(改完拿现有账本重核,防只改一份漏其余)、查问题(数字对不上、客户质疑出处)。触发词:出数据报告、做报告、改报告、更新数据、数据补录、口径调整、重新生成报告、交付前检查、数字对不上、可追溯、审计报告。项目里已有 ledger.yaml / indicators.yaml 时,改动报告前后都应复核。产出四件套:audit.md 结论、audit.html 审计凭证、evidence.csv 证据清单、manifest.json 机检回执。不适用:改的是纯文字(不含数字)、或报告里没有需要追溯的指标。" 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-16 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. 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
p = subprocess.run(self.argv, input=str(sql), capture_output=True,Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.p = subprocess.run([sys.executable, gw, "--sql", sql, "--out", out, "--limit", "10", "--timeout", "120"],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.proc = subprocess.run(cmd, env=env)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.return subprocess.run(cmd, capture_output=True, text=True).returncodeFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.p = subprocess.run([sys.executable, self.script, "--sql", str(sql),Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.p = subprocess.run(cmd, capture_output=True, text=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.r = subprocess.run([sys.executable, str(collect),Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.r = subprocess.run([sys.executable] + args)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.python3 scripts/rla_collect.py --trace run.trace.jsonl --ledger l.json --no-recomputeFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.r = subprocess.run(cmd, capture_output=True, text=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.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 wopy112-gao: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.