@lensmcp/vite-plugin@1.25.35
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe package's bridge and browser instrumentation match its stated Vite observability purpose, and the bridge defaults to loopback with a generated token. Replay is enabled by default when no setting disables it, but the reviewed code sends it to that bridge rather than an unrelated external host.
Decision evidence
public snapshot- The package describes itself as a Vite plugin for source transformation and a browser event bridge.
- When Vite configures the dev server, the plugin starts its bridge with a generated token.
- The injected browser runtime sends events and replay data to the bridge host and port.
- The bridge defaults to the loopback address 127.0.0.1.
- Replay can be disabled with an option or environment setting; otherwise it follows capture settings and defaults on if those settings cannot be read.
Source & flagged code
6 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
lib/plugin.jsView on unpkg · L1When Vite configures the dev server, the plugin starts its bridge with a generated token.
lib/plugin.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.25.35.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.25.35 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.