cue-event-brief-cn@0.2.22
CAUTIONPublisher claims: "A股公告事件速读卡:把一份临时公告(回购/增减持/业绩预告/重大合同/处罚问询等)变成可核对的五段卡——逐字关键数+出处、影响链候选、同类对照、待核清单。评级与目标价一律[待人工],不预测走势。适合「刚出了公告先看什么」「这份公告讲什么」。Do NOT use for: 投资建议或买卖决策、未检索到的数据编造、收益承诺。Triggers: 公告速读 / 公告解读 / 这份公告 / 回购公告 / 增减持 / 业绩预告 / 处罚 / 问询函 / 刚出公告; announcement triage / A-share filing quick-read" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario) on 2026-10-26 and scored it 69/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: npx invocation of non-well-known package; npx invocation of non-well-known package; npx invocation of non-well-known package. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
What would make this Verified
11 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Destructive file system command detected≈ +9 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- 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.
- npx invocation of non-well-known package≈ +4 on the totalPin versions and sources; vendor anything fetched at install time.
- 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.