registry / @lensmcp/vite-plugin / 1.25.6
@lensmcp/vite-plugin@1.25.6
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe flagged dependency bridge is declared alongside the package’s matching LensMCP instrumentation dependencies and is used for the plugin’s development telemetry. The source shows no lifecycle hook or concrete malicious behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
A consumer configures the plugin in a Vite development server; client injection is enabled by default.
Impact
Development telemetry, including console data and fetch metadata, reaches the local LensMCP bridge; no unrelated recipient or concrete attack behavior was established.
Mechanism
The plugin starts a token-protected WebSocket bridge, bound to loopback by default, and the injected runtime sends browser events to it.
AI rationale
The flagged dependency bridge is declared alongside the package’s matching LensMCP instrumentation dependencies and is used for the plugin’s development telemetry. The source shows no lifecycle hook or concrete malicious behavior.
Network endpoints1
127.0.0.1
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json declares LensMCP bridge and instrumentation dependencies and identifies the LensMCP repository.
- The plugin defaults to Vite development serving, binds the bridge to loopback by default, and creates a per-start token.
- The injected runtime sends bounded console and fetch event data over the WebSocket to the plugin bridge.
- The runtime WebSocket uses the plugin host and port and includes the generated token.
Evidence against
- The inspected source supports the package’s declared development observability function; no unrelated recipient or concrete attack behavior was identified.
Behavioral surface
EnvironmentVars
HighEntropyStringsMinified
Source & flagged code
9 flaggedlib/plugin.jsView file
1package = @lensmcp/vite-plugin; repositoryIdentity = lensmcp; dependency = @babel/core
L1: "use strict";var $=Object.defineProperty;var g=(e,t)=>$(e,"name",{value:t,configurable:!0});var G=Object.defineProperty,u=g((e,t)=>G(e,"name",{value:t,configurable:!0}),"d");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 · L11injectClient??!0;let p,c,o;const l=x(t),f=e.aliasValtio??!0,S=e.transformSource??!0,w=e.applyOnBuild??process.env.LENSMCP_VITE_APPLY_ON_BUILD==="1";return{name:"@lensmcp/vite-plugin",apply:u((n,a)=>r&&(a.command==="serve"||w),"apply"),enforce:"pre",wsPort:u(()=>p,"wsPort"),config(n){if(!r)return;const a=checkoutViteCacheDir(n?.root,n?.cacheDir);a&&console.log(`[lensmcp] node_modules is shared with another checkout \u2014 Vite's dependency cache moves to ${
Low
Ai Review Evidence
The plugin defaults to Vite development serving, binds the bridge to loopback by default, and creates a per-start token.
lib/plugin.jsView on unpkg · L11nd:/^valtio$/,replacement:"@lensmcp/valtio-instrumentation"}]}}:Object.keys(s).length?s:void 0},async configureServer(n){if(!r)return;o=J(24).toString("base64url"),c=await ee({host:h,port:e.wsPort??0,bus:t.bus,sessionId:t.sessionId,token:o,...e.wsAllowedOrigin
Findings
1 High2 Medium9 Low
HighCopied Package Dependency Bridgelib/plugin.js
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowHigh Entropy Strings
LowSuspicious Dependency Evidencepackage.json
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
LowAi Review Evidencelib/plugin.js
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.25.6.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.25.6 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.