@lensmcp/vite-plugin@1.25.12
⚠ Under reviewLensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe inspected plugin and bridge source show Vite instrumentation and a local WebSocket event bridge, with no confirmed attack behavior. The selected @lensmcp/react-instrumentation dependency is unresolved and is reached by the transform path, so the source review cannot support a clean verdict.
Decision evidence
public snapshot- The manifest declares @lensmcp/react-instrumentation as a runtime dependency.
- The plugin dynamically imports that dependency during source transformation; its package source was unavailable for inspection, leaving a selected runtime dependency unresolved.
- The inspected bridge code maps browser event envelopes and opens a WebSocket server using configured host and port values.
- The manifest has no lifecycle scripts, and the inspected bridge server accepts WebSocket connections rather than sending events to a remote collector.
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 dynamically imports that dependency during source transformation; its package source was unavailable for inspection, leaving a selected runtime dependency unresolved.
lib/plugin.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.25.12.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.25.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.