@lensmcp/vite-plugin@1.23.12
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 27d ago · by lpm-firewall-aiInspected package.json and lib/plugin.js show a Vite plugin with same-version first-party dependencies, no install hook, and a loopback-default bridge. The environment references support build activation and optional watch roots; no concrete malicious behavior was found.
Decision evidence
public snapshot- package.json declares same-version @lensmcp runtime dependencies and no install lifecycle hook.
- lib/plugin.js activates as a Vite plugin, defaults its WebSocket host to loopback, and starts the bridge only when enabled.
- The environment variables control opt-in build application and extra watched directories; no external network or credential exfiltration behavior was identified.
Source & flagged code
4 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
lib/plugin.jsView on unpkg · L1lib/plugin.js activates as a Vite plugin, defaults its WebSocket host to loopback, and starts the bridge only when enabled.
lib/plugin.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.23.12.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.23.12 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.