@lensmcp/client-runtime
LensMCP browser-side capture layer — errors, console, fetch, and route changes streamed to the LensMCP bridge. Import '@lensmcp/client-runtime/auto' for a zero-build install in any host.
This report shows the evidence for @lensmcp/client-runtime@1.25.40. 1 of 78 known versions is blocked or flagged. The newest version, 1.25.59, is allowed. See all versions.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe default browser replay path records password fields without masking and uploads the recording to the bridge. Credential capture is unrelated to the disclosed event-capture purpose and occurs automatically when the `/auto` entry is imported.
Decision evidence
public snapshot- Importing `auto.js` immediately calls `installLensmcp`.
- Replay is enabled by default and starts unless explicitly disabled.
- The replay privacy defaults set `maskAllInputs` to false.
- The recorder explicitly sets `password` masking to false, allowing password field values into recordings.
- Replay data and blobs are POSTed to `/replay` and `/replay/blob` on the configured endpoint; the default WebSocket host is the page hostname on port 5747.
- The package has no install lifecycle scripts; the behavior is triggered by importing the documented `/auto` entry.
- The stated purpose is browser observability through a LensMCP bridge, and the bridge endpoint can be configured by the user.
Source & flagged code
8 flaggedReplay is enabled by default and starts unless explicitly disabled.
lib/auto.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @lensmcp/client-runtime@1.25.40.
The versions list below shows the verdict for each recorded version.
- Avoid installing @lensmcp/client-runtime@1.25.40. 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.