registry / @lensmcp/vite-plugin / 1.25.1
@lensmcp/vite-plugin@1.25.1
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 17d ago · by lpm-firewall-aiThe manifest has no install lifecycle hooks, and the runtime is activated through Vite plugin configuration. Its inspected event transfer supports the package’s stated observability function and defaults to a local bridge; no concrete attack behavior was found.
Static reason
One or more suspicious static signals were detected.
Trigger
A consumer adds the plugin to Vite configuration and starts the development server; build instrumentation requires explicit opt-in.
Impact
Events are available to the local LensMCP bridge; inspected source does not establish unauthorized collection or transfer.
Mechanism
The plugin injects a browser client that sends observability events, including fetch metadata, to the bridge. The default host is loopback, though the consumer can configure it.
AI rationale
The manifest has no install lifecycle hooks, and the runtime is activated through Vite plugin configuration. Its inspected event transfer supports the package’s stated observability function and defaults to a local bridge; no concrete attack behavior was found.
Network endpoints1
127.0.0.1
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest identifies the package, exports its Vite entrypoint, and lists matching LensMCP dependencies; it contains no lifecycle scripts.
- The plugin defaults its WebSocket host to loopback and runs on Vite serve, with builds requiring an explicit opt-in.
- When enabled, it starts a bridge on the configured host and port, using a generated token.
- The injected client connects to that bridge, and its fetch instrumentation reports request metadata as observability events.
Evidence against
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 G=Object.defineProperty;var g=(e,t)=>G(e,"name",{value:t,configurable:!0});var J=Object.defineProperty,w=g((e,t)=>J(e,"name",{value:t,configurable:!0}),"g"),q=Obje...
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 · L11wsHost??"127.0.0.1",i=e.injectClient??!0;let p,c,o;const l=W(t),f=e.aliasValtio??!0,R=e.transformSource??!0,y=e.applyOnBuild??process.env.LENSMCP_VITE_APPLY_ON_BUILD==="1";return{name:"@lensmcp/vite-plugin",apply:u((n,a)=>r&&(a.command==="serve"||y),"apply"),enforce:"pre",wsPort:u(()=>p,"wsPort"),config(n){if(!r)return;const a=checkoutVit
Low
Ai Review Evidence
The plugin defaults its WebSocket host to loopback and runs on Vite serve, with builds requiring an explicit opt-in.
lib/plugin.jsView on unpkg · L11configureServer(n){if(!r)return;o=z(24).toString("base64url"),c=await ne({host:h,port:e.wsPort??0,bus:t.bus,sessionId:t.sessionId,token:o,...e.wsAllowedOrigins?{allowedOrigins:e.wsAllowedOrigins}:{}}),p=c.port,n.middlewa
Findings
1 High2 Medium6 Low
HighCopied Package Dependency Bridgelib/plugin.js
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowHigh Entropy Strings
LowSuspicious Lifecycle 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.25.1.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.25.1 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.