cue-watchlist-digest-cn@0.2.22
CAUTIONPublisher claims: "自选清单日报(状态文件驱动):把公司名或 6 位代码落成 watchlist.json,每次运行从既有域取数与上次快照做差,产出「今日新增/近端变更/需人工」日报,每条挂官方出处+asof;同日首跑按差集给增量、再跑复用当日记账(幂等只在当日内成立)。适合「我这几只票今天有什么新公告」「回购和激励推进到哪了」这类逐日重复需求。Do NOT use for: 行情、涨跌、资金流与北向(该域未开放,以 catalog 现值为准,本件不装)、风险评分或评级、一次性历史复盘。Triggers: 自选清单日报 / 我的票今天有什么新消息 / 盯公告 / watchlist daily digest" 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%- 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.
- Python subprocess execution detected≈ +4 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- 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.
- 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.