registry / @iamem/amem / 0.1.2
@iamem/amem@0.1.2
Local personal agent memory for Cursor and Claude Code. Private to your machine — never shared.
AI Security Review
scanned 28d ago · by lpm-firewall-aiThe install lifecycle performs a limited telemetry request to the package's own domain and does not access credentials in the reviewed code. The flagged agent configuration and backup operations are exposed through explicit CLI setup paths, so the source does not establish a concrete attack surface.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Package installation triggers the telemetry hook; Cursor and pinned-rule writes require invoking their CLI setup commands.
Impact
The telemetry reveals basic installation and platform metadata. The reviewed source does not establish credential theft, remote code execution, or unconsented agent configuration changes during installation.
Mechanism
The telemetry hook posts package/version and runtime platform fields to getamem.com. The reviewed setup functions write generated Cursor rules or hooks, and the backup scheduler creates a local scheduled backup when explicitly invoked.
AI rationale
The install lifecycle performs a limited telemetry request to the package's own domain and does not access credentials in the reviewed code. The flagged agent configuration and backup operations are exposed through explicit CLI setup paths, so the source does not establish a concrete attack surface.
Evidence
package.jsonscripts/postinstall.jsdist/install/cursor.jsdist/rules-sync.jsdist/backup-schedule.jsdist/embed.jsdist/cli.js
Network endpoints1
getamem.com
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json runs a postinstall telemetry script; its prepare script only builds the package.
- The postinstall request sends package, version, Node version, platform, and architecture to getamem.com.
- Cursor rule installation writes under the selected repository's .cursor/rules directory.
- Pinned rules are generated from pinned local claims and written under the repository's .cursor/rules directory.
- Cursor installation is called from the CLI's Cursor setup path.
- Pinned rule synchronization is called from a CLI command.
- Backup scheduling is exposed as an explicit function and creates a user backup directory when called.
- The flagged embedding backend handles a caller-configured external command; this excerpt shows no remote payload or credential transfer.
Evidence against
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/embed.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.1.2.
See all versions of @iamem/amem for other recorded verdicts.
- Review the evidence and your use of @iamem/amem@0.1.2 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.