claude-recall@0.44.0
Persistent memory for Claude Code and Pi with native Skills integration, automatic capture, failure learning, and project scoping
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe install hook performs an unprompted, home-wide repair of package-owned Claude Code hooks, creating a real agent configuration lifecycle risk. The repair is narrowly scoped and backed up, with no inspected evidence of unrelated configuration changes or a concrete attack chain.
Decision evidence
public snapshot- `package.json` runs `scripts/postinstall.js` during installation; that script automatically launches repair with `--auto --scope all`.
- The repair scans Claude Code settings at user scope and across projects under the home directory. It targets recognizable Claude Recall hooks and proposes a replacement only for stale commands when the hook ID is known and the package is on `PATH`.
- When a repair applies, it backs up each settings file before writing the change. The install hook supplies `--auto`, so this repair can happen without an interactive confirmation.
- The other inspected integration code shows explicit CLI setup for installing hooks, project skill generation, and memory sync to Claude Code’s memory directory. The MCP repair module addresses server registration separately.
- The automatic repair is limited to existing Claude Recall hook commands; the inspected logic does not show it adding hooks or changing unrelated hook commands.
Source & flagged code
20 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to claude-recall@0.44.0.
See all versions of claude-recall for other recorded verdicts.
- Review the evidence and your use of claude-recall@0.44.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.