@lensmcp/vite-plugin@1.22.5
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 27d ago · by lpm-firewall-aiSource inspection shows user-invoked Vite instrumentation with matching LensMCP dependencies and a loopback WebSocket default. The reporting behavior fits the package function, and no concrete malicious behavior was identified.
Decision evidence
public snapshot- The manifest identifies a Vite plugin with matching LensMCP runtime dependencies and no install lifecycle hook.
- The plugin activates through Vite and defaults its WebSocket host to loopback; its browser runtime reports console and fetch metadata for observability.
- Fetch reporting sends request URLs and status metadata, but inspected code shows no credential collection or unrelated network destination.
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 plugin activates through Vite and defaults its WebSocket host to loopback; its browser runtime reports console and fetch metadata for observability.
lib/plugin.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.22.5.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.22.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.