@yoooclaw/phone-notifications@1.14.2
后台同步手机通知数据到本地存储,供 Agent 查询消费
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe manifest has no install-time hook, and the credential exchange uses the plugin’s configured link secret with its own YoooClaw service to obtain and save the plugin API key. The installer’s shell commands are documented for explicit user execution.
Decision evidence
public snapshot- The manifest’s only lifecycle script is prepublishOnly, which runs the build; it declares no install, preinstall, or postinstall hook.
- Provisioning skips the exchange when an API key already exists and no link secret is configured, or when the saved link-secret hash is unchanged.
- When provisioning runs, it posts the configured link secret and plugin metadata to the service’s instance-ready endpoint, then saves the returned API key locally.
- The production service host is openclaw-service.yoooclaw.com, matching the package’s YoooClaw service purpose.
- The plugin can perform the credential exchange automatically during startup when configured with a link secret.
- The request also includes the machine hostname.
- The shipped installer documents commands that pipe scripts from artifact.yoooclaw.com to a shell; these are user-run instructions, not lifecycle behavior.
Source & flagged code
7 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.14.2.
See all versions of @yoooclaw/phone-notifications for other recorded verdicts.
- Review the evidence and your use of @yoooclaw/phone-notifications@1.14.2 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.