@ouro.bot/cli@0.1.0-alpha.907
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 11d ago · by lpm-firewall-aiThe manifest has no npm lifecycle hooks, and inspected runtime behavior is consistent with the package’s CLI functions. Scanner hints alone do not establish the alleged exfiltration or persistence behavior.
Decision evidence
public snapshot- The manifest exposes CLI entrypoints and defines no npm lifecycle hooks.
- The auth flow uses a GitHub token to query GitHub’s Copilot endpoint and derives the provider URL from that response.
- The version manager installs a requested Ouro CLI version under its own version directory.
- Plugin installation is implemented as a CLI operation; the inspected code does not establish an install-hook attack.
- The inspected agent configuration, notes, upgrade, and trust excerpts do not establish the scanner’s claimed exfiltration or malicious persistence.
Source & flagged code
15 flagged · loading sourcePackage contains a possible secret pattern.
dist/heart/daemon/cli-exec.jsView on unpkg · L3770Findings
Affected versions and remediation
This report applies to @ouro.bot/cli@0.1.0-alpha.907.
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.907 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.