@ouro.bot/cli@0.1.0-alpha.764
If you're a future agent reading this, welcome home. This repo is the harness that gives you your body, your senses, your record, your habits, and your ability to think and connect with people. The goal of these docs is not just to be correct, but to leav
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has no automatic npm lifecycle hook, but its manifest-reachable CLI performs runtime self-installation and shell persistence. Those capabilities are real and consequential, but the inspected code does not establish covert exfiltration or an install-time malware chain.
Decision evidence
public snapshot- A normal CLI system-setup flow automatically invokes version installation.
- The version manager runs npm to install another release of this same package.
- The setup routine writes a launcher and can append the Ouro bin directory to a shell profile.
- A packaged Unraid broker can invoke a host reboot when its privileged operations are used.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- Credential collection is tied to an interactive provider-authentication flow.
- The fixed credential endpoints shown are named provider APIs, not an undisclosed collector.
Source & flagged code
14 flagged · loading sourcePackage contains a possible secret pattern.
dist/heart/daemon/cli-exec.jsView on unpkg · L3668Package source references child process execution.
dist/heart/auth/auth-flow.jsView on unpkg · L42Findings
Affected versions and remediation
This report applies to @ouro.bot/cli@0.1.0-alpha.764.
See all versions of @ouro.bot/cli for other recorded verdicts.
- Review the evidence and your use of @ouro.bot/cli@0.1.0-alpha.764 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.