@ouro.bot/cli@0.1.0-alpha.779
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 a concrete user-invoked persistence and runtime self-install chain. No automatic npm lifecycle trigger or confirmed credential exfiltration was found, so a warning is proportionate rather than a block.
Decision evidence
public snapshot- Running `ouro up` automatically performs system setup that installs a command and persists a versioned runtime.
- The PATH installer can overwrite a pre-existing `~/.local/bin/ouro` launcher and append to a shell profile.
- The runtime runs `npm install` for the same package name into a user-home version directory.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- The credential code is reached through explicit authentication flows and uses provider-specific endpoints.
- No source inspected shows silent credential exfiltration, remote code evaluation, or install-time execution.
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.779.
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.779 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.