@ouro.bot/cli@0.1.0-alpha.802
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 real user-triggered persistence and runtime self-install capability, so it merits a warning. Static inspection did not establish malicious install-time execution, exfiltration, or broad foreign control-surface mutation.
Decision evidence
public snapshot- User-invoked system setup installs an Ouro command and can amend the active shell profile.
- The CLI can install another release of itself with npm into its private version directory.
- The self-install path is reached when the current-version link does not match the running release.
- package.json has bin entrypoints but no preinstall, install, or postinstall lifecycle hook.
- Credential collection is tied to interactive provider authentication and sends the GitHub token only to GitHub's Copilot endpoint.
- No concrete secret exfiltration, remote payload execution, or foreign AI-agent control-surface modification was found.
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.802.
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.802 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.