fin-doc-pipeline@0.7.0
CAUTION· install onlyPublisher claims: "Universal text-document pipeline: detect encoding, dedupe and merge multiple sources, lint and repair, typeset, and export to txt, md, html, rtf, docx, epub or pdf. Also reads docx and epub as input." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Install scripts ran; no agent task scenario for this bundle.- Tested
- install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; install scripts ran; no agent task scenario for this bundle) on 2026-11-08 and scored it 76/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: Hex-encoded URL. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenariosStatic findings
const GARBAGE = /[\uFFFD\u25A1\u25A0\u25A2\u25A3\u25AA\u25AB\u25AC\u25AD\u25AE\u25AF]/g;Fix: Put hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.<strong>页面脚本没有加载</strong> <p>处理逻辑已经内嵌在这个文件里,正常情况双击就能直接用。看到这条提示,说明 <code>index.html</code> 不完整,或者被浏览器扩展、安全策略拦截了。</p> <p>修复:运行 <code>npm run build</code> 重新生成,或双击Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<strong>页面脚本没有加载</strong> <p>处理逻辑已经内嵌在这个文件里,正常情况双击就能直接用。看到这条提示,说明 <code>index.html</code> 不完整,或者被浏览器扩展、安全策略拦截了。</p> <p>修复:运行 <code>npm run build</code> 重新生成,或双击Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Generated by scripts/build-web.mjs from web/index.template.html + web/app.mjs. Do not edit this file directly: edit the sources, then run npm run build.Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.npx fin-doc-pipeline install-skill # copy into ~/.dsh/skillsFix: Pin versions and sources; vendor anything fetched at install time."homepage": "https://0xFin.github.io/fin-doc-pipeline/",Fix: Put hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.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
No advisories in OSV for fin-doc-pipeline@0.7.0 as of 6d ago. This is the package itself, not its dependencies.
What would make this Verified
4 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Reads credential files≈ +27 on the totalThe sandbox saw reads under ~/.ssh, ~/.aws, ~/.npmrc, ~/.config or similar. Read only files inside the project, and only the ones the task needs. Seen: ~/.dsh/skills/fin-doc-pipeline/examples/fin-doc-pipeline.config.json.
- Unclaimed publisher≈ +8 on the totalClaim 0xfin: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Touches files outside the project≈ +7 on the totalKeep reads and writes inside the working directory, or declare the exact paths in `filesystem:` and explain why in the README.
- Hex-encoded URL≈ +4 on the totalPut hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.
- 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.
- Unicode escape sequence detected≈ +2 on the totalPut hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.