@lensmcp/vite-plugin@1.25.31
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe package exports a Vite plugin with no lifecycle scripts. Its bridge defaults to loopback, replay uses the configured endpoint, and the inspected code revealed no unrelated credential collection or external exfiltration.
Decision evidence
public snapshot- Metadata identifies a Vite plugin and exports its plugin entry point; no lifecycle scripts are declared.
- The entry point exports the Vite plugin and bridge helpers.
- The plugin starts its bridge from Vite's configureServer hook and generates a per-instance token.
- The bridge host defaults to 127.0.0.1, and replay upload uses the configured endpoint with credentials omitted.
- Replay recording is controlled by the replay option, LENSMCP_REPLAY, or the capture configuration.
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 starts its bridge from Vite's configureServer hook and generates a per-instance token.
lib/plugin.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.25.31.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.25.31 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.