@iamem/amem@0.7.3
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 default postinstall hook sends limited telemetry to getamem.com, which makes this suspicious under the install-time telemetry rule. The reviewed backup persistence is user-triggered, and the telemetry payload contains no sensitive machine or project details.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall, unless AMEM_TELEMETRY_DISABLED, CI, or NODE_ENV=test is set.
Impact
The install event is disclosed to the package service; the observed payload does not contain host, user, project, or credential data.
Mechanism
The hook sends an HTTPS POST to getamem.com with the package name and version, Node version, platform, architecture, and timestamp.
AI rationale
The default postinstall hook sends limited telemetry to getamem.com, which makes this suspicious under the install-time telemetry rule. The reviewed backup persistence is user-triggered, and the telemetry payload contains no sensitive machine or project details.
Evidence
package.jsonscripts/postinstall.js
Network endpoints1
getamem.com
Decision evidence
public snapshotAI called this Suspicious at 97.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest runs scripts/postinstall.js during installation.
- The postinstall hook sends package name and version, Node version, platform, architecture, and a timestamp; it does not include host, user, project, or credential data.
- The hook POSTs the payload to getamem.com, with opt-outs for AMEM_TELEMETRY_DISABLED, CI, and NODE_ENV=test.
- Backup persistence is created only by the explicit `amem backup schedule` command.
Evidence against
- The install ping contains package and runtime metadata rather than machine identifiers or sensitive data.
- The package describes itself as local personal agent memory, and the reported backup schedule is an explicit user command.
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.3.
See all versions of @iamem/amem for other recorded verdicts.
- Review the evidence and your use of @iamem/amem@0.7.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.