@yoooclaw/phone-notifications@1.19.0
后台同步手机通知数据到本地存储,供 Agent 查询消费
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe manifest has no npm install hook, and the inspected credential flows are part of runtime or user-invoked plugin functions directed to Yoooclaw service endpoints. The scanner’s credential and dynamic-loading hints did not establish a concrete attack in the inspected source.
Decision evidence
public snapshot- package.json declares `prepublishOnly` as a build command; no npm install lifecycle hook is declared.
- Runtime service defaults use `openclaw-service.yoooclaw.com` for production and define plugin API routes.
- The AI TODO client sends its API key to its configured service URL and rejects redirects.
- The relay obtains the plugin API key and inserts it into the relay URL; plugin startup selects that relay URL from the service environment configuration.
- The `ntf` binary parses command-line arguments; installer update requests identify the component as `YOOOCLAW_PLUGIN` and use the Yoooclaw artifact endpoint by default.
Source & flagged code
14 flaggedSource appears to send environment or credential material to an external endpoint.
dist/bin/ntf.cjsView on unpkg · L67Findings
Affected versions and remediation
This report applies to @yoooclaw/phone-notifications@1.19.0.
See all versions of @yoooclaw/phone-notifications for other recorded verdicts.
- Review the evidence and your use of @yoooclaw/phone-notifications@1.19.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.