@lensmcp/vite-plugin@1.23.13
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe flagged runtime bridge connects to matching first-party LensMCP components, while the source shows Vite instrumentation over a loopback-default WebSocket. No concrete malicious behavior was identified.
Decision evidence
public snapshot- The manifest has no install lifecycle scripts and depends on matching @lensmcp bridge and instrumentation packages.
- The plugin is enabled by default for Vite serve and defaults its WebSocket host to loopback; build application requires explicit configuration.
- The browser runtime sends instrumentation and page events over the plugin WebSocket, consistent with the package’s Vite observability purpose.
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 is enabled by default for Vite serve and defaults its WebSocket host to loopback; build application requires explicit configuration.
lib/plugin.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.23.13.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.23.13 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.