registry / @iamem/amem / 0.3.4
@iamem/amem@0.3.4
Local personal agent memory for Cursor and Claude Code. Private to your machine — never shared.
AI Security Review
scanned 13d ago · by lpm-firewall-aiInspected source shows a limited package-aligned install beacon and user-invoked local backup scheduling, with no confirmed malicious behavior. The flagged Cursor and rules-sync writes are local integration behavior, and the inspected dependency install hook builds its native module.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Package installation sends the beacon; backup persistence requires running `amem backup schedule`.
Impact
The beacon permits package install telemetry. The backup schedule runs local backups at the configured time; inspected source does not establish credential disclosure, destructive behavior, or stealth persistence.
Mechanism
The beacon posts package version, Node version, platform, and architecture. The backup command writes a platform-specific local schedule for encrypted backups.
AI rationale
Inspected source shows a limited package-aligned install beacon and user-invoked local backup scheduling, with no confirmed malicious behavior. The flagged Cursor and rules-sync writes are local integration behavior, and the inspected dependency install hook builds its native module.
Evidence
scripts/postinstall.jsdist/backup-schedule.jsdist/cli.jsdist/install/cursor.jsdist/rules-sync.js
Network endpoints1
getamem.com
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook sends package version, Node version, platform, and architecture to getamem.com; it does not collect host, user, home, or project identifiers in the inspected request body.
- The install beacon is skipped when AMEM_TELEMETRY_DISABLED, CI, or NODE_ENV=test is set.
- Backup scheduling is exposed through the explicit `amem backup schedule` command; the flagged module writes a local backup schedule.
- Cursor hook installation writes an amem hook entry into Cursor configuration; rules sync writes a generated local rule file.
- The required better-sqlite3 dependency source has a native build install script, and its inspected entrypoint delegates to its database module.
Evidence against
- The postinstall beacon runs automatically unless an opt-out, CI, or test condition applies.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
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
HighPrevious Version Dangerous Deltadist/backup-schedule.js
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.3.4.
See all versions of @iamem/amem for other recorded verdicts.
- Review the evidence and your use of @iamem/amem@0.3.4 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.