@iamem/amem@0.7.4
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 default postinstall hook reports limited package and runtime metadata to the package’s own service. Install-time telemetry is warning-level under the review rules, while the other flagged persistence is user-triggered and no exfiltration of host, project, or credential data was found.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
npm installation runs the package’s postinstall hook by default.
Impact
The publisher receives an install event without an explicit user request, even though the hook offers an opt-out.
Mechanism
The hook posts package and runtime metadata to the package’s own beacon. Runtime usage telemetry is disclosed and limited to anonymous usage metadata.
AI rationale
The default postinstall hook reports limited package and runtime metadata to the package’s own service. Install-time telemetry is warning-level under the review rules, while the other flagged persistence is user-triggered and no exfiltration of host, project, or credential data was found.
Evidence
package.jsonscripts/postinstall.jsdist/telemetry.jsdist/cli.js
Network endpoints2
getamem.com/api/beacon/npm-installgetamem.com/api/beacon/usage
Decision evidence
public snapshotAI called this Suspicious at 95.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest runs scripts/postinstall.js automatically after installation.
- The install hook sends package name and version, Node version, platform, architecture, and a timestamp to the package’s getamem.com beacon; it supports an opt-out but runs by default.
- Runtime usage pings are described as anonymous, limited to feature counts and platform/runtime metadata, and can be disabled.
- Backup scheduling is reached through the explicit `amem backup schedule` command.
Evidence against
- The install hook does not include hostnames, usernames, project paths, environment variables, or file contents in its payload.
- The package describes its runtime telemetry and provides environment-variable and command-line opt-outs.
- The flagged backup persistence is installed only when the user invokes the scheduling command.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
Source & flagged code
8 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
4 High7 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
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
LowNon Install Lifecycle Scripts
LowScripts Present
Affected versions and remediation
This report applies to @iamem/amem@0.7.4.
See all versions of @iamem/amem for other recorded verdicts.
- Review the evidence and your use of @iamem/amem@0.7.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.