registry / @iamem/amem / 0.4.0
@iamem/amem@0.4.0
Local personal agent memory for Cursor and Claude Code. Private to your machine — never shared.
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe automatic postinstall sends limited package metadata to the package-aligned getamem.com endpoint and has opt-out and CI/test guards. The flagged agent configuration and persistence behaviors are invoked through explicit commands, and the inspected dependency install is ordinary native setup.
Static reason
One or more suspicious static signals were detected.
Trigger
npm installation triggers the metadata ping; Cursor setup, rules sync, and backup scheduling require their respective user commands.
Impact
No concrete attack impact was established from these behaviors.
Mechanism
The ping posts package version, Node version, platform, architecture, and timestamp, with telemetry, CI, and test guards. Agent rules, hooks, and backup schedules are written locally by their command handlers.
AI rationale
The automatic postinstall sends limited package metadata to the package-aligned getamem.com endpoint and has opt-out and CI/test guards. The flagged agent configuration and persistence behaviors are invoked through explicit commands, and the inspected dependency install is ordinary native setup.
Evidence
scripts/postinstall.jsdist/install/cursor.jsdist/rules-sync.jsdist/backup-schedule.js
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with medium false-positive risk.
Evidence for AI clean decision
- package.json declares the install hook as a package-local postinstall script.
- The hook sends only package and runtime metadata to getamem.com; it skips when telemetry is disabled, in CI, or in test mode.
- Cursor hook and rule files are written by the explicit setup command; the hook invokes amem to store local memory.
- Pinned Cursor rules are written by the explicit rules sync command after a feature check.
- The backup scheduler is reached through the explicit backup schedule command; better-sqlite3 uses its ordinary native installer, and the inspected search source performs local text indexing.
Evidence against
- The postinstall telemetry runs by default unless an opt-out or CI/test condition applies.
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.4.0.
See all versions of @iamem/amem for other recorded verdicts.
- Review the evidence and your use of @iamem/amem@0.4.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.