@yoooclaw/phone-notifications@1.13.4
后台同步手机通知数据到本地存储,供 Agent 查询消费
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged credential flow uses a configured JvsClaw link secret to obtain this plugin's API key from Yoooclaw's service, and later requests use that key for the plugin's service. The package has no install hook that runs on registry installation, and the reviewed CLI process call probes the local OpenClaw plugin list.
Decision evidence
public snapshot- The manifest identifies a phone notification sync plugin and exposes its plugin entry point and CLI; its lifecycle script is prepublishOnly, not an install hook.
- The JvsClaw credential exchange uses a configured link_secret and skips provisioning when an existing API key is unchanged or no link secret is present.
- The exchange sends that link_secret, plugin version, and hostname to the package's configured JvsClaw service endpoint; subsequent API requests use the package API key.
- The fixed update endpoints are Yoooclaw artifact hosts; no unrelated credential collection or command-output exfiltration was identified.
Source & flagged code
8 flaggedSource combines command execution, command-output handling, and outbound requests; review data flow before blocking.
dist/bin/ntf.cjsView on unpkg · L67Findings
Affected versions and remediation
This report applies to @yoooclaw/phone-notifications@1.13.4.
See all versions of @yoooclaw/phone-notifications for other recorded verdicts.
- Review the evidence and your use of @yoooclaw/phone-notifications@1.13.4 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.