registry / @lensmcp/vite-plugin / 1.25.53
@lensmcp/vite-plugin@1.25.53
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package’s runtime behavior is consistent with its stated purpose: it collects browser and build observability events and forwards them through a local bridge or an explicitly configured LensMCP sink. The inspected code shows no unrelated collector, credential theft, or concealed automatic behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
Vite invokes the plugin’s server setup when the plugin is enabled.
Impact
Expected observability data, including browser errors, console events, and fetch events, is sent to the configured LensMCP runtime.
Mechanism
The plugin injects a browser runtime that sends documented app events over a token-protected WebSocket, then publishes them to LensMCP’s in-process bus or configured event sink.
AI rationale
The package’s runtime behavior is consistent with its stated purpose: it collects browser and build observability events and forwards them through a local bridge or an explicitly configured LensMCP sink. The inspected code shows no unrelated collector, credential theft, or concealed automatic behavior.
Evidence
.lensmcp/cache/vite/... (conditional Vite cache relocation)capture.json (read for replay settings)
Network endpoints2
ws://127.0.0.1:<ephemeral-port> by default; host and port are configurableLENSMCP_UDS, LENSMCP_IPC_SOCKET, or LENSMCP_EVENT_FILE for the configured LensMCP event sink
Decision evidence
public snapshotAI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes the plugin through index.js and lists its LensMCP runtime dependencies.
- The README describes collecting browser errors, console output, fetch events, and other app events over a WebSocket as the package’s observability feature.
- The bridge starts from Vite’s configureServer hook and receives the configured host, port, and a generated token.
- The README documents forwarding events to an in-process bus or an environment-configured LensMCP sink.
Evidence against
Behavioral surface
EnvironmentVars
HighEntropyStringsMinified
Source & flagged code
5 flaggedlib/plugin.jsView file
1package = @lensmcp/vite-plugin; repositoryIdentity = lensmcp; dependency = @babel/core
L1: "use strict";var z=Object.defineProperty;var g=(e,n)=>z(e,"name",{value:n,configurable:!0});var Z=Object.defineProperty,d=g((e,n)=>Z(e,"name",{value:n,configurable:!0}),"c");import...
L2: `);if(t!==B)return null;const u=f??e.wsPort??0,r=process.env.LENSMCP_APP||process.env.NX_TASK_TARGET_PROJECT;return buildInlineClientRuntime({host:p,port:u,token:o,hmrRecovery:e.hm...
L3: (() => {
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 · L11nc configureServer(t){if(!s)return;o=Q(24).toString("base64url"),c=await ie({host:p,port:e.wsPort??0,bus:n.bus,sessionId:n.sessionId,token:o,...e.wsAllowedOrigins?{allowedOrigins:e.wsAllowedOrigins}:{}}),f=c.port,t.middlewares.use(l
Low
Ai Review Evidence
The bridge starts from Vite’s configureServer hook and receives the configured host, port, and a generated token.
lib/plugin.jsView on unpkg · L1package.jsonView file
Findings
1 High2 Medium5 Low
HighCopied Package Dependency Bridgelib/plugin.js
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowHigh Entropy Strings
LowSuspicious Dependency Evidencepackage.json
LowAi Review EvidenceREADME.md
LowAi Review Evidencelib/plugin.js
LowAi Review EvidenceREADME.md
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.25.53.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.25.53 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.