@lensmcp/vite-plugin@1.22.4
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe flagged runtime bridge is first-party package functionality: the source defaults to a loopback host and sends browser telemetry to the configured bridge. The inspected behavior is package-aligned and does not establish malicious activity.
Decision evidence
public snapshot- The package entrypoint exposes the Vite plugin, and the manifest identifies matching LensMCP bridge and instrumentation dependencies.
- The plugin defaults its WebSocket host to loopback and injects a browser client that connects to the configured host and port.
- The injected client reports fetch URLs and results to the bridge; this is consistent with the plugin’s stated browser event bridge function.
- No install lifecycle scripts are declared in the manifest.
- Inspected source shows no credential collection or outbound credential forwarding; observed browser events go to the configured bridge endpoint.
Source & flagged code
7 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 loopback and injects a browser client that connects to the configured host and port.
lib/plugin.jsView on unpkg · L1The plugin defaults its WebSocket host to loopback and injects a browser client that connects to the configured host and port.
Findings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.22.4.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.22.4 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.