@ouro.bot/cli@0.1.0-alpha.781
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 no install lifecycle hook, so the source does not meet the policy threshold for malicious install-hook abuse. Its user-invoked runtime persistence and self-update behavior warrant a warning.
Decision evidence
public snapshot- CLI system setup invokes a PATH installer that can update shell profiles and replace recognized Ouro launchers.
- Runtime setup installs the same package version with npm into a user home directory and activates it through a symlink.
- On macOS, the CLI writes and starts its own LaunchAgent daemon.
- The manifest exposes CLI binaries but contains no preinstall, install, or postinstall hook.
- Credential collection is part of explicit provider authentication and sends the GitHub token only to the GitHub API endpoint shown.
- No source evidence establishes secret exfiltration, arbitrary remote code execution, or foreign AI-agent configuration writes.
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.781.
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.781 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.