registry / @iamem/amem / 0.4.3
@iamem/amem@0.4.3
Local personal agent memory for Cursor and Claude Code. Private to your machine — never shared.
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe postinstall hook sends limited package and runtime metadata to getamem.com, the package's matching service domain, and supports disabling the request through an environment variable. The inspected configuration and backup writes are reached through CLI feature paths, and no concrete attack behavior was established.
Static reason
One or more suspicious static signals were detected.
Trigger
npm installation triggers the beacon; invoking Cursor setup, rules sync, or backup schedule activates the corresponding feature.
Impact
The inspected behavior supports package telemetry and requested product setup, with no confirmed credential theft, harmful persistence, or unconsented agent control.
Mechanism
The beacon posts package and runtime metadata to getamem.com. CLI commands write generated Cursor configuration or install a scheduled local backup.
AI rationale
The postinstall hook sends limited package and runtime metadata to getamem.com, the package's matching service domain, and supports disabling the request through an environment variable. The inspected configuration and backup writes are reached through CLI feature paths, and no concrete attack behavior was established.
Evidence
scripts/postinstall.jsdist/install/cursor.jsdist/rules-sync.jsdist/backup-schedule.js
Network endpoints1
getamem.com
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json runs scripts/postinstall.js after installation.
- The install beacon sends package, version, Node version, platform, architecture, and timestamp to getamem.com, the package's matching service domain.
- The beacon exits when AMEM_TELEMETRY_DISABLED, CI, or test mode is set.
- The Cursor installer writes generated rules and hooks, and the CLI calls it for Cursor setup.
- Pinned rule sync is feature-gated and exposed through the CLI rules sync command.
- The inspected dependency hook builds its native module; its entrypoint loads local database modules, and search queries local full-text data.
Evidence against
- The beacon runs automatically after installation unless disabled; the inspected payload contains package and runtime metadata.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
HighEntropyStrings
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.4.3.
See all versions of @iamem/amem for other recorded verdicts.
- Review the evidence and your use of @iamem/amem@0.4.3 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.