@yoooclaw/phone-notifications@1.16.1
后台同步手机通知数据到本地存储,供 Agent 查询消费
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe runtime credential flow uses the package’s own API key with its YoooClaw service, and saving the key is an explicit CLI action. The flagged README token mention is CI documentation, while the declared prepublish hook builds the package and does not run as an install hook.
Decision evidence
public snapshot- The manifest exposes a plugin entry point and an `ntf` CLI for the phone notifications package.
- The plugin reads its own API key from `YOOOCLAW_API_KEY` or its local `credentials.json`; the CLI has an explicit command to save that key.
- The plugin’s service URLs are built from YoooClaw service hosts, and the key is used for the plugin’s relay credential.
- The manifest’s `prepublishOnly` script builds the package; it is not an install hook.
- The README’s `NPM_TOKEN` mention is in CI/CD secrets documentation, not runtime code.
- The reviewed command execution and network requests serve CLI and notification-service functions; no unrelated data transfer or account action was identified.
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.16.1.
See all versions of @yoooclaw/phone-notifications for other recorded verdicts.
- Review the evidence and your use of @yoooclaw/phone-notifications@1.16.1 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.