registry / @lensmcp/vite-plugin / 1.24.2
@lensmcp/vite-plugin@1.24.2
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 24d ago · by lpm-firewall-aiSource inspection supports a development observability plugin: its bridge and instrumentation dependencies match its exported Vite plugin, and its default bridge host is loopback. The diagnostic capture is package-aligned, with no concrete attack behavior identified.
Static reason
One or more suspicious static signals were detected.
Trigger
A project enables the plugin and starts Vite serve mode; the browser client is injected by default.
Impact
Diagnostic data may include application console arguments and requested URLs, but the inspected source establishes no unrelated recipient or malicious action.
Mechanism
The browser client forwards console events and fetch metadata to the bridge. Its default host is loopback.
AI rationale
Source inspection supports a development observability plugin: its bridge and instrumentation dependencies match its exported Vite plugin, and its default bridge host is loopback. The diagnostic capture is package-aligned, with no concrete attack behavior identified.
Network endpoints1
127.0.0.1
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exports a Vite plugin entrypoint and declares matching LensMCP bridge and instrumentation dependencies.
- The plugin is enabled for Vite serve mode by default and defaults its WebSocket host to loopback.
- When the injected browser client runs, it forwards console events and fetch metadata to the LensMCP bridge for development diagnostics.
- The inspected source shows no credential collection, external exfiltration, or install-time execution.
Evidence against
- The plugin observes console arguments and fetch URLs, which can include application data; the inspected code routes these events through its development bridge.
Behavioral surface
EnvironmentVars
HighEntropyStringsMinified
Source & flagged code
6 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,h=g((e,t)=>G(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 · L11led??!0,p=e.wsHost??"127.0.0.1",i=e.injectClient??!0;let f,c,s;const l=x(t),m=e.aliasValtio??!0,S=e.transformSource??!0,w=e.applyOnBuild??process.env.LENSMCP_VITE_APPLY_ON_BUILD==="1";return{name:"@lensmcp/vite-plugin",apply:h((n,a)=>r&&(a.command==="serve"||w),"apply"),enforce:"pre",wsPort:h(()=>f,"wsPort"),config(n){if(!r)return;const a=checkoutViteCacheDi
Low
Ai Review Evidence
The plugin is enabled for Vite serve mode by default and defaults its WebSocket host to loopback.
lib/plugin.jsView on unpkg · L1335try { send({ kind: 'console', level, args: args.map((a) => safe(a)) }); } catch {}
const result = original.apply(this, args);
// Vite's only signal that it gave up on the HMR socket is this line (see the HMR watchdog above).
if (level === 'error' && typeof args[0] === 'string' && args[0].indexOf(VITE_GAVE_UP) === 0) {
try { onViteGaveUp(args[0]); } catch (
Findings
1 High2 Medium6 Low
HighCopied Package Dependency Bridgelib/plugin.js
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowHigh Entropy Strings
LowSuspicious Dependency Evidencepackage.json
LowSuspicious Dependency Evidenceindex.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.24.2.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.24.2 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.