@lensmcp/vite-plugin@1.25.49
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package behavior matches its stated purpose: instrumenting a Vite app and sending captured events to a local LensMCP bridge. The flagged source structure and dependency bridge imports did not reveal an unrelated collector, credential theft, or other concrete attack.
Decision evidence
public snapshot- The package entrypoint only re-exports the Vite plugin and event mapper.
- The README describes the browser events the plugin collects and says they are sent to LensMCP over a local WebSocket.
- The plugin defaults its WebSocket host to 127.0.0.1 and creates a per-server token for the injected runtime.
- Session replay is documented as streaming recordings to the bridge, with a LENSMCP_REPLAY setting to disable it.
- The package metadata and entrypoint show no install-time hook or top-level action.
- The reviewed data flow uses the plugin's local bridge; no unrelated collector or credential theft was identified.
- The scanner flags and minified source did not reveal concrete attack behavior.
Source & flagged code
7 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
lib/plugin.jsView on unpkg · L1Source fingerprint signature matches a known malicious package signature; route for source-aware review.
lib/plugin.jsView on unpkgFindings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.25.49.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.25.49 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.