owlmem@0.4.0
OwlMem command line: end-to-end encrypted vault for your AI agents, and a local MCP server.
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe flagged shell and network behavior belongs to an explicit vault feature, with vault reads routed through an approval-aware OwlMem API and matching secrets masked in tool output. The source shows no install hook, automatic command execution, or unrelated credential recipient.
Decision evidence
public snapshot- The manifest exposes owlmem.mjs as a CLI and defines no install lifecycle script.
- Requests use the OwlMem service by default and send its agent token to that service.
- Vault reads go through an approval-aware request path before decryption.
- Shell execution is exposed as an explicitly called MCP tool; it uses caller-selected vault items and masks matching values in returned output.
- The inspected runtime helpers write messages to stderr, encode item paths, and list item names and descriptions.
- The scanner flags command execution combined with network access, but the inspected shell path is the documented vault_run tool, not an automatic command or hidden exfiltration path.
Source & flagged code
7 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
owlmem.mjsView on unpkg · L27Findings
Affected versions and remediation
This report applies to owlmem@0.4.0.
See all versions of owlmem for other recorded verdicts.
- Review the evidence and your use of owlmem@0.4.0 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.