@ouro.bot/cli@0.1.0-alpha.780
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 an automatic runtime persistence and self-install chain after user CLI invocation, which warrants a warning. It does not meet the blocking lifecycle-abuse rule because package installation itself has no preinstall, install, or postinstall hook.
Decision evidence
public snapshot- The normal CLI setup path automatically installs a shell command and repairs launchers.
- Setup reinstalls the same package version with npm under the user's Ouro directory.
- The CLI creates and starts a macOS launch agent for its daemon.
- The manifest exposes CLI entry points but has no npm install lifecycle hook.
- The observed mutations follow an invoked CLI setup path, not package installation.
- The self-install targets the same scoped package and an explicit version.
- Credential collection requires an interactive authentication flow; no credential exfiltration was confirmed.
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.780.
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.780 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.