owlmem@0.7.6
OwlMem command line: connect your AI apps to OwlMem in one command (npx -y owlmem install), an end-to-end encrypted vault for your AI agents, and a local MCP server.
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe source supports conditional exposure of an existing credential to an operator-configured endpoint, so a warning is appropriate. The default recipient is package-aligned, and the inspected source does not establish covert collection or malicious intent.
Decision evidence
public snapshot- The client defaults to https://owlmem.com, but OWLMEM_URL can replace the request base; requests send the token from OWLMEM_TOKEN or local configuration as a bearer credential.
- Credential-bearing calls support vault operations, MCP requests, and a command wrapper that loads user-selected vault values into a child process environment. These are runtime operations, not install hooks.
- The manifest exposes owlmem.mjs as a CLI and declares no lifecycle scripts.
- The inspected source does not show a hidden package-selected recipient: the default host is the OwlMem service, while another destination requires the operator to set OWLMEM_URL.
- The reviewed callers use the shared request helper for vault and user-invoked client operations; no automatic install-time credential transfer is shown.
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 · L40Findings
Affected versions and remediation
This report applies to owlmem@0.7.6.
See all versions of owlmem for other recorded verdicts.
- Review the evidence and your use of owlmem@0.7.6 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.