@lensmcp/vite-plugin@1.25.5
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 16d ago · by lpm-firewall-aiSource inspection found browser telemetry aligned with the Vite plugin's stated observability purpose, sent through a configurable WebSocket bridge that defaults to localhost. The inspected source did not establish a malicious attack surface.
Decision evidence
public snapshot- package.json identifies the package and points its main and module entries to index.js; that entry exports the Vite plugin implementation.
- The plugin activates for Vite serve by default, with build activation controlled by applyOnBuild or an environment setting; its WebSocket host defaults to 127.0.0.1.
- The server bridge receives a generated token and uses the configured host and port; the browser runtime connects to the injected WebSocket URL.
- The runtime sends browser diagnostics and instrumentation events over that bridge, including page URL and fetch metadata, consistent with the package's Vite observability purpose.
Source & flagged code
9 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
lib/plugin.jsView on unpkg · L1package.json identifies the package and points its main and module entries to index.js; that entry exports the Vite plugin implementation.
lib/plugin.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.25.5.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.25.5 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.