@ouro.bot/cli@0.1.0-alpha.810
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 1mo ago · by lpm-firewall-aiNo concrete secret exfiltration or malicious install-time hook was found. However, automatic launcher persistence plus runtime installation of the same package is a meaningful supply-chain and persistence risk that merits a warning.
Decision evidence
public snapshot- CLI system setup installs an executable launcher, changes shell PATH, and may repair a prior launcher.
- The running CLI installs another @ouro.bot/cli release with npm and activates it under the user home directory.
- The installer runs automatically from the CLI system-setup path rather than an npm lifecycle hook.
- package.json has no preinstall, install, or postinstall hook.
- Credential collection is reached through the explicit ouro auth command and uses provider-specific login flows.
- Launcher repair is limited to paths or contents identified as Ouro-owned.
Source & flagged code
14 flagged · loading sourcePackage contains a possible secret pattern.
dist/heart/daemon/cli-exec.jsView on unpkg · L3739Package 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.810.
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.810 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.