@yoooclaw/phone-notifications@1.17.0
后台同步手机通知数据到本地存储,供 Agent 查询消费
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe source shows runtime update-report telemetry that can include error messages and log tails, alongside the package’s API key. The key goes to the package’s own service, so this does not establish credential theft, but the undisclosed collection of potentially identifying log data warrants a warning.
Decision evidence
public snapshot- Runtime update reports include update stage, result, versions, environment, and optional error messages or log tails.
- The report sender includes the package API key in the POST body.
- Report context targets the environment-specific plugin update-report endpoint and uses a device identity.
- A startup heartbeat records and flushes reports when a report context exists.
- The manifest has no install, preinstall, or postinstall hook; prepublishOnly only builds the package.
- The API key is the package’s own service credential and is sent to its configured plugin report endpoint.
- The manifest describes a phone-notification plugin and exposes its CLI as the package entry points.
Source & flagged code
6 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.17.0.
See all versions of @yoooclaw/phone-notifications for other recorded verdicts.
- Review the evidence and your use of @yoooclaw/phone-notifications@1.17.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.