@beeos-ai/cli@1.2.7
BeeOS CLI — run AI agents from your desktop
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe bundled installers send default-on telemetry containing a hostname-derived identifier to BeeOS, which is identifying runtime information and warrants a warning. This is triggered by running the installer rather than by npm installation, and the reviewed CLI source did not show automatic credential exfiltration.
Decision evidence
public snapshot- The shell installer builds a host_hint from the machine hostname and architecture and includes it with install event, OS, Node version, and status fields in telemetry.
- The installer posts this telemetry to the BeeOS API by default and sends a start event when its install routine begins; telemetry can be disabled with BEEOS_NO_TELEMETRY=1.
- The manifest has no npm install lifecycle hook; prepublishOnly only runs the build.
- Telemetry is sent to the package publisher’s API and contains install metadata rather than credentials, file contents, or project data.
- The CLI’s API-key option is forwarded to a separately invoked device-agent command; no automatic key collection or redirect was identified.
Source & flagged code
8 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to @beeos-ai/cli@1.2.7.
See all versions of @beeos-ai/cli for other recorded verdicts.
- Review the evidence and your use of @beeos-ai/cli@1.2.7 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.