@ouro.bot/cli@0.1.0-alpha.771
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 contains meaningful runtime persistence and self-update behavior, but no npm lifecycle hook or concrete malicious exfiltration path was found. Because high-risk compiled modules and the self-installing update chain remain present, downgrade to a warning rather than mark clean.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user runs the Ouro CLI, an update path, or its command-install feature.
Impact
A selected package release can execute after installation, and the Ouro command can persist in the user's shell environment.
Mechanism
Runtime self-update plus user-home launcher and shell-profile modification.
AI rationale
The package contains meaningful runtime persistence and self-update behavior, but no npm lifecycle hook or concrete malicious exfiltration path was found. Because high-risk compiled modules and the self-installing update chain remain present, downgrade to a warning rather than mark clean.
Evidence
dist/heart/versioning/ouro-version-manager.jsdist/heart/versioning/ouro-path-installer.jsdist/heart/daemon/cli-defaults.js~/.ouro-cli/versions/<version>~/.ouro-cli/bin/ouro~/.local/bin/ouro
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Suspicious at 76.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest exposes CLI entrypoints that can run package code.
- The runtime updater installs another release of the same package under the user's CLI directory and activates it.
- The CLI installer writes an executable launcher and can append its directory to a shell profile.
- The authentication flow reads an existing Codex token from the local home directory during an explicit auth flow.
- Additional high-risk modules execute constrained system probes and supplied absolute-path adapters.
Evidence against
- package.json contains no preinstall, install, postinstall, or prepare lifecycle hook.
- The observed credential collection is inside named interactive authentication functions, not install-time code.
- The updater fetches from the npm registry and names the same scoped package; no source evidence showed secret exfiltration or remote payload execution.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
Source & flagged code
14 flagged · loading sourcedist/heart/daemon/cli-exec.jsView file
3668patternName = generic_password
severity = medium
line = 3668
Medium
Secret Pattern
Package contains a possible secret pattern.
dist/heart/daemon/cli-exec.jsView on unpkg · L3668dist/heart/auth/auth-flow.jsView file
42exports.runRuntimeAuthFlow = runRuntimeAuthFlow;
L43: const child_process_1 = require("child_process");
L44: const fs = __importStar(require("fs"));
High
Child Process
Package source references child process execution.
dist/heart/auth/auth-flow.jsView on unpkg · L42286baseUrl: input.provider === "openai-compatible"
L287: ? "https://api.z.ai/api/paas/v4/"
L288: : "https://generativelanguage.googleapis.com/v1beta/openai/",
...
L291: if (input.provider === "github-copilot") {
L292: let token = process.env.GH_TOKEN?.trim() || process.env.GITHUB_TOKEN?.trim() || "";
L293: if (!token) {
L294: writeAuthProgress(input, "checking GitHub CLI credentials...");
L295: const result = spawnSync("gh", ["auth", "token"], { encoding: "utf8" });
L296: token = (result.status === 0 && result.stdout ? result.stdout.trim() : "");
Findings
1 Critical8 High7 Medium6 Low
CriticalPrevious Version Dangerous Deltadist/heart/daemon/cli-defaults.js
HighChild Processdist/heart/auth/auth-flow.js
HighShelldist/senses/bluebubbles/semantic-receipts.js
HighSame File Env Network Executiondist/heart/auth/auth-flow.js
HighCredential Redirect Persistencedist/heart/auth/auth-flow.js
HighCommand Output Exfiltrationdist/heart/daemon/sanctuary-acceptance-harness.js
HighTrigger Reachable Persistencedist/heart/versioning/ouro-path-installer.js
HighRuntime Package Installdist/heart/versioning/ouro-version-manager.js
HighSemantic Analysis Limiteddist/heart/auth/auth-flow.js#virtual:normalized:round1
MediumSecret Patterndist/heart/daemon/cli-exec.js
Affected versions and remediation
This report applies to @ouro.bot/cli@0.1.0-alpha.771.
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.771 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.