@lensmcp/vite-plugin@1.25.51
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package is a legitimate observability plugin, but replay is enabled when its settings cannot be read and the README does not specifically disclose session replay. Because this captures app session activity automatically, warn users; the inspected path sends it to the local bridge rather than an unrelated collector.
Decision evidence
public snapshot- When LENSMCP_REPLAY and the replay option are unset, failure to read the capture settings makes replayEnabled return true.
- In Vite's HTML transform, the plugin injects the replay module whenever replay is enabled.
- The replay recorder starts with a dynamically built HTTP endpoint using the plugin's host and port; the default host is 127.0.0.1.
- The package describes its normal browser event streaming, but does not disclose session replay in that description.
- The package has no lifecycle scripts; it runs as a Vite plugin when configured.
- The bridge defaults to loopback and requires a per-server token for WebSocket connections.
- The package's stated purpose is frontend observability, and it documents streaming app events to LensMCP.
Source & flagged code
5 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
lib/plugin.jsView on unpkg · L1In Vite's HTML transform, the plugin injects the replay module whenever replay is enabled.
lib/plugin.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.25.51.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.25.51 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.