registry / @iamem/amem / 0.7.5
@iamem/amem@0.7.5
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 install hook can send a small package and runtime metadata beacon, but it checks the user’s telemetry policy first; telemetry defaults to off. The flagged persistence behavior is reached through explicit backup scheduling or service installation commands.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The package manager runs the postinstall hook, which sends only if an existing telemetry policy enables it. Backup schedules and login services require their respective CLI commands.
Impact
No automatic credential, project, or memory exfiltration or unauthorized persistence was identified.
Mechanism
The install beacon sends package and runtime metadata to getamem.com. Backup scheduling writes platform-specific local schedule files when requested.
AI rationale
The install hook can send a small package and runtime metadata beacon, but it checks the user’s telemetry policy first; telemetry defaults to off. The flagged persistence behavior is reached through explicit backup scheduling or service installation commands.
Evidence
~/.amem/policy.toml~/.amem/telemetry.json~/Library/LaunchAgents/co.amem.backup.plist~/.config/systemd/user/amem-backup.service~/.config/systemd/user/amem-backup.timer
Network endpoints1
getamem.com
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package’s default policy sets telemetry to false, and the install hook stays quiet without an enabled telemetry policy.
- The install beacon payload contains the package name and version, Node version, platform, architecture, and timestamp.
- Runtime usage reporting checks that telemetry is enabled before sending.
- Backup persistence is installed only in the explicit `backup schedule` command path.
Evidence against
- The package declares a postinstall script that can send an install beacon when telemetry is enabled.
- The package can install local backup schedules and login services when their commands are invoked.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
HighEntropyStringsPossibleObfuscationUrlStrings
Source & flagged code
9 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
5 High7 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSandbox Evasion Gated Capabilityscripts/postinstall.js
HighTrigger Reachable Persistencedist/backup-schedule.js
HighSemantic Analysis Limiteddist/search.js#virtual:normalized:round1
HighPrevious Version Dangerous Deltadist/telemetry.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
Low
Affected versions and remediation
This report applies to @iamem/amem@0.7.5.
See all versions of @iamem/amem for other recorded verdicts.
- Review the evidence and your use of @iamem/amem@0.7.5 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.