@lensmcp/vite-plugin@1.21.1
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection shows an explicitly integrated development observability plugin, not install-time or covert malware. Its telemetry hooks are package-aligned, user-invoked, and default to a loopback bridge with no fixed external receiver.
Decision evidence
public snapshot- Explicitly configured Vite plugin injects a browser observability runtime.
- Runtime captures console, error, fetch, and route metadata over a WebSocket.
- WebSocket host defaults to loopback but is configurable by the plugin user.
- package.json has no lifecycle scripts.
- No child-process, shell, eval, filesystem-write, or credential-harvesting code found.
- No fixed external endpoint or remote payload loader is present.
- The runtime is activated only when the consumer adds and enables the Vite plugin.
Source & flagged code
4 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
lib/plugin.jsView on unpkg · L1Explicitly configured Vite plugin injects a browser observability runtime.
lib/plugin.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.21.1.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.21.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.