registry / @lensmcp/vite-plugin / 1.22.3
@lensmcp/vite-plugin@1.22.3
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 27d ago · by lpm-firewall-aiSource inspection shows a Vite development instrumentation plugin whose browser client reports diagnostics to a bridge, defaulting to loopback. No install-time execution, unrelated fixed recipient, or concrete malicious behavior was identified.
Static reason
One or more suspicious static signals were detected.
Trigger
A project enables and runs the plugin under Vite’s dev server.
Impact
Diagnostic data may include application console content and request URLs, but the inspected behavior is consistent with the plugin’s stated instrumentation role and does not establish an attack surface.
Mechanism
The browser client sends console events and fetch request metadata to the bridge; the default host is loopback.
AI rationale
Source inspection shows a Vite development instrumentation plugin whose browser client reports diagnostics to a bridge, defaulting to loopback. No install-time execution, unrelated fixed recipient, or concrete malicious behavior was identified.
Evidence
package.jsonlib/plugin.js
Network endpoints1
127.0.0.1
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exports a Vite plugin entry point and lists matching LensMCP instrumentation dependencies.
- The plugin defaults to enabled and uses 127.0.0.1 as its WebSocket host.
- The dev-server hook starts the bridge when the plugin is enabled.
- The injected browser client sends console events and fetch metadata through its WebSocket; this is consistent with the plugin’s instrumentation purpose.
Evidence against
- The inspected manifest and entry point show no install lifecycle hook; runtime behavior is activated through the Vite plugin.
- The default WebSocket host is loopback; no unrelated fixed recipient or credential harvesting was identified in the inspected source.
Behavioral surface
EnvironmentVars
HighEntropyStringsMinified
Source & flagged code
8 flaggedlib/plugin.jsView file
1package = @lensmcp/vite-plugin; repositoryIdentity = lensmcp; dependency = @babel/core
L1: "use strict";var V=Object.defineProperty;var p=(e,t)=>V(e,"name",{value:t,configurable:!0});var $=Object.defineProperty,d=p((e,t)=>$(e,"name",{value:t,configurable:!0}),"u");import...
L2: (() => {
High
Copied Package Dependency Bridge
Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.
lib/plugin.jsView on unpkg · L11const o=e.enabled??!0,m=e.wsHost??"127.0.0.1",a=e.injectClient??!0;let v,u;const g=L(t),l=e.aliasValtio??!0,b=
Low
Ai Review Evidence
The plugin defaults to enabled and uses 127.0.0.1 as its WebSocket host.
lib/plugin.jsView on unpkg · L11async configureServer(n){if(!o)return;u=await z({host:m,port:e.wsPort??0,bus:t.bus,sessionId:t.sessionId}),v=u.port,n.ws.on("vite:error",s=>{g(j(s,t.sessionId))});const i=resolveExtraWatchRoots(process.env.LENSMCP_WATCH_
Low
Ai Review Evidence
The dev-server hook starts the bridge when the plugin is enabled.
lib/plugin.jsFindings
2 High2 Medium7 Low
HighCopied Package Dependency Bridgelib/plugin.js
HighSemantic Analysis Limitedpackage.json
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowHigh Entropy Strings
LowSuspicious Dependency Evidencepackage.json
LowSuspicious Dependency Evidencepackage.json
LowAi Review Evidencelib/plugin.js
LowAi Review Evidencelib/plugin.js
LowAi Review Evidencelib/plugin.js
LowAi Review Evidencelib/plugin.js
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.22.3.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.22.3 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.