@lensmcp/vite-plugin@1.25.58
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 3h ago · by lpm-firewall-aiThe entry point exposes the advertised Vite plugin and bridge functionality. The bridge starts as part of Vite server configuration and defaults to the loopback host; the suspiciously flagged event-mappers.js is not imported by the entry point.
Decision evidence
public snapshot- The package entry point exports the Vite plugin and bridge event mapper.
- The plugin starts its bridge from Vite’s server configuration and defaults its host to 127.0.0.1.
- The bridge dependency handles client event envelopes and publishes mapped events through a configured bus or sink.
- The manifest declares LensMCP bridge and instrumentation dependencies consistent with the plugin’s stated purpose.
- The flagged event-mappers.js file is not imported by the plugin entry point; the entry point uses envelopeToEvent from @lensmcp/bridge.
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 starts its bridge from Vite’s server configuration and defaults its host to 127.0.0.1.
lib/plugin.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.25.58.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.25.58 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.