@lensmcp/vite-plugin@1.24.5
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 22d ago · by lpm-firewall-aiInspected source shows a Vite development observability plugin whose browser telemetry goes to its plugin-created bridge, defaulting to loopback. The scanner hints do not establish malicious behavior.
Decision evidence
public snapshot- The manifest points to index.js, has no lifecycle scripts, and declares version-matched LensMCP bridge and instrumentation dependencies.
- The plugin runs for Vite serve by default, uses 127.0.0.1 as its default host, and starts its bridge when the Vite server is configured.
- The browser runtime connects to the plugin-generated WebSocket and sends event frames through it.
- The runtime reports bounded console and error details, fetch metadata, and instrumentation events, consistent with the plugin’s browser-observability role.
- The entrypoint exports the Vite plugin and bridge helpers.
Source & flagged code
9 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
lib/plugin.jsView on unpkg · L1The plugin runs for Vite serve by default, uses 127.0.0.1 as its default host, and starts its bridge when the Vite server is configured.
lib/plugin.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.24.5.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.24.5 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.