@lensmcp/vite-plugin@1.24.3
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 23d ago · by lpm-firewall-aiSource inspection supports ordinary Vite observability behavior: the manifest uses version-matched LensMCP bridge and instrumentation dependencies, and the runtime sends event batches to the configured bridge. No malicious behavior was established.
Decision evidence
public snapshot- The manifest points to an entrypoint with version-matched LensMCP bridge and instrumentation dependencies, consistent with a Vite observability plugin.
- The plugin activates during Vite serve by default and builds a browser WebSocket URL from its configured host, server port, and token.
- The injected browser runtime sends queued event batches to that WebSocket; the inspected code shows no unrelated external recipient or credential collection.
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 activates during Vite serve by default and builds a browser WebSocket URL from its configured host, server port, and token.
lib/plugin.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.24.3.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.24.3 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.