@lensmcp/vite-plugin@1.22.2
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe inspected entrypoint and flagged source implement Vite instrumentation and a local WebSocket event bridge consistent with the package's stated purpose. The scanner signals do not establish an attack surface.
Decision evidence
public snapshot- The package exports its Vite plugin through index.js and lists LensMCP bridge and instrumentation packages as runtime dependencies.
- The plugin runs when enabled as a Vite plugin, defaults its WebSocket host to 127.0.0.1, and starts the bridge on the configured host and port.
- The injected browser client sends instrumentation and development-server events over that WebSocket; the inspected excerpts show no credential collection or unrelated outbound destination.
Source & flagged code
5 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
lib/plugin.jsView on unpkg · L1The plugin runs when enabled as a Vite plugin, defaults its WebSocket host to 127.0.0.1, and starts the bridge on the configured host and port.
lib/plugin.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.22.2.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.22.2 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.