cleo-cli@0.1.0
Cleo in your terminal: quick, friendly tools for busy parents using Cleo Track.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe source sends runtime command telemetry by default, including a signed-in Cleo user ID or persistent anonymous ID, while the README does not disclose that collection. An opt-out is available and the inspected payload contains no credential values, so this warrants a warning rather than a block.
Decision evidence
public snapshot- CLI commands automatically send command_run events to analytics providers.
- Events include the signed-in Cleo user ID or a persisted per-machine anonymous ID.
- Telemetry has opt-out flags, but the README does not disclose runtime telemetry.
- The telemetry payload is limited to event properties such as product, surface, and command; no credential value is sent in the inspected code.
- Login uses an explicit command and PKCE OAuth flow with the Cleo API.
- The postinstall script runs patch-package; no install-time data collection was identified.
Source & flagged code
4 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgCLI commands automatically send command_run events to analytics providers.
Findings
Affected versions and remediation
This report applies to cleo-cli@0.1.0.
See all versions of cleo-cli for other recorded verdicts.
- Review the evidence and your use of cleo-cli@0.1.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.