@iamem/amem@0.7.0
Local personal agent memory for Cursor and Claude Code. Private to your machine — never shared.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe postinstall hook sends telemetry by default, which the review rules classify as suspicious even though the payload is limited and the behavior is disclosed with an opt-out. The flagged backup persistence is only installed through an explicit CLI command.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install, unless CI or test mode is active or AMEM_TELEMETRY_DISABLED is set.
Impact
The vendor receives install and runtime platform counts; no sensitive host or project data was identified in the payload.
Mechanism
scripts/postinstall.js posts package, version, Node, platform, architecture, and timestamp fields to getamem.com.
AI rationale
The postinstall hook sends telemetry by default, which the review rules classify as suspicious even though the payload is limited and the behavior is disclosed with an opt-out. The flagged backup persistence is only installed through an explicit CLI command.
Evidence
package.jsonscripts/postinstall.js
Network endpoints1
getamem.com
Decision evidence
public snapshotAI called this Suspicious at 95.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest runs scripts/postinstall.js during npm installation.
- The hook posts an npm_install event to getamem.com.
- The event contains the package name and version, Node version, platform, architecture, and timestamp.
- The package documents the install ping and offers AMEM_TELEMETRY_DISABLED=1 to opt out.
- Backup scheduling is invoked through the explicit `amem backup schedule` command.
Evidence against
- The telemetry payload does not include credentials, hostnames, usernames, paths, environment variables, or project contents.
- The install ping is skipped in CI, test mode, or when AMEM_TELEMETRY_DISABLED is set.
- The backup persistence behavior is behind an explicit CLI command, not an automatic install action.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
7 flaggedpackage.jsonView file
•scripts.postinstall = node ./scripts/postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node ./scripts/postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/app-shell.jsView file
28try {
L29: const require = createRequire(pkgJson);
L30: const bin = require("electron");
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/app-shell.jsView on unpkg · L28Findings
3 High7 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighTrigger Reachable Persistencedist/backup-schedule.js
HighSemantic Analysis Limiteddist/search.js#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requiredist/app-shell.js
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencedist/backup-schedule.js
MediumShips Build Helperscripts/mdm-offboard.sh
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to @iamem/amem@0.7.0.
See all versions of @iamem/amem for other recorded verdicts.
- Review the evidence and your use of @iamem/amem@0.7.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.