@lensmcp/vite-plugin@1.25.30
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe reviewed code matches the package’s stated purpose: it instruments a Vite-served app and forwards browser events to a local LensMCP bridge. Replay uses that same host and port, with an option to disable it; no unrelated external endpoint or harmful behavior was identified.
Decision evidence
public snapshot- The package describes itself as a LensMCP Vite plugin providing a browser event bridge and identifies its repository as the LensMCP project.
- When Vite configures the dev server, the plugin creates a bridge with a random token; the bridge checks allowed origins and validates the token on connections.
- The replay client is configured to send to an HTTP endpoint built from the bridge host and port, and its uploader uses POST requests. The default host is local, and the host is configurable.
- Replay can be disabled with LENSMCP_REPLAY=0/off/false or with the plugin option.
Source & flagged code
7 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
lib/plugin.jsView on unpkg · L1When Vite configures the dev server, the plugin creates a bridge with a random token; the bridge checks allowed origins and validates the token on connections.
lib/plugin.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.25.30.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.25.30 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.