@mnemom/mnemom@0.17.23
Transparent AI agent tracing
AI Security Review
scanned 3h ago · by lpm-firewall-aiSource inspection confirms that an Anthropic API key is sent to the package’s default Mnemom gateway during the Remote Control API-key flow, without recipient-specific consent. This concrete credential disclosure supports blocking; the manifest does not establish an install-time attack.
Decision evidence
public snapshot- The agent resolves an Anthropic API key for API-key authentication and passes it to the Remote Control launch.
- The launcher sends that key to the proxy over stdin; the proxy puts it in the x-api-key header on requests routed to the gateway.
- The gateway door defaults to https://gateway.mnemom.ai, with an override available.
- The package manifest has no install hook; its prepublishOnly script only runs the build.
- The transfer is part of an agent launch and can use a configured gateway override.
- No install-time credential transfer is established.
Source & flagged code
6 flagged · loading sourcePackage source references child process execution.
dist/lib/update/min-version.jsView on unpkg · L6Package source references shell execution.
dist/lib/oauth.js#virtual:normalized:round1View on unpkg · L272Findings
Affected versions and remediation
This report applies to @mnemom/mnemom@0.17.23.
See all versions of @mnemom/mnemom for other recorded verdicts.
- Avoid installing @mnemom/mnemom@0.17.23. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.