@octavus/agent@1.0.34
Octavus Agent CLI - run one of your cloud Octavus Agents on a machine you control, using that machine as the agent's computer. The agent lives in the cloud (fully configured and observable); the local machine only supplies the computer and the trigger.
AI Security Review
scanned 3d ago · by lpm-firewall-aiSource inspection found no install hooks. The flagged agent-instruction helper has no invocation in the bundled entrypoint, while the active CLI and local tools support the package's stated user-run cloud-agent function.
Decision evidence
public snapshot- The manifest exposes an Octavus command-line tool and defines no npm lifecycle scripts.
- A run requires a configured platform and API key, then sends the caller's prompt to the configured session endpoint; the production default is Octavus's own service.
- The flagged helper collects workspace instructions, but a search of the bundled entrypoint found no invocation of that helper.
- The runtime tools provide the expected local computer, workspace file, and browser functions; file writes are limited to allowed directories, and the browser extension bridge binds to loopback.
Source & flagged code
9 flagged · loading sourcePackage source references child process execution.
dist/computer-mcp/dist/index.jsView on unpkg · L54Package source references a known benign dynamic code generation pattern.
dist/computer-mcp/dist/index.jsView on unpkg · L5Findings
Affected versions and remediation
This report applies to @octavus/agent@1.0.34.
See all versions of @octavus/agent for other recorded verdicts.
- Review the evidence and your use of @octavus/agent@1.0.34 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.