@ouro.bot/cli@0.1.0-alpha.765
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 not a confirmed malicious install chain because the package has no install lifecycle hook and the observed mutations follow user-invoked CLI flows. Its persistence, self-installation, and root deployment broker are nevertheless dangerous capabilities that warrant a warning.
Decision evidence
public snapshot- An interactive hatch choice runs system setup.
- Setup writes an Ouro launcher and appends its directory to a shell profile.
- The CLI can reinstall its own package version under the user profile at runtime.
- A shipped Unraid broker is root-only and can invoke a host reboot.
- The manifest has command entrypoints but no preinstall, install, or postinstall hook.
- The setup path is reached after the user chooses hatch, not during npm installation.
- Credential collection shown here uses an interactive prompt or existing local login and calls provider endpoints.
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.765.
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.765 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.