@lensmcp/vite-plugin@1.24.4
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe runtime behavior is consistent with a Vite diagnostics plugin: its default bridge host is loopback, and its client reports browser events to that bridge. The scanner’s bridge signal is explained by the manifest’s matching LensMCP bridge dependency and the source’s local event transport.
Decision evidence
public snapshot- The manifest points package imports to index.js and lists matching LensMCP bridge and instrumentation dependencies.
- The plugin defaults to enabled for Vite serve and uses 127.0.0.1 as its default host.
- The development server creates a tokenized bridge on that host using an ephemeral port by default.
- The injected client sends browser readiness and diagnostic events, including console and fetch metadata, through the bridge.
- The entrypoint exports the Vite plugin and its bridge envelope helper.
- The inspected source shows no package-selected external recipient or credential collection; the observed event transport is the plugin’s local development bridge.
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 defaults to enabled for Vite serve and uses 127.0.0.1 as its default host.
lib/plugin.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.24.4.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.24.4 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.