@lensmcp/vite-plugin@1.25.16
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 15d ago · by lpm-firewall-aiSource inspection shows an ordinary Vite observability plugin with a loopback event bridge and aligned LensMCP dependencies. The scanner’s bridge signal reflects an explicit runtime dependency, and no concrete attack surface was found.
Decision evidence
public snapshot- The manifest exports the Vite plugin entrypoint and declares the bridge and core as same-version dependencies.
- The plugin starts its bridge when Vite serves; build use requires an explicit environment opt-in or configuration.
- The bridge exports a server and publisher, and its event mapper converts browser console events into client-runtime events.
- The inspected bridge and core manifests identify same-version LensMCP packages; the Babel entrypoint exposes compiler APIs.
- No attack behavior was identified in the inspected entrypoints or required dependency paths.
Source & flagged code
9 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 when Vite serves; build use requires an explicit environment opt-in or configuration.
lib/plugin.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.25.16.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.25.16 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.