@octavus/agent@1.0.20
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 24d ago · by lpm-firewall-aiStatic inspection found no install lifecycle hook or confirmed malicious behavior. The agent-integration location reads workspace instruction files and does not itself modify an external agent control surface.
Decision evidence
public snapshot- The manifest exposes a command-line binary and has no lifecycle scripts.
- The command-line bundle reads workspace instruction files into a local context collection; the inspected code performs reads only.
- The bundled computer and browser components are invoked through their respective local tool interfaces.
- The filesystem component requires command-line directories or MCP roots before operating.
- The extension connects only to a loopback WebSocket.
- The code component resolves relative paths from the current working directory and limits displayed text.
Source & flagged code
12 flagged · loading sourcePackage source references child process execution.
dist/computer-mcp/dist/index.jsView on unpkg · L53Source file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/computer-mcp/dist/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to @octavus/agent@1.0.20.
See all versions of @octavus/agent for other recorded verdicts.
- Review the evidence and your use of @octavus/agent@1.0.20 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.