@lensmcp/vite-plugin@1.25.50
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe entry point exposes the Vite plugin and LensMCP event mapping, and the plugin starts its authenticated bridge when Vite configures a server. The reviewed source shows no install-time behavior or unrelated collection; runtime event handling fits the package’s observability purpose.
Decision evidence
public snapshot- package.json declares no lifecycle scripts and exports index.js as its entry point.
- index.js exports the Vite plugin and an event mapper from the LensMCP bridge.
- The plugin defaults its WebSocket host to 127.0.0.1 and starts the bridge during Vite server configuration with a generated token and the supplied bus and session ID.
- The event mapper converts client runtime errors into LensMCP events, consistent with the package’s stated observability purpose.
Source & flagged code
6 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
lib/plugin.jsView on unpkg · L1The plugin defaults its WebSocket host to 127.0.0.1 and starts the bridge during Vite server configuration with a generated token and the supplied bus and session ID.
lib/plugin.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.25.50.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.25.50 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.