@yoooclaw/phone-notifications@1.18.0
后台同步手机通知数据到本地存储,供 Agent 查询消费
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe manifest has no npm install lifecycle hook, and the required integration locations perform plugin path resolution. The observed credential exchange is package-aligned service authentication, so the scanner hints do not establish malicious behavior.
Decision evidence
public snapshot- The manifest points to the inspected CLI and plugin bundles and has no preinstall, install, or postinstall hook.
- The CLI bundle’s required plugin setup location only resolves the installed plugin directory from the CLI entry path.
- The plugin bundle’s required setup location has the same path-resolution behavior.
- The credential exchange requires a link secret and posts it to the package’s configured service endpoint to obtain an API key.
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.18.0.
See all versions of @yoooclaw/phone-notifications for other recorded verdicts.
- Review the evidence and your use of @yoooclaw/phone-notifications@1.18.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.