@lensmcp/vite-plugin@1.25.18
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected runtime behavior is consistent with a Vite observability plugin using same-version LensMCP components and a local bridge. Static hints alone do not establish malicious behavior.
Decision evidence
public snapshot- package.json declares the LensMCP runtime dependencies and contains no lifecycle hook.
- The plugin defaults to enabled, applies during Vite serving, and uses a loopback host for its bridge.
- The bridge and client runtime are same-version LensMCP packages; event mapping handles browser events, and the client runtime includes a session replay recorder.
- Core event storage defaults to a project-local LensMCP events file; no attack behavior was identified in the inspected source.
Source & flagged code
9 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
lib/plugin.jsView on unpkg · L1The plugin defaults to enabled, applies during Vite serving, and uses a loopback host for its bridge.
lib/plugin.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.25.18.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.25.18 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.