@lensmcp/vite-plugin@1.21.5
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe observed collection behavior is an explicit Vite-plugin capability and defaults to a loopback bridge. No install-time execution, external exfiltration endpoint, persistence, destructive action, or hidden payload was found.
Decision evidence
public snapshot- The Vite plugin injects a browser runtime that captures console output and fetch metadata.
- The runtime opens a WebSocket using the configured host and port; the default host is loopback.
- package.json has no preinstall, install, postinstall, or other lifecycle script.
- The package runs only when a consumer adds and enables the Vite plugin; no external endpoint, shell execution, file write, or credential harvesting is present in inspected source.
Source & flagged code
7 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
lib/plugin.jsView on unpkg · L1The Vite plugin injects a browser runtime that captures console output and fetch metadata.
lib/plugin.jsView on unpkg · L209Findings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.21.5.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.21.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.