cue-cn-contract-clauses@0.1.5
CAUTIONPublisher claims: "合同逐条拆解起草:输入是一份合同正文(本地文件或解析通道取回的正文),产出四节清单——一句话概览(标的、期限、价款,只写文里有的)、逐条要点(每条一句原文摘,挂 [S#] 与页码或行号)、需盯条款(单方变更/自动续约/排他/违约金/争议解决地/数据与保密/责任上限七类逐类点名,没有的写未见到)、来源与解析日。机检 check_clauses.py 五道:形制与条数带/锚与定位/引文逐字回原文/七类点名/法律意见与效力断言零命中,零网络。适合签前自查。Do NOT use for: 实务级法律意见、条款效力判断、替代律师审查、评级排序。Triggers: 合同要点 / 条款清单 / 签前自查" 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-03 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,320 lines in 17 files.
What would make this Verified
13 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim huhoo: 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.