@ouro.bot/cli@0.1.0-alpha.791
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-aiThis is a high-impact persistent CLI and credential-management capability with runtime self-installation, but the inspected source does not show an install hook, stealthy exfiltration, or a concrete malicious payload. It warrants a warning rather than a publication block.
Decision evidence
public snapshot- CLI runtime automatically performs system setup, including a recovery launcher and version installation.
- Runtime code runs npm install for another @ouro.bot/cli release under the user's home directory.
- The selected openai-codex auth flow reads local Codex tokens and stores supplied credentials in an Ouro vault.
- The launcher installer writes executable files and appends a PATH export to the user's shell profile.
- package.json has no preinstall, install, or postinstall hook.
- Credential access is conditional on an explicit provider-auth flow; no fixed credential-exfiltration endpoint was found.
- The package-owned updater and launcher behavior is visible in source rather than obfuscated.
Source & flagged code
14 flagged · loading sourcePackage contains a possible secret pattern.
dist/heart/daemon/cli-exec.jsView on unpkg · L3706Package 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.791.
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.791 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.