registry / @iamem/amem / 0.4.1
@iamem/amem@0.4.1
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 reviewed lifecycle behavior is a disclosed, package-aligned install ping with limited metadata, while the flagged agent configuration and backup writes are reached through explicit CLI commands. The inspected dependency install step is ordinary native setup, and the source does not establish a concrete attack surface.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing the package triggers the postinstall hook.
Impact
The request reports an installation to the package endpoint; the inspected payload does not include user, project, or credential data.
Mechanism
The hook sends the package name and version, Node version, platform, architecture, and timestamp; it skips this request when telemetry is disabled, in CI, or during tests.
AI rationale
The reviewed lifecycle behavior is a disclosed, package-aligned install ping with limited metadata, while the flagged agent configuration and backup writes are reached through explicit CLI commands. The inspected dependency install step is ordinary native setup, and the source does not establish a concrete attack surface.
Evidence
package.jsonscripts/postinstall.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
- The manifest runs a postinstall script; it also declares better-sqlite3 as its runtime dependency.
- The postinstall hook sends package and runtime details to getamem.com, and skips the ping when telemetry is disabled, in CI, or during tests. The README describes an optional anonymous install ping.
- Cursor hook setup and pinned-rule sync are invoked by explicit CLI commands; backup scheduling is also invoked through an explicit CLI command.
- The inspected better-sqlite3 install script uses its native prebuild or node-gyp setup, and its entrypoint re-exports its database implementation.
- Search builds a parameterized local query scoped to the repository and a limit.
Evidence against
- The postinstall hook sends an install event automatically unless one of its skip conditions applies.
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.1.
See all versions of @iamem/amem for other recorded verdicts.
- Review the evidence and your use of @iamem/amem@0.4.1 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.