owlmem@0.4.1
OwlMem command line: end-to-end encrypted vault for your AI agents, and a local MCP server.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe scanner’s command and network signals correspond to explicit vault features: authenticated API calls and a caller-supplied command runner. The inspected source shows no install-time execution or independent exfiltration path, so the package is clean.
Decision evidence
public snapshot- The manifest exposes one CLI entrypoint and defines no lifecycle scripts.
- Requests send a bearer token to the configured API base, which defaults to owlmem.com.
- Sensitive vault operations use an approval-required flow that waits for the owner’s response.
- The MCP command runner uses a caller-supplied command and vault references; returned output is masked.
- The MCP runner can execute shell commands with vault values in their environment, a capability that could be misused if invoked with an untrusted command.
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.1.
See all versions of owlmem for other recorded verdicts.
- Review the evidence and your use of owlmem@0.4.1 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.